Downloads |
Document ID: 50028
Contents
Introduction
Prerequisites
Requirements
Components Used
Conventions
Report Statistics Categories
Related Information
Introduction
This document briefly explains how long statistics that are used for various Cisco MeetingPlace reports are kept and how this data retention is controlled.
Prerequisites
Requirements
There are no specific requirements for this document.
Components Used
The information in this document is based on Cisco MeetingTime, all versions.
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.
Report Statistics Categories
The Cisco MeetingPlace report statistics fall into three categories:
Report Statistics Kept According to the “Days Until Mtg Stats Purged” Setting
The "Days until mtg stats purged" setting is located by clicking the Configure tab, then choosing Scheduling Parameters. It controls how long most meeting information data are kept in the system.
Report Statistics Kept for 60 Days
One exception to the way meeting information data are stored is peg counts. This is a separate data area that keeps counters of major events in the system, such as how often different features are invoked. It also provides the data used in the Scheduling Statistics report and in the Port Usage report. These data are kept for 60 days, and that time period is not configurable.
Other
Falling into the category of "other" are the scheduling failures data, another special case. These data are stored as a collection of 1,000 records that is kept as a circular list. It is kept this way because a user who attempts to schedule 20 years in the future or 10 years in the past on Cisco MeetingPlace Web or Cisco MeetingPlace Simple Mail Transfer Protocol (SMTP) Email Gateway receives the error "too far in advance" or "time has already past". So that these failures can be tracked, the data are kept in this special format. The allowable date range for searching these data is any legal date, that is, from January 1, 1970 to September 23, 2033.
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: 50028 |