Re: H323 gateway names transport via ECMA QSig

techdepart · ‎08-05-2010

Hello,

I have a problem with the transport of the names via E1 Qsig enabled. Names should be packed into the facility and coded ROSE profile and ECMA.

Here is the configuration of the serial interface:

interface Serial0/1/1:15
no ip address
encapsulation hdlc
isdn switch-type primary-qsig
isdn overlap-receiving
isdn protocol-emulate network
isdn incoming-voice voice
isdn map address .* plan isdn type national
isdn supp-service name calling ie 40 cs 0 profile ROSE operation-value-tag ECMA
isdn negotiate-bchan
isdn outgoing ie facility
isdn outgoing display-ie
isdn outgoing ie connected-number
isdn outgoing ie caller-number
isdn outgoing ie called-number
no cdp enable

I have tried to change almost every configuration option with ROSE profile which is requested on the other side. But gateway sends setups with the facility coded with profile NetworkExtension (0x9F) instead of the ROSE (0x91) selected.

Is it an IOS bug have i missed some configuration step?

IOS version Cisco IOS Software, 3800 Software (C3845-ADVENTERPRISEK9_IVS-M), Version 12.4(22)T, RELEASE SOFTWARE (fc1)

IQ931 trace:

Aug 5 18:02:34.325: ISDN Se0/1/1:15 Q931: TX -> SETUP pd = 8 callref = 0x562A
        Bearer Capability i = 0x8090A3
                Standard = CCITT
                Transfer Capability = Speech
                Transfer Mode = Circuit
                Transfer Rate = 64 kbit/s
        Channel ID i = 0xA18381
                Preferred, Channel 1
        Facility i = 0x9FAA068001018201018B0100A109020215D70201008000       <--------------sended
        Calling Party Number i = 0x2181, '90760140'
                Plan:ISDN, Type:National
        Called Party Number i = 0xA1, '9023333'
                Plan:ISDN, Type:National
Aug 5 18:02:34.381: ISDN Se0/1/1:15 Q931: RX <- CALL_PROC pd = 8 callref = 0xD62A
        Channel ID i = 0xA98381
                Exclusive, Channel 1
Aug 5 18:02:34.385: ISDN Se0/1/1:15 Q931: RX <- ALERTING pd = 8 callref = 0xD62A
        Facility i = 0x91AA06800100820100A116020101020101800E506176656C205472756E6563656B           <--------requested
        Progress Ind i = 0x8088 - In-band info or appropriate now available
Aug 5 18:02:34.777: ISDN Se0/1/1:15 Q931: TX -> DISCONNECT pd = 8 callref = 0x562A
        Cause i = 0x8290 - Normal call clearing
Aug 5 18:02:34.813: ISDN Se0/1/1:15 Q931: RX <- RELEASE pd = 8 callref = 0xD62A
Aug 5 18:02:34.813: ISDN Se0/1/1:15 Q931: TX -> RELEASE_COMP pd = 8 callref = 0x562A

Thank you for the answer.

Best regards,

Michal Levak

paolo bevilacqua · ‎08-05-2010

I think you will need helo from the highest TAC level on this.

Sometime not even Cisco Engineering is positive on how things are supposed to work wrt transporting advanced IEs, due to the messed up nature of the ISDN code.