CHAPTER16 Services
Mediant 1000 Gateway & E-SBC | User's Manual
#
# clients.conf - client configuration directives
#
client 10.31.4.47 {
secret = FutureRADIUS
shortname = audc_device
}
2. If access levels are required, set up a Vendor-Specific Attributes (VSA) dictionary for the
RADIUS server and select an attribute ID that represents each user's access level. The
example below shows a dictionary file for FreeRADIUS that defines the attribute "ACL-Auth-
Level" with "ID=35". For the device's user access levels and their corresponding numeric
representation in RADIUS servers, see Configuring Management User Accounts.
#
# AudioCodes VSA dictionary
#
VENDOR AudioCodes 5003
ATTRIBUTE ACL-Auth-Level 35 integer AudioCodes
VALUE ACL-Auth-Level ACL-Auth-UserLevel 50
VALUE ACL-Auth-Level ACL-Auth-AdminLevel 100
VALUE ACL-Auth-Level ACL-Auth-SecurityAdminLevel 200
3. Define the list of users authorized to use the device, using one of the password authentication
methods supported by the server implementation. The example below shows a user
configuration file for FreeRADIUS using a plain-text password:
# users - local user configuration database
john Auth-Type := Local, User-Password == "qwerty"
Service-Type = Login-User,
ACL-Auth-Level = ACL-Auth-SecurityAdminLevel
sue Auth-Type := Local, User-Password == "123456"
Service-Type = Login-User,
ACL-Auth-Level = ACL-Auth-UserLevel
4. Record and retain the IP address, port number, shared secret code, vendor ID, and VSA
access level identifier (if access levels are implemented) used by the RADIUS server.
Configuring RADIUS-based User Authentication
The following procedure describes how to configure RADIUS-based login authentication. For a
detailed description of the RADIUS parameters, see RADIUS Parameters.
➢ To configure RADIUS-based login authentication:
1. Open the Authentication Server page (Setup menu > Administration tab > Web & CLI folder
> Authentication Server).
2. From the 'Use RADIUS for Web/Telnet Login' drop-down list, select Enable to enable
RADIUS authentication for Web and Telnet login:
3. When implementing Web user access levels, do one of the following:
- 207 -