From: Brian Dennis (brian@labforge.com)
Date: Sat Jul 05 2003 - 21:40:13 GMT-3
What problem would it create if the dialer idle-timeout is 0?
If you omit the dialer-list and/or dialer-group the router will not be
able to initiate a call as expected but the router will drop every call
in 120 seconds due to the fact that there is no interesting traffic. The
dialer idle-timeout will need to be set to 0 to stop the router from
dropping the call due to the lack of interesting traffic.
Brian Dennis, CCIE #2210 (R&S/ISP-Dial/Security)
-----Original Message-----
From: SHARMA,MOHIT (HP-Germany,ex1) [mailto:mohit.sharma@hp.com]
Sent: Saturday, July 05, 2003 4:05 PM
To: 'Brian Dennis'; 'Volkov, Dmitry (IDS Canada)';
ccielab@groupstudy.com
Subject: RE: Legacy DDR with ISDN callback - how to restrict server to
initiate e the call ?
Hi Brian,
If you set the dialer idle-timeout to 0, how will it work when it gives
a
callback? would'nt it create problems???
Will it not work just by omitting the dialer-group/list command?
On the other hand when you do not specify the intersting traffic, what
will
reset the idle-timeout during th callback call????
-----Original Message-----
From: Brian Dennis [mailto:brian@labforge.com]
Sent: Sunday, July 06, 2003 12:34 AM
To: 'Volkov, Dmitry (IDS Canada)'; ccielab@groupstudy.com
Subject: RE: Legacy DDR with ISDN callback - how to restrict server to
initiate e the call ?
On the callback server set the dialer idle-timeout to 0 and do not
configure a dialer-list and/or dialer-group. This way the callback
server can never initiate a call or drop a call due to the lack of
interesting traffic.
Brian Dennis, CCIE #2210 (R&S/ISP-Dial/Security)
-----Original Message-----
From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf Of
Volkov, Dmitry (IDS Canada)
Sent: Saturday, July 05, 2003 3:08 PM
To: 'ccielab@groupstudy.com'
Subject: Legacy DDR with ISDN callback - how to restrict server to
initiat e the call ?
Old problem, I checked archives, No result :(
R2 - callback client; R3 callback server; Legacy DDR. Callback works
fine.
No AAA server.
Question: How to prevent R3 to do first call to R2 and to keep callback
client/server setup ?
One possible solution - to remove "dialer-group"
statement from R3 and to put very high "dialer idle-timeout " - this is
ugly.
If I remove dial-string from dialer map on R3 it will never call back.
How
to tell R3 required string to call back in this case ?
username r3 password 0 cisco
R2#
interface BRI1/0
ip address 133.33.23.2 255.255.255.252
encapsulation ppp
dialer map ip 133.33.23.1 name r3 broadcast 5550131
dialer load-threshold 2 either
dialer-group 1
isdn switch-type basic-ni
isdn spid1 42255501210101 5550121
isdn spid2 42255501220101 5550122
no cdp enable
ppp callback request
ppp authentication chap callin
ppp multilink
end
username r2 password 0 cisco
R3#
interface BRI0
ip address 133.33.23.1 255.255.255.252
encapsulation ppp
dialer map ip 133.33.23.2 name r2 class test broadcast 5550121
dialer-group 1
isdn switch-type basic-ni
isdn spid1 42255501310101 5550131
isdn spid2 42255501320101 5550132
no cdp enable
ppp callback accept
ppp authentication chap callin
ppp multilink
end
!
map-class dialer test
dialer callback-server username
This archive was generated by hypermail 2.1.4 : Wed Aug 06 2003 - 06:52:25 GMT-3