This document should serve as a guide if you are selected to move to a different primary Geo-redundant node.

What to Expect

Most of the changes need to be done by the SkySwitch Team, few changes will be required on your end. There will be zero-minimal downtime (in the case where devices need to reboot).

  1. We will make DNS Record Changes to point your devices to the new primary (and secondary) node. Devices that are currently provisioned to NDP should move over on their own after the DNS records are changed. Some devices may require a reboot for the changes to take effect.
  2. We will set your dashboard account to utilize your new primary node, so you will still be able to see active calls.
  3. We will re-direct your inbound DID's to first route to your new Geo-Node. In the case where a device does not move over, Inbound calls will still route over to server where the phones are registered.
  4. We will email you a list of devices that did not move over automatically. Any manually configured devices that aren't setup to use the DNS SRV Record {reseller-id}.hpbx.outboundproxy.com (ie. 15611.hpbx.outboundproxy.com) will need to be reconfigured manually.
  5. If you are not already utilizing this our current the following DNS CNAME Format- You will need to re-point your Branded Portal CNAME record to {reseller-id}-hpbx.dashmanager.com (ie. 15611-hpbx.dashmanager.com). Using this format will automate any future changes.
  6. You will need to ensure your trunks and devices are allowed to receive traffic from the new Geo-Node. This will usually be important where trunks are doing IP Authentication on your side.