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. If you'd prefer to explore, try our test area to get started. And see here for current known issues.

New Member

trouble troubleshooting isdn here is the debug

Hello,

I am having another problem with an isdn site. Verizon has checked teh line and has cleared it but it will not connect to the other side. I can see that it never even makes it to the other side.

Here is the debug R0: TX -> INFOc sapi = 0 tei = 104 ns = 26 nr = 62 i = 0x080157050402889018 01832C0B3138363035333330373634 Nov 15 10:00:54: SETUP pd = 8 callref = 0x57 Nov 15 10:00:54: Bearer Capability i = 0x8890 Nov 15 10:00:54: Channel ID i = 0x83 Nov 15 10:00:54: Keypad Facility i = '18605330764' Nov 15 10:00:54: ISDN BR0: RX <- RRr sapi = 0 tei = 104 nr = 27 Nov 15 10:00:54: ISDN BR0: RX <- INFOc sapi = 0 tei = 104 ns = 62 nr = 27 i = 0x0801D702180189 Nov 15 10:00:54: CALL_PROC pd = 8 callref = 0xD7 Nov 15 10:00:54: Channel ID i = 0x89 Nov 15 10:00:54: ISDN BR0: TX -> RRr sapi = 0 tei = 104 nr = 63 Nov 15 10:00:54: ISDN BR0: received HOST_PROCEEDING call_id 0x8116 Nov 15 10:00:55: ISDN BR0: RX <- INFOc sapi = 0 tei = 104 ns = 63 nr = 27 i = 0x0801D7450802829F340103 Nov 15 10:00:55: DISCONNECT pd = 8 callref = 0xD7 Nov 15 10:00:55: Cause i = 0x829F - Normal, unspecified Nov 15 10:00:55: Signal i = 0x03 - Network congestion tone on Nov 15 10:00:55: ISDN BR0: TX -> RRr sapi = 0 tei = 104 nr = 64 Nov 15 10:00:55: ISDN BR0: TX -> INFOc sapi = 0 tei = 104 ns = 27 nr = 64 i = 0x0801574D Nov 15 10:00:55: RELEASE pd = 8 callref = 0x57 Nov 15 10:00:55: ISDN BR0: received HOST_DISCONNECT call_id 0x8116 Nov 15 10:00:55: ISDN BR0: Event: Call to 18605330764 was hung up. Nov 15 10:00:55: ISDN BR0: process_disc_ack(): call id 0x8116, ces 1, call type DATA Nov 15 10:00:55: ISDN BR0: RX <- RRr sapi = 0 tei = 104 nr = 28 Nov 15 10:00:55: ISDN BR0: RX <- INFOc sapi = 0 tei = 104 ns = 64 nr = 28 i = 0x0801D75A Nov 15 10:00:55: RELEASE_COMP pd = 8 callref = 0xD7 Nov 15 10:00:55: ISDN BR0: TX -> RRr sapi = 0 tei = 104 nr = 65 Nov 15 10:00:55: ISDN BR0: received HOST_DISCONNECT_ACK call_id 0x8116 Nov 15 10:00:55: ISDN BR0: HOST_DISCONNECT_ACK: call type is DATA Nov 15 10:00:56: ISDN BR0: Outgoing call id = 0x8117, dsl 0 Nov 15 10:00:56: ISDN BR0: Event: Call to 18605330764 at 64 Kb/s Nov 15 10:00:56: ISDN BR0: process_bri_call(): call id 0x8117, called_number 186 05330764, speed 64, call type DATA Nov 15 10:00:56: CC_CHAN_GetIdleChanbri: dsl 0 Nov 15 10:00:56: Found idle channel B1 Nov 15 10:00:56: ISDN BR0: TX -> INFOc sapi = 0 tei = 104 ns = 28 nr = 65 i = 0x08015805040288901801832C0B3138363035333330373634 Nov 15 10:00:56: SETUP pd = 8 callref = 0x58 Nov 15 10:00:56: Bearer Capability i = 0x8890 Nov 15 10:00:56: Channel ID i = 0x83 Nov 15 10:00:56: Keypad Facility i = '18605330764' Nov 15 10:00:56: ISDN BR0: RX <- RRr sapi = 0 tei = 104 nr = 29 Nov 15 10:00:56: ISDN BR0: RX <- INFOc sapi = 0 tei = 104 ns = 65 nr = 29 i = 0x0801D802180189 Nov 15 10:00:56: CALL_PROC pd = 8 callref = 0xD8 Nov 15 10:00:56: Channel ID i = 0x89 Nov 15 10:00:57: ISDN BR0: TX -> RRr sapi = 0 tei = 104 nr = 66 Nov 15 10:00:57: ISDN BR0: received HOST_PROCEEDING call_id 0x8117 Nov 15 10:00:57: ISDN BR0: RX <- INFOc sapi = 0 tei = 104 ns = 66 nr = 29 i = 0x0801D8450802829F340103 Nov 15 10:00:57: DISCONNECT pd = 8 callref = 0xD8 Nov 15 10:00:57: Cause i = 0x829F - Normal, unspecified Nov 15 10:00:57: Signal i = 0x03 - Network congestion tone on Nov 15 10:00:57: ISDN BR0: TX -> RRr sapi = 0 tei = 104 nr = 67 Nov 15 10:00:57: ISDN BR0: TX -> INFOc sapi = 0 tei = 104 ns = 29 nr = 67 i = 0x0801584D Nov 15 10:00:57: RELEASE pd = 8 callref = 0x58 Nov 15 10:00:57: ISDN BR0: received HOST_DISCONNECT call_id 0x8117 Nov 15 10:00:57: ISDN BR0: Event: Call to 18605330764 was hung up. Nov 15 10:00:57: ISDN BR0: process_disc_ack(): call id 0x8117, ces 1, call type DATA Nov 15 10:00:57: ISDN BR0: RX <- RRr sapi = 0 tei = 104 nr = 30 Nov 15 10:00:57: ISDN BR0: RX <- INFOc sapi = 0 tei = 104 ns = 67 nr = 30 i = 0x0801D85A Nov 15 10:00:57: RELEASE_COMP pd = 8 callref = 0xD8 Nov 15 10:00:57: ISDN BR0: TX -> RRr sapi = 0 tei = 104 nr = 68 Nov 15 10:00:57: I

