Page Comparison

<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>

...

• 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)
  • 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

...

• 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

...

• 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
• Pre-answer services do not work after switch to failover PBX
• 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
• Login/logout via 99 service is restricted for failover user
• Language and region settings are not synced during sync_pbx script execution

...

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).
  
  

<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>

...