CLUSTERID on CDR

[Ronit Malhotra]

On Enterprise parameter we have given CUCM1 as cluster id, when i check cdr logs, two subscriber show correct clusterid and other two show 

cmr_StandAloneCluster_02 

cmr_StandAloneCluster_04 subsequently 

Call manager service and cdr are restarted when clusterid was changed earlier.

DB replication is good

The only difference i found is Cluster02 and 04 are separated over wan from Publisher

[Nikhil Aind · Accepted solution]

Hi Ronit,

Since CallManager service has already been restarted it should be creating the CDR records with the specified ClusterID which can be seen in the call manager logs, You can try to restart the below services on the respective nodes :

- CDR Agent
- CDR Repository Manager

In worst cases you might have to go for a cluster reboot.

Regards,

Nikhil

*****Please rate helpful posts*****