Qsig MD110 callback & CLID not working?

carlnewton · ‎03-11-2009

All,

I currently have a problem with a 2851 connecting via a Qsig link to an MD110 ericsson system.

The first problem is that call back does not work, and i am unable to find any specific configuration guides for this... I have made all the changes depicted in the integration guide (Cisco MD110 BC13 ISO QSIG.pdf FYI) but when you press the call back button it just says "Call back is not available to xxxx"

Cisco to Cisco call back works fine.

My other problem is CLID. Ericson to cisco CLID works great. Cisco to ericsson however does not. If i look at the debugs i can see that there is a facilities message missing. Looking at the debug the only facilities message i can see when converted to ASCII from hex (using http://www.paulschou.com/tools/xlate/) is an ascii message containing the CALLED party number, not the calling.

Is there a parameter i have to enable somewhere to tell the CCM to transmit the calling party number via a QSIG facilities message to the other end?

*Mar 11 12:39:31: ISDN Se0/0/0:15 Q931: SETUP pd = 8 callref = 0x08DD

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, '4688'

Plan:Unknown, Type:Unknown

Called Party Number i = 0x80, '3954'

Plan:Unknown, Type:Unknown

*Mar 11 12:39:31: ISDN Se0/0/0:15 Q921: User RX <- RR sapi=0 tei=0 nr=7

*Mar 11 12:39:31: ISDN Se0/0/0:15 Q921: User RX <- INFO sapi=0 tei=0, ns=6 nr=7

*Mar 11 12:39:31: ISDN Se0/0/0:15 Q931: CALL_PROC pd = 8 callref = 0x88DD

Channel ID i = 0xA9839F

Exclusive, Channel 31

Progress Ind i = 0x8181 - Call not end-to-end ISDN, may have in-band info

*Mar 11 12:39:31: ISDN Se0/0/0:15 Q921: User TX -> RR sapi=0 tei=0 nr=7

*Mar 11 12:39:32: ISDN Se0/0/0:15 Q921: User RX <- INFO sapi=0 tei=0, ns=7 nr=7

*Mar 11 12:39:32: ISDN Se0/0/0:15 Q931: ALERTING pd = 8 callref = 0x88DD

Facility i = 0x9FAA068001008201008B0100A115020101020101800D416C62657274204F6C69766572

Facility i = 0x9FAA068001008201008B0100A1100201020201553008820301B850860101

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

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

*Mar 11 12:39:32: ISDN Se0/0/0:15 Q921: User TX -> RR sapi=0 tei=0 nr=8

*Mar 11 12:39:35: ISDN Se0/0/0:15 Q921: User RX <- INFO sapi=0 tei=0, ns=8 nr=7

*Mar 11 12:39:35: ISDN Se0/0/0:15 Q931: CONNECT pd = 8 callref = 0x88DD

Facility i = 0x9FAA068001008201008B0100A115020103020102800D416C62657274204F6C69766572

Facility i = 0x9FAA068001008201008B0100A1100201040201553008820301B850860101

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

*Mar 11 12:39:35: ISDN Se0/0/0:15 Q921: User TX -> RR sapi=0 tei=0 nr=9

*Mar 11 12:39:35: ISDN Se0/0/0:15 Q921: User TX -> INFO sapi=0 tei=0, ns=7 nr=9

*Mar 11 12:39:35: ISDN Se0/0/0:15 Q931: CONNECT_ACK pd = 8 callref = 0x08DD

*Mar 11 12:39:35: ISDN Se0/0/0:15 Q921: User RX <- RR sapi=0 tei=0 nr=8

*Mar 11 12:39:38: ISDN Se0/0/0:15 Q921: User RX <- INFO sapi=0 tei=0, ns=9 nr=8

*Mar 11 12:39:38: ISDN Se0/0/0:15 Q931: DISCONNECT pd = 8 callref = 0x88DD

Cause i = 0x8190 - Normal call clearing

*Mar 11 12:39:38: ISDN Se0/0/0:15 Q921: User TX -> RR sapi=0 tei=0 nr=10

*Mar 11 12:39:38: ISDN Se0/0/0:15 Q921: User TX -> INFO sapi=0 tei=0, ns=8 nr=10

*Mar 11 12:39:38: ISDN Se0/0/0:15 Q931: RELEASE pd = 8 callref = 0x08DD

*Mar 11 12:39:38: ISDN Se0/0/0:15 Q921: User RX <- RR sapi=0 tei=0 nr=9

*Mar 11 12:39:38: ISDN Se0/0/0:15 Q921: User RX <- INFO sapi=0 tei=0, ns=10 nr=9

*Mar 11 12:39:38: ISDN Se0/0/0:15 Q931: RELEASE_COMP pd = 8 callref = 0x88DD

carlnewton · ‎03-11-2009

The reason i say theres a facilities message missing is because if you look here at this call from MD110 to Cisco, this is a working call - the hex value that exists just below the channel ID when converted to ASCII lists the calling number's name. The value below lists the called numbers name (Tony/Jurgen Calling and IPTTest1 is called)

In the above non-working example, this hex value for calling number is not transmitted by the CCM...

RPH-VoIP-DC020305#

*Mar 11 12:45:57: ISDN Se0/0/0:15 Q921: User RX <- INFO sapi=0 tei=0, ns=59 nr=64

*Mar 11 12:45:57: ISDN Se0/0/0:15 Q931: SETUP pd = 8 callref = 0x0C19

Bearer Capability i = 0x8090A3

Standard = CCITT

Transfer Capability = Speech

Transfer Mode = Circuit

Transfer Rate = 64 kbit/s

Channel ID i = 0xA18393

Preferred, Channel 19

Facility i = 0x9FAA068001008201008B0100A1100201010201553008820301B850860101

Facility i = 0x9FAA068001008201008B0100A11A0201020201008012546F6E79204C656172792F4A757267656

E20

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

Calling Party Number i = 0x2981, '4634'

Plan:Private, Type:National

Called Party Number i = 0xA9, '8271'

Plan:Private, Type:National

Shift to Codeset 4

Codeset 4 IE 0x31 i = 0x80

*Mar 11 12:45:57: ISDN Se0/0/0:15 Q921: User TX -> RR sapi=0 tei=0 nr=60

*Mar 11 12:45:57: ISDN Se0/0/0:15 Q921: User TX -> INFO sapi=0 tei=0, ns=64 nr=60

*Mar 11 12:45:57: ISDN Se0/0/0:15 Q931: SETUP_ACK pd = 8 callref = 0x8C19

Channel ID i = 0xA98393

Exclusive, Channel 19

*Mar 11 12:45:57: ISDN Se0/0/0:15 Q921: User RX <- RR sapi=0 tei=0 nr=65

*Mar 11 12:46:01: ISDN Se0/0/0:15 Q921: User TX -> INFO sapi=0 tei=0, ns=65 nr=60

*Mar 11 12:46:01: ISDN Se0/0/0:15 Q931: CALL_PROC pd = 8 callref = 0x8C19

*Mar 11 12:46:01: ISDN Se0/0/0:15 Q921: User TX -> INFO sapi=0 tei=0, ns=66 nr=60

*Mar 11 12:46:01: ISDN Se0/0/0:15 Q931: ALERTING pd = 8 callref = 0x8C19

Facility i = 0x9FAA06800100820100A11002010102010180084950545465737431

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

*Mar 11 12:46:01: ISDN Se0/0/0:15 Q921: User RX <- RR sapi=0 tei=0 nr=66

*Mar 11 12:46:01: ISDN Se0/0/0:15 Q921: User RX <- RR sapi=0 tei=0 nr=67

*Mar 11 12:46:02: ISDN Se0/0/0:15 Q921: User RX <- INFO sapi=0 tei=0, ns=60 nr=67

*Mar 11 12:46:02: ISDN Se0/0/0:15 Q931: DISCONNECT pd = 8 callref = 0x0C19

Cause i = 0x8190 - Normal call clearing

paolo bevilacqua · ‎03-11-2009

Hi, how have you set the GW in CM? H.323 or MGCP ? Adn if H.323 it's a GW or intercluster trunk ?

For example if it's an H.323 GW then it's normal that callback it's not available (not sure about intercluster trunk).

Similarly if H.323 or MGCP there are different ways to manipulate CLID to be displayed correctly.

carlnewton · ‎03-11-2009

Hi, The gateway is set as an MGCP endpoint. The problem is not necessarily the CLID (the number comes through ok) the problem is that we dont get the calling name cisco-ericsson, but we do get it ericsson to cisco.

Thanks

Carl

paolo bevilacqua · ‎03-11-2009

Hi, with mgcp you have two 'dialect' options in the Qsig settings for the GW and that's all.

With H.323 you would have more control, ie the calling name can be sent either in Qsig encoding or diaply IE.

carlnewton · ‎03-11-2009

Hi,

Thanks for the response but i don't understand what your saying.

The calling name does not appear to be being sent at all at the moment (cisco to ericson) but it is ericson to cisco.

So the Qsig link obviously supports the service to pass calling name but its currently only working one way. The ccm doesnt seem to be supplying this informaiton on the calls it initiates, but is capable of receiving the information on calls it receives.

do i need to do something to make it transmit this information?

paolo bevilacqua · ‎03-11-2009

Hi, what I'm saying is that with MGCP, all the possible settings are in CM, GW properties page. I'm really unable how to fix anything in this case.

If it would have been H.323, I could have indicated the commands necessary to encode calling name at router level.

carlnewton · ‎03-12-2009

Oh right ok, thanks anyway for your help!

does anyone else know how i can do this through the gateway property pages?

Thanks in advance!

florianfetty · ‎04-03-2009

Hi!

I`ve the same issue on CUCM <-> Philips Sopho! Incoming the name is displayed, outgoing there is no setup facility ie sent.

Also, the checkbox for "Display IE Delivery" on MGCP`s endpoint-configuration page is greyed out!

Greetz; Florian