3 REPLIES
Bronze

Re: trouble troubleshooting isdn here is the debug

You need to have Verizon check the call setup versus the integrity of the line. If you are not seeing the call being received at the remote end (which is likely), that simply means that the carrier is NOT deliverying the call setup information - likely due to Network congestion, as the cause code says. The carrier should be able to monitor the network switches to see how far the call setup travels, and who and why it's not getting any further.

Cisco Employee

Re: trouble troubleshooting isdn here is the debug

Open a case with tac with this output

Debug ppp neg

Debug ppp auth

Debug isdn Q931

Bronze

Re: trouble troubleshooting isdn here is the debug

This makes no sense. From the debug (which covers the q931 call setup), we see that the call is not being established; therefore, any PPP debug would be pointless.

Nov 15 10:00:54: SETUP pd = 8 callref = 0x57

Nov 15 10:00:54: Bearer Capability i = 0x8890

Nov 15 10:00:54: Channel ID i = 0x83

Nov 15 10:00:54: Keypad Facility i = '18605330764'

Nov 15 10:00:54: ISDN BR0: RX <- RRr sapi = 0 tei = 104 nr = 27

Nov 15 10:00:54: ISDN BR0: RX <- INFOc sapi = 0 tei = 104 ns = 62 nr = 27 i = 0x0801D702180189

Nov 15 10:00:54: CALL_PROC pd = 8 callref = 0xD7

Nov 15 10:00:54: Channel ID i = 0x89

Nov 15 10:00:54: ISDN BR0: TX -> RRr sapi = 0 tei = 104 nr = 63

Nov 15 10:00:54: ISDN BR0: received HOST_PROCEEDING call_id 0x8116

Nov 15 10:00:55: ISDN BR0: RX <- INFOc sapi = 0 tei = 104 ns = 63 nr = 27 i = 0x0801D7450802829F340103

Nov 15 10:00:55: DISCONNECT pd = 8 callref = 0xD7 Nov 15 10:00:55:

Cause i = 0x829F - Normal, unspecified

Nov 15 10:00:55: Signal i = 0x03 - Network congestion tone on

Work with the carrier once more.

204
Views
0
Helpful
3
Replies