Storing Cdrs On The Device - AudioCodes Mediant 1000B User Manual

User's Manual
Note:
•
If you do not configure an IP address for a CDR server, the device sends CDRs to
the Syslog server, as configured in 'Enabling Syslog' on page 848.
•
The device sends CDRs only for dialog-initiating INVITE messages (call start), 200
OK responses (call connect) and BYE messages (call end). For SBC calls only: If
you want to enable the generation of CDRs for non-call SIP dialogs (such as
SUBSCRIBE, OPTIONS, and REGISTER), use the EnableNonCallCdr parameter.

51.2.5 Storing CDRs on the Device

The CDRs of Gateway and SBC calls generated by the device can also be stored locally
on the device (RAM).
Note:
You can specify the calls (configuration entities) for which you wish to create and store
CDRs locally. This is done using Logging Filter rules in the Logging Filters table. For
example, you can configure a rule to create CDRs for traffic belonging only to IP Group 2
and store the CDRs locally.
The CDRs are saved in a comma-separated values file (*.csv), where each CDR is shown
on a dedicated row. An example of a CSV file with two CDRs are shown below:

CSV file viewed in Excel:

CSV file viewed in a text editor (Notepad):
To view the CDR column headers corresponding to the CDR data in the CSV file, run the
following CLI command:

SBC CDRs:
(config-system)# cdr
(cdr)# cdr-format show-title local-storage-sbc
session id,report type,call duration, call end time, call
connect time,call start time, call originator, termination
reason, call id, srce uri, dest uri

Gateway CDRs:
(config-system)# cdr
(cdr)# cdr-format show-title local-storage-gw
Note:
device removes the extra characters.
You can do the following with locally saved CDR files (*.csv), through the CLI (root menu):
Version 7.0
When the device is reset or powered off, stored CDRs are deleted..
Each CDR can contain up to 1023 characters. If it contains more than this, the
51. Reporting Information to External Party
825 Mediant 1000B Gateway and E- SBC