debug isdn q931

Answered Question
Jun 14th, 2012

Hi!

After upgrade Cisco2811 to IOS 15.1(3)T we have problem with outgoing calls. We got from PSTN switch error message-

Jun 14 10:15:55.361: ISDN Se0/0/0:15 Q931: RX <- DISCONNECT pd = 8  callref = 0xBD5F

    Cause i = 0x829C - Invalid number format (incomplete number)

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

    Display i = 'WRONG NUMBER '

From debug i see after

RX <- ALERTING

my gateway send

TX -> INFORMATION

and after it we got

RX <- DISCONNECT

Jun 14 10:15:45.341: ISDN Se0/0/0:15 Q931: TX -> SETUP pd = 8  callref = 0x3D5F

    Bearer Capability i = 0x8090A3

        Standard = CCITT

        Transfer Capability = Speech 

        Transfer Mode = Circuit

        Transfer Rate = 64 kbit/s

    Channel ID i = 0xA9838F

        Exclusive, Channel 15

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

    Calling Party Number i = 0x2181, 'XXXXXXX'

        Plan:ISDN, Type:National

    Called Party Number i = 0x81, 'XXXXXXX'

        Plan:ISDN, Type:Unknown

Jun 14 10:15:45.361: ISDN Se0/0/0:15 Q931: RX <- SETUP_ACK pd = 8  callref = 0xBD5F

    Channel ID i = 0xA9838F

        Exclusive, Channel 15

Jun 14 10:15:45.365: ISDN Se0/0/0:15 Q931: RX <- CALL_PROC pd = 8  callref = 0xBD5F

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

Jun 14 10:15:48.861: ISDN Se0/0/0:15 Q931: RX <- ALERTING pd = 8  callref = 0xBD5F

Jun 14 10:15:55.345: ISDN Se0/0/0:15 Q931: TX -> INFORMATION pd = 8  callref = 0x3D5F

    Sending Complete

Jun 14 10:15:55.361: ISDN Se0/0/0:15 Q931: RX <- DISCONNECT pd = 8  callref = 0xBD5F

    Cause i = 0x829C - Invalid number format (incomplete number)

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

    Display i = 'WRONG NUMBER '

Is it correct?

P.S. Number format is correct

Best regards,

Mike

I have this problem too.
0 votes
Correct Answer by Daniele Giordano about 1 year 10 months ago

What is the number type of called and calling?

In your setup you have

Calling Party Number i = 0x2181, 'XXXXXXX'

        Plan:ISDN, Type:National

Called Party Number i = 0x81, 'XXXXXXX'

        Plan:ISDN, Type:Unknown

Is it right?

Do you have already try to change?

You must use "isdn map address" command under serial interface.

Regards.

  • 1
  • 2
  • 3
  • 4
  • 5
Average Rating: 5 (1 ratings)
Correct Answer
Daniele Giordano Thu, 06/14/2012 - 03:38

What is the number type of called and calling?

In your setup you have

Calling Party Number i = 0x2181, 'XXXXXXX'

        Plan:ISDN, Type:National

Called Party Number i = 0x81, 'XXXXXXX'

        Plan:ISDN, Type:Unknown

Is it right?

Do you have already try to change?

You must use "isdn map address" command under serial interface.

Regards.

rmv72 Thu, 06/14/2012 - 04:02

Certainly i have changed number.

Seems i have

CSCtb34920

Symptoms: Calls may intermittently be dropped or disconnected.

The debug output for "debug isdn q931" will reveal that the gateway is  sending a Q.931 INFORMATION message similar to the following:

Aug 11 13:51:20.137 EST: ISDN Se0/2/1:23 Q931: TX -> INFORMATION pd = 8 callref = 
0x80AE

The connected service provider switch may respond with a Q.931 STATUS message similar to the following:

Aug 11 13:51:20.197 EST: ISDN Se0/2/1:23 Q931: RX <- STATUS pd = 8 callref = 0x00AE 
Cause i = 0x81E17B - Message type not implemented Call State i = 0x0A

The connected service provider switch may also respond with a Q.931 DISCONNECT message similar to the following:

Aug 11 13:51:20.297 EST: ISDN Se0/2/1:23 Q931: RX <- DISCONNECT pd = 8 callref = 
0x00AE Cause i = 0x81E4 - Invalid information element contents

But it seems it's resolved in last versions... How to check it?

Ayodeji oladipo... Thu, 06/14/2012 - 04:42

The bug you are talking about does not affect your IOS version. The disconnect cause in the bug also is not the same as yours..So I dont think you are hitting that bug.. More details below os the IOS affected.

First Found in: (2)

12.4(24)T,12.4(15)T8

More

Less

Status:

Fixed (Resolved)

Last Modified:

Jan 12,2012

Known Affected Versions: (246)

12.4(9)XG5,12.4(9)XG4,12.4(9)XG3,12.4(9)XG2

12.4(9)XG1,12.4(9)XG,12.4(9)T7,12.4(9)T6,12.4(9)T5

--------

Fixed in: (14)

15.1(24.6.13)PIL12,15.1(1)XB,15.0(1)M

12.4(24.6.11)PIB12,12.4(24.6)PI11v,12.4(24.6)M0.1

12.4(24)YE,12.4(24)T2,12.4(24)MDA1,12.4(24)MD

12.4(24)GC2,12.4(22)T4,12.4(22)MDA4,12.4(15)T10

Please rate useful posts

"For the love of God is broader than the measure of man's mind And the heart of the Eternal is most wonderfully kind"


rmv72 Thu, 06/14/2012 - 04:58

"This problem may occur when an IP phone user blind  transfers a call to another destination (another IP phone, IVR, IPCC  queue, etc). The transfer request triggers the Cisco Unified  Communications Manager (CUCM) server to send an H.225 INFORMATION  message with a Signal IE to the Cisco IOS H.323 gateway indicating to  start/stop playing ringback tone toward the PSTN. The Cisco IOS H.323  gateway should generate the ringback tone, but it should NOT send the  Q.931 INFORMATION message toward the connected service provider switch. "

How to stop it?

Actions

Login or Register to take actions

This Discussion

Posted June 14, 2012 at 3:29 AM
Stats:
Replies:4 Avg. Rating:5
Views:2211 Votes:0
Shares:0
Tags: cucm, q931, ios15
+

Related Content

Discussions Leaderboard

Rank Username Points
1 21,026
2 15,047
3 10,314
4 7,999
5 4,856
Rank Username Points
154
95
75
66
55