An Overview of RADIUS on the IMG
Topic Location: Product Description > RADIUS
Overview
The IMG uses Remote Authentication Dial In User Service (RADIUS) for streaming the Call Detail Records (CDR). The implementation is compliant with RFC 2865 and RFC 2866. The RADIUS messages are sent to external RADIUS servers. The IMG RADIUS interface generates an ACCESS, a START & a STOP Request for the inbound leg and a START & STOP Request for the outbound leg of the call, as well as data associated with the INVITE, the 200 OK, the BYE and the CANCEL methods for those legs utilizing a SIP protocol.
Specifications
The IMG implementation of RADIUS is based on the following RADIUS RFCs: RFC 2865 - Remote Authentication
RFC 2866 - RADIUS Accounting
Formats
The IMG supports the Dialogic RADIUS formats, which Includes some attributes defined by RFC 2865 and RFC 2866, as well as Dialogic Vendor Specific Attributes (VSA).
Scenarios
The IMG supports RADIUS Authentication and Accounting. Users have the option of using one of the following scenarios:
Authentication and Accounting
In this case an Authentication Server and an Accounting Server are both assigned to the RADIUS client on the IMG.
Accounting only
In this case only an Accounting Server is assigned to the RADIUS client on the IMG.
Authentication only
In this case only an Authentication Server is assigned to the RADIUS client on the IMG.
See RADIUS Scenarios for more details.
As per RFC 2865 and RFC 2866, the IMG by default uses port 1812 for Authentication and port 1813 for Accounting. However, these ports are also configurable through the ClientView GUI. When implementing Authentication and Accounting, both processes can be either on the same or separate servers.
The RADIUS attributes and VSA’s included in the messages will vary based on the following:
Protocol Used
What leg of the call the protocol is used
Whether it is a TDM protocol (SS7 or ISDN) or IP protocol (SIP or H.323). The User name and Password values configured for the Authentication Server used will be included in the user name and password attributes in the Access Request message sent from the IMG.
1