Polycom RMX 1500 Administrator's Manual page 866

Polycom RMX 1500/2000/4000 Getting Started Guide
The Conference Summary Record
C-2
The MCU sends the entire CDR file via API or HTTP, and the RMX or
external application does the processing and sorting. The RMX ignores
events that it does not recognize, that is, events written in a higher version
that do not exist in the current version. Therefore, to enable compatibility
between versions, instead of adding new fields to existing events, new
fields are added as separate events, so as not to affect the events from
older versions. This allows users with lower versions to retrieve CDR files
that were created in higher versions.
This appendix describes the fields and values in the unformatted CDR records.
Although the formatted files contain basically the same information, in a few
instances a single field in the unformatted file is converted to multiple lines in the
formatted file, and in other cases, multiple fields in the unformatted file are
combined into one line in the formatted file.
In addition, to enable compatibility for applications that were written for the MGC
family, the unformatted file contains fields that were supported by the MGC
family, but are not supported by the RMX, whereas these fields are omitted from
the formatted file.
The conference summary record (the first record in the unformatted CDR
file) contains the following fields:
Table C-1 Conference Summary Record Fields
Field
File Version
Conference Routing
Name
Internal Conference ID
Reserved Start Time
Reserved Duration
Actual Start Time
Description
The version of the CDR utility that created the file.
The Routing Name of the conference.
The conference identification number as assigned by
the system.
Not supported.
Contains the same value as the Actual Start Time
field.
The amount of time the conference was scheduled to
last.
The actual time the conference started in local time.