Fqdn problems after upgrade

[godskitchen]

Hello all,

I am trying to upgrade a clients 3cx server (local hosted) to V 16.

They were on v12.5 (yes, it should have been done before now but was out of my control)

I have got the installation up to V 15.5 SP6.

During the installation and restore of the system (upgrade path 12.5 - 14 - 15.5) I got a warning that the licence would not allow use of a 3cx Fqdn. I did not have time to mess around as the system is in use 24/7 and I chose the option that let me proceed.

The message also said to contact sales....

The licence was an 8 channel standard, it is now listed as Professional Annual.

Does anyone know what I need to do? Any advice greatly appreciated.

 

[Saqqara]

I think the message says it - you need to contact sales

 

[TBWD]

Since V15 the licence is tied to a FQDN, not so before V15, the licence is invalid for updating, my guess, you will need to purchase a new licence, IE Contact Sales

 

[godskitchen]

Thanks for the replies.

Yes, I had thought I might need to contact sales but wanted to see if anyone had come across this before and maybe I was missing something simple.

The client is not using any of the "Pro" features and never have, it was just that at the time they thought that would fit their needs best.

As such (I intend to move them to v16 ASAP) could I not just use a new key for the free edition in place of the existing key? If I have to change the fqdn then so be it, it was only created yesterday.

 

[AWS2P]

could I not just use a new key for the free edition in place of the existing key? If I have to change the fqdn then so be it, it was only created yesterday.

If you need only STD license then yes ask with new email adress a new key, On old PBX do a backup without key and FQDN and restore it on new PBX.

 

[TBWD]

Using the Standard Edition will require a 3cx FQDN, and you should be able to put in a new licence key