CUCM 7.1 MGCP QSIG to Meridian - one way caller-name indication

Answered Question
Apr 19th, 2010
User Badges:

Hi All,


We have just setup a QSIG link between new CUCM 7.1(3) and Nortel Meridian Op.81 using MGCP gateway. The problem we have - there is no caller-name information coming across from CUCM to Meridian. The other way around - Meridian to CUCM - caller name is shown all right. Also we have an old CCM 4.1 connected to the same Meridian using QSIG over MGCP gateway. In the case of calls from this CCM 4.1 to Meridian the name goes across all right. When you trace the call from CCM 4.1 to Meridian you can see a Facility element going across (where I assume the caller name is). But the similar trace for the call between CUCM 7.1 and Meridian does not show any Facility element going from CUCM to Meridian at all. So I wonder if we need to do anything special in CUCM 7.1(3) to enable sending out Caller Name across QSIG link in MGCP configuration.


By the way, if you go to CCM 4.1 MGCP configuration of the link you can see that some tick boxes are ticked there by default: Display IE Delivery, Send Extra Leading Character In DisplayIE, Setup non-ISDN Progress Indicator IE Enable. If you go to the same configuration page in CUCM 7.1 the same settings default to "Disabled", the tick-boxes are not ticked and greyed-out.


Thanks for the help.

Correct Answer by Rob Huffman about 7 years 3 months ago

Hi Alexander,


You may be seeing this bug;


CSCtc68166 Bug Details Bug #16 of 31 | < Previous | Next >



ASN.1  ROSE OID Encoding and Calling Name in setup msg using PRI QSIG.
Symptom:

Outbound calls over  QSIG gateway fail
or
supplementary services like calling name,  connected name, callback etc.. fail

Conditions:

CUCM  7.X and higher

QSIG configuration :
Serviceparameter - QSIG  variant = ECMA
Serviceparameter - ASN.1 ROSE OID Encoding  = ECMA  (GLOBAL)

Gateway - QSIG Variant = No Changes
Gateway - ASN.1  ROSE OID Encoding  = No Changes

Workaround:

Configure  on gateway

Gateway - QSIG Variant = ECMA
Gateway - ASN.1 ROSE  OID Encoding  = ECMA (GLOBAL)

Further Problem  Description:

With the configuration documented under  conditions, CUCM will encode the Facility/Rose Invoke as ECMA / Local  while it is expected to be ECMA / Global. (as configured on the remote  PBX)
Depending on the remote PBX configuration/type the call will get  released or Rose Invoke will get rejected.
Status
Fixed            

Severity       
3 - moderate


Last Modified
In  Last Year        

Product
Cisco  Unified Communications Manager (CallManager)         

Technology


1st Found-In
8.0(0.99091.11)       
            
Fixed-In
8.0(0.98000.68)
7.1(3.21900.2)
7.1(2.32020.1)
7.1(3.21005.1)
7.1(4.98000.60)
8.0(1.10000.40)





Cheers!

Rob



Please  support CSC Helps Haiti


https://supportforums.cisco.com/docs/DOC-8895


https://supportforums.cisco.com/docs/DOC-8727

  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 5 (1 ratings)
Loading.
Correct Answer
Rob Huffman Mon, 04/19/2010 - 10:37
User Badges:
  • Super Red, 40000 points or more
  • Hall of Fame,

    Founding Member

  • Cisco Designated VIP,

    2017 IP Telephony, Unified Communications

Hi Alexander,


You may be seeing this bug;


CSCtc68166 Bug Details Bug #16 of 31 | < Previous | Next >



ASN.1  ROSE OID Encoding and Calling Name in setup msg using PRI QSIG.
Symptom:

Outbound calls over  QSIG gateway fail
or
supplementary services like calling name,  connected name, callback etc.. fail

Conditions:

CUCM  7.X and higher

QSIG configuration :
Serviceparameter - QSIG  variant = ECMA
Serviceparameter - ASN.1 ROSE OID Encoding  = ECMA  (GLOBAL)

