From: Duongla (duongla@vnn.vn)
Date: Wed Sep 21 2005 - 23:37:34 GMT-3
Hi ,
Your problem is as follows: when client router calls the server router, the
server will disconnect the call by sending DISCONNECT message to the ISDN
switch and try to call back the client. For some reason, the ISDN does not
send this msg to the client router. As a result, the server has released the
call but the client still has CALL PROCEEDING status. By default, the client
router will wait for T310=30 seconds before it disconnects the call which
has been made to the server before. During this time the server calls back
to client and call will fail. Be noted that the server will call back just
one time.
Try to reduce T310 on the client router: isdn T310 5
and set the time the server will wait before call back: dialer
enable-timeout 10
HTH
Duongla
----- Original Message -----
From: "Niche" <jackyliu419@gmail.com>
To: "Godswill Oletu" <oletu@inbox.lv>
Cc: <ccielab@groupstudy.com>
Sent: Tuesday, September 20, 2005 2:34 PM
Subject: Re: isdn call back problem
> Hi,
>
> Yep, I did exactly what this document said. No good =/
>
> Cheers~
> Jacky
>
> On 9/20/05, Godswill Oletu <oletu@inbox.lv> wrote:
> >
> > manually configure the the 'dialer wait-for-carrier-time <seconds>' on
the
> > remote router to be at least twice the value of the 'dialer
enable-timeout
> > <seconds>' on the local router.
> > see if this link will help you....
> >
> >
>
http://www.cisco.com/univercd/cc/td/doc/product/software/ios122/122cgcr/fdial
> _c/fnsprt10/dafcalid.htm
> > HTH
> > Godswill Oletu
> >
> > ----- Original Message -----
> > *From:* Niche <jackyliu419@gmail.com>
> > *To:* Godswill Oletu <oletu@inbox.lv>
> > *Cc:* ccielab@groupstudy.com
> > *Sent:* Tuesday, September 20, 2005 2:57 AM
> > *Subject:* Re: isdn call back problem
> >
> > Hi,
> >
> > Thanks for the reply =)
> >
> > I did configured "dialer wait-for-carrier-time <seconds>" on the remote
> > router, no good..
> >
> > I tried these debug commands, the conclusion seem it's related to
carrier
> > timeout which I still haven't find a way to solve the problem.
> >
> > Did anyone can use this command to establish a callback connection
> > successfully?
> >
> > Cheers~
> > Jacky
> >
> > On 9/20/05, Godswill Oletu <oletu@inbox.lv> wrote:
> > >
> > > Jacky,
> > >
> > > You need to configure 'isdn caller <remote-number> callback' on the
> > > local
> > > router and also
> > > 'dialer wait-for-carrier-time <seconds>' on the remote router.
> > >
> > > Check to see what your 'show dialer'; 'debug isdn event' and 'debug
isdn
> > >
> > > q931' is giving you.
> > >
> > > HTH
> > >
> > >
> > > ----- Original Message -----
> > > From: "Niche" <jackyliu419@gmail.com>
> > > To: < ccielab@groupstudy.com>
> > > Sent: Tuesday, September 20, 2005 2:23 AM
> > > Subject: isdn call back problem
> > >
> > >
> > > > Hi Group,
> > > >
> > > > AFAIK, there are 2 way to configure ISDN call back
> > > >
> > > > 1. calling router: ppp callback request
> > > > callback router: ppp callback accept,
> > > > dialer map ip w/ class CALLBACK (e.g)
> > > > map-class dialer CALLBACK w/ dialer callback-server username
> > > >
> > > > 2. By using "isdn caller <remote peer phone no> callback" command at
> > > the
> > > > callback side.
> > > >
> > > > So far, I don't have any problem with the first method.
> > > >
> > > > However, the 2nd method seems not working. I have been trying to
copy
> > > the
> > > > lab workbook model answer but still no luck. May be it's isdn
> > > simulator
> > > > limitation?
> > > >
> > > > I have turned on debug dialer and it showed that the carrier
timeout.
> > > I
> > > > have
> > > > modified the isdn carrier timeout setting and also the callback time
> > > > interval setting (make the callback happen sooner, like 2 seconds).
No
> > >
> > > > good..
> > > >
> > > > Any body can give me some hints?
> > > >
> > > > Cheers~
> > > > Jacky
> > > >
> > > >
> > >
This archive was generated by hypermail 2.1.4 : Sun Oct 02 2005 - 14:40:16 GMT-3