Re: Problem with ISDN when calling between two routers from CH1 to CH2 on same number.

From: Wu Jiang (wujiang@xxxxxxxxx)
Date: Thu Feb 01 2001 - 01:04:33 GMT-3


   
Try this command:
dialer pool-member 1 max-link 1

Wu

----- Original Message -----
From: "Flack, Les" <les_flack@hotmail.com>
To: <ccielab@groupstudy.com>
Sent: Wednesday, January 31, 2001 11:45 PM
Subject: Re: Problem with ISDN when calling between two routers from CH1 to CH2
 on same number.

> Justin,
>
> Your description certainly fits the symptoms but unfortunately I've no
> conrol over the Switch as its a British Telecom ISDN (Highway service).
> Tariq suggested I ask the provider for multi channel subscriber no's but I
> tried that today and BT wont play ball. Another suggestion from the group
> was to use caller id to screen calls, I havn't tried that yet but I dont
> think that will help as both the calling and called routers will use the
> same number. Any other suggestions welcome.
>
> regards
>
> Les
> ----- Original Message -----
> From: "Justin Menga" <Justin.Menga@computerland.co.nz>
> To: "'Flack, Les'" <LFlack@thrupoint.net>; <ccielab@groupstudy.com>
> Sent: Wednesday, January 31, 2001 12:01 PM
> Subject: RE: Problem with ISDN when calling between two routers from CH1 to
> CH2 on same number.
>
>
> > Les, I think this has something to do with your ISDN switching in the
> middle
> > - if you have a single switch in the middle, it looks like the call setup
> is
> > being routed both back to your 2500 B2 channel (like feedback) and also to
> > your 1600. It looks like the 2500 accepts the 'feedback' call first, and
> > the circuit is then established between 2500 B1 and 2500 B2. If you have
> > control over the ISDN switch then try using unique numbers - addresses
> > usually have one major rule - UNIQUENESS
> >
> > I know it sounds ludicrous but I have many a time configured the wrong
> phone
> > numbers and got weird crazy stuff like above....
> >
> > Regards,
> >
> > Justin Menga CCIE #6640 MCSE+I CCSE
> > WAN Specialist
> > Computerland New Zealand
> > PO Box 3631, Auckland
> > DDI: (+64) 9 360 4864 Mobile: (+64) 25 349 599
> > mailto: justin.menga@computerland.co.nz
> >
> >
> >
> > -----Original Message-----
> > From: Flack, Les [mailto:LFlack@thrupoint.net]
> > Sent: Wednesday, January 31, 2001 8:06 AM
> > To: ccielab@groupstudy.com
> > Subject: Problem with ISDN when calling between two routers from CH1 to
> > CH2 on same number.
> >
> >
> > Hi all,
> >
> > I'm having a problem with ISDN when calling between two routers =
> > from CH1 to CH2 on the same number. (My isdn line has the same number =
> > for both B channels.)
> >
> > For example:
> >
> > My 1600 at 12.0(14) calls out of B1 and my 2500 11.3(11a) receives on =
> > B2 no problem.
> >
> > but if I try to make the call from the 2500 to the 1600 the 2500 calls =
> > out on B1 AND receives the call on B2. The 1600 does see the call come =
> > in on B2 but receives a HOST_DISCONNECT_ACK before it can setup the =
> > call.
> >
> > What am I doing wrong??
> >
> > regards,
> >
> > Les
> >
> > 1600 (r6#)
> >
> > interface BRI0
> > ip address 172.168.65.1 255.255.255.0
> > no ip directed-broadcast
> > encapsulation ppp
> > ip ospf network point-to-point
> > no ip mroute-cache
> > dialer map ip 172.168.65.2 name r5 broadcast 9583
> > dialer-group 1
> > isdn switch-type basic-net3
> > ppp authentication chap
> > ppp chap hostname r6
> > ppp chap password 7 1511021F0725
> > end
> >
> > r6#
> > 1d05h: ISDN BR0: Incoming call id =3D 0x2E
> > 1d05h: ISDN BR0: received HOST_INCOMING_CALL call_id 0x2E
> > 1d05h: ISDN BR0: Event: Received a call from <unknown> on B2 at 64 Kb/s
> > 1d05h: ISDN BR0: Event: Accepting the call id 0x2E
> > 1d05h: %LINK-3-UPDOWN: Interface BRI0:2, changed state to up
> > 1d05h: %ISDN-6-CONNECT: Interface BRI0:2 is now connected to unknown
> > 1d05h: BR0:2 PPP: Treating connection as a callin
> > 1d05h: ISDN BR0: received HOST_DISCONNECT_ACK call_id 0x2E
> > 1d05h: %LINK-3-UPDOWN: Interface BRI0:2, changed state to down
> > 1d05h: ISDN BR0: received HOST_DISCONNECT_ACK call_id 0x2E
> > r6#
> >
> > 2500 (r5#)
> >
> > interface BRI0
> > ip address 172.168.65.2 255.255.255.0
> > no ip directed-broadcast
> > encapsulation ppp
> > no ip mroute-cache
> > dialer map ip 172.168.65.1 name r6 broadcast 9583
> > dialer-group 1
> > ppp authentication chap
> > ppp chap hostname r5
> > ppp chap password 7 045802150C2E=20
> >
> > r5#
> > 1d05h: ISDN BR0: Outgoing call id =3D 0x801E
> > 1d05h: ISDN BR0: Event: Call id 0x801E to 9583 at 64 Kb/s
> > 1d05h: ISDN BR0: received HOST_INFORMATION call_id 0x801E
> > 1d05h: ISDN BR0: Incoming call id =3D 0x66
> > 1d05h: ISDN Event: dsl 0 call_id 0x801E B channel assigned by switch 0
> > ISDN BR0: received HOST_INCOMING_CALL call_id 0x66
> > 1d05h: ISDN BR0: llc valid, speed 64, call type is Sync
> > speed:-1 async:Y
> > 1d05h: ISDN BR0: Event: Received a call from <unknown> on B2 at 64 Kb/s
> > 1d05h: ISDN BR0: Event: Accepting the call id =3D 0x66
> > 1d05h: %LINK-3-UPDOWN: Interface BRI0:2, changed state to up
> > 1d05h: ISDN BR0: received HOST_ALERTING call_id 0x801E
> > 1d05h: ISDN BR0: received HOST_CONNECT call_id 0x801E
> > 1d05h: %LINK-3-UPDOWN: Interface BRI0:1, changed state to up
> > 1d05h: ISDN BR0: Event: Connected to 9583 on B1 at 64 Kb/s
> > r5#
> > 1d05h: %ISDN-6-CONNECT: Interface BRI0:2 is now connected to unknown
> > 1d05h: %ISDN-6-CONNECT: Interface BRI0:1 is now connected to 9583
> > r5# =20
> >
> > ---------------------------------------End-------------------------------=
> > ------------
> >
> >



This archive was generated by hypermail 2.1.4 : Thu Jun 13 2002 - 10:28:32 GMT-3