3CX Phone System lost FQDN

[imediasystems]

Hi together,

a 3CX Phone System of a customer lost the FQDB as it was not updated to 15.5 SP6 in time. The 3CX itself still shows the FQDN but in the Customer Portal the FQDB and IP are "released". To backup the 3CX without "FQDN and License-Key" and restore it didn't help. "Refresh License Key Information" or clicking "Edit" in the "License Settings" and then clicking "OK" without changing anything didn't help.

As this is a productive environment, a reinstallation of the whole System would be a nightmare. Is there any chance to reactive the ....3cx.de FQDN, without reinstallation?

Regards,
Andreas

 

[imediasystems]

Is there no one who has a tip? Possibly someone from 3CX directly?
@JohnS_3CX ?

 

[JohnS_3CX]

Hi @imediasystems

FQDN binding will occur either:

a) during a brand new fresh installation
b) during a fresh installation with backup restore (without key and and FQDN)

If you simply restored the backup from the management console of the existing system, it will not work as this does not trigger the FQDN binding process. I don't think you will be able to avoid re-installation and reprovisioning at this point..

 

[commercial1]

Had this the other week and we had to install a new instance using a new fqdn and restore data back.

 

[imediasystems]

Hi @JohnS_3CX,

there is no option to trigger that process, at least for a existing FQDN? The FQDN is still configured in the PBX itself but not at your servers.

As my customer is paying for maintenance I would expect a bit more professional services from your side. Especially because neither the customer nor I as a 3CX partner received any information before the FQDN was released.

Regards,
Andreas Fink

 

[JohnS_3CX]

Hi Andreas,

Since the FQDN was released there are no other options now unfortunately, you will have to reinstall using your backup (minus key & FQDN) select a new FQDN at that point.

We informed everyone who were active customers that they must upgrade to V15SP6 otherwise they will lose the ability to contact the activation servers, which include the FQDN. It is released after 60 days of no communication with the activation server, and given that SP6 was released last August we gave enough time for everyone to be on the last supported version in order to ensure smooth operation
https://www.3cx.com/docs/fqdn-management-allocation/#h.9wczlzx5rbke