RE: interesting traffic on server (isdn callback)

From: Michael Snyder (msnyder@revolutioncomputer.com)
Date: Sun Feb 08 2004 - 13:15:51 GMT-3


I've had problems without the dialer-group or at least a dialer watch
commands in the bri configs. When I don't need it I normally put a
dialer-list 1 protocol ip deny.

Is there a difference between not having, and denying everything with
it?

At one time I thought there was, and haven't reexamined it since.

BTW, someone posted the isdn rollover delay 1 command a few weeks back.
Thank you. You would not believe how I fought with my damn routers
getting multiline dialback to work. I added that command and life is
good.

Speaking of timing with callback, what timing settings do you use?
Carrier wait of 2 on one side, and (can't think of it right now) of 4 on
the other side?
    

-----Original Message-----
From: Dmitry Volkov [mailto:dmitry.volkov@rogers.com]
Sent: Sunday, February 08, 2004 9:28 AM
To: security@groupstudy.com
Subject: interesting traffic on server (isdn callback)

Group,

when we configure isdn callback - what is the common sense/opinion about
"dialer-group" & "dialer idle-timeout" commands
on Server ?

I'm asking NOT about real world but about different lab exercises we all
doing in out test environment targeting to pass lab test.

My logic - since server usually doesn't suppose to call client (only
callback) so server doesn't need "dialer-group" at all and need "dialer
idle-timeout 0"
It's duty of client to maintain / break call.

Does anybody have different opinion / approach ?

Thanks,
Dmitry



This archive was generated by hypermail 2.1.4 : Fri Mar 05 2004 - 07:13:47 GMT-3