Html |
---|
<div id="fb-root"></div> <script>(function(d, s, id) { var js, fjs = d.getElementsByTagName(s)[0]; if (d.getElementById(id)) return; js = d.createElement(s); js.id = id; js.src = 'https://connect.facebook.net/en_US/sdk.js#xfbml=1&version=v2.11'; fjs.parentNode.insertBefore(js, fjs); }(document, 'script', 'facebook-jssdk'));</script> |
...
Info |
---|
Failover service allows using one PBX as a backup for another one when the latter goes down. This guide describes the supported features and the procedure to set up the service. WMS version: 5.0X / 4.0X Created: December 2017 Updated: October November 2021 Permalink: https://confluence.wildix.com/x/dABuAQ |
...
- Activate WMS network between the PBXs
- Set failover PBX in WMS -> Users -> PBXs:
- Click Failover column near the PBX you wish to set up failover for
- Failover setup dialog opens
- Select the failover PBX from the list
- Click Ok
- Make all the configuration on the main PBX (devices, Dialplan, call groups etc.)
- Disable devices sync from WMP on Failover PBX (available starting from WMS version 3.88.41514.30): add “disable_sync_portal=1”, “disable_sync_manual=1” to the config file /rw2/etc/pbx/device_sync.conf
- Make replication for main Main PBX configuration:
- Access the failover PBX via SSH as root
- Run shell script sync_pbx
- Select 1 (Configure)
Enter IP
of the Main PBXor PBX domain of the Main PBX
Note Note: Starting from WMS 5.04 Beta, it is possible to enter remote PBX domain name instead of PBX IP.
- Enter the admin password of the Main PBX
- Set failover PBX as secondary DNS server on unsupported devices
...
Note |
---|
Notes for Cloud PBXs:
|
...
Current limitations
Warning |
---|
All the points related to the current section were tested on WMS 4. |
No support for failover mode via /rw2/etc/phone_failover.conf
- No support for failover mode via secondary DNS Configuration
- No Full TLS Support (check the table provided in the Chapter “Device configuration and switching timeout”)
- It’s necessary to configure separate DHCP server in the local network where phones and gateways are connected
- Changes to configurations of the PBX which synchronizes its configuration from another one will be lost after each sync, Admin should apply all changes only on the source PBX
- No notification present on phone’s display when switching to backup PBX in failover scheme
- Unsupported devices (see the chapter “Failover by DNS”):
- W-AIR
- W04BRI
- W01GSM
- W01FXS (pre 2015)
- Outgoing SIP trunks
- iOS clients
- W-PA
- No XML Browser-based services like history / phonebooks when connected to failover PBX
- Call group with ‘Call All 32’ strategy – calls do not work for failover user
- Call through remote PBXs of WMS network does not work if Main PBX is unavailable
- Continuity feature does not work after switch to failover PBX (invalid for WMS 5.0, refer to the chapter Support of user features)
- Pre-answer services do not work after switch to failover PBX (invalid for WMS 5.0, refer to the chapter Support of user features)
- Call to the failover WP480 2015-2016 device can not be completed normally
- Return from semi-attended transfer is not performed
- after transfer from remote user to failover user
- after transfer from failover user to remote user
- BLF presence status of the local user is unavailable for failover user; call can’t be picked up via BLF key
- BLF presence status of the failover user is unavailable for local user; call can’t be picked up via BLF key
- Impossible to perform calls from Kite to failover user via WMS network Server PBX in case main PBX is unavailable
- Email notifications are unavailable for failover user; user features are not available on failover PBX (invalid for WMS 5.0, refer to the chapter Support of user features)
- Login/logout via 99 service is restricted for failover user
- Language and region settings are not synced during sync_pbx script execution
...
Note | ||
---|---|---|
| ||
Starting from WMS version 3.88.40477.20 the embedded DNS server is no more available for remote networks by default. If your failover PBX is remote or Cloud, follow the guide /wiki/spaces/DOC/pages/30279583 to disable the DNS restrict "mode". To temporarily enable DNS queries, use /etc/init.d/dns_restrict stop. But in order to always allow DNS queries, it is necessary to make the following change in file /etc/default/dns_restrict: dns_local=0 and then reboot the PBX. |
Note |
---|
Note: For DaySaver, follow instructions in the guide guide How to configure Failover by DNS for DaySaver. |
...
Run the following command on a Failover PBX to copy user files (which are encrypted) from a Main PBX:
Code Block scp admin@<pbx A>:/etc/user.d/*.lua /etc/user.d/ or scp -P 2222 admin@<pbx A>:/etc/user.d/*.lua /etc/user.d/ - for Cloud
where <PBX A> is a domain name of a Main PBX.
Then you need to set an owner of the copied files by running the command on the Failover PBX:
Code Block chown wms:wms /etc/user.d/*lua
...