Cisco Cisco TelePresence Management Suite (TMS) Version 15 Maintenance Manual
The ETL log is available as part of the Download Diagnostic Files download bundle. The data is kept for 30 days. It is a
self-cleaning log that contains log level information only.
self-cleaning log that contains log level information only.
Troubleshooting
For troubleshooting assistance see
Call Detail Records
In Cisco TMS:
Reporting > Call Detail Record
The pages in the
Reporting > Call Detail Record
menu section contain reporting options for call detail records from all
supported Cisco TMS-managed systems.
What is a Call Detail Record?
A call detail record is created as a call (videoconference or audio) ends. Different systems generate their CDRs and
share them with Cisco TMS using different mechanisms. For this reason, data is sometimes processed and interpreted
differently, which may lead to discrepancies in CDRs from different systems that participated in the same call.
share them with Cisco TMS using different mechanisms. For this reason, data is sometimes processed and interpreted
differently, which may lead to discrepancies in CDRs from different systems that participated in the same call.
Key information in a CDR includes:
■
Call participants (systems)
■
Duration
■
Encryption mode and protocols used
CDR-based reports are commonly used in planning and reviewing how a telepresence network deployment is used.
CDRs may reveal where more telepresence resources are needed, as well as potential under utilization of existing
equipment. Below are brief descriptions of the different types of systems for which Cisco TMS statistics can be generated,
and how they are retrieved.
CDRs may reveal where more telepresence resources are needed, as well as potential under utilization of existing
equipment. Below are brief descriptions of the different types of systems for which Cisco TMS statistics can be generated,
and how they are retrieved.
Note that CDRs in Cisco TMS should be considered best effort, and the quality of the data presented relies on the quality
of data received from the systems.
of data received from the systems.
Endpoints
Endpoints managed by Cisco TMS will generate a CDR and communicate it to Cisco TMS immediately after the call
ends.
ends.
Reports based on endpoint CDRs can be generated either in the Endpoints and MCUs page, where you also have the
option of seeing the two different CDRs accumulated, or in the Endpoints page.
option of seeing the two different CDRs accumulated, or in the Endpoints page.
Note that both of these reports only include endpoints managed by Cisco TMS. Statistics for provisioned endpoints are
available in the
available in the
page.
MCUs
The Cisco TMS Database Scanner Service requests MCU CDRs at regular intervals.
Reports based on MCU CDRs can be generated either in the Endpoints and MCUs page, where you also have the
option of seeing the two different CDRs accumulated, or in the MCUs page.
option of seeing the two different CDRs accumulated, or in the MCUs page.
External participants will appear only in MCU CDR reports, not in endpoint reports.
Gatekeeper and VCS
Cisco VCS sends call data and other events to Cisco TMS as the events occur. On the
Gatekeeper CDRs
page, you can
create reports based on this call data.
The chart shows the amount of calls handled by each device type. To get call data for a specific Cisco VCS, click on a
bar in the chart, or select a system in the
bar in the chart, or select a system in the
Data
tab.
200
Cisco TelePresence Management Suite Administrator Guide
Reporting