Can not provision new device

[ionut]

When you factory reset a Fanvil phone the default time server values are "time.nist.gov" and "pool.ntp.org". If the phone cannot contact those either because they are blocked by the firewall or because the DNS is not resolving correctly then the phone cannot validate the validity of the certificate and provisioning will fail. If you use your own time server then you need to apply the settings into the phone and then try to provision.

Thank you. Yes, the environment is isolated, the IPs aren't NATed.

 

[Vassilis Mitropoulos]

Hello mate,
I put the same time server in the PBX and the ip phone device but the device did not reboot after provision so the process isn't able to complete.

 

[YiannisH_3CX]

I put the same time server in the PBX and the ip phone device but the device did not reboot after provision so the process isn't able to complete.

I do not think you have the same issue as @ionut. Are you able to provision other devices or is the issue only with Fanvil devices?

 

[Vassilis Mitropoulos]

I do not think you have the same issue as @ionut. Are you able to provision other devices or is the issue only with Fanvil devices?

I tried only with Fanvil. I don't have other devices.

 

[YiannisH_3CX]

Try it with a 3CX client and let us know if that is working. Download it and run it on a PC in the same network. Let the client start without configuration so it appears under the Phones tab as a new device. Try to assign that to an extension and see if that is working.

 

[Vassilis Mitropoulos]

Try it with a 3CX client and let us know if that is working. Download it and run it on a PC in the same network. Let the client start without configuration so it appears under the Phones tab as a new device. Try to assign that to an extension and see if that is working.

Neither that way provision works

 

[YiannisH_3CX]

Neither that way provision works

Then i would suspect the reason the provisioning fails is different and not related to Fanvil devices. In this case like i mentioned before you will need to run a wireshark capture while trying to provision to see why it is failing.
What is the local IP range you are using? Also your provisioning link includes the local IP of FQDN?

 

[Vassilis Mitropoulos]

Then i would suspect the reason the provisioning fails is different and not related to Fanvil devices. In this case like i mentioned before you will need to run a wireshark capture while trying to provision to see why it is failing.
What is the local IP range you are using? Also your provisioning link includes the local IP of FQDN?

The local ip range is 150.81.1.XXX and yes the provision link includes the local ip of FQDN.
I don't know if there is something must be changed in the nginx.cfg file

 

[YiannisH_3CX]

Please note that the IP range 150.81.1.XXX is not a valid IP range as per RFC1918 and that is why you cannot provision a local device.
https://www.3cx.com/3cxacademy/videos/basic/installing/

 

[Vassilis Mitropoulos]

At the parameters and in the LOCALSUBNETS I have added the the local IP of our network. Also before the upgrade of our PBX provision works fine without this problem.