Configuring Interactive Dial Requests

Configuring Interactive Dial RequestsConfiguring for Interactive Dial-Back

The following example sets the access server to a predefined phone number:

Local> CHANGE DIALER AT_HOME PORT 1-16 IDENT "DIALS YOU AT HOME"

The dialer service AT_HOME is set up to allow any phone number to be dialed, but the user’s security profile allows for a connection to be made using only one number.

The ports are all set up to be ACCESS DYNAMIC, so they can be used for dial-in and also dial-back.

The user dials in, enters his user name and password, and is successfully authenticated. As a result, the security component creates and maintains an authorization profile for this user. This authorization profile, which is also known as the active user database, contains among other things the phone number(s) that the user is authorized to use on a dial-back request.

Security Profile Information

For more information about user security profiles, see the user accounts information in the Determining Security Configuration section in Chapter 22.

Interactive Dial-Back (Dial Service) Example

The following example shows how the user specifies a dialer service and how the service operates:

Local> DIAL AT_HOME

Local -019- Dial request queued, will be attempted in 30 seconds

Local> LOGOUT

Local -020- Logged out port 10 on server NAS700

In this example, the access server uses a security realm (RADIUS, or local profile) for authorization when the user logs in. The user’s RADIUS/local profile is maintained while the user is logged in. The profile is checked to see if the user is authorized for dial-back. In this particular example, the authorization database has but a single phone number that the access server would use when calling back this particular user.

Managing Dial Services 21-15