Problem with Provisionning

[Francois86]

Hi,
I have a problem with provisionning on my 3CX installation.
My 3CX server and phones are in the same LAN.
I captured packet during the provisionning, and I see a error 403 Forbidden.
Do you think that this error is the origin of my provisionning problem ?

In the nginx.conf, I have this config :

server {
[...]

allow 192.168.0.0/16;
allow 172.16.0.0/12;
allow 10.0.0.0/8;
allow 127.0.0.1;
allow ::0/0;
deny all;

My lan is in 192.22.0.x/24.
Do you think that I must add this range in the file nginx.conf ?

Somes informations about my config :

• 3CX Version, Pro Annual 16.0.8.9
• Server OS, . Debian 9
• Is the 3CX Server Hosted and where? Hosted in my local network
• IP Phone Make/Model/Firmware / Yealink T54W 96.86.0.5
• Provisioning Method: Local
• Trunk Provider : Alphalink
• Has the Firewall Checker passed: YES
• Are custom Phone Templates being used: NO

Thanks for you help,
François

 

[cobaltit]

No, you don't want to be editing the nginx config. That would create an unsupported configuration. What you should do is fix your network to use a proper RFC1918 private network range.

https://en.wikipedia.org/wiki/Private_network

 

[Francois86]

I change my ip network in 192.168.181.x/24 but I have always the same problem.
I have an error 403 on the request provisionning since the phone.
Are you an another idea of my problem ?

 

[CloudAware]

The first thing that springs to mind is that the https configuration is not the same as the http configuration. I would guess the https configuration is generating the error and the http configuration is only doing a https redirect.

 

[JohnS_3CX]

Hi,

- Is the PBX in 192.168.x.x ? If not then please do so

- Have you restarted the PBX after changing the network to 192.168.x.x? If not, then do so then log into the management console and fix the error that will appear (tell the PBX to learn the new IP)

- Once both the above have been done, then install 1 phone on 192.168.x.x and reset it. You should now finally be in a supported scenario, and that phone should provision

NOTE: Do not edit the nginx conf, if you have and did not keep a backup of the file, then remove 3CX entirely and reinstall it fresh after you have fixed the network to be RFC1918 compliant ie. 10.0.0.0/8,169.254.0.0/16,172.16.0.0/12,192.168.0.0/16

 

[Francois86]

Hi,

I resolved my problem temporary to allowing my network in the nginx.conf.
I know that it's not the better solution, but now the provisionning is working.

I will planner the changing of my network with a good private network.

Thanks all for your help,

François