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>

...

 <div class="lang-box-pdf">
	<div>
		<div class="google-lang">
			<div id="google_translate_element">
			</div>
			<script type="text/javascript">
					function googleTranslateElementInit() {
						new google.translate.TranslateElement({pageLanguage: 'en', includedLanguages: 'de,es,fr,it,nl', autoDisplay: false}, 'google_translate_element');
						}
			</script>
			<script type="text/javascript" src="//translate.google.com/translate_a/element.js?cb=googleTranslateElementInit"></script>
		</div>
		
		<div class="pdf-button">
			<a href="https://confluence.wildix.com/spaces/flyingpdf/pdfpageexport.action?pageId=23986292" alt="Convert to .pdf" title="Convert to .pdf"><img src="https://confluence.wildix.com/download/attachments/14549012/pdf-button-download-wildix-documentation.png"></a>
		</div>
	</div>
</div>

...

Requirements

• Minimal WMS version 3.86
• 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

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 

Anchor
Supporteddevices Supporteddevices

All the devices that support double registration:

...

• 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

...

Make sure all WP phones can resolve the domain pbx.wildixin.com as the local PBX IP, otherwise BLFs, Voicemail Notifications and DND Status will not be shown on the device.

...

• 9 sites connected via WMS Network
• Server PBX installed in Data center in the Netherlands
• 8 client PBXs installed in:
  
  • Germany
  • France
  • Italy
  • Spain
  • Hungary
  • Poland
  • Russia 
  • China - Hong-Kong
    
• All the configuration is made on the Server PBX (users, devices, Dialplan, call groups...)
• The script running on each client PBX regularly copies the configuration from the Server PBX

• Server PBX has no active load (no calls) in this scenario, all the calls pass through client PBXs

• In case any of the client PBXs goes down, the Server PBX takes over 

Current limitationslimitations 

• 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

...

• 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

  
  

...

...