I would think that the " dialer load-threshold 1 either" will cause both BRI
B channels to be always busy when the link is up.
That statment says when the first B channel reaches 1/255 usage, which would
be immediately, the second B channel should connect.
Isn't the first B channel BRI1/0:0, anyhow? You mentioned that a call was
already placed on BRI1/0:1, which would support my suspicion about both
BRI1/0 B channels having called the other router.
-----Original Message-----
From: Jim Warner [mailto:warner@cats.UCSC.EDU]
Sent: Monday, August 20, 2001 9:38 AM
To: cisco-nsp@puck.nether.net
Cc: kashmir@cats.UCSC.EDU
Subject: [nsp] 2nd BRI call problem
Hello. We have 3 BRI interfaces on two routers named coast and summit.
When trying to place a call from coast to summit, the first call
completes, but when the second call is placed (to the same dialer string),
I get a busy error message. I thought since there is an available B
channel on that same BRI interface on summit, that the second B-channel
should connect. For testing purposes, I had summit call coast, and this
worked correctly, with both B-channels on coast connecting when the same
dialer string was called.
I am suspicious of the ISDN switches between both my routers which are
PacBell and Verizon. Is there anything I can do to narrow down where the
busy signal is coming from?
Below you will find some debug output that contains the busy error and
also the configuration of coast and summit.
Thanks for the help,
DEBUG:
------
A call to string 1234 has already been completed on BRI1/0:1 and now a
second call is attempted:
Aug 15 23:04:14.229 UTC: BR1/0 DDR: rotor dialout [priority]
Aug 15 23:04:14.229 UTC: BR1/0 DDR: Attempting to dial 1234
Aug 15 23:04:14.229 UTC: ISDN BR1/0: Outgoing call id = 0x811A, dsl 8
Aug 15 23:04:14.229 UTC: ISDN BR1/0: Event: Call to 1234 at 64 Kb/s
Aug 15 23:04:14.229 UTC: ISDN BR1/0: process_bri_call(): call id 0x811A,
called_number 1234, speed 64, call type DATA
Aug 15 23:04:14.229 UTC: CC_CHAN_GetIdleChanbri: dsl 8
Aug 15 23:04:14.233 UTC: Found idle channel B2
Aug 15 23:04:14.233 UTC: ISDN BR1/0: TX -> SETUP pd = 8 callref = 0x1C
Aug 15 23:04:14.237 UTC: Bearer Capability i = 0x8890
Aug 15 23:04:14.237 UTC: Channel ID i = 0x83
Aug 15 23:04:14.237 UTC: Keypad Facility i = '1234'
Aug 15 23:04:14.817 UTC: ISDN BR1/0: RX <- CALL_PROC pd = 8 callref =
0x9C
Aug 15 23:04:14.821 UTC: Channel ID i = 0x8A
Aug 15 23:04:14.825 UTC: ISDN BR1/0: LIF_EVENT: ces/callid 2/0x811A
HOST_PROCEEDING
Aug 15 23:04:15.069 UTC: %LINEPROTO-5-UPDOWN: Line protocol on Interface
BRI1/0:1, changed state to up
Aug 15 23:04:16.597 UTC: ISDN BR1/0: RX <- DISCONNECT pd = 8 callref =
0x9C
Aug 15 23:04:16.597 UTC: Cause i = 0x8091 - User busy
Aug 15 23:04:16.601 UTC: Signal i = 0x04 - Busy tone on
Aug 15 23:04:16.609 UTC: ISDN BR1/0: LIF_EVENT: ces/callid 2/0x811A
HOST_DISCONNECT
Aug 15 23:04:16.609 UTC: ISDN BR1/0: Event: Call to 1234 was hung up.
-------
COAST:
-------
Cisco 2621, IOS (tm) C2600 Software (C2600-I-M), Version 12.1(2)T
Basic Rate ISDN software, Version 1.1., 4 ISDN Basic Rate interface(s)
!
interface BRI1/0
no ip address
encapsulation ppp
no ip mroute-cache
dialer pool-member 1 priority 250
isdn switch-type basic-ni
isdn spid1
isdn spid2
no fair-queue
!
interface Dialer0
ip unnumbered Tunnel0
encapsulation ppp
load-interval 30
dialer remote-name summit
dialer pool 1
dialer idle-timeout 30
dialer string 1234
dialer string 5678
dialer string 9012
dialer load-threshold 1 either
dialer max-call 6
dialer-group 5
no fair-queue
ppp authentication chap
ppp multilink
!
------
SUMMIT:
------
Cisco 2621, IOS (tm) C2600 Software (C2600-I-M), Version 12.0(5)T1
Basic Rate ISDN software, Version 1.1., 4 ISDN Basic Rate interface(s)
!
interface BRI1/0
no ip address
no ip directed-broadcast
encapsulation ppp
no ip mroute-cache
dialer pool-member 1
isdn switch-type basic-ni
isdn spid1
isdn spid2
!
interface Dialer0
ip unnumbered Tunnel0
no ip directed-broadcast
encapsulation ppp
dialer remote-name coast
dialer pool 1
dialer-group 5
ppp authentication chap
ppp multilink
!
This archive was generated by hypermail 2b29 : Sun Aug 04 2002 - 04:12:49 EDT