Remote extensions with public IP

[Varun Bhagaloo]

Has anyone been able to successfully connect remote extensions using the 3CX server's public IP?

We have a customer on a perpetual standard license that's about to reach the one year mark and they'll loose the FQDN, and the latest version of 3CX does not allow custom FQDN.

 

[Evolute IT]

Has anyone been able to successfully connect remote extensions using the 3CX server's public IP?

We have a customer on a perpetual standard license that's about to reach the one year mark and they'll loose the FQDN, and the latest version of 3CX does not allow custom FQDN.

The latest version DOES allow for custom FQDN. Just pay for a Pro or Enterprise edition. If it's a perpetual, you can trade-it in to get a Annual license for V16.

 

[Saqqara]

Is this a commercial perpetual standard license, is so why not pay for maintenance then you can get updates, keep 3cx fqdn, and ssl certificates.

 

[leejor]

Contacting the server should not be a problem. Auto-provisioning a set probably will be. Try manual provisioning a set/ATA, using the public IP, and see how it goes. I would also advise, seriously considering, the previos sugestions.