Version 7.2 843 Mediant 1000B Gateway & E-SBC
User's Manual 54. Reporting Information to External Party
"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:
Figure 54-3: CDR Types for SBC Signaling
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)
Call originator (Orig CDR field) - indicates the call direction (caller)
Call duration (Durat CDR field) - call duration (elapsed time) from call connect
Call time is based on SetupTime, ConnectTime and ReleaseTime CDR fields
Table 54-2: Default CDR Fields for SBC Signaling
CDR Field Description CDR Report Type
(SBCReportType)
Format
SBCReportType
Report type:
"CALL_START": CDR sent upon an
INVITE message.
"CALL_CONNECT": CDR sent upon a
200 OK response.
"CALL_END": CDR sent upon a BYE
message.
"DIALOG_START"
"DIALOG_END"
- String
EPTyp
Endpoint type: "SBC" All String
SIPMethod
SIP message type All String (up to
10
characters)
SIPCallId
Unique ID of call All String (up to
50
characters)