Customer case 07Replication broken, phones still working
A nightly Health Check caught a failed subscriber before the next reboot exposed it.
- 1
Situation
After a maintenance window, the CUCM database replication between the publisher and one subscriber never came back. Phones stayed registered and calls kept flowing, so nobody noticed.
- 2
What the data showed
The Health Check turned red the next morning on the replication check, with the affected node named and the history showing the first nightly run that reported it.
Health Check · cluster board, six areas with every check - 3
Resolution
The subscriber was repaired that day. Had it stayed broken, every change made on the publisher – new phones, dial-plan changes, forwards – would have silently skipped that node, and the eventual repair would have taken hours.