Cdr Field Description; Cdr Fields For Sbc Signaling - AudioCodes Mediant 4000 SBC User Manual


RADIUS server. For CDR in RADIUS format, see ''Configuring RADIUS Accounting''
on page 750. To configure RADIUS servers for CDR reporting, see ''Configuring
RADIUS Servers'' on page 229.
Note: To view SBC CDRs stored on the device's memory, see Viewing SBC CDR
History on page 723.

52.2.1 CDR Field Description

This section describes the default CDR fields that are generated by the device.
Note: You can customize the default CDR fields if desired. For customizing SBC-
related CDRs, see Customizing CDRs for SBC Calls on page 743.

52.2.1.1 CDR Fields for SBC Signaling

The default CDR fields for SBC signaling are listed in the following table.
A typical SBC session consists of two SBC legs. Each leg generates its own signaling
CDRs. Each leg generates three different CDR types (SBCReportType), which are sent to
the CDR server at different stages of the SIP dialog:

"CALL_START": CDR is sent upon an INVITE message.

"CALL_CONNECT": CDR is sent upon a 200 OK response (i.e., call is established).

"CALL_END": CDR is sent upon a BYE message (i.e., call ends)
The CDR types for SBC signaling and the SIP dialog stages are shown in the following
figure:
CDRs belonging to the same SBC session (both legs) have the same Session ID
(SessionId CDR field). CDRs belonging to the same SBC leg have the same Leg ID (LegId
CDR field)
For billing applications, the CDR that is sent when the call ends (CALL_END) is usually
sufficient. Billing may be based on the following:

Leg ID (LegId CDR field)

Source URI (SrcURI CDR field)

Destination URI (DstURI CDR field)
User's Manual
Figure 52-3: CDR Types for SBC Signaling
734
Mediant 4000 SBC
Document #: LTRT-40203