Chapter 18-The Call Detail Record (CDR) Utility
Polycom, Inc. 18-3
Multi-Part CDR Files
By default, the maximum CDR (Call Data Record) file size is limited to 1MB. When a CDR
file reaches a size of 1MB the file is saved and further call data recording is stopped and the
additional data is lost.
The RMX can be configured to keep recording the data in multiple CDR file set of 1MB each.
Multi-Part CDR ensures that conference call data from long duration or permanent
conferences is recorded and not lost.
Guidelines
• Multi-Part CDR is enabled by setting the value of the ENABLE_MULTI_PART_CDR
System Flag to YES.
The flag’s default value is NO.
When the flag value is NO, CDR file size is limited to one file of 1MB and further call
data recording is stopped.
To modify the default setting, the flag must be manually added to the System
Configuration. For more information see the RealPresence Collaboration Server (RMX)
1500/2000/4000 Administrator’s Guide, "Modifying System Flags” on page 22-1.
• If the flag value is set to YES, when a CDR file reaches 1MB, an additional CDR file is
created and added to the CDR file set for that conference.
•If the flag value is changed from YES to NO (or visa versa) all existing CDR files are
retained.
CDR File Contents
The general conference section or record contains information such as the Routing Name
and ID, and the conference starting date and time.
The event sections or records contain an event type heading or event type code, followed by
event data. For example, an event type may be that a participant connects to the conference,
and the event data will list the date and time the participant connects to the conference, the
participant name and ID, and the participant capabilities used to connect to the conference.
To enable compatibility for applications that written for the MGC family, the RealPresence
Collaboration Server CDR file structure is based on the MGC CDR file structure.
The unformatted and formatted text files contain basically the same information. The
following differences should be noted between the contents of the unformatted and
formatted text files:
• In many cases a formatted text file field contains a textual value, whereas the equivalent
unformatted file field contains a numeric value that represents the textual value.
• For reading clarity, in a few instances, a single field in the unformatted file is converted
to multiple fields in the formatted text file, and in other cases, multiple fields in the
unformatted file are combined into one field in the formatted file.
• To enable compatibility between MGC CDR files and RealPresence Collaboration
Server CDR files, the unformatted file contains fields that were applicable to the MGC
MCUs, but are not supported by the RealPresence Collaboration Server MCUs. These
fields are omitted from the formatted text file.