RADIUS Servers

The IMG 2020 can be configured to communicate with multiple RADIUS Servers (Remote Authentication Dial In User Service) for generating inbound ACCESS, START, and STOP Requests and outbound START and STOP requests used for authentication and accounting (RFC 2865 and RFC 2866). To configure IMG 2020 to communicate with an external RADIUS server the RADIUS Servers and RADIUS Server objects must be configured. The RADIUS Servers object is created as a container or parent object to each of the individual external RADIUS servers that are in your network. To create the RADIUS Servers object, right click on External Network Elements object and select New Radius Servers. Once the Radius Servers object is created then the RADIUS Server object can be created. See below on information on how to configure the RADIUS Servers object.

Web GUI Page

Dialogic > External Network Elements > New Radius Servers

Maximum Objects

One Radius Servers object per External Network Elements object

Related Topics and Dependencies

The Radius Servers object is a parent or container which will have multiple RADIUS Server objects configured under it. Each RADIUS Server object is considered an external RADIUS server. Once the RADIUS Servers and RADIUS Server objects have been configured, the IMG 2020 can then be configured to be a Client of each of these external RADIUS servers. See RADIUS Client link.

RADIUS Server

RADIUS Client

IMG 1010 - RADIUS - Overview

Configuring Free Radius on Linux

Field Descriptions

Nothing needs to be configured in the RADIUS Servers object. The fields in the RADIUS Servers object are for monitoring only. Below is description of each.

Authentication Servers Configured - Number of external AUTHENTICATION RADIUS Servers configured to communicate with the IMG 2020.

Accounting Servers Configured - Number of external ACCOUNTING RADIUS Servers configured to communicate with IMG 2020

Return to Documentation Home I Return to Sangoma Support