When CDR reporting runs for a date range with ART/CAR, the report generation fails, and the "30023: Data is not available for the date range selected" error message appears, or the CAR tool is not able to generate reports for a certain date range
When the Administrative Reporting Tool (ART)/CDR Analysis and Reporting (CAR) tools are used in order to generate a report, the 30023: Data is not available for the date range selected error message appears. Data is available only from xx-yyy-zzzz to xx-yyy-zzzz, and no reports are generated.
This error can occur if ART does not get the CDR data to report.
In order to determine if there are any records in the Structured Query Language (SQL) database, complete these steps:
Choose Start > Programs > SQL > Enterprise Manager > Microsoft SQL Servers > SQL Server Group.
Choose Publisher Server > Databases.
Choose CDR > Tables. Right-click the CallDetailRecord table.
Choose Open Table > Return All Rows. Determine if there are any records.
If many records appear, complete this procedure to remove records from ART:
Choose Programs > SQL Server > Query Analyzer. Log in and choose ART database.
Run these queries:
delete from Tbl_Load_History delete from Tbl_Dump_PkID delete from Tbl_Error_Id_Map delete from Tbl_Billing_Data delete from Tbl_Billing_Error delete from Tbl_Dump_CallDetailRecord delete from Tbl_Dump_CallDetailRecordDiagnostic
This forces ART to get all the old CDRs into ART in the next scheduled loading time. By default, CDR data is loaded every day from midnight to 5 a.m.
Restart the CDR Insert and DBL Monitor Services from CCM Administration > Application >Cisco CCM Serviceability >Tools > Control Center.
Note: Information deletes from the ART database but not from the CDR.
Note: If you do not see any records, there are no CDR entries for that time and date range. Determine if conditions are met for CDR generation. CDR records are generated in these circumstances:
The service parameters CdrEnabled and CallDiagnosticsEnabled are set to True.
The call is established and has a talk duration greater than 0.
The call fails and has a cause code that reflects the error.
In order to set the service parameters, choose Service > Service Parameters, and make sure that the service parameters CdrEnabled and CallDiagnosticsEnabled are set to True in all of the Cisco CallManager servers, both publisher and subscriber.
I am setting up a bulk update in CUCM to add jabber phones to all my deskphone users. I have a bat phone template I adapted from one I made for desk phones and I have a user template for use with "Update Users - Custom File". I have used the users t...
Dear Experts, We have UCCX 11.5 system. Currently we are doing call redirect to PSTN number after office hours.During this pandemic situation, managing calls by one person is beyond control. So we would like to create a script for adding multipl...
I have many users that are now working from home. Some of them do not have voice mail because their job duties don't require it. They were given Jabber for Windows to use as a softphone for home use. Several times a day, I get multiple n...
Do the 7800 and 8800 series phones honor the Maximum Number of Calls line setting?I have them set to Max Number of Calls = 2 and Busy Trigger =1.The Busy Trigger works as expected.But I am able to stack up at least 4 calls on the line with the Max Calls s...
HiWe have contact center express at our end. We need to integrate to Google Contact Center AI.But we do not find additional info. Did any body dis similar thing is past if yes. Please let me knowhow it done? Danny