Customizing Cdrs For Sbc Calls - AudioCodes Mediant 3000 User Manual

User's Manual
Parameter
RADIUS Attribute Type
radius-type
[GWCDRFormat_Radius
Type]
RADIUS Attribute ID
radius-id
[GWCDRFormat_Radius
ID]

52.2.3 Customizing CDRs for SBC Calls

The SBC CDR Format table lets you customize SBC-related CDRs that are generated by
the device for the following:
Version 7.0
You can configure the name to be enclosed by apostrophes (single or
double). For example, if you want the CDR field name to appear as
'Phone Duration', you must configure the parameter to 'Phone Duration'.
You can also configure the CDR field name with an equals (=) sign, for
example "call-connect-time=".
Notes:

For RADIUS Attributes that do not require a prefix name, leave the
parameter undefined.

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 Gateway).
Defines an ID for the RADIUS Attribute. For vendor-specific Attributes,
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.
Notes:

The parameter is applicable only for RADIUS accounting (i.e., 'CDR
Type' parameter configured to RADIUS Gateway).

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
Add), the device automatically replaces the value with the RADIUS
Attribute's ID according to the RFC:

Destination Number: 30

Source Number: 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.
775
52. Reporting Information to External Party
Description
Mediant 3000