Engage - CUCM failover improvements
"Engage is bad at handling circumstances where a cucm primary goes down and voips fail over to a secondary. We have to manually restart the cucm service in Admin console when this happens. When primary comes back on, another manual restart of cucm service is required.
In future versions of engage, the system should recognize the failover occurred and cycle its service automatically. This will allow the system to leverage Cisco cucm a failover process effectively and minimize downtime."
Andy Kusters at VA Milwaukee provided this feedback in regards to a CUCM failover always having a handful of phones stuck in a 'failed' state where they won't register properly until they are power cycled (Audit event ).