CHAPTER 51 Reporting Information to External Party
●
Signaling CDRs: This CDR contains SIP signaling information. A typical SBC session
consists of two SBC legs. Each leg generates its own signaling CDRs. Each leg
generates three different CDR Report Types (CDRReportType), which are sent to the
CDR server at different stages of the SIP dialog:
◆
◆
◆
The CDR Report 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 and it may be based on the following CDR fields:
●
Leg ID
●
Source URI
●
Destination URI
●
Call originator (i.e., caller)
●
Call duration
●
Call time
The Syslog displays CDRs in tabular format, whereby the CDR field names are displayed on the
first lines and their corresponding values on the subsequent lines, as shown in the example below
of an SBC signaling CDR sent at the end of a normally terminated call:
[S=40] |CDRReportType |EPTyp |SIPCallId |SessionId |Orig |SourceIp |SourcePort
|DestIp |DestPort |TransportType |SrcURI |SrcURIBeforeMap |DstURI
Figure 51-1: SBC CDR Report Types for Media
"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)
Figure 51-2: CDR Report Types for SBC Signaling
- 769 -
Mediant 4000 SBC | User's Manual