CHAPTER57 Reporting Information to External Party
Mediant 1000 Gateway & E-SBC | User's Manual
Parameter Description
✔ 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.
Customizing CDRs for SBC Calls and Test Calls
The SBC CDR Format table lets you customize CDRs for SBC calls and CDRs for Test Calls that
are generated by the device for the following CDR types:
■ CDRs (media and SIP signaling) sent in Syslog messages. For CDRs sent in Syslog
messages, you can customize the name of the CDR field. You can configure up to 128 Syslog
CDR customization rules.
■ CDRs related to RADIUS accounting and sent in RADIUS accounting request messages. For
RADIUS accounting CDRs, you can customize the RADIUS Attribute's prefix name and
RADIUS Attribute's ID, for standard RADIUS Attributes and vendor-specific RADIUS
Attributes (VSA). For example, instead of the default VSA name, "h323-connect-time" with
RADIUS Attribute ID 28, you can change the name to "Call-Connect-Time" with ID 29. You
can configure up to 40RADIUS-accounting CDR customization rules. For more information on
RADIUS accounting, see Configuring RADIUS Accounting.
■ CDRs stored locally on the device. For local storage of CDRs, you can customize the name of
the CDR field. You can configure up to 64 locally-stored CDR customization rules. For more
information on storing CDRs on the device, see Storing CDRs on the Device.
■ CDRs (signaling only) sent to the REST server in JSON format using the device's REST API.
You can configure up to 64 JSON CDR customization rules. For more information on CDRs
and REST, see Configuring CDR Reporting to REST Server on page975.
If you do not configure a CDR customization rule for a specific CDR, the device generates the
CDR in a default CDR format. For a detailed description of all the fields that can be present in the
CDR (customized and default), see CDR Field Description.
● The following standard RADIUS Attributes cannot be customized: 1 through 6, 18
through 20, 22, 23, 27 through 29, 32, 34 through 39, 41, 44, 52, 53, 55, 60 through
85, 88, 90, and 91.
● If the RTCP XR feature is unavailable (not licensed or disabled), the R-factor VoIP
metrics are not provided in CDRs (CDR fields, Local R Factor and Remote R
Factor) generated by the device. Instead, these CDR fields are sent with the value
127, meaning that information is unavailable.
● Test Call CDRs include "CALL_START", "CALL_CONNECT" and "CALL_END"
CDR Report Types.
● To view historical CDRs that are stored on the devicesee Viewing CDR History of
SBC and Test Calls on page958.
The following procedure describes how to customize SBC and Test Call CDRs through the Web
interface. You can also configure it through ini file [SBCCDRFormat] or CLI ( configure
troubleshoot > cdr > cdr-format sbc-cdr-format).
- 1020 -
To Next Page
Loading...
Need help?
General
