Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Announcements

Welcome to Cisco Support Community. We would love to have your feedback.

For an introduction to the new site, click here. And see here for current known issues.

New Member

QSIG trunk with Nortel Meridian

Hi,

I need to integrate CUCM 6.0 with Nortel CS1000M for my client. I put an MGCP gateway and configured QSIG trunk

beteween CUCM and PBX. The connectivity is like this

CUCM --> MGCP --> QSIG --> PBX

Now the calls are working both ways from IP Phones at CUCM to POTS phones at PBX and vice versa. Caller ID and

Caller Name are going from PBX to CUCM. But NOT from CUCM to PBX. The client is taking care of their PBX configuration,

they use QSIG variant (IFC:ESIGX ESGF) at PBX. I am using default QSIG configuration on CUCM. i.e. ISO QSIG E1.

I have already enabled the commmands " isdn outgoing ie facility" at the gateway. Below are the some commands enabled at the gateway.

interface Serial0/0/1:15

no ip address

encapsulation hdlc

no logging event link-status

isdn switch-type primary-qsig

isdn timer T310 120000

isdn protocol-emulate network

isdn incoming-voice voice

isdn bind-l3 ccm-manager

isdn outgoing ie facility

isdn outgoing ie extended-facility

isdn outgoing display-ie

isdn outgoing ie connected-number

isdn outgoing ie caller-number

isdn outgoing ie caller-subaddr

isdn outgoing ie called-number

no cdp enable

Can anyone confirms the configuration and shed some light if my above configuration and signalling are compatible. I also see a QSIG variant ECMA in service perimeter at CUCM but dont know if its compatible.

I dont know anything about Nortel configuration. Is it possible that incoming CLID and Caller Name is not enabled at Nortel PBX for incoming calls.

Thanks in advance.

6 REPLIES
Green

Re: QSIG trunk with Nortel Meridian

Could you please try to play with those parameters in CUCM side:

ASN.1 ROSE OID Encoding

QSIG Variant

Also paste debug isdn q931 for 2 calls, incoming from PBX and another from CUCM to PBX.

Thanks

New Member

Re: QSIG trunk with Nortel Meridian

Please find the debug result below from both ways.

PBX to CUCM

==============

*Sep 15 04:57:45.030: ISDN Se0/0/1:15 Q931: RX <- SETUP pd = 8 callref = 0x2600

Bearer Capability i = 0x8090A3

Standard = CCITT

Transfer Capability = Speech

Transfer Mode = Circuit

Transfer Rate = 64 kbit/s

Channel ID i = 0xA98381

Exclusive, Channel 1

Facility i = 0x91AA068001008201008B0100A11C0202010006042B0C09008010554E494649454420434F4D4D20494244

Progress Ind i = 0x8183 - Origination address is non-ISDN

Calling Party Number i = 0x0980, '6600'

Plan:Private, Type:Unknown

Called Party Number i = 0x89, '1102'

Plan:Private, Type:Unknown

Sending Complete

Locking Shift to Codeset 5

Codeset 5 IE 0x31 i = 0x80

Codeset 5 IE 0x32 i = 0x81

*Sep 15 04:57:45.054: ISDN Se0/0/1:15 Q931: TX -> CALL_PROC pd = 8 callref = 0xA600

Channel ID i = 0xA98381

Exclusive, Channel 1

*Sep 15 04:57:45.054: ISDN Se0/0/1:15 Q931: TX -> ALERTING pd = 8 callref = 0xA600

Progress Ind i = 0x8088 - In-band info or appropriate now available

*Sep 15 04:58:23.906: ISDN Se0/0/1:15 Q931: TX -> CONNECT pd = 8 callref = 0xA600

Facility i = 0x91AA06800100820100A11102010206042B0C09028006557365722032

Connected Number i = 0x0083, '1102'

*Sep 15 04:58:23.942: ISDN Se0/0/1:15 Q931: RX <- CONNECT_ACK pd = 8 callref = 0x2600

CUCM to PBX

==========

2821-GW#

*Sep 15 04:59:35.402: ISDN Se0/0/1:15 Q931: TX -> SETUP pd = 8 callref = 0x0003

Sending Complete

Bearer Capability i = 0x8090A3

Standard = CCITT

Transfer Capability = Speech

Transfer Mode = Circuit

Transfer Rate = 64 kbit/s

Channel ID i = 0xA98381

Exclusive, Channel 1

Facility i = 0x91AA06800100820100A11102010006042B0C09008006557365722032

Calling Party Number i = 0x0181, '1102'

Plan:ISDN, Type:Unknown

Called Party Number i = 0x80, '6600'

Plan:Unknown, Type:Unknown

*Sep 15 04:59:35.530: ISDN Se0/0/1:15 Q931: RX <- CALL_PROC pd = 8 callref = 0x8003

Channel ID i = 0xA98381

Exclusive, Channel 1

*Sep 15 04:59:35.542: ISDN Se0/0/1:15 Q931: RX <- ALERTING pd = 8 callref = 0x8003

Facility i = 0x91AA068001008201008B0100A11C0202010006042B0C09018010554E494649454420434F4D4D204942

Locking Shift to Codeset 5

Codeset 5 IE 0x32 i = 0x81

*Sep 15 04:59:42.114: ISDN Se0/0/1:15 Q931: RX <- CONNECT pd = 8 callref = 0x8003

Facility i = 0x91AA068001008201008B0100A11C0202010006042B0C09028010554E494649454420434F4D4D204942

Progress Ind i = 0x8182 - Destination address is non-ISDN

Connected Number i = 0x0080, '6600'

Locking Shift to Codeset 5

Codeset 5 IE 0x32 i = 0x81

*Sep 15 04:59:42.118: ISDN Se0/0/1:15 Q931: TX -> CONNECT_ACK pd = 8 callref = 0x0003

Any idea

Thanks

Green

Re: QSIG trunk with Nortel Meridian

Which service parameter is configured in CUCM

From PBX we are getting 0x91 is

ECMA (Protocol Profile 0x91)

Also from CUCM...we are sending ECMA

This link is form other PBX but mentions parameters describe above if you change them any luck?

http://www.cisco.com/en/US/tech/tk1077/technologies_tech_note09186a00803d22cd.shtml

New Member

Re: QSIG trunk with Nortel Meridian

Yes, it was set to ECMA at service parameters.

I changed it to service parameter

ISO (Protocol Profile 0x9F)

Use Local Value.

The result is the same. Anything else i can check out there. Also, is everything configured correctly at Gateway?

New Member

Re: QSIG trunk with Nortel Meridian

Resolved.

Cli was not enabled at Nortel Extension.

Thanks for all the help.

New Member

Re: QSIG trunk with Nortel Meridian

Hi sfurgani

I have the same problem here, do you have the commands you put on the nortel PABX to enable CLI?

regards

solomon

970
Views
0
Helpful
6
Replies