Last Updated on May 10, 2021 by Jaron Davis
Occasionally there are issues with CUCM CDR that causes CUCM to not provide CDR records to Variphy. I am going to go through the most common issue. Be aware, there could be issues such as database replication errors that would also cause CDR to fail.
First, open a CLI session with the subscriber.
Enter the following command into both nodes:
admin:file list activelog /cm/cdr
You may see a result similar to this:
admin:file list activelog /cm/cdr cmr_ANH-CALLMAN1-Cluster_02_202105101455_268659 cmr_ANH-CALLMAN1-Cluster_02_202105101456_268660 cmr_ANH-CALLMAN1-Cluster_02_202105101457_268661 cmr_ANH-CALLMAN1-Cluster_02_202105101458_268662 cmr_ANH-CALLMAN1-Cluster_02_202105101459_268663 cmr_ANH-CALLMAN1-Cluster_02_202105101500_268664 cmr_ANH-CALLMAN1-Cluster_02_202105101501_268665 cmr_ANH-CALLMAN1-Cluster_02_202105101502_268666 cmr_ANH-CALLMAN1-Cluster_02_202105101503_268667 cmr_ANH-CALLMAN1-Cluster_02_202105101504_268668 cmr_ANH-CALLMAN1-Cluster_02_202105101505_268669 cmr_ANH-CALLMAN1-Cluster_02_202105101506_268670 cmr_ANH-CALLMAN1-Cluster_02_202105101507_268671 cmr_ANH-CALLMAN1-Cluster_02_202105101508_268672 ... dir count = 0, file count = 7563
The file count should be low, usually around 5, so if there are thousands, as shown above, this means the subscriber isn’t passing these files to the publisher for distribution.
To resolve the problem, we need to restart CDR services.
Navigate to Cisco Unified Servicability:
Navigate to Tools > Control Center – Network Services
Select the publisher (10.100.0.10) and select Go.
Restart CDR services in this order:
- 10.100.0.10 – Cisco CDR Repository Manager
- 10.100.0.10 – Cisco CAR Scheduler
- 10.100.0.10 – Cisco CDR Agent
- 10.100.0.11 – Cisco CDR Agent
After you’ve reset the services, confirm in the subscriber CLI that stored CDR files are reducing.
file list activelog /cm/cdr dir count = 0, file count = 5