Could you post the output from a 'debug dialer events' command. Then we can see the reason that routerB initiates the call.
______________________________ Thomas Crowe Senior Systems Engineer / Senior Architect EMC Proven Master Architect CTS Professional Services - Atlanta ______________________________ -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] Sent: Thursday, June 13, 2002 6:34 PM To: [EMAIL PROTECTED] Subject: ISDN -- challenge! [7:46496] Router A and Router B are connected to an Atlas 550 via BRI interfaces Router A ---- ATLAS --- ROUTER B Both router are configured with DDR Dialer maps so that Router A can call router B or vice-versa (basic stuff). When Router A is called by Router B, Router A answers normally and the link goes up, but then (surprisingly), Router A attempts to initiate a connection to Router B . This connection fails because I only configured the phone number for one channel (Isdn error 17: User is busy). Is this calling of Router A a normal behavior? (I don't think so!) I fixed the problem by simpling removing the phone number from the map statement of Router A. I am posting here the debug before and after I removed the phone number on A. The debug where captured on Router A. I have spent the day on the apparently trivial question: why is Router A calling Router B when I have no call back of any sort. Still no light ... Want to step up to the challenge? :) Before: 00:32:45: ISDN BR0/0: RX on B1 at 64 Kb/s 00:32:45: ISDN BR0/0: Event: Accepting the call id 0xD 00:32:193273528320: %LINK-3-UPDOWN: Interface BRI0/0:1, changed state to up 01:51:113824615516: %LINK-3-UPDOWN: Interface BRI0:1, changed state to up 00:32:45: ISDN BR0/0: TX -> CALL_PROC pd = 8 callref = 0x84 00:32:45: Channel ID i = 0x89 00:32:45: ISDN BR0/0: TX -> CONNECT pd = 8 callref = 0x84 00:32:45: Channel ID i = 0x89 00:32:45: ISDN BR0/0: RX SETUP pd = 8 callref = 0x09 00:32:47: Bearer Capability i = 0x8890 00:32:47: Channel ID i = 0x83 00:32:47: Keypad Facility i = '5553333' 00:32:47: ISDN BR0/0: RX RELEASE pd = 8 callref = 0x09 00:32:47: ISDN BR0/0: RX SETUP pd = 8 callref = 0x0A 00:32:49: Bearer Capability i = 0x8890 00:32:49: Channel ID i = 0x83 00:32:49: Keypad Facility i = '5553333' 00:32:49: ISDN BR0/0: RX RELEASE pd = 8 callref = 0x0A 00:32:49: ISDN BR0/0: RX SETUP pd = 8 callref = 0x0B 00:32:51: Bearer Capability i = 0x8890 00:32:51: Channel ID i = 0x83 00:32:51: Keypad Facility i = '5553333' 00:32:51: %ISDN-6-CONNECT: Interface BRI0/0:1 is now connected to isdn3 00:32:51: ISDN BR0/0: RX RELEASE pd = 8 callref = 0x0B 00:32:51: ISDN BR0/0: RX SETUP pd = 8 callref = 0x0C 00:32:53: Bearer Capability i = 0x8890 00:32:53: Channel ID i = 0x83 00:32:53: Keypad Facility i = '5553333' 00:32:53: ISDN BR0/0: RX RELEASE pd = 8 callref = 0x0C 00:32:53: ISDN BR0/0: RX on B1 at 64 Kb/s 00:41:53: ISDN BR0/0: Event: Accepting the call id 0x10 00:41:227633266688: %LINK-3-UPDOWN: Interface BRI0/0:1, changed state to up 02:00:146028888128: %ISDN-6-CONNECT: Interface BRI0:1 is now connected to 5551234 00:41:53: ISDN BR0/0: TX -> CALL_PROC pd = 8 callref = 0x85 00:41:53: Channel ID i = 0x89 00:41:53: ISDN BR0/0: TX -> CONNECT pd = 8 callref = 0x85 00:41:53: Channel ID i = 0x89 00:41:53: ISDN BR0/0: RX <- CONNECT_ACK pd = 8 callref = 0x05.. 02:00:37: %LINEPROTO-5-UPDOWN: Line protocol on Interface BRI0:1, changed state to up 00:41:56: %LINEPROTO-5-UPDOWN: Line protocol on Interface BRI0/0:1, changed state to up. 02:00:40: %ISDN-6-CONNECT: Interface BRI0:1 is now connected to 5551234 isdn1 00:41:59: %ISDN-6-CONNECT: Interface BRI0/0:1 is now connected to isdn3.. [GroupStudy.com removed an attachment of type text/x-vcard which had a name of Thomas Crowe.vcf] Message Posted at: http://www.groupstudy.com/form/read.php?f=7&i=46564&t=46496 -------------------------------------------------- FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
