How to configure Failover by DNS for DaySaver

This document outlines steps that are required to configure failover by DNS for DaySaver.

Created: October 2021

Updated: November 2021


DaySaver documentation:

Note: This configuration is supported starting from WMS 5.04 Beta.

  1. First of all, you need to reset the DaySaver:
    1. Open the DaySaver web interface 
    2. Go to System -> Backup/Restore/Upgrade -> Backup/Restore
    3. In the section Reset to defaults, tick off all the options and click Reset

      Important: If DaySaver firmware is lower than v., before proceeding with the configuration, go to DaySaver web interface -> Network Settings -> disable the option Disable Private Internets(RFC2918) DNS responses -> save the settings, and reboot the device. 

  2. Disable limitations for DNS queries on the Main PBX. Consult the following documentation on how to do it: /wiki/spaces/DOC/pages/30279583
  3. Check the provisioning file /rw2/etc/provision.conf and in case it contains the parameter FailoverByDns=yes, change its value to ‘no’: FailoverByDns=no, consult the documentation for details: Provisioning Custom Settings
  4. Provision DaySaver to PBX in an automatic mode (Auto-provisioning), documentation: Provisioning of Wildix devices - Admin Guide

    Note: Sometimes you may need to wait for up to 5 minutes before DaySaver gets provisioned. 

  5. Configure the following settings in the WMS:

    1. In WMS -> Devices, select the DaySaver and click Edit
    2. Fill out DNS server fields as mentioned below:

      • DNS Server: enter the IP address of the Main PBX 
      • Secondary DNS: enter the IP address of the Failover PBX

    3. Enable the checkbox Use received IP and click Save
    4. Click Configure/ Sync the device for the DNS settings to apply
    5. Wait for 1 or 2 minutes and go to DaySaver web interface and reboot the device

  6. In the provisioning file /rw2/etc/provision.conf, add the parameter FailoverByDns=yes and the section [daysaver]
  7. In WMS -> Devices, click Configure/ Sync the device again. The device should reboot. If it doesn’t, reboot it from its web interface
  8. Check SIP configuration on the web interface of the device: the SIP Server Address and Outbound Proxy Address fields should contain the domain name