Server Redundancy

Server redundancy is often required in VoIP deployments to ensure continuity of phone service if, for example, the call server is taken offline for maintenance, the server fails, or the connection between the phone and the server fails.

Polycom phones support failover and fallback server redundancy types. In some cases, you can deploy a combination of the two server redundancy types. Consult your SIP server provider for recommended methods of configuring phones and servers for failover configuration.

Note that the default value of the new parameters reg.x.server.y.failOver.concurrentRegistration and voIpProt.server.y.failOver.concurrentRegistration=0 effective UC Software 5.5.2 for Polycom Trio systems change default behavior in previous releases. Prior to UC Software 5.5.2, the server you specify in y concurrently registers with other configured servers. As of UC Software 5.5.2, server y is added to the set of redundant failover servers. If you want to register the server concurrently with other servers set reg.x.server.y.failOver.concurrentRegistration=1 or voIpProt.server.y.failOver.concurrentRegistration=1.

Note: The concurrent failover/fallback feature is not compatible with Microsoft environments.

For more information, see Technical Bulletin 5844: SIP Server Fallback Enhancements on Polycom Phones and Technical Bulletin 66546: Configuring Optional Re-Registration on Failover Behavior.