From: Brian Dennis (bdennis@internetworkexpert.com)
Date: Mon Aug 23 2004 - 02:48:59 GMT-3
Outside of dialer watch and dialer persistence, without the dialer-group
command the router will drop the call after the idle-timeout expires
(default 120 seconds).
As far as using dialer idle-timeout 0 command, have you tested it to see
if it ever drops? Look at the output of the show dialer command below:
Rack1R4#sho dialer
BRI0/0 - dialer type = ISDN
Dial String Successes Failures Last DNIS Last status
0 incoming call(s) have been screened.
0 incoming call(s) rejected for callback.
BRI0/0:1 - dialer type = ISDN
Idle timer (never), Fast idle timer (20 secs)
Wait for carrier (30 secs), Re-enable (15 secs)
Dialer state is data link layer up
Dial reason: ip (s=183.1.45.4, d=183.1.45.5)
Interface bound to profile Di1
Time until disconnect never <-----------------
Current call connected 00:00:53
Connected to 5272015 (5272015)
Notice that the time until disconnect is "never".
Brian Dennis, CCIE #2210 (R&S/ISP-Dial/Security)
bdennis@internetworkexpert.com
Internetwork Expert, Inc.
http://www.InternetworkExpert.com
Toll Free: 877-224-8987
Direct: 775-745-6404 (Outside the US and Canada)
-----Original Message-----
From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf Of
marc van hoof
Sent: Sunday, August 22, 2004 10:30 PM
To: ccielab@groupstudy.com
Subject: isdn timers and dialer maps
If dialer idle-timeout is set to 0, the interface sets the idle timer to
the
max 2147483 and starts counting down. It seems like dialer idle-timeout
0
means doesn't mean it will never disconnect, it just means "make the
timer
so long that the chance of not getting interesting traffic is next to
nothing"
If I apply this to an interface which has no dialer-group command on it,
and
hence the interface doesn't know what is interesting traffic and what
isn't,
does that mean that one day the link WILL disconnect ?
Thanks,
-marc.
This archive was generated by hypermail 2.1.4 : Fri Sep 03 2004 - 07:02:47 GMT-3