provisioning errors

[IT Zero]

I have a strange problem......I have 3 x Fanvil phones (X5U, X5U-V2 and V64) that were originally provisioned as Stun on our 3cx instance. We have an SBC with 1 x Snom 760 behind it.
I noticed the Fanvils were not behind the SBC and were provisioned as STUN. I have deleted the phones from the users and reset the phones, but the 3 Fanvils DO NOT show up on the phone tab of the 3cx console.
I have tried a brand new Fanvil and Snoms which all show up in bold under the phones tab in 3cx (V18).
I have restarted both the SBC and the 3cx lightsail server (To clear any Cache of MAC addresses?)
Still nothing

We are getting this error in the logs:
Provisioning file /provisioning/0x1rwdf7xd734/firmware/fanvil/version.txt requested by 217.155.103.190 could not be generated
3CX Template Parser ID: 30040 02/10/2023 12:57:57 PM

The phone seems to 1/2 provision, however on the phone GUI i get a timeout on the line page in red

who is going to save me?

 

[JohnS_3CX]

Hi,

Firstly, look at your IP blacklist and ensure their IPs are not blacklisted.
Now factory reset them again. You must be absolutely sure that they were indeed reset:
https://www.3cx.com/sip-phones/factory-reset-fanvil-x-series/

What do you mean by half provisioned, what did you see there exactly that led you to this?

 

[IT Zero]

to reset them i kept my finger on the OK button for 5 seconds, which reset them. When i followed this article, the phone goes into recovery mode, and not Post Mode.

When i say half configured, the phone seems to get the settings, but im getting the template error in the logs of the 3cx console AND the phone wont register the line. When i switch the phone back to STUN in the 3cx management console, it seems to work fine.

 

[JohnS_3CX]

Provisioning file /provisioning/0x1rwdf7xd734/firmware/fanvil/version.txt requested by 217.155.103.190 could not be generated
3CX Template Parser ID: 30040 02/10/2023 12:57:57 PM

Ignore this - it is entirely irrelevant (for 3CX) and it will go away in the next firmware release. We are aware of it and it shows up even on healthy phones that provision just fine.

When i say half configured, the phone seems to get the settings, but im getting the template error in the logs of the 3cx console AND the phone wont register the line. When i switch the phone back to STUN in the 3cx management console, it seems to work fine.

Ok this is more specific, so you see the account details provision (ie. the logo background changes, the extension name appears correct?) but the phone does not register. This is what we need to look at in detail.

1. Check that the phone firmware is the latest that appears here: https://www.3cx.com/support/phone-firmwares/
2. Check that you have only a single SBC on 3CX, and that it appears green (registered).
3. If you have more than one SBC, edit your extension that failed to register and check that it has indeed been set to SBC mode, and that the correct SBC exists in the drop down menu.
4. You might have to reprovision the phone by rebooting it if you needed to make any corrections
5. When done, you can log into the phone web interface, look at the SIP Proxy, and confirm that it has the same LAN IP populated there as your SBC machine.
6. It should go without saying, but the SBC machine must be on the same LAN and IP range as your Fanvils otherwise the phone will find it impossible to register
7. Just in case - ensure that the LAN where the phones live does not have DHCP Option 66 sending them towards an erroneous provisioning server!

Let me know if the above helps!

Side Note: The reset guide is specific per model, ie. the X5 method only works for X5. If you try on X5U-V2 it will go to Recovery because different model generation, different behavior. The OK button method should work just fine though!

 

[sigmaIT]

I seem to be having similar problem tried to configure 2 fanvil v65's on different networks as router phones. both get message sip register failed after provisioning, hard reset one and removed it from 3cx, now it wont provision at all even with stun. The one that was reset asks for the extension and pin but now reports upgrade failed when entered.

 

[JohnS_3CX]

I seem to be having similar problem tried to configure 2 fanvil v65's on different networks as router phones. both get message sip register failed after provisioning, hard reset one and removed it from 3cx, now it wont provision at all even with stun. The one that was reset asks for the extension and pin but now reports upgrade failed when entered.

You gotta make sure you have the correct firmware installed first. Have you checked our new guides? They have been entirely re-written

 

[sigmaIT]

Configured an SBC on a windows computer and this allowed the reset v65s to connect, not optimal but no choice

 

[JohnS_3CX]

Configured an SBC on a windows computer and this allowed the reset v65s to connect, not optimal but no choice

I think you either didn't have the correct firmware (mandatory for Router phone mode) or maybe you did not set them up as router phones from the Web Client?

I can confirm that the V65 works correctly when I test it here from my end.

 

[sigmaIT]

Firmware was verified numerous times, got yellowgrid involved who provide us with some 3cx support, they couldn't see any problem, the sbc on the trunks page was added automatically as it was added correctly. Set up an x4u v2 as a router phone on another install without any issues.

 

[JohnS_3CX]

Any chance that the MAC had a typo? That's pretty much the main thing that would prevent the login prompt from popping up.

Feel free to send me a private message with your MAC and FQDN and I can take a quick look.

 

[sigmaIT]

Ok finally got to the bottom of the problem, 3cx allows router phones to be provisioned if they are on wifi using the ethernet mac address, but once provisioned they simply will not register.
In addition using the wifi mac address asks for the user and password when booted but does nothing after that. This really does need to be made clear in the documentation that router phones can not be used in wireless offices. Tested on 2 v65s and a t53w, using a cable solved the problem instantly.

 

[JohnS_3CX]

Just to clarify as we did on other forum posts too: We do not support using IP phones over WiFi.

We only test and support them over LAN.