Migrated 3CX to the cloud but provisioning stops

[abacusadmin]

Hi

I was running 3CX 15.5.15502.6 on Windows on-site no problems. Have migrated to the cloud using Amazon Lightsail. The migration appears to have been successful. The SIP trunk connects no problem but can't get any phones to auto-provision.

The phones are Snom 720 desk phones that were working fine on 15.5.15502.6. Yes, I know they are EOL and not officially supported but they have worked with my custom templates. I have copied my custom template and amended the URL string with the new URL that the migrated 3CX server shows for each extension.

The on-site provisioning URL before (on-site) and after (cloud) are:

Before http://my-internal-ip:5000/provisioning/my-url/cfg{mac}

After http://my-FQDN/provisioning/old.my-url - Copy/cfg{mac}

Notice how the "old " is prefixed and " - Copy" is added to the the provisioning URL.

I have changed each extension "Provisioning Method" to "Direct SIP (STUN - remote)" but this doesn't help.

I don't want to use an SBC because each of the 3CX servers I'm going to migrate to the cloud will only have a few phones and I would prefer not to have a SBC which is a single point of failure.

Thanks

 

[Saqqara]

As you have moved the server to the cloud, the url has to be encrypted so https (this is for security and can not be changed) - this is for stun or sbc phone setup.

Have you unticked ' Disallow use of extension outside the LAN (Remote extensions using Direct SIP or STUN will be blocked)' under Options for each phone.

Check the 3CX blacklist, and remove any entries.

As you are setting up the phones as stun, please follow 3CX supported method

Give each phone as static IP (can be done via DHCP)
Assigned different SIP ports , block of RTP ports to the phone.
Setup port forwarding on the router protecting the phones - so that the correct SIP , RTP ports are forwarded to the correct phone.

For example

Ext 340 - SIP Port 5065 RTP ports 14000 - 14012
Ext 350 - SIP Port 5066 RTP ports 14013 - 14025
and so on

https://www.3cx.com/3cxacademy/videos/intermediate/configuring-remote-extensions/

All info on setting up phones is here - https://www.3cx.com/sip-phones/snom-710-720-760/

Deleting existing phone config within 3CX, adding in using stun and mac address and factory defaulting the phone. After the reboot the phone should ask for username and password (just follow info in the above url)

 

[abacusadmin]

Thanks for the detailed reply.

You say " the url has to be encrypted so https (this is for security and can not be changed) - this is for stun or sbc phone setup". But when I check my now cloud-migrated 3CX server the URL is still http and not https in the Provisioning Link for each extension. How do I change it to https?

Thanks

 

[AWS2P]

URL should be something starting https, on my pbx cloud they are like :

 

[Saqqara]

When you add a brand new phone, via stun or sbc the url should be https

If your devices are not, I suggest you delete them within the 3CX management console , factory default the phones and re-add them using stun as per info here https://www.3cx.com/sip-phones/snom-710-720-760/