.. _resilience_administration_automatic_failover: ***************************************** Administration in Automatic Failover Mode ***************************************** In Automatic failover mode, there is an heartbeat link between Standby and Main XiVO. As soon as Standby XiVO detects Main as unreachable, it will become active - see :ref:`resilience_architecture_failover_mode`. This page describes when the failover and fallback are triggered and what manual steps might be necesseray in the different deployment type. .. contents:: :local: XiVO Deployment =============== Failover to Standby ------------------- What happens: * When Standby does not ping Main anymore, Standby node starts the telephony service * The supported phones should automatically register and send their calls towards the Standby Manual actions: None Failback to Main ------------------ What happens: * When Standby pings Main again, the standby shutdown the telephony services * The supported phones should automatically register and send their calls towards the main Manual actions: None CC Deployment ============= Failover to Standby ------------------- What happens: * Standby CC starts needed services when it detects Standby XiVO went to status *Active* * Main CC stops needed services when it detects Main XiVO went to status *Inactive* Manual actions: * The users must reconnect manually to the CC Standby by entering the new CC Standby FQDN in their browser Failback to Main ------------------ What happens: * Standby CC stops needed services when it detects Standby XiVO went to status *Inactive* * Main CC starts needed services when it detects Main XiVO went to status *Active* Manual actions: * The users must reconnect manually to the CC Main by entering the new CC Main FQDN in their browser XDS Deployment ============== Failover to Standby ------------------- What happens: * When the standby takes over the telephony service, it registers to the other MDS Manual actions: None Failback to Main ------------------ What happens: * When the main is back again, it registers to the other MDS Manual actions: None Edge Deployment =============== * A single Edge stack is relaying its services to either the Main or the Standby XiVO machines. Failover to Standby ------------------- What happens: * Edge detects that Main CC/XiVO are not working and redirects the traffic to Standby CC/XiVO Manual actions: * The users must refresh its Web page to reconnect (no need to change FQDN) Failback to Main ------------------ What happens: * Edge detects that Standby CC/XiVO are not working and redirects the traffic to Main CC/XiVO Manual actions: * The users must refresh its Web page to reconnect (no need to change FQDN)