cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
747
Views
0
Helpful
2
Replies

QSIG setting on Route list/ caller id not working between cisco and nortel phones

Ayaz Khan
Level 1
Level 1

Hello,

Issue is Caller ID is not working for calls form Cisco phones to Nortel phones.  We have CM System version: 8.6.1.20000-1.  We have identified a bug CSCsr03923.

CLID not sent in QSIG call

Symptom:

Calling out of a qsig link does not include a facility message containing clid

Conditions:

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.

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.

Thanks,

1 Accepted Solution

Accepted Solutions

Karthik Sivaram
Level 4
Level 4

hello Ayaz,

Why do you think the problem is on the cisco end?

That bug you have referred is only when the facility

message does not include the clid. Is this what

you see in the the "debug isdn q931"?

Also the bug is relevent only for the older versions

of callmanger and not the 8.6 version your on.

I have a suggestion for you make sure that you check with the

Nortel to see if they support the Facility IE sent by the

CallManager.

Some PBX's will not understand the  facility IE and discard the

Facility IE sent by Callmanager and you may encounter such a

problem.

Hope that helps!

Thanks,

Karthik

View solution in original post

2 Replies 2

Karthik Sivaram
Level 4
Level 4

hello Ayaz,

Why do you think the problem is on the cisco end?

That bug you have referred is only when the facility

message does not include the clid. Is this what

you see in the the "debug isdn q931"?

Also the bug is relevent only for the older versions

of callmanger and not the 8.6 version your on.

I have a suggestion for you make sure that you check with the

Nortel to see if they support the Facility IE sent by the

CallManager.

Some PBX's will not understand the  facility IE and discard the

Facility IE sent by Callmanager and you may encounter such a

problem.

Hope that helps!

Thanks,

Karthik

Hello Karthik,

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.

The other post is,

Calling name not displaying PRI QSIG

https://supportforums.cisco.com/message/3588323#3588323

Please let me know if you have any ideas.

Thanks,

Ayaz