Hi All
We are a partner and ha've been using v16 fine for a few days. I thought I would migrate to a new server with more disk space and RAM on Amazon LightSail. I also wanted to change the FQDN to a new one e.g. xxx.3cx.co.uk to yyy.3cx.co.uk.
I did a backup, released the license key, restored the backup and everything looked fine. I had done this many times with v15 with no problems at all.
After a few minutes, the phone (Yealink) started dropping offline and giving "register failed" errors. They are running the recommended firmware for v16.
More worryingly, BLF then stopped working and nothing would get that back on, including reboots of the PBX which is running on Amazon Lightsail.
The BLFs started to not work and would show people on the phone, even when they were off. This happened with the Yealink phone as well as the Mac client, Windows client and iOS client.
I thought this may just be a fluke, so I tried it with another (much smaller) PBX which was already on LightSail and found exactly the same when I restored it to a new VM.
Going in to the handset and disabling the extension and re-enabling it gets it to re-register again, but it drops off again after a while.
Pointing the phone back to the original v16 PBX works fine and incoming calls work, however it's not possible to re-license this without a reinstall.
The problems are the same whether connecting directly or through the SBC. The issue is the same on handsets which have real IP (no-NAT) as well as NATed handsets.
I am running on Debian 9.5.
I've turned on verbose logging for the moment.
UPDATE: I have wiped the installation and restored, but using the original FQDN to see if that makes a difference.
Any help would be greatly appreciated!
John
We are a partner and ha've been using v16 fine for a few days. I thought I would migrate to a new server with more disk space and RAM on Amazon LightSail. I also wanted to change the FQDN to a new one e.g. xxx.3cx.co.uk to yyy.3cx.co.uk.
I did a backup, released the license key, restored the backup and everything looked fine. I had done this many times with v15 with no problems at all.
After a few minutes, the phone (Yealink) started dropping offline and giving "register failed" errors. They are running the recommended firmware for v16.
More worryingly, BLF then stopped working and nothing would get that back on, including reboots of the PBX which is running on Amazon Lightsail.
The BLFs started to not work and would show people on the phone, even when they were off. This happened with the Yealink phone as well as the Mac client, Windows client and iOS client.
I thought this may just be a fluke, so I tried it with another (much smaller) PBX which was already on LightSail and found exactly the same when I restored it to a new VM.
Going in to the handset and disabling the extension and re-enabling it gets it to re-register again, but it drops off again after a while.
Pointing the phone back to the original v16 PBX works fine and incoming calls work, however it's not possible to re-license this without a reinstall.
The problems are the same whether connecting directly or through the SBC. The issue is the same on handsets which have real IP (no-NAT) as well as NATed handsets.
I am running on Debian 9.5.
I've turned on verbose logging for the moment.
UPDATE: I have wiped the installation and restored, but using the original FQDN to see if that makes a difference.
Any help would be greatly appreciated!
John
Last edited:
