Administrator’s Guide for SIP-T2 Series/T19(P) E2/T4 Series/CP860 IP Phones656fallback purpose.Phone Configuration for Redundancy ImplementationTo assist in explaining the redundancy behavior, an illustrative example of how an IPphone may be configured is shown as below. In the example, server redundancy forfallback and failover purposes is deployed. Two separate servers (a working serverand a fallback server) are configured for per line registration.Working Server: Server 1 is configured with the domain name of the working server. Forexample: yealink.pbx.com. DNS mechanism is used such that the working server isresolved to multiple servers for failover purpose. The working server is deployed inredundant pairs, designated as primary and secondary servers. The primary server hasthe highest priority server in a cluster of servers resolved by the DNS server. Thesecondary server backs up a primary server when the primary server fails and offersthe same functionality as the primary server.Fallback Server: Server 2 is configured with the IP address of the fallback server. Forexample, 192.168.1.15. A fallback server offers less functionality than the working server.Phone RegistrationRegistration method of the failover mode:The IP phone must always register to the primary server first except in failoverconditions. If this is unsuccessful, the phone will re-register as many times as configureduntil the registration is successful. When the primary server registration is unavailable,the secondary server will serve as the working server.Registration methods of the fallback mode include: Concurrent registration (default): The IP phone registers to two SIP servers (workingserver and fallback server) at the same time. In a failure situation, a fallback server