CLID Only displays AFTER call is answered

[DARWIN]

Hola helpful community,

So my users have complained that caller ID only displays after they pickup the phone.
We're using software version 6.0, I've gone through the COS options used for the users, and my settings look ok (see attachment)

Am I missing something?

Cheers,
A.D

[619Tech]

Are these inbound calls to DID's that ring straight to extensions? Are they ringing into a group or path that may be using another COS? Are they front ended by another device that may be using another COS (NuPoint, IVR, etc...)? Is the inbound call traversing a Mitel network between controllers (Ntwk COS)?

[DARWIN]

Are these inbound calls to DID's that ring straight to extensions? Are they ringing into a group or path that may be using another COS? Are they front ended by another device that may be using another COS (NuPoint, IVR, etc...)? Is the inbound call traversing a Mitel network between controllers (Ntwk COS)?

Hey, both internal and external-originating calls do this. The answer to your other questions is no.
We're doing our testing from one internal extension to another (No DID involved), and the calling # only displays after the phone is off hook.

I was fairly sure it would be COS related, and I've updated the COS like I'd attached in my original post, for both the devices(phones) and the trunks.

[ralph]

Are these calls ringing the prime line or a key appearance?

Ralph

[jrg0852]

How about the COS for the lines?

[DARWIN]

Ralph, it's on the prime line.
jrg, the COS for the associated trunks also had the proper permissions/options.

Currently suspecting this COS option to be the culprit:

Hot Desk External User – Display Internal Calling ID
Select "Yes" to display the extension user's name and extension number on calls to an external hot desk user. The default (No) displays the public identity (i.e., the  corporate telephone number) of the outgoing trunk.
CLID for internal calls to EHDUs is supported on PRI or SIP trunks.

I'll update the thread if this fixes the issue.

Thanks again

[DARWIN]

That indeed fixed it!

Cheers,
AD