Managing Reports
Note:
For attended conferences, the system can be configured to automatically assign
Note:
conference IDs (see
manually assign IDs. For unattended conferences, the system automatically
assigns an ID.
How the System Manages Detail Records
The system offers two methods for saving CDR and CODR files—text files or a relational
database. For additional information on using the relational database method for detail records,
refer to the S6200/S6800 Media Server Relational Database Guide. The remainder of this
chapter will discuss using text files to manage detail records.
When using text files to manage detail records, the system saves the CDRs and CODRs it
generates each day to a single text file for each type of report. The system saves CDR files to
the /usr/dcb/cdr directory in the date.cdr format (Sep08.cdr) and CODR files to the /usr/dcb/
codr directory in the date.cod format (May08.cod).
The system stores CDR and CODR files in their default directories. The system saves 30 files,
automatically deleting the oldest file. The system does not delete CDR and CODR files stored
outside their default directories, so files can be saved for safekeeping outside the default
directories.
About CDR and CODR Formats
The system, by default, creates call and conference records including all available data field
values. The records are stored in their respective files in a raw tabular format without column
headings. The files can be copied to a remote host for further processing (e.g., formatted with a
text editor and imported into a spreadsheet).
included in CDRs and CODRs.
214 Administration and Maintenance of the S6200/S6800 Servers
System Configuration
Figure 17
on page 45), or operators can
shows the default order of data fields