User's Manual 986 Document #: LTRT-10632
Mediant 800B Gateway & E-SBC
CDR Field Title
Q.850 protocol termination reason (0-127).
PstnTermReason
Remote IP address of the incoming RTP stream
that the device "latched" on to as a result of the
RTP latching mechanism for NAT traversal.
LatchedRtpIp
Latching of a new T.38 stream - new IP address
LatchedT38Ip
63.2.2 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. The table lets you 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. The table lets you configure up to 40 RADIUS-accounting CDR customization
rules. For more information on RADIUS accounting, see 'Configuring RADIUS
Accounting' on page
998.
CDRs stored locally on the device. For local storage of CDRs, you can customize the
name of CDR fields. The table lets you configure up to 64 locally-stored CDR
customization rules. For more information on local storage of CDRs, see 'Storing
CDRs on the Device' on page
995.
If you do not configure a CDR customization rule for a specific CDR, the device generates
the CDR in a default CDR format (see 'CDR Field Description' on page 966).
Note:
• 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.
The following procedure describes how to customize Gateway CDRs through the Web
interface. You can also configure it through ini file (GWCDRFormat) or CLI (configure
troubleshoot > cdr > cdr-format gw-cdr-format).
To customize Gateway CDRs:
1. Open the Gateway CDR Format table (Troubleshoot menu > Troubleshoot tab >
Call Detail Record folder > Gateway CDR Format).
To Next Page
Loading...
Need help?
General
