Matrix SPARSH VP110 User Guide 257
the DNS server. The secondary server backs up a primary server when the primary server fails and offers
the same functionality as the primary server.
• Fallback Server: Server 2 is configured with the IP address of the fallback server. For example,
192.168.1.15. A fallback server offers less functionality than the working server.
Phone Registration
Registration methods of the fallback mode include:
• Concurrent registration: The IP phone registers to two SIP servers (working server and fallback server)
at the same time. In a failure situation, a fallback server can take over the basic calling capability, but
without some of the advanced features offered by the working server (default registration method).
• Successive registration: The IP phone only registers to one server at a time. The IP phone first registers
to the working server. In a failure situation, the IP phone registers to the fallback server.
When registering to the working server, the IP phone must always register to the primary server first except in
failover conditions. When the primary server registration is unavailable, the secondary server will serve as the
working server.
Fallback Scenario
The following introduces a REGISTER fallback scenario. The SIP server 1 (working server) and SIP server 2
(fallback server) are configured with the IP address respectively for account 1. The parameter
“account.1.fallback.redundancy_type” is configured as 1 (Successive Registration).
REGISTER Fallback
The phone has ability to fail over to a fallback server when the working server has no response to a REGISTER
request.
• The phone sends a REGISTER request to the working server.
• The phone retries REGISTER requests to the working server (three times by default).
• After no response from the working server, the phone sends a REGISTER request to the fallback server.
• The fallback server responds with 200 OK to the REGISTER request.
The phone sends REGISTER requests to the working server to detect whether the server is available at intervals
defined by the "account.1.fallback.timeout" parameter after failing over to the fallback server. When the working
server recovers, the phone has ability to fail back next REGISTER request to the working server.
The following introduces an INVITE fallback scenario. The SIP server 1 (working server) and SIP server 2 (fallback
server) are configured with the IP address respectively for account 1. The parameter
"account.1.fallback.redundancy_type" is configured as 0 (Concurrent Registration).
INVITE Fallback
The phone has ability to fail over to a fallback server when the working server has no response to an INVITE
request.
To Next Page
Loading...
Need help?
General
