I am running CME 3.3 and have a PRI to the PSTN. When a call comes in from the PSTN the phones display the calling number, but not the calling name. According to a q931 debug, i am receving the facility IE with the calling name as i can go back and see it in the debugs, but it doesn't display on the phone.
Here is a link to a tech note discussing caller ID name delivery issues with CM, what you can do at which versions/switch type-so you should have switch type NI2 and check the checkbox:
NI2/NI3 CNID (Bellcore GR-1367)
With the advent of Cisco CallManager 3.3(3), CallManager supports Calling Party Name by way of the Q.931 Facility IE based on the Bellcore GR-1367-CORE specification. This is also known as the NI3 CNID service. Briefly stated, Cisco CallManager PRI gateways are able to use the Facility IE encoded with the CallingName Remote Operations Service Element.
When you select Primary NI2 as the protocol, the Send Calling Name in Facility IE checkbox becomes available as shown here:
Mary Beth, OP is referring to CME, not CM. I've gone through this with TAC and they told me it won't be fixed until CME 4 (Q2 2006 release). They gave me a bug ID but it's one of the hidden ones that you can't see on the site.
You might possibly check with your PRI provider and see if they can provide the Caller ID name data in plain text format instead of hex (like it is with facility ID). SBC can't do it for us locally, so we'll wait.
SIP traces provide key information in troubleshooting SIP Trunks, SIP
endpoints and other SIP related issues. Even though these traces are in
clear text, these texts can be gibberish unless you understand fully
what they mean. This document attempts to br...
Please find the attached HTML document, download and open it on your PC.
This provides an easy to use form where you simply answer a few
questions and it will render the proper jabber-config.xml file for you
to copy/paste. There is built in logic to verif...
CUCM Database Replication is an area in which Cisco customers and
partners have asked for more in-depth training in being able to properly
assess a replication problem and potentially resolve an issue without
involving TAC. This document discusses the bas...