Document ID: 49566
Contents
Introduction
Prerequisites
Requirements
Components Used
Conventions
Conference Server Analysis
Related Information
Introduction
This document explains how to determine the total number of seconds or minutes used for each Cisco MeetingTime conference server.
Prerequisites
Requirements
There are no specific requirements for this document.
Components Used
The information in this document is based on these software versions:
-
Cisco MeetingTime (all versions)
-
Microsoft Excel
The information in this document was created from the devices in a specific lab environment. All of the devices used in this document started with a cleared (default) configuration. If your network is live, make sure that you understand the potential impact of any command.
Conventions
For more information on document conventions, refer to the Cisco Technical Tips Conventions.
Conference Server Analysis
Complete these steps:
-
Log in to Cisco MeetingTime.
-
From the Reports tab, run the Raw Meeting Details report for the dates you want to analyze.
-
After the report has completed, save the file as a .csv.
-
Open the report in Microsoft Excel.
-
Sort the file by column header PriUnitNum.
-
Sort by the number in the PriUnitNum column to separate the information for each server.
-
1 = conference server 1
-
2 = conference server 2
-
3 = conference server 3
-
-
Decide what type of usage information you want to get from the data.
-
Usage Minutes
-
Sum each worksheet by the column header TotConfPortSec. This gives you the “total conference port seconds” for each conference call.
-
Divide this number by 60 to get the usage minutes for that specific server.
-
-
No-Show Meetings
-
Sort each worksheet by the column header TotConfPortSec.
-
Count the number of meetings that have a 0 in this column. The 0 means that no one dialed in to the call.
-
-
Related Information
- Voice Technology Support
- Voice and Unified Communications Product Support
- Recommended Reading: Troubleshooting Cisco IP Telephony

- Technical Support - Cisco Systems
| Updated: Jan 31, 2006 | Document ID: 49566 |
