It is not abnormal to see one or more CUCM nodes stop sending CDR and CMR files from CUCM to VoIP Detective. The best way to isolate this when you see call records successfully produced for phones registered to some of your CUCM nodes, but not others. The good news is that this is easily remedied by restarting the CDR services on your CUCM nodes.
At a high level, we will restart the CUCM services that create CDR and CMR files, starting on the Publisher, then proceeding to each of the subscribers.
Restarting the CUCM CDR services is generally not service or user impacting, however please follow your organization's maintenance and change control recommendations.
- Log into your CUCM Publisher's "Cisco Unified Serviceability"
- Go to Tools -> Control Center - Network Services
- On the Publisher, restart the CDR Repository Manager. Wait for the service to return to Running status, then proceed.
- On the Publisher, restart the Cisco CDR Agent. Wait for the service to return to Running status, then proceed.
- On each of your CUCM Subscriber nodes, restart the Cisco CDR Agent. Wait for the service to return to Running status, then proceed to the next node.
That should be all it takes to restart your CDR services. Another option would be to restart your CUCM servers, however that would certainly impact call processing, and would need to be done inside of a change window.