AudioCodes Mediant 800B - CDR Fields for SBC Media

Version 7.2 971 Mediant 800B Gateway & E-SBC
User's Manual 63. Reporting Information to External Party
CDR Field Description CDR Report Type
(SBCReportType)
Format
SipTermDesc
Description of SIP termination
reason:
 SIP Reason header, if exists, for
example: SIP ;cause=200
;text="Call completed
elsewhere".
 If no SIP Reason header exists,
the description is taken from the
reason text, if exists, of the SIP
response code, for example:
"417 Unknown Resource-
Priority".
 If no reason text exists in the SIP
response code, the description is
taken from an internal SIP
response mapping mechanism.
For example, if the device
receives a SIP response "422", it
sends in the CDR "422 Session
Interval Too Small method" as
the description.
"CALL_END" String (up to 26
characters)
Caller
Name of caller All String (up to 36
characters)
Callee
Name of called party All String (up to 36
characters)
Below shows an example of an SBC signaling CDR sent at the end of a call (call was
terminated normally):
[S=40] |SBCReportType |EPTyp |SIPCallId |SessionId |Orig |SourceIp
|SourcePort |DestIp |DestPort |TransportType |SrcURI
|SrcURIBeforeMap |DstURI |DstURIBeforeMap |Durat |TrmSd |TrmReason
|TrmReasonCategory |SetupTime |ConnectTime |ReleaseTime
|RedirectReason |RedirectURINum |RedirectURINumBeforeMap
|TxSigIPDiffServ|IPGroup (description) |SrdId (name)
|SIPInterfaceId |ProxySetId |IpProfileId (name) |MediaRealmId
(name) |DirectMedia |SIPTrmReason |SIPTermDesc |Caller |Callee
[S=41] |CALL_END |SBC |20767593291410201017029@10.33.45.80
|1871197419|LCL |10.33.45.80 |5060 |10.33.45.72 |5060 |UDP
|9001@10.8.8.10 |9001@10.8.8.10 |6001@10.33.45.80
|6001@10.33.45.80 |15 |LCL |GWAPP_NORMAL_CALL_CLEAR
|NORMAL_CALL_CLEAR |17:00:29.954 UTC Thu Oct 14 2014
|17:00:49.052 UTC Thu Oct 14 2014 |17:01:04.953 UTC Thu Oct 14
2014 |-1 | | |40 |1 |0 (SRD_GW) |1 |1 |1 () |0 (MR_1) |no |BYE
|Q.850 ;cause=16 ;text="loc |user 9928019 |
63.2.1.2 CDR Fields for SBC Media
The default CDR fields for SBC media are listed in the following table. The media CDRs
are published for each active media stream, thereby allowing multiple media CDRs, where
each media CDR has a unique call ID corresponding to the signaling CDR.