Thanks for you help, Jim.

I will try setting both sides to 56, however I have verified that it does
not appear to be a speed mismatch between the routers with the "debug q931"
output.  Although I guess it could still be that the telco only provisioned
a 56k line?  But the other B channel is connected fine at 64k.....

Anyway, I'll include the debug q931 output from both routers, and see what
you think.  I found that each router is sending to the other a Bearer
Capability of i = 0x8890 which according to CCO, is 64k.

Also, according to CCO the problem does not appear to be at the q931 layer,
as a CONNECT_ACK is received by both routers.  It also suggests that when
the cause of the disconnection is "Cause i = 0x8090 - Normal call clearing",
as it is in this case, it is usually a problem with a higher layer.  I think
I might be slowly getting there (optimist!).

Thanks again for any help and further suggestions you might have.  From
this, do you still think I should try setting both ends to 56k??  I am in
Australia, if that helps!

Also - to give you some more background on the issue, this setup is about 1
month old.  It was working fine with both channels up at 128k, then after
about a week the second channel just started disconnecting every 20secs.
The IT guy that normally looks after the routers is on holidays, and cant be
contacted to determine whether he changed anything.  What possible problems
could it be if this was caused by the Telco?  Keep in mind that the first B
channel is up fine and does not disconnect....

Thanks again for all your help!

Sam.

Here is the debug q931 output from the 1720 (calling) router:
06:21:236223201963: ISDN BR0: TX ->  SETUP pd = 8  callref = 0x23
06:21:238379534836:         Bearer Capability i = 0x8890
06:21:236223201280:         Channel ID i = 0x83
06:21:236223201280:         Called Party Number i = 0x80, '0353324231',
Plan:Unknown, Type:Unknown
06:21:55: ISDN BR0: RX   CONNECT_ACK pd = 8  callref = 0x23
06:21:246967297336: %LINK-3-UPDOWN: Interface BRI0:2, changed state to up
06:22:17: %ISDN-6-DISCONNECT: Interface BRI0:2  disconnected from 0353324231
clarendon, call lasted 20 seconds
06:22:73014444032: ISDN BR0: TX ->  DISCONNECT pd = 8  callref = 0x23
06:22:75170777588:         Cause i = 0x8090 - Normal call clearing
06:22:17: ISDN BR0: RX   RELEASE_COMP pd = 8  callref = 0x23
06:22:73014444036: %LINK-3-UPDOWN: Interface BRI0:2, changed state to down


Here is the debug q931 output from the 2611 (called) router:
07:18:52: ISDN BR0/1: RX 
on B2 at 64 Kb/s
07:18:227633266687: ISDN BR0/1: TX ->  CALL_PROC pd = 8  callref = 0xD6
07:18:225498880444:         Channel ID i = 0x8A
07:18:52: %LINK-3-UPDOWN: Interface BRI0/1:2, changed state to up
07:18:223338299392: ISDN BR0/1: TX ->  CONNECT pd = 8  callref = 0xD6
07:18:52: ISDN BR0/1: RX   RELEASE pd = 8  callref = 0xD6
07:19:57995155900:         Cause i = 0x8090 - Normal call clearing
07:19:13: ISDN BR0/1: RX 
To: 
Sent: Tuesday, July 03, 2001 2:50 AM
Subject: Re: ISDN B Channel Disconnecting Cont... [7:10596]


