From: Daniel Free (danrose111@earthlink.net)
Date: Wed Jun 04 2003 - 05:53:15 GMT-3
Hi,
The following is from the same Cisco page as:
>Dialer callback-secure
>To enable callback security, use the dialer callback-secure interface
>configuration command. Use the no form of this command to disable callback
>security.
Usage Guidelines
This command affects those users that are not authorized to be called back
with the dialer callback-server command. If the username (hostname in the
dialer map command) is not authorized for callback, the call will be
disconnected if the dialer callback-secure command is configured. If the
dialer callback-secure command is not configured, the call will not be
disconnected. In either case, callback has not occurred.
Example
The following partial example configures BRI0 with the commands required to
make it function as the callback server on the shared network. Callback
security is enabled on BRI0, such that any user other than atlanta will be
disconnected and not called back.
interface BRI0
ip address 171.1.1.9 255.255.255.0
encapsulation ppp
dialer callback-secure
dialer enable-timeout 2
dialer map ip 171.1.1.8 name atlanta class dial1 81012345678901
dialer-group 1
ppp callback accept
ppp authentication chap
!
map-class dialer dial1
dialer callback-server username
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
So with the dialer callback-secure configured this router will only callback
a
router called atlanta. If a router named newyork called this router it would
not
accept it and immediately disconnect the call. Without the callback-secure
command
configured if a router named newyork called this router it would not
immediately
disconnect the call however it still would not callback the router named
newyork.
Either way in the above config only a router named atlanta would receive a
callback.
Callback-secure is only configured on the callback server.
For the second part of your question:
>I am tasked with "validating calling router using CallerID". Would this
>accomplish this? Could someone dummy up the this command?
I am not too familiar with CallerID but the following is from CCO and would
tend to believe that this method would be better than callback-secure for
what
you have been tasked to accomplish.
How It Works
ISDN caller ID callback allows great flexibility for you to define which
calls to accept, which to deny, and which calls to reject initially but for
which the router should initiate callback. The feature works by using
existing ISDN caller ID screening, which matches the number in the incoming
call against numbers configured on the router, determining the best match
for number in the incoming call, and then, if configured, initiating
callback to the number configured on the router.
When a call is received, the entire list of configured numbers is checked
and the configuration of the best match number determines the action:
If the incoming number is best matched by a number that is configured for
callback, then the incoming call is rejected and callback is initiated.
If the incoming number is best matched by another entry in the list of
configured numbers, the call is accepted.
If the incoming number does not match any entry in the configured list, the
call is rejected and no callback is started.
Best of luck.
Danny
----- Original Message -----
From: "Jason Cash" <cash2001@swbell.net>
To: <ccielab@groupstudy.com>
Sent: Tuesday, June 03, 2003 7:57 PM
Subject: ISDN - callback-secure
> What exactly does this command do? It is not thoroughly explained on
> Cisco's website:
>
>
>
> Dialer callback-secure
>
> To enable callback security, use the dialer callback-secure interface
> configuration command. Use the no form of this command to disable callback
> security.
>
>
>
> What is actually going on when this is enabled? Should it only be
config'd
> on the callback server?
>
>
>
> I am tasked with "validating calling router using CallerID". Would this
> accomplish this? Could someone dummy up the this command?
This archive was generated by hypermail 2.1.4 : Fri Jul 04 2003 - 11:10:52 GMT-3