>From router B, I pinged a boggus destination. This triggered the bri interface on router B. Here is the output of the "debug dialer events" from Router A. You can see that router A (for no apparent reason) is trying to call router B (even though it is router B who initiated the call.) Of course the result of this is that the isdn timers will time out because the only channel available is busy with the call initiated by router B.
Why would router A attempt to call the next hop? (172.16.1.2) Sending 5, 100-byte ICMP Echos to 1.2.3.6, timeout is 2 seconds: 00:17:27: BR0/0 DDR: Dialing cause ip (s=172.16.1.1, d=172.16.1.2) 00:17:27: BR0/0 DDR: Attempting to dial 5554000 00:17:27: BRI0/0: wait for isdn carrier timeout, call id=0x8006. 00:17:29: BR0/0 DDR: Dialing cause ip (s=172.16.1.1, d=172.16.1.2) 00:17:29: BR0/0 DDR: Attempting to dial 5554000 00:17:29: BRI0/0: wait for isdn carrier timeout, call id=0x8007. 00:17:31: BR0/0 DDR: Dialing cause ip (s=172.16.1.1, d=172.16.1.2) 00:17:31: BR0/0 DDR: Attempting to dial 5554000 00:17:31: BRI0/0: wait for isdn carrier timeout, call id=0x8008. 00:17:33: BR0/0 DDR: Dialing cause ip (s=172.16.1.1, d=172.16.1.2) 00:17:33: BR0/0 DDR: Attempting to dial 5554000 00:17:33: BRI0/0: wait for isdn carrier timeout, call id=0x8009. 00:17:35: BR0/0 DDR: Dialing cause ip (s=172.16.1.1, d=172.16.1.2) 00:17:35: BR0/0 DDR: Attempting to dial 5554000 00:17:35: BRI0/0: wait for isdn carrier timeout, call id=0x800A. Success rate is 0 percent (0/5) Message Posted at: http://www.groupstudy.com/form/read.php?f=7&i=46607&t=46496 -------------------------------------------------- FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
