Configuring Radius Accounting - AudioCodes Mediant 800B User Manual

User's Manual
59.3

Configuring RADIUS Accounting

The device can send accounting data of SIP calls as call detail records (CDR) to a RADIUS
Accounting server. CDR-based accounting messages can be sent upon call release, call
connection and release, or call setup and release. This section lists the CDR attributes for
RADIUS accounting.
The following figure shows the interface between the device and the RADIUS server,
based on the RADIUS Accounting protocol. For each CDR that the device sends to the
RADIUS server, it sends an Accounting-Request Stop with all the CDR attributes. When
the RADIUS server successfully receives all the CDR attributes, it responds with an
Accounting-Response Stop ACK message to the device. If the device does not receive the
Accounting-Response ACK message, it can resend the Accounting-Request Stop with all
CDR attributes again, up to a user-defined number of re-tries (see 'Configuring RADIUS
Packet Retransmission' on page 235).
There are two types of data that can be sent to the RADIUS server. The first type is the
accounting-related attributes and the second type is the vendor specific attributes (VSA):

Standard RADIUS attributes (per RFC): A typical standard RADIUS attribute is
shown below. The RADIUS attribute ID depends on the attribute.
The following figure shows a standard RADIUS attribute collected by Wireshark. The
bottom pane shows the RADIUS attribute information as sent in the packet; the upper
pane is Wireshark's interpretation of the RADIUS information in a more readable
format. The example shows the attribute in numeric format (32-bit number in 4 bytes).
Figure 59-13: Example of Standard RADIUS Attribute Collected by Wireshark

Vendor-specific RADIUS attributes: RADIUS attributes that are specific to the
Version 7.2
Figure 59-12: Typical Standard RADIUS Attribute
59. Reporting Information to External Party
915 Mediant 800B Gateway & E-SBC