From: John Matus (John.Matus@tokiom.com)
Date: Fri Nov 11 2005 - 20:58:15 GMT-3
tom,
'no dialer-group x' only negates the statement 'dialer-group x'. it does
not act like a 'deny' statement.
Regards,
John D. Matus
Technical Support / PAS
Fujitsu Consulting
626-568-7716
John.Matus@tokiom.com
Thomwin Chen
<thomwin_chen@yah
oo.com> To
Sent by: Montiean <noktes@bellsouth.net>,
nobody@groupstudy ccielab@groupstudy.com
.com cc
Subject
11/11/2005 03:49 Re: dialer-group under BRI
PM interface
Please respond to
Thomwin Chen
<thomwin_chen@yah
oo.com>
Montiean,
if the tasks ask about Legacy DDR you still need the remote side calling
number mapped to the remote IP.
and if another requirement says that this side can't initiate a call then
you should specify
: no dialer-group 1 <just for explicitness>
and to avoid disconnection from this called side, you need to specify
dialer idle-timeout 0
R2
int bri0/0
dialer map ip 12.12.12.1 name R1 broadcast 1111
no dialer-group 1 <just for explicitness>
dialer idle-timeout 0
please correct it if I'm wrong...
Rgds,
Thomwin
Montiean <noktes@bellsouth.net> wrote:
Folks,
Let say the question asking only one side to initiate the call so on
other site will just configure "dialer map" without remote isdn calling
number. This would be enough not to let the router call out.
However, in some solution guide from lab workbook use additional command
like " dialer-group" on the side that doesnot need to initiate the call. As
I know, dialer-group will use to screen the traffic to initiate the call. I
am not sure why we still need it as above scenario.
Any ideas?
Thanks,
Montiean
This archive was generated by hypermail 2.1.4 : Thu Dec 01 2005 - 09:12:06 GMT-3