The Cisco CallManager Serviceability CAR tool, formerly known as Administrative Reporting Tool (ART), generates reports of information for quality of service (QoS), traffic, user call volume, billing, and gateways. The CAR tool generates reports in either Portable Document Format (PDF) or Comma-Separated Values (CSV) format. The PDF format limits the number of records in the CAR reports to 5000, and CSV format limits the number of records to 20,000. If the number of records exceeds these limits, a message warns that the results are truncated. To avoid truncating reports, reduce the date range and regenerate the reports.
Note
CAR is not installed during the standard Cisco CallManager installation and must be added separately.
If CAR is running on your system before you upgrade to a new version of Cisco CallManager, the upgrade process automatically upgrades CAR. If Cisco CallManager is being installed for the first time, CAR has to be installed manually from the Cisco CallManager Administration. You can install CAR from the standard plug-ins web page (Application > Install Plugins). You must install CAR on the Cisco CallManager publisher that hosts the CDR database. CAR uses the Cisco Tomcat service.
CDRs and CMRs
Call detail records (CDRs) and Call Management Records (CMRs) are both stored in the CDR database, accessible with the Microsoft SQL Server Enterprise Manager. Choose Start > Programs > Microsoft SQL Server > Enterprise Manager to open the Microsoft SQL Server Enterprise Manager on the Cisco CallManager publisher. Both types of records store information about a call. The CDR table stores details about the call itself, whereas the CMR table stores information about QoS parameters for the same call. The SQL database refers to the CDR and CMR tables as CallDetailRecord (for CDRs) and CallDetailRecordDiagnostic (for CMRs), as shown in Figure 33-1. For every CDR entry, CallManager also generates a CMR entry.
Figure 33-1. CDR and CMR Tables in the SQL 2000 Database
Note
When you purge a record in the CDR database, CallManager deletes the related entries for a call in both the CallDetailRecord and CallDetailRecordDiagnostic tables.
The CallDetailRecord table stores extensive information about a call. Each record has a unique identifier called the pkid that enables you to find and identify a single record. The CallDetailRecord table also contains information about the calling party, called party, duration of or information about call forwarding, CMC, and FAC, to name the most important fields of a record. In total, the CallDetailRecord table contains 68 information fields.
The number of columns for the CallDetailRecordDiagnostic table, in contrast to the CallDetailRecord table, is very small. It has only 18 information fields. A unique identifier (pkid) for every call is included in the CallDetailRecordDiagnostic table as well. The pkid for a call in the CallDetailRecordDiagnostic table is not the same as the pkid for the same call in the CallDetailRecord table. To reference a call in the tables, use the oriLegCallIdentifier and destLegIdentifier field information. Among other things, information about the packets sent and received, jitter, and latency are stored for QoS reports.
CAR Users
CAR has a distinct management interface from the Cisco CallManager Administration and Serviceability web pages, as shown in Figure 33-2. The available menus in CAR depend on the level of the user authenticating to the system. CAR provides reporting capabilities for three levels of users:
Figure 33-2. CDR Analysis and Reporting Administrative Interface
CAR Report Types and User Levels
There are three report types available in CAR:
The administrator can generate all types of reports: user reports, system reports, and device reports. Managers can generate only parts of the user and system reports, such as billing, Top N, and QoS reports, and only for employees who report directly or indirectly to the manager. Users can check only their own bills in general or in detail, and send the report by e-mail. Table 33-1 summarizes these rights.
Report |
Administrator |
Manager |
User |
---|---|---|---|
User Reports |
Full Access |
Bills, Top N |
Only their own bills |
System Reports |
Full Access |
QoS |
No Access |
Device Reports |
Full Access |
No Access |
No Access |
CAR Configuration |
Part I: Cisco CallManager Fundamentals
Introduction to Cisco Unified Communications and Cisco Unified CallManager
Cisco Unified CallManager Clustering and Deployment Options
Cisco Unified CallManager Installation and Upgrades
Part II: IPT Devices and Users
Cisco IP Phones and Other User Devices
Configuring Cisco Unified CallManager to Support IP Phones
Cisco IP Telephony Users
Cisco Bulk Administration Tool
Part III: IPT Network Integration and Route Plan
Cisco Catalyst Switches
Configuring Cisco Gateways and Trunks
Cisco Unified CallManager Route Plan Basics
Cisco Unified CallManager Advanced Route Plans
Configuring Hunt Groups and Call Coverage
Implementing Telephony Call Restrictions and Control
Implementing Multiple-Site Deployments
Part IV: VoIP Features
Media Resources
Configuring User Features, Part 1
Configuring User Features, Part 2
Configuring Cisco Unified CallManager Attendant Console
Configuring Cisco IP Manager Assistant
Part V: IPT Security
Securing the Windows Operating System
Securing Cisco Unified CallManager Administration
Preventing Toll Fraud
Hardening the IP Phone
Understanding Cryptographic Fundamentals
Understanding the Public Key Infrastructure
Understanding Cisco IP Telephony Authentication and Encryption Fundamentals
Configuring Cisco IP Telephony Authentication and Encryption
Part VI: IP Video
Introducing IP Video Telephony
Configuring Cisco VT Advantage
Part VII: IPT Management
Introducing Database Tools and Cisco Unified CallManager Serviceability
Monitoring Performance
Configuring Alarms and Traces
Configuring CAR
Using Additional Management and Monitoring Tools
Part VIII: Appendix
Appendix A. Answers to Review Questions
Index