Hi Experts,
I am writing this blog for work around for the following error while pulling the CDR reports you dont see the data(NULL files) or "10021 there are no matching records".
For CUCM, there is no CDR database, we have only CAR database. Here, once the call is completed, the CDRs will be generated at location "/var/log/active/cm/cdr" and from there files will be pushed to "/var/log/active/cm/cdr_repository/tmp" folder by CDR Agent service. In case of cluster, the CDRs generated on the subscriber will be pushed to publisher server (CAR operates only on publisher).
Later, CDR Repository Manager service, pushes the CDR files from “/var/log/active/cm/cdr_repository/tmp” to “/var/log/active/cm/cdr_repository/preserve/<yyyyMMdd>/” folders based on the date of the file, and corresponding softlinks will be created under “/var/log/active/cm/cdr_repository/destination1(2/3)/<yyyyMMdd>/ ”for billing servers, (according to configuration under ccmservice->tools->CDR Management page). The files are accessed through softlinks for processing and once all the softlinks for a particular file are processed successfully, the file will be moved to ”/var/log/active/cm/cdr_repository/processed/<yyyyMMdd>/ “ folders and the corresponding softlinks will be deleted.
Please follow the below work around:
- Please verify the CDR configuration on System->Service Parameters in the CUCM Administration.
- Please check the relevant services for CDR on the specific nodes on CUCM Serviceability
If the service parameter for CDR is set to True and services are up then check the following
System > Service Parameters
On the resulting page, select one of the servers in the cluster which has the Cisco CallManager Service activated and running.
Select the Cisco CallManager Service option from the list in the Service field.
One the service parameters are shown on the page, locate the System section and enable the following settings to true:
- CDR Enabled Flag set this to True
- CDR Log Calls with Zero Duration Flag(optional)
====================================================
To configure the number of days the system should hold CDR
Go to CAR
System > Database > Configure Automatic Purge
Change the value of "Max Age of Call Detail Records"
---------------You can use the following to see the status of CDR Load for any particular DATE-----------------------------------------
Go to CAR Page <CUCMIP>/car
System>Log Screens>Event Log
Select CDR Load push it right and then select the date to see CDR report card.
---------------------------------------------------------
If the services are up and running now proceed to restart the services, please note there is not impact of these services restart and can be done even during bussiness hours
Before the services restart you will have to Disable Loader
System > Scheduler > CDR Load
Uncheck "Continuous Loading 24/7" check "Disable Loader" and Click "UPDATE"
On Publisher
1. go to Cisco Unified Serviceability > Tools > Control Center - Feature Services
restart CDR Services
Cisco SOAP - CDRonDemand Service
Cisco CAR Web Service
2. Then go to Cisco Unified Serviceability > Tools > Control Center - Network Services(or you can directly go to Network services using related links on Feature Services)
restart all the CDR services (except Cisco CAR DB - you can not restart this service)
Cisco CDR Repository Manager
Cisco CDR Agent
Cisco CAR Scheduler
Cisco SOAP - CallRecord Service
On Subscribers
restart Cisco CDR Agent Service
Once all the services are restarted
Go back to CAR
System > Scheduler > CDR Load
Uncheck "Disable Loader" check "Continuous Loading 24/7" and Click "UPDATE"
Wait for sometime(depends upon your size of cluster, may takes even few hours before you can see the CDR)
You can use PUB CLI to see the files
admin:file list activelog /cm/cdr_repository/preserve
admin:file list activelog /cm/cdr_repository/processed
It will show the date then you can use the date to view the the entries for that date using following command
admin:file list activelog /cm/cdr_repository/preserve/20190123
The last line of the output will be like below
dir count = 0, file count = 971
The count with every refresh(means executing the same command after few seconds) must decrease in preserve and at the same time increase in processed
admin:file list activelog /cm/cdr_repository/processed/20190123
*20190123 here means Jan, 23rd, 2019
Thanks Muk
Please rate helpful, if this helps
