We have a 3640 and a 5300 each connected to a PABX. The two routers communicate over an IP WAN. The routers also point to CCM version 3.0(7). The routers use QSIQ for communication with the PABX. The IOS versions are 12.1..T. CLID in the phone-to- phone/PC-to-phone scenario works but in the phone-to-PC scenario it doesn't. It may be that the CLID is carried in some proprietory QSIQ way? Can anyone help?
What does the PC have to do with anything? Are you using SoftPhone? Or something else?
With Q.SIG, the caller ID number is still sent in a Calling Party Number IE just like with other Q.931 signaling. However the caller's name is sent in a Facility IE rather than the Display IE used in Q.931 protocols. Therefore the caller name definitely won't show up since the CallManager currently does not decode Q.SIG elements such as those found in the Facility IE, where most of the supplementary service information (including caller name) is contained. However the caller ID number should show up.
The CLID doesn't show up. We used the 'debug voip ccapi inout' and 'debug isdn Q.931' debugs but nothing came up. Althoug the call setup was successful the calling number was blank. I will double check.
If you are looking at a 'debug isdn q931' while the PABX is sending a call to us and the calling party number field is either blank or not present... then either the incoming call from the PSTN did not have a caller ID or the PABX is not properly configured to send it.
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...