Cisco outgoing call display name not working


(Nav Singh) #1

We have a mixture of Cisco 7942 and 7962s, and just recently our phones have stopped displaying the Name of the extension being dialed. For example if I dial 66022 my phone displays 66022 (66022), instead of Nav-Test (66022). So with the help of a colleague, we figured out that enabling Find Me/Follow Me on the extension (66022) fixed the display name issue. With FM/FM turned on, when I dial 66022, my phone displays Nav-Test (66022) correctly.

Did a packet capture and noticed some differences with FM/FM both disabled and enabled.

FM/FM Disabled
SIP/2.0 180 Ringing
Via: SIP/2.0/UDP 172.21.18.67:5060;branch=z9hG4bK3fbc08f2;received=172.21.18.67
From: “66008” sip:66008@10.50.160.81;tag=00260bd7db3400244680b498-148ee722
To: sip:66022@10.50.160.81;tag=as1eac74ec
Call-ID: 00260bd7-db34000d-c6fa6b10-014178ca@172.21.18.67
CSeq: 102 INVITE
Server: FPBX-14.0.13.23(13.29.2)
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH, MESSAGE
Supported: replaces, timer
Contact: sip:66022@10.50.160.81:5160
Remote-Party-ID: “Nav-Test” sip:66022@10.50.160.81;party=called;privacy=off;screen=no
Content-Length: 0

SIP/2.0 180 Ringing
Via: SIP/2.0/UDP 172.21.18.67:5060;branch=z9hG4bK3fbc08f2;received=172.21.18.67
From: “66008” sip:66008@10.50.160.81;tag=00260bd7db3400244680b498-148ee722
To: sip:66022@10.50.160.81;tag=as1eac74ec
Call-ID: 00260bd7-db34000d-c6fa6b10-014178ca@172.21.18.67
CSeq: 102 INVITE
Server: FPBX-14.0.13.23(13.29.2)
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH, MESSAGE
Supported: replaces, timer
Contact: sip:66022@10.50.160.81:5160
Remote-Party-ID: “66022” sip:66022@10.50.160.81;party=called;privacy=off;screen=yes
Content-Length: 0

So in this capture the first “Status 180 Ringing” shows Remote-Party-ID: “Nav-Test” which is correct. But then for some reason the second “Status 180 Ringing” changes to Remote-Party-ID: “66022”. Also noticed “screen”=no in the first 180 Ringing packet, then changes to “screen”=yes in the second 180. This traffic is being sent from FreePBX (10.50.160.81) to my desk phone (172.21.18.67). The server (10.50.160.81) for some reason is altering the RPID.

FM/FM Enabled
SIP/2.0 180 Ringing
Via: SIP/2.0/UDP 172.21.18.67:5060;branch=z9hG4bK0b95eb9f;received=172.21.18.67
From: “66008” sip:66008@10.50.160.81;tag=00260bd7db34049c70533a7e-66827c33
To: sip:66022@10.50.160.81;tag=as258bc2f5
Call-ID: 00260bd7-db34001e-1d7da114-5f5d4145@172.21.18.67
CSeq: 102 INVITE
Server: FPBX-14.0.13.23(13.29.2)
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH, MESSAGE
Supported: replaces, timer
Contact: sip:66022@10.50.160.81:5160
Remote-Party-ID: “Nav-Test” sip:66022@10.50.160.81;party=called;privacy=off;screen=no
Content-Length: 0

SIP/2.0 180 Ringing
Via: SIP/2.0/UDP 172.21.18.67:5060;branch=z9hG4bK0b95eb9f;received=172.21.18.67
From: “66008” sip:66008@10.50.160.81;tag=00260bd7db34049c70533a7e-66827c33
To: sip:66022@10.50.160.81;tag=as258bc2f5
Call-ID: 00260bd7-db34001e-1d7da114-5f5d4145@172.21.18.67
CSeq: 102 INVITE
Server: FPBX-14.0.13.23(13.29.2)
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH, MESSAGE
Supported: replaces, timer
Contact: sip:66022@10.50.160.81:5160
Content-Length: 0

In this capture the first “Status 180 Ringing” packet has the Remote-Party-ID: “Nav-Test”, but the second “Status 180 Ringing” doesn’t even include the Remote-Party-ID header at all. This traffic is also coming from FreePBX (10.50.160.81) to my phone (172.21.18.67).

Seems like my solution to this problem is enabling FM/FM on every single extension, but I thought I would post this on the forums to see if anyone has seen this before. This is my first time posting on these forums, if more information is needed, please let me know.

Thanks!


#2

If this just recently started happening, then you need to figure out what changed right before it started happening. If you updated a module (probably core), then the issue is likely a bug and you should report it.

On the other hand, if you implemented a corporate directory, or made any configuration changes to the phones, then it may not be a bug.


(Nav Singh) #3

There was an update done over the Christmas/New Years break, so I guess this could be a bug.

Thanks for the reply!


(Nav Singh) #4

So I opened a bug report, and I was told that this is a support issue, not a bug. I still haven’t been able to find a solution other than enabling FM/FM on all the extensions. If anyone has any other suggestions please let me know.


(Charles Darwin) #5

Do you have a problem just with extensions or external calls too? For external calls there is an alternative for Ciscos.
Do you know the outbound CNAM module? You can use it with CID Superfecta to lookup names when you dial out.
Once the outgoing call is connected, it will update the name.


(Nav Singh) #6

The issue is only with dialing extensions internally. Does the CNAM module apply to extension dialing as well?


(Charles Darwin) #7

No, it is just for outgoing calls. If you have a LDAP phonebook, it will display the names…but you have to set it up in an outbound route…