Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.



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>

...

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

...

Warning

Important!!! This DNS configuration can be applied only to Wildix devices that support double registration (e.g. Wildix phones of WP4X0 series. The full list of devices can be found in Currently supported features & scenarios section, "Supported devices"). On other Wildix devices (check the list in Current limitations/ special configuration section, "Unsupported devices") set up DNS Server = IP address of Main PBX; Secondary DNS: IP address of Failover PBX.

...

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>

...