Solved 3CX Cloud local phone provisioning does not work

[assid]

My local phone is phone provisioning through the 3CX cloud server, but http displays 403, and I can access it normally on the 3cx cloud server,I need help, thanks!

 

[NikosT_3CX]

Hi, are you using SBC to provision your phone ?
Also with http this will not work, you need https since the PBX is in the Cloud and not Local.

 

[JohnS_3CX]

Local phones need an SBC in order to provision on Hosted By 3CX deployments.

See requirements and limitations here:
https://www.3cx.com/ordering/pricing/hosted-info/

 

[TekServPros1]

Fanvil phones are not provisioning with 3CX hosted. We have a few test phones (X4, X5S, X6U) that were connected and worked fine with a privately hosted PBX. We wiped the phones and have an SBC setup. The phones have the recommend firmware and the show in the dashboard as new, when you assign an ext to the phone nothing happens. The Events and Activity Log does not show any information.

 

[JohnS_3CX]

Hi @TekServPros1

The phones are only expected to work if they have been set up using the procedure in our guides. You did not mention anything so I cannot assume that the guides were followed (especially firmware and reset are the most critical):
https://www.3cx.com/sip-phones/

It's very good that the phones appear as bold in the "Phones" section, you halfway there. Let us know how you get on

 

[TekServPros1]

Hi yes, the firmware and the reset was done prior to moving the device over to the hosted 3cx version. The phone does show in bold, I have even assigned the phone to an ext, but the phone is still in bold.

 

[JohnS_3CX]

Unfortunately I cannot see that image.

Does your PBX have valid certificates?

3CX or Custom FQDN?

What phones do you use and what firmware version?

If SSL is broken it will not provision.

 

[TekServPros1]

Using Fanvil (X4, X5S, X6U), they worked fine when self-hosted. Moved to a test on the 3CX host now they will not auto provision with an SBC. All phones have the latest firmware recommended by 3CX.

We are using a custom FQDN and the certificates are valid.

 

[JohnS_3CX]

Ok with a custom FQDN, you also need to use certificates that your phones accept. For this you will have to contact the manufacturer and check their documentation, because using certs they don't include onboard the device will result in SSL failure = no provisioning.

You might also have to ensure that intermediate certs are valid across the whole chain.
This tool can help you verify, just type your {fqdn}:{https port} in and check
https://www.sslshopper.com/ssl-checker.html

 

[JohnS_3CX]

@assid since your thread has been hijacked do you still face the issue or can we close the thread?

@TekServPros1 next time open a new thread instead so we can ensure everyone gets help