Setting Up A Third-Party Radius Server - AudioCodes Mediant 4000 SBC User Manual

CHAPTER 16 Services
When RADIUS authentication is used, the RADIUS server stores the user accounts - usernames,
passwords, and access levels (authorization). When a management user (client) tries to access
the device, the device sends the RADIUS server the user's username and password for
authentication. The RADIUS server replies with an acceptance or a rejection notification. During
the RADIUS authentication process, the device's Web interface is blocked until an acceptance
response is received from the RADIUS server. Communication between the device and the
RADIUS server is done using a shared secret, which is not transmitted over the network.
To implement RADIUS, you need to do the following:
■ Set up a RADIUS server (third-party) to communicate with the device - see
Party RADIUS Server
■ Configure the device as a RADIUS client for communication with the RADIUS server - see
Configuring RADIUS Authentication

Setting Up a Third-Party RADIUS Server

The following procedure provides an example for setting up a third- party RADIUS sever,
FreeRADIUS which can be downloaded from www.freeradius.org. Follow the instructions on this
Web site for installing and configuring the server. If you use a RADIUS server from a different
vendor, refer to its appropriate documentation.
➢
To set up a third-party RADIUS server (e.g., FreeRADIUS):
1. Define the device as an authorized client of the RADIUS server, with the following:
● Predefined shared secret (password used to secure communication between the device
and the RADIUS server)
● Vendor ID (configured on the device in
Below is an example of the clients.conf file (FreeRADIUS client configuration):
#
# clients.conf - client configuration directives
#
client 10.31.4.47 {
secret
shortname
}
Configuring the RADIUS Vendor
= FutureRADIUS
= audc_device
- 212 -
Mediant 4000 SBC | User's Manual
Setting Up a Third-
ID)