8.2 Server Redundancy
Server redundancy is often required in VoIP deployments to ensure continuity of phone service, for example,
the call server offline for maintenance, the server crashes, or the connection between the IP phone and the
server fails.
Two types of redundancy are possible. In some cases, a combination of the two may be deployed:
•
Failover: In this mode, the full phone system functionality is preserved by having a second equivalent
capability call server take over from the one that has gone down/off-line. After the IP phone fails to
register to the primary server, it will send the register message to secondary server.
•
Fallback: Compared with failover mode, fallback mode supports the policy of primary server first,
which means IP phone always attempts to register to the primary server, it will return to the primary
server once the primary server is available.
8.2.1 Registration Method of Failover/Fallback Mode with Outbound Proxy
Currently there is a binding relationship between SIP server and outbound proxy address. That means if you
configure outbound proxy address1, the IP phone always sends SIP request message with server1 parameter
to outbound proxy address1; when the outbound proxy address1 is not available, the phone will send SIP
request message with server2 parameter to outbound proxy address2.
8.2.2 Failover/Fallback Mode Configuration
The following table lists the parameters you can use to configure failover/fallback server redundancy
Note: X means account ID. It can be number 1~8 for M3/M5/M7, and 1-20 for M8.
To Next Page
Loading...
