AudioCodes Mediant 500 MSBR, Руководство пользователя

Страница: 887 / 1248

Version 7.2 887 Mediant 500 MSBR
User's Manual 61. Reporting Information to External Party
61.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:
Figure 61-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 61-2: Default CDR Fields for SBC Signaling
CDR Field Description CDR Report Type
(SBCReportType) Format
SBCReportT
ype Report type:

"CALL_START":
CDR sent upon an
INVITE message.

"CALL_CONNEC
T": CDR sent
upon a 200 OK
response.

"CALL_END":
CDR sent upon a
BYE message.
- String