Solved Unable to provision phones on an SBC - New Network

[Alphabetic]

Debian Hosted
18.0 U6 Build 908
Firewall test passing

SBC is a Pi and is registered. 18.1.36
Can see the phones in the tab but when assigning, nothing happens.

floods of entries for Provisioning file /provisioning/xiipiikcsa6n/TcxProvFiles/3cxProv_8J5PHUNzzzz426.xml requested by <IP> could not be generated

Phone is asking for username and password.

Sent "assign ext", phone flashes then provisions.

I have configured option 66 in DHCP for provisioning so dont know why it isnt pulling..

thus far i've managed to get 2 phones connected to the SBC after moving location.

 

[JohnS_3CX]

- Upgrade to U7, it removes the need for username / password during provisioning and allows them to provision automatically after a factory reset. Option 66 becomes unnecessary.

- If you were using this in the Anti-Hacking module then each phone will have a unique URL (which would mean Option 66 was not working)


- The phones must absolutely be factory reset, otherwise they will carry over outdated information.

- Check the IP blacklist, that's a major one, provisioning will be denied

- The error message you mentioned above does not look like anything that known 3CX phones would ask for. I suspect that is either unrelated, or a misconfigured option 66 (again, not needed in U7 autoprovisioning via the new RPS features we introduced).

 

[Alphabetic]

- Upgrade to U7, it removes the need for username / password during provisioning and allows them to provision automatically after a factory reset. Option 66 becomes unnecessary.

- If you were using this in the Anti-Hacking module then each phone will have a unique URL (which would mean Option 66 was not working)
View attachment 34860

- The phones must absolutely be factory reset, otherwise they will carry over outdated information.

- Check the IP blacklist, that's a major one, provisioning will be denied

- The error message you mentioned above does not look like anything that known 3CX phones would ask for. I suspect that is either unrelated, or a misconfigured option 66 (again, not needed in U7 autoprovisioning via the new RPS features we introduced).

I think the new sonicwall filtering was causing some network trouble as the phones eventually provisioned.