AudioCodes Mediant 4000 SBC, User Manual

Page: 837 / 1037

CHAPTER 51 Reporting Information to External Party
Mediant 4000 SBC | User's Manual
Parameter Description
✔
Local Output Packets: 48
If you configure the value to 0 and the RADIUS Attribute is not any of
the ones listed above, the configuration is invalid.
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 ).
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).
- 804 -