From: ying chang (ying_c@xxxxxxxxxxx)
Date: Wed Apr 10 2002 - 10:40:19 GMT-3
I don't think we can do the dialer watch-list with callback the way you
describe here. The reason is as soon as the watched route disappear, it will
trigger r1 to call r2, however, r2 has to drop the call to call r1 back, and
this will trigger r1 to make another call. The result is we'll be in some
kind of race condition, you call me, I call you, ... sometimes it will get
settle down, but you probably cannot expect you are going to have a
consistent result. This can be seen via debug command. Anyway, the best we
can do is to make r1 as the callback server and r2 as callback client, I
know this doesn't make a whole lot of sense, as when r1 call r2, it just
connect the call and r2 will not callback, but what else can you do to have
both live peacefully together?
just my 2 cents.
Chang
>From: Richard Furda <riso@furda.net>
>Reply-To: Richard Furda <riso@furda.net>
>To: ccielab@groupstudy.com
>Subject: ISDN callback & watch-list problem
>Date: Wed, 10 Apr 2002 05:07:36 +0000 (GMT)
>
>Hello,
>
>I am having a problem with ISDN when using callback & watchlist together.
>Scenario as follows:
>
>
><R1> ======== <isdn cloud> ======= <R2>
>
>R1 is ppp callback client
>R2 is pp callback server
>
>
>1. When R1 bri0 IP pings R2's bri0 IP address, callback is OK.
>
>2. When a watch-list triggers a ISDN call to R2 following will happen:
>
> * R1 makes a call to R2
>
> * R2 disconnects R1 and initiates callback
>
> * even though the following is configure on R1's bri0, R1 keeps
> making new calls while R2 disconnects them because it wants to
> initiate callback. Since I have 1 BRI (calling from 1 B channel to
> the other) link will endlessly flap - cool loop :)
>
> dialer hold-queue 10
> dialer enable-timeout 20
>
>
>R1 runs Version 12.0(9)
>R2 runs Version 12.1(1)
>
>any ideas?
>
> Thanks,
> Rich
This archive was generated by hypermail 2.1.4 : Thu Jun 13 2002 - 10:58:03 GMT-3