Issues activating my NFR license

[MartinPosse]

Hello
Today I had to move my pbx from AWS to OVH. I installed it on a Debian 9 VPS and after the full restore and activation, I was unable to receive and send calls. Some troubleshooting later and comparing my own installation with a second one I have for a customer, I determined the only difference was the OS version (second installation is on Debian 8).
So, I redeployed the server using Debian 8 and installed the pbx again, but when getting to the license key section of the configuration wizard, now it tells me that the key is for a different version of the PBX.
The key is for version 16, and I am guessing the default packages that you download are from v16 as well, so I don't understand the problem.
Additionally, I created a Free Trial, which generates a v16 key, and this one is also unable to be activated.
I am currently down with my phone and unable to obtain something that could help online.
Has anyone experienced this? Is support watching these posts?

Thanks!

 

[Saqqara]

You can not run license keys for ver 16 on version 15. When you use a 15.5 license key in version 16, the key is automatically upgraded.

As you have installed Debian 8, guessing your are running a very old version of 3cx

You need to reinstall using Debian 9 and 3cx ver 16.

Do not understand why you installed Debian 8

 

[MartinPosse]

I installed debian 8, because I was having problems with the pbx receiving and issuing calls, there is no support from 3cx anywhere and the only reference I have is another pbx in the same cloud vendor whose only difference is the os version (all other configurations the same).

 

[cobaltit]

https://www.3cx.com/docs/recommended-hardware-specifications-for-3cx/
https://www.3cx.com/docs/manual/
https://www.3cx.com/docs/manual/
https://helpdesk.3cx.com/support/home

No support from 3CX anywhere? There's guides all over the place. Your initial problem with being unable to make/receive calls could be any number of issues. If you are using the 3CX FQDN there is a 6 hr TTL for updates. There's no mention of whether your SIP trunk was registered or not nor whether make/receive calls was external calls or internal or both. But that could be that your SIP trunk provider is IP authenticated and needs to be updated/advised of your IP change.

 

[YiannisH_3CX]

Hello @MartinPosse

Please note the V16 does not work with Debian 8 so i am guessing you installed a earlier version of the PBX which caused the licence error.
I would recommend installing Debian 9 and V16 again to bypass the licence error and see if you still have the audio issues.
Then we can help you figure out what is causing that.