its a cucm 8.6 with 2911 acting as gateway to nortel option61c. its mgcp based QSIG. regular call dialing between the system works fine. however, call display from cisco to pbx is not working. i do not see the cucm sending this information to the 2911 gw at all. PBX->cisco call display works fine.. also the alerting names both way works fine.
it is just dialing from cisco phone to pbx phone does not display the name nor the gateway shows the name.
this is waht i have under the serial interface.
no ip address
isdn switch-type primary-qsig
isdn incoming-voice voice
isdn supp-service name calling profile Network-Extension operation-value-tag local
isdn bind-l3 ccm-manager
isdn outgoing ie progress-indicator
isdn outgoing display-ie
isdn outgoing ie user-user
no cdp enable
this is an mgcp gw and the above mention commands not really going to help. although i tried it.
also got these commands with no luck.
voice service voip
cucm gateway is configured for mgcp with the followings:
PRI protocol type:PRI ISO QSIG T1 qsig varient:no changes ASN.1 ROSE OID Encoding:no changes
i did tweek the above mentioned values around to do more testing however i couldnt get the callign name to go on the gw at least.
display IE displayed: greyed out redirect number IE delivery-outbound:checked redirect number IE delivery-inbound:checked
i have fixed this problem. i was doing a bug scrup and came up with this bug CSCsr03923
CLID not sent in QSIG call
Symptom: Calling out of a qsig link does not include a facility message containing clidConditions: 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.Workaround: 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.
eventhough it says hte bug has been fixed in cucm ver 7, i tried the workaround, which is to delete and readd route group and list and it worked fine.
Are you getting this error “Installer User Interface Mode Not Supported. The installer cannot run in this UI mode. To specify the interface mode, use the -i command-line option, followed by the UI mode identifier. The value UI mode identifiers...
The below trick might come handy when you have to add a new node to a cluster but you don't have or is unsure of the security password for the publisher. This procedure has been around for ages.
1) Login into the CLI of the Publisher.