Radius-Based Services; Enabling Radius Services; Configuring Radius Servers - AudioCodes Mediant 1000B User Manual

15.2

RADIUS-based Services

The device supports Remote Authentication Dial In User Service (RADIUS), by acting as a
RADIUS client. You can use RADIUS for the following:

Authentication and authorization of management users (login username and
password) to gain access to the device's management interface.

Accounting where the device sends accounting data of SIP calls as call detail records
(CDR) to a RADIUS Accounting server (for third-party billing purposes).

15.2.1 Enabling RADIUS Services

Before you can implement any RADIUS services, you must enable the RADIUS feature, as
described in the procedure below.

To enable RADIUS:
1. Open the Authentication Settings page (Configuration tab > System menu >
Management > Authentication Settings).
2. From the 'Enable RADIUS Access Control' drop-down list, select Enable.
3. Click Submit, and then reset the device with a burn-to-flash for your settings to take
effect.

15.2.2 Configuring RADIUS Servers

The RADIUS Servers table lets you configure up to three RADIUS servers. The RADIUS
servers can be used for RADIUS-based management-user login authentication and/or
RADIUS-based accounting (sending of SIP CDRs to the RADIUS server).
When multiple RADIUS servers are configured, RADIUS server redundancy can be
implemented. When the primary RADIUS server is down, the device sends a RADIUS
request twice (one retransmission) and if both fail (i.e., no response), the device considers
the server as down and attempts to send requests to the next server. The device continues
sending RADIUS requests to the redundant RADIUS server even if the primary server
returns to service later on. However, if a device reset occurs, the device sends RADIUS
requests to the primary RADIUS server. By default, the device waits for up to two seconds
(i.e., timeout) for a response from the RADIUS server for RADIUS requests and
retransmission before it considers the server as down.
For each RADIUS server, the IP address, port, and shared secret can be configured. Each
RADIUS server can be defined for RADIUS-based login authentication and/or RADIUS-
based accounting. By setting the relevant port (authentication or accounting) to "0" disables
the corresponding functionality. If both ports are configured, the RADIUS server is used for
authentication and accounting. All servers configured with non-zero Authorization ports
form an Authorization redundancy group and the device sends authorization requests to
one of them, depending on their availability. All servers configured with non-zero
Accounting ports form an Accounting redundancy group and the device sends accounting
CDRs to one of them, depending on their availability. Below are example configurations:

Only one RADIUS server is configured and used for authorization and accounting
purposes (no redundancy). Therefore, both the Authorization and Accounting ports are
defined.
User's Manual
Figure 15-6: Enabling RADIUS
222
Mediant 1000B Gateway and E- SBC
Document #: LTRT-27044