Configuring Cdr Reporting - AudioCodes Mediant 4000 SBC User Manual

Hide thumbs Also See for Mediant 4000 SBC:
Table of Contents

Advertisement

Parameter
RADIUS Attribute Type
radius-type
[SBCCDRFormat_RadiusType]
RADIUS Attribute ID
radius-id
[SBCCDRFormat_RadiusID]

49.2.3 Configuring CDR Reporting

To enable and configure CDR reporting, follow the procedure below. For detailed
descriptions of the parameters, see ''Syslog, CDR and Debug Parameters'' on page 742.
To configure CDR reporting:
1.
Enable the Syslog feature for sending log messages generated by the device to a
collecting log message server. For more information, see ''Enabling Syslog'' on page
687.
2.
Open the Call Detail Record Settings page (Troubleshoot menu > Troubleshoot tab
User's Manual
The parameter's value is case-sensitive. For example, if you
want the CDR field name to be Phone-Duration, you must
configure the parameter to "Phone-Duration" (i.e., upper case "P"
and "D").
Defines whether the RADIUS Attribute of the CDR field is a standard
or vendor-specific attribute.
[0] Standard = (Default) For standard RADIUS Attributes.
[1] Vendor Specific = For vendor-specific RADIUS Attributes
(VSA).
Note: The parameter is applicable only for RADIUS accounting (i.e.,
'CDR Type' parameter configured to RADIUS SBC).
Defines an ID for the RADIUS Attribute. For VSAs, this represents
the VSA ID; for standard Attributes, this represents the Attribute ID
(first byte of the Attribute).
The valid value is 0 to 255 (one byte). The default is 0.
Note:
The parameter is applicable only for RADIUS accounting (i.e.,
'CDR Type' parameter configured to RADIUS SBC).
For VSA's (i.e., 'RADIUS Attribute Type' parameter configured to
Vendor Specific), the parameter must be configured to any
value other than 0.
For standard RADIUS Attributes (i.e., 'RADIUS Attribute Type'
parameter configured to Standard), the value must be a
"known" RADIUS ID (per RFC for RADIUS). However, if you
configure the ID to 0 (default) for any of the RADIUS Attributes
(configured in the 'Column Type' parameter) listed below and
then apply your rule (Click Apply), the device automatically
replaces the value with the RADIUS Attribute's ID according to
the RFC:
Destination Username: 30
Source Username: 31
Accounting Status Type: 40
Local Input Octets: 42
Local Output Octets: 43
Call Duration: 46
Local Input Packets: 47
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.
664
Mediant 4000 SBC
Description
Document #: LTRT-41729

Advertisement

Table of Contents
loading

Table of Contents