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

ISDN Disconnect?

Any ideas on the reason for disconnect?????

Type escape sequence to abort.

Sending 5, 100-byte ICMP Echos to 10.3.102.5, timeout is 2 seconds:

3d00h: ISDN BR0/0: Outgoing call id = 0xAED3, dsl 0

3d00h: ISDN BR0/0: Event: Call to 00121564353230101 at 64 Kb/s

3d00h: ISDN BR0/0: process_bri_call(): call id 0xAED3, called_number 00121564353230101, speed 64, call type DATA

3d00h: CC_CHAN_GetIdleChanbri: dsl 0

3d00h: Found idle channel B1

3d00h: ISDN BR0/0: Activating

3d00h: ISDN BR0/0 EVENT: State = 4, Old State = 4

3d00h: ISDN BR0/0: L1 is IF_ACTIVE

3d00h: ISDN BR0/0 EVENT: State = 4, Old State = 4

3d00h: ISDN BR0/0: Recvd MPH_EI2_IND from L1

3d00h: %ISDN-6-LAYER2UP: Layer 2 for Interface BR0/0, TEI 106 changed to up

3d00h: ISDN BR0/0: TX -> SETUP pd = 8 callref = 0x31

3d00h: Bearer Capability i = 0x8890

3d00h: Channel ID i = 0x83

3d00h: Keypad Facility i = '00121564353230101'

3d00h: ISDN BR0/0: RX <- CALL_PROC pd = 8 callref = 0xB1

3d00h: Channel ID i = 0x89

3d00h: ISDN BR0/0: received HOST_PROCEEDING call_id 0xAED3.

3d00h: ISDN BR0/0: RX <- ALERTING pd = 8 callref = 0xB1

3d00h: Progress Ind i = 0x8482 - Destination address is non-ISDN

3d00h: Progress Ind i = 0x8488 - In-band info or appropriate now available

3d00h: ISDN BR0/0: received HOST_ALERTING call_id 0xAED3

3d00h: ISDN BR0/0: HOST_ALERTING: DEV_CALL_PROGRESSING: VOICE ERROR: Bearer capability not available(0x3A): bchan 0, call id AED3...

3d00h: ISDN BR0/0: RX <- DISCONNECT pd = 8 callref = 0xB1

3d00h: Cause i = 0x849F - Normal, unspecified

3d00h: ISDN BR0/0: TX -> RELEASE pd = 8 callref = 0x31

3d00h: ISDN BR0/0: received HOST_DISCONNECT call_id 0xAED3

3d00h: ISDN BR0/0: Event: Call to 00121564353230101 was hung up.

3d00h: ISDN BR0/0: process_disc_ack(): call id 0xAED3, ces 1, call type DATA

3d00h: ISDN BR0/0: Outgoing call id = 0xAED4, dsl 0

3d00h: ISDN BR0/0: Event: Call to 00121564353230101 at 64 Kb/s

3d00h: ISDN BR0/0: process_bri_call(): call id 0xAED4, called_number 00121564353230101, speed 64, call type DATA

3d00h: CC_CHAN_GetIdleChanbri: dsl 0

3d00h: Found idle channel B2

3d00h: ISDN BR0/0: TX -> SETUP pd = 8 callref = 0x32

3d00h: Bearer Capability i = 0x8890

3d00h: Channel ID i = 0x83

3d00h: Keypad Facility i = '00121564353230101'

3d00h: ISDN BR0/0: RX <- RELEASE_COMP pd = 8 callref = 0xB1

3d00h: ISDN BR0/0: received HOST_DISCONNECT_ACK call_id 0xAED3

3d00h: ISDN BR0/0: HOST_DISCONNECT_ACK: call type is DATA

3d00h: ISDN BR0/0: RX <- CALL_PROC pd = 8 callref = 0xB2

3d00h: Channel ID i = 0x89

3d00h: ISDN BR0/0: received HOST_PROCEEDING call_id 0xAED4

3d00h: ISDN BR0/0: RX <- DISCONNECT pd = 8 callref = 0xB2

3d00h: Cause i = 0x83A2 - No circuit/channel available

3d00h: ISDN BR0/0: TX -> RELEASE pd = 8 callref = 0x32

3d00h: ISDN BR0/0: received HOST_DISCONNECT call_id 0xAED4

3d00h: ISDN BR0/0: Event: Call to 00121564353230101 was hung up.

3d00h: ISDN BR0/0: process_disc_ack(): call id 0xAED4, ces 1, call type DATA

3d00h: ISDN BR0/0: RX <- RELEASE_COMP pd = 8 callref = 0xB2

3d00h: ISDN BR0/0: received HOST_DISCONNECT_ACK call_id 0xAED4

3d00h: ISDN BR0/0: HOST_DISCONNECT_ACK: call type is DATA.

Success rate is 0 percent (0/5)

thnaks in advance.

2 REPLIES
New Member

Re: ISDN Disconnect?

There certainly isn't a whole lot of consistancy in the cause codes. First and foremost, Gemplus.com appears to be a US website, so the 001+ dialing looks awkward. Verify that first.

Without SERVICE TIMESTAMPS DEBUG DATETIME MSEC LOCAL, it's gonna be a little difficult to distinguish lines, but I'll give it my best....

Given the first two messages:

3d00h: Progress Ind i = 0x8482 - Destination address is non-ISDN

3d00h: Progress Ind i = 0x8488 - In-band info or appropriate now available

the Cause Code Field table at http://www.cisco.com/univercd/cc/td/doc/product/software/ios113ed/dbook/disdn.htm#xtocid282502 tells us that it's the telco from the destination that's talking, and they're saying that the number we're calling isn't ISDN.

On the next call,

3d00h: Cause i = 0x83A2 - No circuit/channel available

is an intermediate network--somewhere between here and there--that's saying that they don't have an ISDN channel available to place the call on.

The first call situation, I've seen where an ISDN device doing a data call is trying to call a DOV (Data Over Voice) device, or there being a problem with the telco at the far end.

The second situation, I've seen when trying to call remote areas like the Northwest Territories of Canada where there aren't a lot of ISDN circuits available.

If you're responsible for both ends, contact the telco at the far end. If you're not responsible for the far end, ask if there's problems with the remote site making local calls or calling back to you?

New Member

Re: ISDN Disconnect?

This might help:

http://www.cisco.com/warp/public/129/isdn_disc_code.html

The first disconnect comes from "From the public network near the remote user (remote telco switch)" and it says it is because "Normal, unspecified"...not very helpful.

The second disconnect comes from "From the transit network (in the ISDN cloud)" and says "No circuit/channel available".

Might need to change your config so it has "service timestamp debug datetime msec" so we can see at what point things are happening.

For the first disconnect I would get the debug isdn q931 from the called router to see if the setup even hits it, and to see what happens after that.

For the second disconnect I would call the telco and ask them what is up, maybe their network is congested.

Josh

869
Views
0
Helpful
2
Replies
CreatePlease login to create content