This section describes the ASCII and streaming Call Detail Record (CDR) format.
Various Sonus elements such as GSX, PSX, NBS9000 and SBC use many of the same CDR fields. Because of this, some fields in the “Accounting Records” table below do not apply to SBC call details, but instead simply indicate pass-though type messages (for example, ISUP and PSTN fields).
Refer to the CDR Examples topic for example CDRs.
Refer to the CDR vs. VSA Fields topic for a mapping of CDR to Vendor Specific Attributes (VSAs) for RADIUS servers.
For more information on known limitations, refer to release notes at SBC Release Information.
Accounting File Version
The CAM version of SBC SW release V 04.00.00 is 80.00.00 (major CAM version is 80, minor CAM version is 0, special CAM version is 0). The associated hex format of the CAM file version is "00500000" as shown in below header example.
Sonus Networks, Inc.00000000FF600000500000000000000060V04.00.00 00000000000000000000000000000000000ACT2009010515113200000000000000.
Every event log file, including accounting logs, contains a file header.This header consists of a 128-character string terminated by a carriage return. Each field in the event log file header is defined in the following table:
ASCII OEM string, blank padded, (for example "Sonus Networks, Inc.")
Old CAM File Version. Always "FF".
Hex offset to the Event Log Type, or the number of bytes from the beginning of the record to the beginning of the Event Log Type field (in the above example, "60").
New CAM File Version. This value is 00500000, and consists of:
Hex offset to start of data. In this example, "0060".
SBC software revision. In this example, "V 04.00.00".
Event Log Type (same as file extension). In this example, "ACT".
File creation time.
Header terminator (carriage return)
The one line footer, below, is appended to each log file (including accounting logs) when the file is closed under controlled conditions.
DDMMYYYY HHMMSS: File administratively closed.
Controlled conditions include CLI commands (for example,
set oam eventLog
acct rolloverAction...) and automatic roll-overs when maximum file size is reached.
When an uncontrolled file closure occurs, such as an SBC switch-over or system failure, this footer may not be present.