This document describes one reason that data for a certain period of
time does not appear in the reports created by the Call Detail Record (CDR)
Analysis and Reporting (CAR) tool and provides a solution in a Cisco
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
CAR is a tool that provides reports on calls based on CDR records.
Reports provided include calls on a user basis, calls through gateways,
simplified Call Quality, and CDR search mechanism. In addition, limited
database administration (the deletion of records based on DB size) is also
provided. All of this information is installed in the ART database.
The Cisco CallManager records information related to each call in CDRs
and Call Management Records (CMRs). CDRs and CMRs serve as the basic
information source for ART and are stored in the ART database (see
Figure 1—Relationship between CDR and ART
When you run the CDR Analysis and Reporting tool, reports fail to
display data for a certain period of time.
When the user runs CDR reporting for a date range using ART / CAR,
report generation fails with the 30023: Data is not available
for the date range selected error message, or the CAR tool is
not able to generate reports for a certain date range.
Complete these steps to determine if there are any records in the SQL
Select Start > Programs > SQL > Enterprise Manager
> Microsoft SQL Servers > SQL Server Group.
Select Publisher Server >
Select CDR > Tables and right click on the
Select Open Table > Return All Rows and
determine if there are any records.
If you see records, then problem is that the CDR database and ART
database are out of synchronization. Follow the procedure in
Cause 1 to resolve the problem. If you do not
see any records, there are no CDR entries for that time and date range. Refer
to the procedure in Cause 2 to determine if you
have met the conditions for CDR generation. If you use Cisco CallManager
release 4.1(3) or later, the problem can also be caused when the contents of
the Comments column exceeds 256 characters. See Cause
3 to verify whether this is the cause of problem and for the steps to
resolve the issue. If these solutions do not resolve the issue, uninstall CDR
from Add/Remove Programs, delete the ART
database manually, and then reinstall the CDR from the CCM
Administration > Plugins
Note: If there is more than one user associated with a device (MAC
address), the report gives results only for the last "most recent" user
associated with that device. For example, if there are two users associated
with the same device, based on which user the database sees as "first," the
reports for all other associated users is always empty. These are just some
considerations to keep in mind when you contrast these two types of database
queries within CAR/ART. If you want to run Billing or other reports instead of
CDR searches on these users who currently come up "empty," you need to query
SQL to find out all users associated with the device in question, and then
remove all associations from that device except for the one you want.
Note: If Cisco CallManager does not create the new CDR records, and the
error message ReadConfiguration Unable to read/write to Source
directory is received, make sure that c:\Program
Files\Cisco\CallDetail is shared on Publisher and Subscribers. If
shared, check the security settings to make sure if the ccmcdr
user has the modify rights to this folder.
Note: Data is available in CDR from the date it is configured.
If you see records while you query the CDRDetailRecord table, then the
CDR database does contain all the missing CDRs. However, these missing CDRs do
not exist in the ART database. The root cause for this problem is that the CDR
database and ART database are out of synchronization.
Complete these steps to synchronize these two
Purge the ART database.
Select Start > Programs > Microsoft SQL Server >
Select the ART database from the drop-down list of database
selection (see the red arrow in Figure
Figure 2—SQL Query Analyzer
Run these SQL query commands:
Restart the Cisco CAR Scheduler service.
It should start to load CDRs as per the CDR load setting. Cisco
recommends that you perform this process after hours so that it does not impact
normal call processing.
If you do not see any records, there are no CDR entries for that time
and date range. Determine if you have met the conditions for CDR generation.
CDR records are generated in these circumstances:
The CallManager service parameters CDR Enabled and Call Diagnostics
Enabled are set to True.
The call is established and has a talk duration greater than
The call fails and has a cause code to reflect the
Complete these steps to enable CDR generation.
Go to the Service menu and select Service
Parameters from Cisco CallManager Administration
Select the Cisco CallManager service for each
server in the cluster.
Scroll down to CDR Enabled Flag under the System
section. Set the value of this parameter to
Scroll down to Call Diagnostics Enabled under the
Clusterwide Parameter (Device - General) section and assign a value of
True to this parameter.
Go to the System menu and select
Enterprise Parameters from the Cisco CallManager
Scroll down to the CDR Parameters section of the
Enterprise Parameters Configuration page.
Enter 1 for the CDR File Time Interval
Select CDRs will be inserted into database for the
The value is set during the CallManager installation for the CDR
UNC Path. Make sure the value is not empty or invalid.
If the Cisco CallManager server is standalone, then enter the value
as StandAloneCluster for the Cluster ID. Otherwise, enter the
ID of the Cisco CallManager cluster.
Enter the directory for local CDR files that are written by Cisco
CallManager for the Local CDR Path. The value should not be empty or invalid,
or Cisco CallManager cannot write CDRs.
Leave the value field empty for the Off Cluster CDR Connection
Go to theService menu and select Service
Parameters from the Cisco CallManager Administration
Select the Cisco Database Layer Monitor
Scroll down to Max CDR Records under the
Clusterwide Parameters (Parameters that apply to all servers) section. Set the
value as 1500000.
Go to the Tools menu and select Control
Center from the Cisco CallManager Serviceability
Make sure these services are activated for each sever in the
Activate the Cisco CDR Insert service in the
Note: Sometimes, the zero and minimum duration calls to 911 do not show up
in the CDR database if the calls are hung up quickly (as if 911 was dialed
mistakenly). This issue can happen when the CDR parameter called Log
calls with zero duration is set to False. Unless this parameter is
enabled, the server does not log calls with zero duration in the CDR database.
This includes calls that are never connected. In this situation, go to the
CallManager Service Parameters and make sure that the Log
calls with zero duration flag is set to True.
In Cisco CallManager release 4.1(3) or later, when the content of the
Comments column exceeds 256 characters, an attempt to run the CAR/ART report
receives the 30023:Data is not available for the date range
selected error. This issue is tracked by Cisco bug ID
(registered customers only)
Complete these steps to verify whether the problem is due to loading of
Select Start > Programs >
Microsoft SQL Server > Query
Select the CDR database from the drop-down list of
Execute the query select max(len(comment)) from
CallDetailRecord. If the return value is more than 256, then
perform the steps to resolve the problem.
Select the ART database from the database selection drop-down
Execute these SQL commands.
Alter Table Tbl_Billing_Data Alter Column Comment
Alter Table Tbl_Billing_Error Alter Column Comment
Alter Table Tbl_Dump_CallDetailRecord Alter Column
Configure the loader to run or take default loader
Start the CAR Scheduler.
If the CAR data does not populate, and the error [Root
exception is javax.net.ssl.SSLHandshakeException:
sun.security.validator.ValidatorException: No trusted certificate
found] appears in the DC Directory logs, disable SSL from the
UMDirectoryConfiguration.ini as given in these
Use a text editor to open
C:\dcdsrvr\DirectoryConfiguration.ini, and verify
C:\dcdsrvr\Config\UMDirectoryConfiguration.ini, and verify the
Open HKEY_LOCAL_MACHINE > SOFTWARE > Cisco Systems,
Inc. > Directory Configuration and verify that
Restart IIS, Cisco Tomcat, and Cisco CAR services from Windows
The number of calls that is reported through CDR does not match the
number of calls that shows up in the Cisco Agent Desktop Agent Call Log. This
issue can occur when the size of the CDR database contains more records. In
this case, refer to
Shrink the CDR Database to resolve the issue.
After you upgrade from Cisco CallManager 4.x to 6.0.1, CAR is unable to
load CDR flat files into the CAR database. This can also result in the error
message Data is not available for the date range
In order to resolve the issue, perform these steps:
From CLI, run this query: Run sql Select
max(Error_Record_Id) from car:tbl_error_id_map <value A>
Get the result of the above query as <value A> and run
this: run sql update car:tbl_system_preferences set param_value=
<value A+1> where param_name='MAX_ERROR_RECORD_ID'
For example, if max(Error_Record_Id) from
100, use the
If these steps did not resolve the issue, perform this
Go to the Cisco CallManager CAR page.
Go to System > Scheduler > CDR Load.
Check the Continuous Loading 24/7 box.
Go to the Load CDR & CMR area, and make sure
that the Time, Loading Interval, and
Duration are configured correctly.
Go to the CallManager Serviceability page.
Go to Tools > Control Center.
Choose the publisher and restart the Cisco CAR