This document describes reasons why Cisco Call Detail Record (CDR)
Analysis and Reporting (CAR) fails to display the most current data and
provides a solution in a Cisco CallManager environment.
Cisco recommends that you have knowledge of these topics:
The information in this document is based on these software and
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.
Technical Tips Conventions for more information on document
When you run CAR, query by date fails occasionally. Further research
reveals that these failures are related to dates. Queries work for old dates,
but queries for recent dates fail consistently.
The error message either says that:
Note: If a phone is associated to multiple users, you cannot see the user
See Figure 1.
Figure 1 – Query Error
This problem is a synchronization issue between the Administrator
Reporting Tool (ART) database and CDR database. The ART database is not updated
daily from the CDR database, and the content on the ART database is less
current than that of the CDR database.
Complete these steps:
Check the CDR Enabled Flag.
It should be set to True on the publisher and all
the subscriber servers.
Complete these steps:
Choose the Service menu and select
Service Parameters from the drop-down list on the Cisco
CallManager Administration page.
Select CallManager from the Server drop-down
Select Cisco CallManager from the Service
Go to the CDR Enable Flag under the System section and select
True from the drop-down list as shown in Figure 2.
Figure 2 – Service Parameter: CDR Enabled Flag
In order to verify that Cisco CDR Insert is activated only on the
Publisher server, complete these steps:
Click the Tools menu and select Control
Center from the drop-down list on the Cisco CallManager Serviceability
Select the Publisher server in the left pane.
Verify that Cisco CDR Insert is activated.
See arrow A in Figure
Figure 3 – Control Center: Cisco CDR
If the Cisco CDR Insert is not activated, go to Step 3.
In order to verify that the Cisco CAR Scheduler task is running on
the Publisher server, complete these steps:
Click the Tools menu and select CDR
Analysis and Reporting from the drop-down list on the Cisco
CallManager Serviceability page.
Enter User Name and Password on
the Logon page for CAR.
Click the System menu and select Control
Center from the drop-down list.
Verify the CAR Scheduler task is running.
See arrow A in Figure
Figure 4 – Control Center: Cisco CDR Analysis and Reporting
The symbol means that this task is running. If this symbol is a
square, click Start to start this task.
The CDR report shows records for fewer days than configured
When trying to view the CDR report for a certain number of days,
reports show fewer than the actual configured days.
An insufficient number of the Max CDR Records
configured in the Service parameters under the Cisco Database Layer
Monitor can cause this problem.
Old CDR records are automatically deleted and recent CDR records are
available in CallManager when the number of CDR reports exceeds the value that
is specified in the Max CDR Records.
The Max CDR Records service parameter for the
Cisco Database Layer Monitor service allows you to set a limit
on the maximum number of CDR reports on the system.
Once a day, Cisco CallManager checks the number of CDR reports on the
system and purges CDR reports if the number of CDR reports exceeds the value
that is specified in the Max CDR Records parameter.
In order to resolve this by changing the Max CDR
Records value, complete these steps:
Choose the Service menu and select Service
Parameters from the drop-down list on the Cisco CallManager
Administration page. Select the CallManager server from the Server drop-down
Select Cisco Database Layer Monitor from the
Service drop-down list.
Set the sufficient value for the Max CDR Records
parameter under the Clusterwide
After you have completed these steps, then try to view the CDR
The CDR report shows no records and the tomcat log shows this
java.lang.OutOfMemoryError: PermGen space
This issue is documented in Cisco bug ID . The workaround is to restart the
tomcat.service. Furthermore, in order to avoid this issue disable the CAR web
service and do not stop/start other web services available in the