Does anyone know how the CUCM handles call ID information from SIP trunk? Basically, a call comes in over the sip trunk with a from and rid header that looks like '"ABC Company Inc." <sip:email@example.com>'. The callmanager properly displays the quoted part of the header onto the screen as who the call comes from, and it even displays the phone number in the notification area of our 7941's and 7961's. The problem lies in the "missed calls" or "recieved calls" directories, where my users cannot "dial" or "edit dial" from the directory list. The phone number that the call came in from is no where to be found. If you push "edit dial" the original phone number is missing, with no way that I've found to retrieve it. I have played with the caller ID options that I can find on the trunk settings, but everything is called party name and number are both allowed. It's odd to me that the only place to identify the phone number of the calling party over the SIP trunk is on the phones small notification area during the brief few second period while the phone is actually ringing. After the line identification disappears from the phones notification area, I can no longer retrieve it from the phone to return the call.
One oddity is that my provider sip trunk shows the info in the format "Name of Caller" <18005551212>18005551212>
but my sip trunk that points to a 2811 voice gateway with a PRI sends the info without the quoted name of caller part, it only has the sip part.... with that, the line ID is stored as a phone number in the missed and recieved calls directory, and the number is available to "dial" and "edit dial". And the phone number is just displayed in place of the name area on the phone's screen...
I am going to begin researching the caveats of an upgrade to 6.1, which I hear as some major sip trunking improvements. I will keep this post up to date if I make any progress... I hope you will do the same..
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...