QSIG setting on Route list/ caller id not working between cisco and nortel phones
Issue is Caller ID is not working for calls form Cisco phones to Nortel phones. We have CM System version: 220.127.116.1100-1. We have identified a bug CSCsr03923.
CLID not sent in QSIG call
Calling out of a qsig link does not include a facility message containing clid
Qsig link to pbx on ccm 6.1.2
Call through a Route List containing at least one QSIG enabled device.
The QSIG device must have been added to a Route Group after the Route Group and Route List were created as non-QSIG.
Check the Route List's Q.SIG setting in the database by running the following at the CLI:
< cmd>run sql select tkqsig from device where name = 'device.name'< /cmd>
substituting the Route List name (case sensitive) for device.name.
If the value for tkqsig is 1 or 2, this is not the correct defect.
If the value for tkqsig is 4, and the Route List has a QSIG device then the database is out of sync.
Add another routelist and use that instead, or remove a route group and add it back.
Further Problem Description:
The QSIG setting setting on a Route List is determined by the combination of devices in its Route Groups. It appears that Route Lists that contain no QSIG devices are not updated correctly when a QSIG device is added to one of the existing Route Groups in the Route List. Changing the content of the Route List forces the QSIG value to be recalculated and corrected.
We have ran the command mentioned in the workaround and are getting the 4 value.
The only thing that is concerning is the verion that this issue has been identified in does not include 8.x. Wondering if we are still hitting this bug.
QSIG setting on Route list/ caller id not working between cisco
I have another post regarding this issue, I have included a debug where display ie field is not appearing, and the display ie checkbox in CUCM is greyed out. We had replaced our gw and we are no longer getting value 4 for CSCsr03923.
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...