-
Cisco CallManager System Guide, Release 3.1(2)
-
Index
-
Preface
-
Introduction
-
Cisco IP Telephony Overview
-
System Configuration Overview
-
System-Level Configuration Settings
-
Clustering
-
Redundancy
-
Call Admission Control
-
Cisco TFTP
-
Device Support
-
Services
-
Auto-Registration
-
Partitions and Calling Search Spaces
-
Understanding Route Plans
-
Understanding the LDAP Directory
-
Managing User Directory Information
-
Media Resource Management
-
Conference Bridges
-
Transcoders
-
Music On Hold
-
Media Termination Points
-
Catalyst DSP Resources for Transcoding and Conferencing
-
SMDI Voice Mail Integration
-
Cisco Unity Messaging Integration
-
Cisco uOne Voice Messaging Integration
-
Cisco DPA Integration
-
Call Park
-
Call Pickup and Group Call Pickup
-
Cisco IP Phone Services
-
Extension Mobility and Phone Login Features
-
Understanding Cisco WebAttendant
-
Custom Phone Rings
-
Understanding Voice Gateways
-
Cisco IP Phones
-
Computer Telephony Integration
-
Administrative Tools Overview
-
Administrative Accounts and Passwords
-
Feedback
Table Of Contents
Bulk Administration Tool (BAT)
Administrative Reporting Tool (ART)
Cisco CallManager Serviceability
CDR-Related Service Parameters
Where to Find More Information
Administrative Tools Overview
This section provides an overview of the following tools for Cisco CallManager administrators:
•
Bulk Administration Tool (BAT)
•
•
•
Bulk Administration Tool (BAT)
The Bulk Administration Tool (BAT), a plug-in application to Cisco CallManager, lets you add, update, or delete a large number of phones, users, Cisco VG200 gateways and ports, and Cisco Catalyst 6000 24 Port FXS analog interface modules to the Cisco CallManager database. Where this was previously a manual operation, BAT helps you automate the process and achieve much faster add, update, and delete operations.
You can access BAT from Cisco CallManager Administration using the Application menu.
For more information, refer to the Bulk Administration Tool Guide for Cisco CallManager.
Administrative Reporting Tool (ART)
The Administrative Reporting Tool (ART) for Cisco CallManager, a web-based reporting application, generates the following reports that provide information regarding voice quality and generates reports on the gateway performance.
•
•
•
•
•
•
The Cisco CallManager records information regarding each call in call detail records (CDRs) and call management records (CMRs). CDRs and CMRs serve as the basic information source for ART and are stored in the ART database.
Users can only access ART through a secured login. The user ID and password for ART access are the same as the user profile set for Cisco CallManager.
To view the reports, you must use Adobe Acrobat Reader, which you can download and install from the ART main screen.
For more information, refer to the Administrative Reporting Tool Guide for Cisco CallManager.
Cisco CallManager Serviceability
Administrators can use the Cisco CallManager Serviceability web-based tool to troubleshoot problems with the Cisco CallManager system. Cisco CallManager Serviceability provides the following services:
•
•
•
•
To access Serviceability from the Cisco CallManager Administration window, choose Applications > Cisco CallManager Serviceability from the menu bar.
For more information, refer to the Cisco CallManager Serviceability Administration Guide.
Remote Network Management
Network management tools, if properly deployed, can provide the network administrator with a complete view into any enterprise network. With the advent of converged networks, it is imperative to have network management systems enable the following capabilities:
•
•
•
Cisco CallManager remote serviceability tools and CiscoWorks2000 provide the above capabilities and enable visibility into the health and availability of the Cisco AVVID network. Considerable management features have been added, starting with Cisco CallManager Release 3.0, to permit visibility into the operation and reporting capability of a Cisco AVVID network. Table 35-1 lists the features provided for network management applications to export data and, particularly for CiscoWorks2000, to provide reporting, proactive management, and debugging capabilities.
For more information on remote network management, refer to the Cisco CallManager Serviceability Administration Guide.
Call Detail Records
When CDR collection is enabled, Cisco CallManager writes call detail records (CDRs) to the SQL database as calls are made. CDR collection is enabled and configured through service parameters that are set in Cisco CallManager Administration. You must enable CDR collection on each Cisco CallManager in the cluster for which you want to generate records (see the "CDR-Related Service Parameters" section).
All CDR records are written to the local database on each Cisco CallManager and then moved from the local database to the publisher database for the cluster in a low priority thread at 1-minute intervals.
If the local database is not available, then they are written to any of the other subscriber databases in the cluster. When the local database becomes available, the writing of new records resumes on the local database.
Enabling CDR Collection
CDR collection is enabled through a Cisco CallManager service parameter named CdrEnabled. To enable CDR collection:
1.
2.
3.
4.
5.
6.
7.
CDR-Related Service Parameters
The following tunable service parameters apply to CDRs:
•
•
•
Removing CDR Records
The CallManager application relies on post-processing applications such as ART or other 3rd-party packages to analyze CDR data. The removal of the CDR data should be done by the administrator when all post-processing applications are through with the data. Because this involves modifying the database, the SQL user CiscoCCMCDR should be used.
If CDR records accumulate to a configured maximum (as set by the MaxCdrRecords service parameter, which defaults to 1.5 million records), then the oldest CDR records are removed along with related CMR records once a day.
When removing CDR data after analysis, be sure to remove all related CMR records also.
Tips
CDR Database Access
The easiest way to read data from the SQL database is to use ODBC. A good connection string would look like one of the following examples depending on whether you need to get to the configuration data or CDRs:
DRIVER={SQL Server};SERVER=machineX;DATABASE=CCM0300
DRIVER={SQL Server};SERVER=machineX;DATABASE=CDR
Be sure to use the correct database name. Previous versions of the product had the CDR tables in the CCM0300 database. The tables have been moved to the CDR database. Also, you will need access to both the configuration database and CDR database to properly resolve the CDR information.
The machine that is the central collector of the CDR information is the machine serving the primary CCM0300 database. To determine the publisher database (machine and name) currently in use by the cluster, perform the following steps:
1.
2.
The Database field in the Database Information area displays the name of the Cisco CallManager server that is the publisher database for the cluster.
Access to CDR records is controlled through SQL Users. Table 35-2 specifies the UserID and password that should be used when accessing the Cisco CallManager database.
Where to Find More Information
Related Topics
•
•
Additional Cisco Documentation
•
•
•
•
•
•
•
•
•
