AudioCodes Mediant 4000 SBC User Manual page 748

example, you can configure a rule to create CDRs for traffic belonging only to IP Group 2
and store the CDRs locally.
The locally stored 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):
Figure 52-8: CSV File of CDRs in 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
You can do the following with locally saved CDR files (*.csv), through the CLI (root menu):

View stored CDR files:
•
View all stored CDR files:
# show storage-history
•
View all stored, unused CDR files:
# show storage-history unused

Delete stored CDR files:
•
Delete all stored files:
# clear storage-history cdr-storage-history all
•
Delete all stored, unused CDR files:
# clear storage-history cdr-storage-history unused

Save stored CDR files to an external destination:
# copy storage-history cdr-storage-history <filename> to
<protocol://destination>
Where:
•
filename: name you want to assign the file. Any file extension name can be used,
but as the file content is in CSV format, it is recommended to use the .csv file
extension.
•
protocol: protocol over which the file is sent (tftp, http, or https).
For example:
copy storage-history cdr-storage-history my_cdrs.csv to
tftp://company.com/cdrs
The following procedure describes how to configure local CDR storage through the Web
interface.
User's Manual 748
Mediant 4000 SBC
Document #: LTRT-40203