Failover - Admin Guide

Watch the video: 

Requirements

• WMS Network must be set up between the PBXs

• Failover PBX must be capable of handling the max load (Main + Failover)

  • WPBX HW – Max 1000 users

  • VM – 1 Core – 2 threads of a Xeon Level CPU for each 500 users

• Primary DNS Server set on devices must be different from Main PBX or an a Secondary DNS Server must be available

Supported scenarios

Hot Standby Mode

• All the configuration is made only on the Primary PBX (users, devices, lines, Dialplan, call groups)

• Secondary PBX has no load, no calls, it regularly copies the configuration from the Primary PBX and takes over in case the Primary PBX goes down

Open

Load Sharing Mode

• Same as in Hot Standby all the configuration is made on the Primary (Server) PBX (users, devices, lines, Dialplan, call groups)

• Secondary PBX has no load, no calls, it regularly copies the configuration from the Primary PBX and takes over in case the Primary PBX goes down

• Configuration sync: all changes must be applied only to Configuration Source PBX

Configuration example provided in the chapter Load Sharing Scenario.

Supported devices & scenarios 

All the devices that support double registration:

• WP4X0, Start, WorkForce, WelcomeConsole, Vision (EOL), SuperVision (EOL)

• Start 5, WorkForce 5, ForcePro 5, WelcomeConsole 5, SuperVision 5

• W24FXSR2/W04FXS/W02FXSR2 (except for W01FXS – pre 2015)

• W04FXO

• PRI

• BRI

• Collaboration (WEB phone) 

• Collaboration Native app (starting from v. 2.1.5)

• Collaboration Chrome extension (starting from v. 1.6.7)

• Incoming SIP trunks (remote operators / devices try to connect to both PBXs)

• WP600AXX (starting from v. 2.8.22)

• Android clients

Failover PBX supports the following call scenarios:

• Internal calls

• Call groups (except for ‘Call All 32’ strategy)

• Calls to/from Wildix gateways

• Calls to/from incoming SIP trunks

• Call transfer

• Return from transfer

Device configuration and switching timeout