Solved Trade in Questions from perpetual to Annual with custom FQDN

[Mocabi]

Hi there,

I have a 3CX system running with my own FQDN not the one provided by 3cx.
Our system is on perpetual and was running fine after the maintenance expired as we only simply used for in house PABX. Our FQDN SSL is running from Let's encrypt and we were told that it will be off by this Summer 2020. So we may head back to continue with the annaul license instead.

Now that we have decided to trade in the license to an annual type. However, we are not sure whether do we need to reinstall the system first to obtain the FQDN from 3CX? or we can simply just hit the convert button?

 

[AWS2P]

Do a backup without FQDN ticked , then you will need to reinstall and restore your backup during reinstall.
It takes less than a quater to do complete change. Then you will have to wait for new FQDN provided by 3CX to be DNS propagated, time depends on which kind of license you have STD and PRO takes 6hours , ENT 6 min.
Phone provisioning needs to be done for remote users

 

[Mocabi]

Many thanks for your kind support.
So it looks like a new installation but the license information will be not back up? can't seem to uncheck only FQDN option?

 

[AWS2P]

Not completely sure about steps you have to follow , so wait for 3CX Staff advice @JohnS_3CX

 

[Mocabi]

Thanks. I will be waiting too

 

[StefanW]

Hi @Mocabi

the things are a bit unrelated from the point of license. Let's untangle it.

Your perpetual license is a version 16 Update 3 but with expired maintenance since 2019.
I suggest trading-in your license as the current one is stuck on this version and cannot be upgraded anymore as it is not covered by software insurance. If you take our offer now, you get 2 years from the moment of your trade-in and until May 2022 you can upgrade to all versions we publish.

In terms of FQDN there are problems regardless of being an own FQDN or one from 3CX. I see a custom FQDN bound to your license but your PBX answer with an expired 3CX FQDN which used to be assigned to you. What happened with the PBX I cannot tell . Managing your own SSL certs is always an administrative task which you can delegate to us and I recommend doing so. But this needs fixing. I see in our system that you are linked to a 3CX Partner. Do you maintain still contact over your 3CX installation?

 

[craigreilly]

This is great - 2 year license to upgrade from a Perpetual to an Annual.
Just did mine... so happy I saw this (and my reseller).
Just refreshed the license after accepting the conversion. All updated.

Thanks @cobaltit

 

[Mocabi]

@StefanW

Noted with many thanks.
we will discuss with the local partner to reinstall and obtain the 3cx FQDN instead. then proceed to the trade-in option.

 

[Mocabi]

had managed to release the FQDN and trade in successfully. now system is back to normal.
thanks a lot for all your kind support and advised!