Gateway - QSIG Variant = No Changes
Gateway - ASN.1  ROSE OID Encoding  = No Changes

Workaround:

Configure  on gateway

Gateway - QSIG Variant = ECMA
Gateway - ASN.1 ROSE  OID Encoding  = ECMA (GLOBAL)

Further Problem  Description:

With the configuration documented under  conditions, CUCM will encode the Facility/Rose Invoke as ECMA / Local  while it is expected to be ECMA / Global. (as configured on the remote  PBX)
Depending on the remote PBX configuration/type the call will get  released or Rose Invoke will get rejected.
Status
Fixed            

Severity       
3 - moderate


Last Modified
In  Last Year        

Product
Cisco  Unified Communications Manager (CallManager)         

Technology


1st Found-In
8.0(0.99091.11)       
            
Fixed-In
8.0(0.98000.68)
7.1(3.21900.2)
7.1(2.32020.1)
7.1(3.21005.1)
7.1(4.98000.60)
8.0(1.10000.40)





Cheers!

Rob



Please  support CSC Helps Haiti


https://supportforums.cisco.com/docs/DOC-8895


https://supportforums.cisco.com/docs/DOC-8727

Alexander.Khlem... Tue, 04/20/2010 - 03:10
User Badges:

Hi Rob,


Thanks a lot for the answer! I have done the setings as recommended in this article but unfortunately it still does not work. Below is an ISDN Q.931 trace from the gateway for the call:


Apr 20 09:59:27.431: ISDN Se1/0:15 Q931: TX -> SETUP pd = 8  callref = 0x0018
        Sending Complete
        Bearer Capability i = 0x8090A3
                Standard = CCITT
                Transfer Capability = Speech
                Transfer Mode = Circuit
                Transfer Rate = 64 kbit/s
        Channel ID i = 0xA9839F
                Exclusive, Channel 31
        Calling Party Number i = 0x0081, '8999'
                Plan:Unknown, Type:Unknown
        Called Party Number i = 0x80, '4155'
                Plan:Unknown, Type:Unknown
Apr 20 09:59:27.591: ISDN Se1/0:15 Q931: RX <- CALL_PROC pd = 8  callref = 0x8018
        Channel ID i = 0xA9839F
                Exclusive, Channel 31
Apr 20 09:59:27.595: ISDN Se1/0:15 Q931: RX <- ALERTING pd = 8  callref = 0x8018

        Facility i = 0x9FAA068001008201008B0100A10C020201000201018003424F42
        Progress Ind i = 0x8182 - Destination address is non-ISDN
Apr 20 09:59:36.895: ISDN Se1/0:15 Q931: TX -> DISCONNECT pd = 8  callref = 0x0018
        Cause i = 0x8190 - Normal call clearing
Apr 20 09:59:36.955: ISDN Se1/0:15 Q931: RX <- RELEASE pd = 8  callref = 0x8018
Apr 20 09:59:36.975: ISDN Se1/0:15 Q931: TX -> RELEASE_COMP pd = 8  callref = 0x
0018


The calling extension in CUCM is 8999, the called extension in Meridian is 4155. There is no Calling Name passed from CUCM to Meridian (as you can see there is no Facility element going from CUCM) but there is Called Name passed from Meridian to CUCM (the only Facility element in the trace is the one sent back by Meridian). The version of CUCM I am using is 7.1.3.30000-1.


Regards,

Alex.

Alexander.Khlem... Thu, 04/22/2010 - 05:34
User Badges:

Hi Rob,


I have upgraded my CUCM to 7.1(5) and it is all working fine now. Thanks for your help with this.


Cheers,

Alex.

Rob Huffman Thu, 04/22/2010 - 06:10
User Badges:
  • Super Red, 40000 points or more
  • Hall of Fame,

    Founding Member

  • Cisco Designated VIP,

    2017 IP Telephony, Unified Communications

Hi Alex,


Nice work my friend


Glad to be of some small help here.


Cheers!

Rob

Actions

This Discussion