AudioCodes E-SBC User Manual

CHAPTER57 Reporting Information to External Party
Mediant 1000 Gateway & E-SBC | User's Manual
Field Description
Coder
Transcoding
[635]
Displays whether there was coder transcoding for the SBC call. The field is a
string:
■ "TRANSCODING"
■ "NO_TRANSCODING"
Note:
■ The field is optional and can be included in the CDR using the SBC CDR
Format table.
■ The field is applicable only to "MEDIA_END" CDR Report Types.
■ The field is applicable only to SBC media CDRs.
■ The field is applicable only to Syslog and RADIUS.
■ The maximum number of characters for Syslog tabular alignment is 17.
Customizing CDRs for Gateway Calls
The Gateway CDR Format table lets you configure CDR customization rules for Gateway-related
CDRs that are generated by the device for the following:
■ CDRs (media and SIP signaling) sent in Syslog messages. For CDRs sent in Syslog
messages, you can customize the name of CDR fields. 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 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 40 RADIUS-
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
CDR fields. You can configure up to 64 locally-stored CDR customization rules. For more
information on local storage of CDRs, 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 page975.
If you do not configure a CDR customization rule for a specific CDR, the device generates the
CDR in a predefined 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.
● To view Gateway CDRs in the Web interface, see Viewing Gateway CDR History
on page957.
● 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.
● To customize CDRs for Test Calls, use the SBC CDR Format table (see
Customizing CDRs for SBC Calls and Test Calls on page1020).
- 1015 -

AudioCodes E-SBC Specifications

General

Brand	AudioCodes
Model	E-SBC
Category	Gateway
Language	English