Analog and digital endpoints do not restart to fail over to an alternate server. However, the MGC of the analog and digital endpoint detects the registration failure and attempts the reregistration on behalf of these endpoints.

The MGC provides the services that allows the server to detect a server failure. After the failure is detected, the MGC does the following:

The MGC attempts to find capacity in the primary server first.

However, if the primary cluster has insufficient capacity to support the fail over, then in a geo-redundant model, the outage time is the sum of the outage time caused during the initial registration failure and the time required to register to the geo-redundant cluster. The outage time is usually short and may not be detected by an end user, unless the user tries to use the endpoint during the fail over.

Depending on factors such as network speed and Session Manager resiliency, the fail-over time for the MGC to register the endpoint to a Device Adapter node is typically five minutes or less in addition to the time required to detect the geo-redundancy failure.

However, even a short interval for detecting the registration failure and failing over may be noticed by the users. Hence, even a very fast switch-over may be noticed by the users.