> I'm not sure if this will help since the problem seems to be brnging up
the
> second B
> channel.
>
> I know if there is a speed mismatch the line will drop after about a 20
> second
> connection.  Does not even bother to do the CHAP before failing.
>
> I ran into this again last week because I had a finger check in a copy
paste
> of
> configurations.  One side I had the statement 'speed 56' in the dialer map
> statement and
> not in the other.  Removed it and everything worked.
>
> Try adding the statement speed 56 on both sides to see if this helps.
>
> The US seems to have more of a problem with needing to set the speed to 56
> than anywhere
> else.
>
> Jim
>
> Sam Deckert wrote:
>
> > Here is the debug isdn events output from when the 1700 disconnects:
> >
> > clarendon2-gw#
> > 04:14:10: ISDN BR0: Event: Hangup call to call id 0x801E
> > 04:14:10: ISDN BR0: process_disconnect(): call id 0x801E, call type is
> DATA,
> > b_idb 0x809D7DF8, ces 1, cause Normal call clearing(0x10)
> > 04:14:10: %ISDN-6-DISCONNECT: Interface BRI0:2  disconnected from
> 0353324231
> > clarendon, call lasted 20 seconds
> > 04:14:49400989532: ISDN BR0: received HOST_DISCONNECT_ACK call_id 0x801E
> > 04:14:47244640256: ISDN BR0: HOST_DISCONNECT_ACK: call type is DATA
> > 04:14:47244640267: %LINK-3-UPDOWN: Interface BRI0:2, changed state to
down
> > 04:14:49398792589: ISDN BR0: received HOST_DISCONNECT_ACK call_id 0x801E
> > 04:14:47244640256: ISDN BR0: HOST_DISCONNECT_ACK: call type is DATA
> >
> > Here is the debug isdn events output from the 2611 side of things:
> > 05:12:32225367844: ISDN BR0/1: received HOST_DISCONNECT call_id 0x25
> > 05:12:30064771072: ISDN BR0/1: Event:  Call to  was hung up.
> > 05:12:32225367716: ISDN BR0/1: process_disc_ack(): call id 0x25, ces 1,
> call
> > type DATA
> > 05:12:30906921739: %ISDN-6-DISCONNECT: Interface BRI0/1:2  disconnected
> from
> > unknown , call lasted 20 seconds
> > 05:12:32222871552: %LINK-3-UPDOWN: Interface BRI0/1:2, changed state to
> down
> > 05:12:32222862421: ISDN BR0/1: received HOST_DISCONNECT_ACK call_id 0x25
> > 05:12:30064771072: ISDN BR0/1: HOST_DISCONNECT_ACK: call type is DATA
> >
> > I am still working on it!  Thought it might be the fast-idle timer, so
made
> > it
> > a large value, to no avail.
> >
> > Thanks again if anyone can help!
> >
> > Sam.
> >
> > ----- Original Message -----
> > From: Sam Deckert
> > To: [EMAIL PROTECTED]
> > Sent: Monday, July 02, 2001 3:09 PM
> > Subject: ISDN B Channel Disconnecting
> >
> > Hello everyone,
> >
> > I am having a bit of an ISDN related problem at the moment and was
> wondering
> > if anyone is able to help.
> >
> > I am connecting two sites together via 128k isdn, with one site having a
> 2611
> > and the other a 1700.
> >
> > I have the two sites permanently connected fine with the first B
channel,
> > however whenever I issue the "dialer load-threshold 1 either" command
one
> > each
> > router to always have the 2nd B channel up, the second B channel
connects
> and
> > remains connected for 20 seconds exactly before disconnecting.  The 1st
B
> > channel remains connected regardless.
> >
> > I have tried changing the idle-timeout values to no avail, and just cant
> > figure it out.
> >
> > I guess it is probably something simple, but just cant work it out.
> >
> > Here is the BRI config of the 2611:
> >
> > username clarendon2-gw password 7 094E1B040D0210
> > !
> > hostname clarendon
> > ip subnet-zero
> > no ip finger
> > !
> > ipx routing 0030.854f.c9e0
> > ipx gns-response-delay 1500
> > isdn switch-type basic-net3
> > !
> > !
> > interface BRI0/1
> >  ip unnumbered BRI0/0
> >  encapsulation ppp
> >  no ip mroute-cache
> >  dialer idle-timeout 2000000
> >  dialer enable-timeout 5
> >  dialer wait-for-carrier-time 15
> >  dialer map ip xxx.xxx.xxx.xxx name clarendon2-gw broadcast
> >  dialer map ipx FEEDBEEF.0002.1761.29dd name clarendon2-gw broadcast
> >  dialer load-threshold 1 either
> >  dialer-group 1
> >  ipx network FEEDBEEF
> >  no ipx route-cache
> >  ipx watchdog-spoof
> >  isdn switch-type basic-net3
> >  isdn calling-number xxxxxxxx
> >  no fair-queue
> >  compress stac
> >  no cdp enable
> >  ppp authentication chap
> >  ppp multilink
> > !
> > dialer-list 1 protocol ip permit
> > dialer-list 1 protocol ipx permit
> > no cdp run
> >
> > Here is the config of the 1700:
> >
> > hostname clarendon2-gw
> > !
> > username clarendon password 7 011153094F0C01
> > !
> > !
> > ipx routing 0002.1761.29dd
> > ipx gns-response-delay 1500
> > isdn switch-type basic-net3
> > !
> > interface BRI0
> >  ip unnumbered FastEthernet0
> >  encapsulation ppp
> >  dialer idle-timeout 2000000
> >  dialer map ip xxx.xxx.xxx.xxx name clarendon broadcast
> >  dialer load-threshold 1 either
> >  dialer-group 1
> >  ipx network FEEDBEEF
> >  no ipx route-cache
> >  ipx watchdog-spoof
> >  isdn switch-type basic-net3
> >  no fair-queue
> >  compress stac
> >  no cdp enable
> >  ppp authentication chap
> >  ppp multilink
> > !
> > ip classless
> > no ip http server
> > !
> > dialer-list 1 protocol ip permit
> > dialer-list 1 protocol ipx permit
> > no cdp run
> > !
> > no scheduler allocate
> > end
> >
> > What do you think???  Any advice, suggestions welcome and most
appreciated!
> >
> > Thanks...
> >
> > Sam.




Message Posted at:
http://www.groupstudy.com/form/read.php?f=7&i=10723&t=10596
--------------------------------------------------
FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html
Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]

Reply via email to