PBX Could Not Be Reached

[Rabie]

Hi,

I have just installed 3CX 16 with a dynamic IP Public on a Windows 10 machine (firewall disabled)
3CX Web et Desktop clients works very well on local network but 3CX Mobile client on Android doesn't working
I get the error: "Provisioning Error. PBX Could Not Be Reached"
The PBX's console management also inaccessible via FQDN or IP.

Thanks in advance!

 

[ChrisC_3CX]

I would first check and make sure that all required ports have been configured correctly: https://www.3cx.com/docs/ports/

Especially the HTTPS port for this case (default: TCP 5001)

 

[Rabie]

In localhost i can access to The PBX's console management (see attach file) and When I ping the FQDN from inside the LAN I have successfull packets with 0% loss

 

[ChrisC_3CX]

That is why I recommend looking into your firewall configuration. The fact that you can access the Management Console on TCP port 5001 when local but not when remote suggests that the firewall configuration and port forwarding required may not be in place.

To be clear I am referring to the network firewall and not the firewall running on the OS which you already disabled.

 

[Rabie]

But the firewall on windows is disabled and the remote desktop client work perfectly

 

[ChrisC_3CX]

The Windows Firewall is most likely not the issue here, but the network firewall is. If for instance this is a home environment and you are using a home modem/router you will need to configure the ports mentioned earlier on there as well. You must get it to a point where you can reach the Management Console from a remote location(you can test with your mobile data connection) and then, once this has been taken care of, try the 3CX mobile clients again.

If you need additional assistance with this I would highly recommend that you contact one of our 3CX Partners.

 

[Rabie]

Thank you very much.