| 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: 3.86 Created: December 2017 Updated: October 2018 Permalink: https://confluence.wildix.com/x/dABuAQ |
...
- Configuration sync: all changes must be applied only to Configuration Source PBX
- Supported devices (devices that support double registration):
- WP, Vision (WP600AXX starting from v. 2.8.22)
- W24FXSR2/W04FXS/W02FXSR2 (except for W01FXS – pre 2015)
- W04FXO
- PRI
- BRI
- Collaboration (WEB phone)
- 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
| Device | Main SIP server | Failover SIP server | Timeouts (s)(switch to backup / main) |
|---|---|---|---|
| WP | TCP / 443 (*) | TCP / 443(*) | 60-105 / 60-105 |
| WP2015 | TCP / 443 (*) | TCP / 443 (*) | 30-60 / 10-60 |
| Vision | TCP / 443 (*) | TCP / 443 (*) | 60-180 / 15-45 |
| W24FXSR2 | TCP / 443 (*) | TCP / 443 (*) | 40-45 / 30-90 |
| W04FXS | TLS / 443 (*) | TLS / 443 (*) | 30 / 45-300 |
| W02FXSR2 | UDP / 5060 | UDP / 5060 | 30-60 / 10-30 |
| W0XPRI | TCP / 443 (*) | TCP / 443 (*) | 10 / 30-180 |
| W01/02BRI | TCP / 443 (*) | TCP / 443 (*) | 10-60 / 60-180 |
| W04FX0 | TLS / 443 (*) | TLS / 443 (*) | 30 / 45-300 |
| WP600AXX | TLS / 443 (*) | TLS / 443 (*) | 60-180 / 15-45 |
| Android clients | TLS / 443 (*) | TLS / 443 (*) | active: 60-180/ 15-45; in background: switch immediately |
(*) – Alternative or default secure port 443 can be used
...
- 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 PBX configuration:
- Access the failover PBX via SSH as root
- Run shell script sync_pbx
- Select 1 (Configure)
- Enter IP of the Main PBX
- Enter the admin password of the Main PBX
- Set failover PBX as secondary DNS server on unsupported devices
...
Per-Service or Mixed mode
- Server PBX is of Per-User type: you can can activate X Client PBXs and share those licenses as described in the previous chapter. Additionally you can add standalone PBXs, but each PBXs will have its own licenses of Per-User or Per-Service kind.
- Server PBX is of Per-Service type: in this case all PBXs must have their own licenses (each PBX handles its own users).
| Html |
|---|
<div class="fb-like" data-href="https://confluence.wildix.com/x/dABuAQ" data-layout="button_count" data-action="recommend" data-size="large" data-show-faces="true" data-share="true"></div> |
...