I have a situation where a Unity Connection cluster has been deployed over a WAN, and there have been connectivity issues between the sites. When this happens, both servers become primary, and when the connection is restored the cluster goes into Split-brain recovery and does not answer calls. The problem with this, is that it can happen during the day, and most calls are routed to Unity Connection first. This means during split-brain recovery, incoming calls are going to busy signals. Anyone have a good workaround for this behavior? I would prefer the cluster be out of sync during the day than not answer calls. I've been disconnecting the Unity Connections subscriber from the network to stop Split-brain recovery, and connecting it back to the network later when an outage is acceptable.