19.08.2013 Views

RMX 2000 Administrator's Guide Version 7.6.1 - Polycom

RMX 2000 Administrator's Guide Version 7.6.1 - Polycom

RMX 2000 Administrator's Guide Version 7.6.1 - Polycom

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

Appendix C<br />

CDR Fields - Unformatted File<br />

The CDR (Call Detail Records) utility is used to retrieve conference information to a file. The<br />

CDR utility can retrieve conference information to a file in both formatted and unformatted<br />

formats.<br />

Unformatted CDR files contain multiple records. The first record in each file contains<br />

information about the conference in general, such as the conference name and start time. The<br />

remaining records each contain information about one event that occurred during the<br />

conference, such as a participant connecting to the conference, or a user extending the length<br />

of the conference. The first field in each record identifies the event type, and this is followed<br />

by values containing information about the event. The fields are separated by commas.<br />

Formatted files contain basically the same information as unformatted files, but with the<br />

field values replaced by descriptions. Formatted files are divided into sections, each<br />

containing information about one conference event. The first line in each section is a title<br />

describing the type of event, and this is followed by multiple lines, each containing<br />

information about the event in the form of a descriptive field name and value.<br />

The field names and values in the formatted file will appear in the language being used for the <strong>RMX</strong><br />

Web Client user interface at the time when the CDR information is retrieved.<br />

The value of the fields that support Unicode values, such as the info fields, will be stored in the CDR<br />

file in UTF8. The application that reads the CDR file must support Unicode.<br />

The MCU sends the entire CDR file via API or HTTP, and the <strong>RMX</strong> or external application<br />

does the processing and sorting. The <strong>RMX</strong> ignores events that it does not recognize, that is,<br />

events written in a higher version that do not exist in the current version. Therefore, to<br />

enable compatibility between versions, instead of adding new fields to existing events, new<br />

fields are added as separate events, so as not to affect the events from older versions. This<br />

allows users with lower versions to retrieve CDR files that were created in higher versions.<br />

This appendix describes the fields and values in the unformatted CDR records.<br />

Although the formatted files contain basically the same information, in a few instances a single field in<br />

the unformatted file is converted to multiple lines in the formatted file, and in other cases, multiple<br />

fields in the unformatted file are combined into one line in the formatted file.<br />

In addition, to enable compatibility for applications that were written for the MGC family, the<br />

unformatted file contains fields that were supported by the MGC family, but are not supported by the<br />

<strong>RMX</strong>, whereas these fields are omitted from the formatted file.<br />

<strong>Polycom</strong>, Inc. C-1

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!