Call Detail Record - AudioCodes Mediant 2000 User Manual

SIP User's Manual
Attribute Attribute
Number Name
Acct-Output-
48
Packets
NAS-Port-
61
Type
Response Attributes
H323-
26 Return-
Code
Acct-
44
Session-ID
Below is an example of RADIUS Accounting, where the non-standard parameters are
preceded with brackets.
Accounting-Request (361)
user-name = 111
acct-session-id = 1
nas-ip-address = 212.179.22.213
nas-port-type = 0
acct-status-type = 2
acct-input-octets = 4841
acct-output-octets = 8800
acct-session-time = 1
acct-input-packets = 122
acct-output-packets = 220
called-station-id = 201
calling-station-id = 202
// Accounting non-standard parameters:
(4923 33) h323-gw-id =
(4923 23) h323-remote-address = 212.179.22.214
(4923 1) h323-ivr-out = h323-incoming-conf-id:02102944 600a1899
3fd61009 0e2f3cc5
(4923 30) h323-disconnect-cause = 22 (0x16)
(4923 27) h323-call-type = VOIP
(4923 26) h323-call-origin = Originate
(4923 24) h323-conf-id = 02102944 600a1899 3fd61009 0e2f3cc5
7.11

Call Detail Record

The Call Detail Record (CDR) contains vital statistic information on calls made by the
device. CDRs are generated at the end and (optionally) at the beginning of each call
(determined by the parameter CDRReportLevel), and then sent to a Syslog server. The
destination IP address for CDR logs is determined by the parameter CDRSyslogServerIP.
For CDR in RADIUS format, refer to ''Supported RADIUS Attributes'' on page 362.
The following table lists the CDR fields that are supported.
Version 5.6
VSA
Purpose
No.
Number of packets sent
during the call
Physical port type of
device on which the call is
active
The reason for failing
103 authentication (0 = ok,
other number failed)
A unique accounting
identifier – match start &
stop
365
7. IP Telephony Capabilities
Value
Example
Format
Numeric
0:
String
Asynchronous
0 Request
Numeric
accepted
String
November 2008
1
AAA
Stop
Acc
Start
Acc
Stop
Acc
Stop
Acc
Stop
Acc