Cisco TELEPRESENCE CALL DETAIL RECORDS FILE FORMAT - Instrukcja Użytkownika Strona 3

  • Pobierz
  • Dodaj do moich podręczników
  • Drukuj
  • Strona
    / 26
  • Spis treści
  • BOOKMARKI
  • Oceniono. / 5. Na podstawie oceny klientów
Przeglądanie stron 2
Introduction
Call Detail Records File Format Reference Guide Page 3 of 26
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 3200 Series, 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:
MCU/MCU MSE blade: When a conference starts or finishes, and in response to other events
such as participants joining and leaving the conference.
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. Note that for ISDN gateways, if logging is
disabled then the gateway will still generate CDRs (although they will not be stored).
Advanced Media gateway: When a call starts, completes, or is disconnected for some other
reason.
The CDR log is stored on the compact flash card of the unit or blade. The log is stored in a proprietary
Cisco format which can only be read on a Cisco unit or blade. You can 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 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.
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. No change will be made to existing logged CDR events.
Przeglądanie stron 2
1 2 3 4 5 6 7 8 ... 25 26

Komentarze do niniejszej Instrukcji

Brak uwag