cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
1563
Views
0
Helpful
6
Replies

ISDN problem

ilyaskhan
Level 1
Level 1

Hi,while configuring ISDN line between 2 sites, i came across a problem regarding the line not coming up. One side has a 2600 series router and the other a 800 series. Ive taken a debug of some commands at the 800 series router side:

Debug dialer events:

6w0d: BR0 DDR: place call

6w0d: BR0 DDR: Dialing cause ip (s=192.168.3.15, d=192.168.0.

6w0d: BR0 DDR: Attempting to dial 065320750

6w0d: BRI0: wait for isdn carrier timeout, call id=0x8B0A

6w0d: BR0 DDR: place call

6w0d: BR0 DDR: Dialing cause ip (s=192.168.3.15, d=192.168.0.

6w0d: BR0 DDR: Attempting to dial 065320750

6w0d: BRI0: wait for isdn carrier timeout, call id=0x8B0B

6w0d: BR0 DDR: place call

6w0d: BR0 DDR: Dialing cause ip (s=192.168.3.15, d=192.168.0.

6w0d: BR0 DDR: Attempting to dial 065320750

6w0d: BRI0: wait for isdn carrier timeout, call id=0x8B0C

Debug isdn events:

6w0d: ISDN Recvd L1 prim 3 dsl 0 state 0 ctrl_state 0

6w0d: ISDN BR0 EVENT: isdn_sw_cstate: State = 0, Old State = 4

6w0d: ISDN BR0: Physical layer is IF_DOWN

6w0d: ISDN BR0: Could not bring up interface

6w0d: ISDN BR0: Shutting down ISDN Layer 3

6w0d: ISDN BR0: Shutting down ME

6w0d: ISDN BR0: Shutting down ISDN Layer 3

6w0d: ISDN BR0: Outgoing call id = 0x8B34, dsl 0

6w0d: ISDN BR0: Event: Call to 065320750 at 64 Kb/s

6w0d: ISDN BR0: process_bri_call(): call id 0x8B34, called_number 065320750, spe

ed 64, call type DATA

6w0d: CCBRI_Go Fr Host InPkgInfo (Len=25) :

6w0d: 1 0 1 8B 34 0 4 2 88 90 18 1 83 70 A 80 30 36 35 33 32 30 37 35 30

6w0d:

6w0d: CC_CHAN_GetIdleChanbri: dsl 0

6w0d: Found idle channel B1

6w0d: ISDN BR0: Activating

6w0d: ISDN BR0 EVENT: isdn_sw_cstate: State = 4, Old State = 4

6w0d: ISDN BR0: Could not bring up interface

6w0d: ISDN BR0: Shutting down ISDN Layer 3

6w0d: ISDN BR0: Activating

6w0d: ISDN BR0: LIF_EVENT: ces/callid 1/0x8B34 HOST_DISCONNECT_ACK

6w0d: ISDN BR0: Error: Unfound B-channel on Disconnect_Ack - callid 0x8B34

6w0d: ISDN BR0: Could not bring up interface

6w0d: ISDN BR0: Shutting down ISDN Layer 3

6w0d: ISDN BR0: Activating

6w0d: ISDN BR0: Outgoing call id = 0x8B35, dsl 0

6w0d: ISDN BR0: Event: Call to 065320750 at 64 Kb/s

6w0d: ISDN BR0: process_bri_call(): call id 0x8B35, called_number 065320750, spe

ed 64, call type DATA

6w0d: CCBRI_Go Fr Host InPkgInfo (Len=25) :

6w0d: 1 0 1 8B 35 0 4 2 88 90 18 1 83 70 A 80 30 36 35 33 32 30 37 35 30

6w0d:

6w0d: CC_CHAN_GetIdleChanbri: dsl 0

6w0d: Found idle channel B1

6w0d: ISDN BR0: Could not bring up interface

6w0d: ISDN BR0: Shutting down ISDN Layer 3

6w0d: ISDN BR0: LIF_EVENT: ces/callid 1/0x8B35 HOST_DISCONNECT_ACK

6w0d: ISDN BR0: Error: Unfound B-channel on Disconnect_Ack - callid 0x8B35

6w0d: ISDN Recvd L1 prim 3 dsl 0 state 3 ctrl_state 0

6w0d: ISDN BR0: L1 persistent Deactivated

6w0d: ISDN BR0: Outgoing call id = 0x8B36, dsl 0

6w0d: ISDN BR0: Event: Call to 065320750 at 64 Kb/s

6w0d: ISDN BR0: process_bri_call(): call id 0x8B36, called_number 065320750, spe

ed 64, call type DATA

6w0d: CCBRI_Go Fr Host InPkgInfo (Len=25) :

6w0d: 1 0 1 8B 36 0 4 2 88 90 18 1 83 70 A 80 30 36 35 33 32 30 37 35 30

Debug isdn q931:

6w0d: ISDN BR0: Could not bring up interface

6w0d: ISDN BR0: Could not bring up interface

6w0d: ISDN BR0: Could not bring up interface

Any idea about the problem? if required i can get the debug from the 2600 series side as well.

1 Accepted Solution

Accepted Solutions

Hi

Please refer to below (look for ---Symptom: The ISDN Call does not Connect Successfully)

http://www.cisco.com/en/US/tech/tk801/tk379/technologies_tech_note09186a0080094bb8.shtml

Hope this help:)

MD

View solution in original post

6 Replies 6

Richard Burts
Hall of Fame
Hall of Fame

It looks to me like the router is having trouble bringing up the interface. The output of show isdn status might be helpful. It would also be helpful if you would post the config (at least all the parts that relate to ISDN).

HTH

Rick

HTH

Rick

makchitale
Level 6
Level 6

Can you please capture the following on both the routers:

deb isdn q931

deb ppp nego

Thanks, Mak

ilyaskhan
Level 1
Level 1

Here is a file containing some debug outputs from the HQ 2600 series.I entered the following commands on both sides with respect to isdn configuration:

On the Global Configuration level:

username (Other Side Hostname) password !@#$%

dialer-list 1 protocol ip permit

isdn switch-type basic-net3

On the interface level:

ip address 192.168.100.x 255.255.255.0

encapsulation ppp

dialer map ip 192.168.100.x name (Other side Hostname) (Other side telephone number)

dialer-group 1

ppp authentication chap

no shutdown.

Thats it.Other than this ive added a static route for the destination networks and nothing more. Any ideas??

Hi

Please refer to below (look for ---Symptom: The ISDN Call does not Connect Successfully)

http://www.cisco.com/en/US/tech/tk801/tk379/technologies_tech_note09186a0080094bb8.shtml

Hope this help:)

MD

Thanks for sending the file with the debug output.

It looks to me that the show isdn status indicates that things are looking normal on the router.

I think there is a clue about what is happening in the debug isdn q931 output. In particular look at these lines of output:

00:25:47: ISDN BR0/0: RX <- CALL_PROC pd = 8 callref = 0x9C

00:27:00: ISDN BR0/0: RX <- DISCONNECT pd = 8 callref = 0x9D

00:27:00: Cause i = 0x829F - Normal, unspecified

The output just before this has indicated that you placed the call. The first line here indicates that you received a call_proceeding response which is normal in call setup. But the next line indicates that you receive a disconnect.

This leads me to believe that the problem is on the router on the other end of the connection attempt. Could you post similar output from that router (especially show isdn status, debug isdn q931. The output of debug dialer events and debug isdn events might also be useful.

HTH

Rick

HTH

Rick

ilyaskhan
Level 1
Level 1

Hi..got the problem solved..after checking all debug and stuff, finally came to know through a LED that line was down from the service provider on the remote side. Once that got fixed, things started working fine from there. thanks for the help.