- Joined
- Sep 14, 2018
- Messages
- 4
- Reaction score
- 0
Currently on v16.0.4.493, hosted at OVH, Debian 9, with an SBC in our main office.
We've been having issues with conference calls with China (garbled on a Yealink CP360, SBC connected, Voxtelesys SIP, US attendees don't seem to suffer), so TPTB want me to move the PBX to another hosting service, Azure.
It looks like I need to back up the current of all except License Key Info, deactivate the current PBX, create a new server at the other host, install, restore, update DNS and activate.
But the documentation appears to be for earlier versions? For instance, how do you really deactivate the current license in v16? I've looked at Settings, License, but my best guess is the Manage License Key, Keys, and for FQDN, Release? Will this deactivate the PBX so that I can create a new one? And will I be able to create the new server, using the same FQDN? I would like to minimize the impact on our phone system as much as possible. Any suggestions are welcome, especially from anyone who has already done this.
We've been having issues with conference calls with China (garbled on a Yealink CP360, SBC connected, Voxtelesys SIP, US attendees don't seem to suffer), so TPTB want me to move the PBX to another hosting service, Azure.
It looks like I need to back up the current of all except License Key Info, deactivate the current PBX, create a new server at the other host, install, restore, update DNS and activate.
But the documentation appears to be for earlier versions? For instance, how do you really deactivate the current license in v16? I've looked at Settings, License, but my best guess is the Manage License Key, Keys, and for FQDN, Release? Will this deactivate the PBX so that I can create a new one? And will I be able to create the new server, using the same FQDN? I would like to minimize the impact on our phone system as much as possible. Any suggestions are welcome, especially from anyone who has already done this.