Call Detail Records; Enabling A Cdr Backup Alarm; Enabling Multi-Part Cdrs - Polycom RealPresence 1800 Administration Manual

Call Detail Records

The Polycom® RealPresence® Collaboration Server (RMX) creates Call Detail Records (CDRs) for every
conference started on it. This section discusses the CDR options that you can configure and the CDR tasks
you may want to perform.
CDR Options
● Enabling a CDR Backup Alarm
● Enabling Multi-part CDRS
CDR Tasks
● View the MCU CDR List
● Retrieve and Save a CDR for Viewing
● Retrieve and Save CDRs for Billing and Reporting

Enabling a CDR Backup Alarm

CDRs can be used by businesses to generate billing information and resource usage reports, so saving
CDRs may be important. However, CDRs are not included in the MCU system backup, so if CDRs are
required for reporting and billing purposes, they should be backed up manually.
The RealPresence Collaboration Server stores the CDRs of up to 2000 conferences. The RealPresence
Collaboration Server 4000 stores the details of up to 4000 conferences. When the MCU threshold is close
to being exceeded, the MCU can display active alarms before overwriting the older CDRs, allowing you to
back up the CDRs before they are deleted.
To enable the CDR backup alarms:
» Set the system flag ENABLE_CYCLIC_FILE_SYSTEM_ALARMS to YES.
When the default setting ULTRA_SECURE_MODE system flag is set to YES and the file storage threshold
limit is reached, an active alarm is triggered with the following message.
"Backup of CDR files is required."

Enabling Multi-Part CDRs

By default, the RealPresence Collaboration Server (also called MCU) limits the CDR file size to 1MB. When
a CDR file reaches that size, the MCU saves the CDR and further call data recording is stopped. In that
case, the additional data is lost.
The MCU can be configured to keep recording the data in multiple CDR file sets of 1MB each. Multi-Part
CDR ensures that all conference call data from long duration or permanent conferences is recorded.
Polycom, Inc. 245