Table of Contents
Advertisement
Introduction
Call Detail Records (CDRs) are used by Cisco TelePresence products for auditing and billing
purposes. The following Cisco TelePresence products are able to generate CDRs:
MCUs: MCU 4200 Series, MCU 4500 Series, MCU MSE 8420 and the MCU MSE 8510.
ISDN gateways: ISDN GW 3241, ISDN GW MSE 8310 and ISDN GW MSE 8321.
IP gateways: IP GW 3500 Series and IP GW MSE 8350.
Advanced Media Gateway: AM GW 3610
When logging is enabled on a Cisco device, CDRs are generated as follows:
On an MCU/MCU MSE blade: when a conference starts or finishes, and in response to other
events such as participants joining and leaving the conference.
On an ISDN gateway or IP gateway unit or blade: When a call starts, completes, transfers to a
multisite call, or is disconnected for some other reason.
On an AM gateway: When a call starts, completes, or is disconnected for some other reason.
The CDR log is stored on the unit's/blade's CompactFlash card. The CDR log is stored in a
proprietary Cisco format. You can only read this format on a Cisco unit or blade, however, it is
possible to export or download the complete CDR log, or part of it, in XML format using the web
interface. The exported log includes all stored CDRs, and all available details, regardless of the
current filtering and display settings set in the web interface.
This document explains the format of the log as exported in XML.
Overview of CDR file formats
CDR files begin with the <cdr_events> opening tag and close with the matching </cdr_events>
closing tag.
Each event starts with:
<event index="number" date="DD Month YYYY" time="hh:mm:ss" type="event type">
and ends with:
</event>
where number is a unique identifier for the event starting at zero and incremented by one for each
CDR event. The fields that occur between the <event> and </event> tags depend on the event.
Note: When using the timestamp on an event you should be aware that changing the time on the
MCU and NTP's UTC Offset (go to Settings > Time) affects the CDR log timestamp in the following
ways:
Changing the time either by changing the system time or via an NTP update causes new events
in the CDR log to show the new time but no change will be made to existing logged CDR events.
With NTP enabled, setting a UTC offset changes the displayed time for all the CDR events. The
stored time remains the same because it is stored in UTC and the offset is applied for display
purposes.
Enabling or disabling NTP when an offset is configured causes the display time to change for all
existing events and the UTC time will change for logging future CDR events. This is because
when NTP is disabled, the current time is treated as UTC with an offset of 0.
Call Detail Record File Format Reference Guide
Introduction
Page 3 of 26
Advertisement
Table of Contents
