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 Caller NAME

Hi,

CUCM 6.1 with MGCP on a 2851

QSig trunk to Ericson MD110 switch

Cannot get caller name to work in outbound direction. It works inbound from PBX. Sends number only on outbound.

Display IE is greyed out in config

My users have their alerting name configured.

Any ideas?

9 REPLIES
Green

Re: QSIG Caller NAME

Check which MD110's version the customer

is running, and old version of MD110 may not interoperate well with CCM. Our

interoperability group has done extensive testing on MD110's running version BC11 and newer.

We do support calling name

Which value syou have under MD110 and in CUCM for:

ASN.1 ROSE OID Encoding

QSIG Variant

?

http://www.cisco.com/en/US/docs/voice_ip_comm/cucme/pbx/interop/notes/608604nt.pdf

Let sus know

New Member

Re: QSIG Caller NAME

HI,

Set QSig Variant to ECMA and ASN.1 ROSE to Use Global Value (ECMA)

Restarted Call Manager service

Result is still same, no names when calling the PBX

Checked MD110 and it is running BC12

New Member

Re: QSIG Caller NAME

I have the same issue - with Opt81

CUCM 6.1.2 with MGCP on 2851

QSig trunk to Opt81

Cannot get Alerting ID to show up on Nortel Phone. It works from Nortel to Cisco IP Phone.

I needed to use QSIG to get Caller ID with Name to make it through the Opt81 all the way to the IP Phone (which works fine now)

ASN.1 ROSE OID Encoding Use Global Value (ECMA)

QSIG Variant ECMA (Protocol Profile 0x91)

Green

Re: QSIG Caller NAME

Can we get detailed CCM SDI SDL traces and debug isdn q931

for an incoming call from PBX

and for an outgoing call to PBX,

please let us know

Calling number

Called number

Timestamps

Thanks

New Member

Re: QSIG Caller NAME

Here's a call from IP Phone to Nortel - just the q931.

VSBWH1VGW3#

Sep 10 11:19:43.160 EDT: ISDN Se0/0/0:23 Q921: User RX <- RR sapi=0 tei=0 nr=33

Sep 10 11:19:44.254 EDT: ISDN Se0/0/0:23 Q921: User TX -> INFO sapi=0 tei=0, ns=33 nr=34

Sep 10 11:19:44.254 EDT: ISDN Se0/0/0:23 Q931: SETUP pd = 8 callref = 0x0003

Sending Complete

Bearer Capability i = 0x8090A2

Standard = CCITT

Transfer Capability = Speech

Transfer Mode = Circuit

Transfer Rate = 64 kbit/s

Channel ID i = 0xA98381

Exclusive, Channel 1

Facility i = 0x91AA06800100820100A11702010006042B0C0900800C54617261205374657068616E

Calling Party Number i = 0x0081, '8573070998'

Plan:Unknown, Type:Unknown

Called Party Number i = 0x80, '916175258448'

Plan:Unknown, Type:Unknown

Sep 10 11:19:44.334 EDT: ISDN Se0/0/0:23 Q921: User RX <- INFO sapi=0 tei=0, ns=34 nr=34

Sep 10 11:19:44.334 EDT: ISDN Se0/0/0:23 Q931: STATUS pd = 8 callref = 0x8003

Cause i = 0x81E4 - Invalid information element contents

Call State i = 0x06

Sep 10 11:19:44.334 EDT: ISDN Se0/0/0:23 Q921: User TX -> RR sapi=0 tei=0 nr=35

Sep 10 11:19:44.366 EDT: ISDN Se0/0/0:23 Q921: User RX <- INFO sapi=0 tei=0, ns=35 nr=34

Sep 10 11:19:44.366 EDT: ISDN Se0/0/0:23 Q931: CALL_PROC pd = 8 callref = 0x8003

Channel ID i = 0xA98381

Exclusive, Channel 1

Sep 10 11:19:44.366 EDT: ISDN Se0/0/0:23 Q921: User TX -> RR sapi=0 tei=0 nr=36

VSBWH1VGW3#

Sep 10 11:19:44.370 EDT: ISDN Se0/0/0:23 Q921: User RX <- INFO sapi=0 tei=0, ns=36 nr=34

Sep 10 11:19:44.370 EDT: ISDN Se0/0/0:23 Q931: ALERTING pd = 8 callref = 0x8003

Facility i = 0x9FAA068001008201008B0100A1110202010002010180084B454E54204D4446

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

Sep 10 11:19:44.370 EDT: ISDN Se0/0/0:23 Q921: User TX -> RR sapi=0 tei=0 nr=37

VSBWH1VGW3#

Sep 10 11:19:47.491 EDT: ISDN Se0/0/0:23 Q921: User RX <- INFO sapi=0 tei=0, ns=37 nr=34

Sep 10 11:19:47.491 EDT: ISDN Se0/0/0:23 Q931: CONNECT pd = 8 callref = 0x8003

Facility i = 0x9FAA068001008201008B0100A1110202010002010280084B454E54204D4446

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

Connected Number i = 0x0080, '6177358448'

Sep 10 11:19:47.491 EDT: ISDN Se0/0/0:23 Q921: User TX -> RR sapi=0 tei=0 nr=38

Sep 10 11:19:47.499 EDT: ISDN Se0/0/0:23 Q921: User TX -> INFO sapi=0 tei=0, ns=34 nr=38

Sep 10 11:19:47.499 EDT: ISDN Se0/0/0:23 Q931: CONNECT_ACK pd = 8 callref = 0x0003

New Member

Re: QSIG Caller NAME

FWIW - I know BC8 will not support calling name outbound from PBX. It has something to do with the way QSig worked on the Ericsson BC8 software.

-Steve

Cisco Employee

Re: QSIG Caller NAME

.

New Member

Re: QSIG Caller NAME

Thanks for the reponses. I checked and it was using the default QSig Varient (ISO protocol profile 0x9F) and the ASN.1 ROSE was set to Use Local Value.

I have changed these to refecl what is shown in the integration documentation for the Ericson, just waiting for a windows now to restart the services.

New Member

Re: QSIG Caller NAME

I set all my service parameters back to defaults, and magically all is working.

Strange.

580
Views
0
Helpful
9
Replies
CreatePlease login to create content