From: Mas Kato (tealp729@xxxxxxxx)
Date: Sat May 19 2001 - 19:49:30 GMT-3
Mohamed,
>From what I've seen, step #3 (server authenticates client) in the
article referenced by that URL is needed so the callback server can pick
the right dialer map to call back on. So somehow, the authenticated user
needs to be mapped to a dial string in such a way it meets your
requirement of the server never initiating the dial.
One way might be to include the dial string on the dialer map back to
the client, make everything uninteresting and disable the dialer
idle-timeout.
Or, check this out:
R2(config)#username r1 ?
access-class Restrict access by access-class
autocommand Automatically issue a command after the user logs
in
callback-dialstring Callback dialstring
callback-line Associate a specific line with this callback
callback-rotary Associate a rotary group with this callback
dnis Do not require password when obtained via DNIS
nocallback-verify Do not require authentication after callback
noescape Prevent the user from using an escape character
nohangup Do not disconnect after an automatic command
nopassword No password is required for the user to log in
password Specify the password for the user
privilege Set user privilege level
<cr>
See anything you could use instead of placing the dial string on the
dialer map? ;-)
Regarding 'callback dialstring,' according to the docs, in order to get
the 'dialer callback-server dialstring' command to work, the calling
number must be available during the callback negotiation phase. I always
thought the calling number (caller ID) was available with ISDN, but
apparently it was an additional call offering (ACO) in those limited
circumstances where I had the opportunity to test this feature. In other
words, I've never been able to get this feature to work either--in my
lab or with real ISDN lines. I've never seen the calling number in the
debugs...
I would imagine if the calling number were picked up during the callback
negotiation, you wouldn't need the dial string on the server's dialer
map, etc.
Regards,
Mas
-----Original Message-----
From: nobody@groupstudy.com [mailto:nobody@groupstudy.com]On Behalf Of
Clifton Stewart
Sent: Saturday, May 19, 2001 3:27 AM
To: MAHeeba@itqan.co.ae
Cc: ccielab@groupstudy.com
Subject: callback
MaHeeba,
Here is a good url.
http://www.cisco.com/warp/public/793/access_dial/isdn-ppp-callback.html
<=== Watch the wordwrap
-Cliff
>--- Original Message ---
>From: Mohamed Heeba <MAHeeba@itqan.co.ae>
>To: "'ccielab@groupstudy.com'" <ccielab@groupstudy.com>
>Date: 5/19/01 2:23:14 AM
>
>guys ;
>notice this configuration provided for callback for ISDN
>this config will allow the server router to initiate calls to
the client
>,suppose this is not required
>ie only the server the router should call the client when the
client send a
>request .
>
>IS THERE ANYWAY TO DO THIS ? AND WHEN WE CAN USE THE USERNAME
>CALLBACK-DAILERSTRING ????
>
>thx in advance
>
>
>
>
>client router
>
>Username r2 pass cisco
>Int bri 0
>Ppp callback request
>Dialer map ip 10.1.1.1 name r2 broadcast 6733097
>ppp auth chap
>dialer-group 1
>!
>dialer-list 1 pro ip permit
>
>server router
>R2
>Usernmae r1 pass cisco
>Int bri 0
>Ppp callback accept
>Ppp callback-secure
>Dialer map ip 10.1.1.2 name r1 class dial1 broadcast 6714207
>ppp auth chap
>dialer-group 1
>!
>dialer-list 1 pro ip permit
>map-calss dialer dial1
>dialer callback-server username
>**Please read:http://www.groupstudy.com/list/posting.html
**Please read:http://www.groupstudy.com/list/posting.html
**Please read:http://www.groupstudy.com/list/posting.html
This archive was generated by hypermail 2.1.4 : Thu Jun 13 2002 - 10:30:45 GMT-3