Fanvil devices not showing up on "Phones" for provisioning

[3CXfan]

I need help on how to get 3CX to detect my Fanvil phones which are not showing up on "Phones" list after following the instructions on this page to factory reset them successfully.

• 3CX Version, Standard Annual 16.0.9
• Server OS, Windows 10
• Is the 3CX Server Hosted and where? Not Hosted
• IP Phones:
  • Fanvil X210 v2.2.13
  • Fanvil X4U v2.2.13
• Provisioning Method: Local
• Has the Firewall Checker passed: YES
• Are custom Phone Templates being used: NO

These phones were previously auto-provisioning to 3CX successfully and they still reside on the same subnet. I had to reset them because of the need to change extension number. But after factory reset, they are not recognized by 3CX anymore.

Everything that I have done so far:

1. I have checked that multi-cast address 224.0.1.75 is active on my single NIC following instructions on this page.
2. I ran Firewall Check and everything still passed
3. Rebooted Windows
4. Unplugged and plugged in IP phones
5. Verified no settings on router, switches have changed
6. Verified that 3CX and phones are on the same subnet

Am I missing anything? Should I factory reset the phones again? Would that help?

 

[nub]

dhcp option 66 ?

 

[3CXfan]

dhcp option 66 ?

There are no DHCP Option 66 related instructions posted by 3CX for Fanvil phones, which all support PnP so I would not know where to begin and according to 3CX on this page: "Manual configuration of IP phones is impractical and leads to many errors so 3CX will provision your phones automatically"

So I am at a loss as to what to do next.

 

[cobaltit]

So you didn't need to reset them to change the extension number. Simply removing the MAC from one extension and then adding it to the other and rebooting would have reassigned them.

But clearly something did change otherwise things should work. How were the phones provisioned before? Are the phones on the current 3CX supported firmware?

 

[ChrisC_3CX]

As @cobaltit mentioned, do make sure that you are running the correct firmware on the phones as for example the Fanvil X210 should be running firmware version 2.2.11 not 2.2.13.

I would recommend factory resetting again once the correct firmware version has been installed.

 

[3CXfan]

As @cobaltit mentioned, do make sure that you are running the correct firmware on the phones as for example the Fanvil X210 should be running firmware version 2.2.11 not 2.2.13.

I would recommend factory resetting again once the correct firmware version has been installed.

First of all, I finally got all my factory reset Fanvil phones to show up by using Fixed IP to on the Gateway to assign a new IP than using the old one. Somehow 3CX just couldn't detect these as newly reset phones on the previous IPs.

I did upgrad all my Fanvil phones to the latest firmware version immediately just now but how come they showed up as "New" again requiring provisioning and assigning to specific extensions? I literally just assigned them earlier this morning. Does provisioning not survive firmware upgrades?

 

[Alphabetic]

Correct method to provision via PNP is outlined here:

https://www.3cx.com/docs/manual/configuring-ip-phones/

Connect the phones then assign the EXT so 3CX will send the phone the prov link.

Unless you have specified your provisioning link in DHCP option 66, the Fanvils wont know where to get it's config file from until 3CX tells it (push it out via assign ext) or it gets it from opt 66.

Though, if you look at the provisioning page in the fanvil phone you will see the option is set to "update after reboot" so you may find rebooting the phones will pull the config.

 

[3CXfan]

Alright, after I updated all my Fanvil phones again to the latest supported firmware versions, then the phones show up provisioned on Phones list.

This is so strange because I just updated all the firmwares yesterday too. Does the "Firmware" button on 3CX not update firmware to the latest supported version in one step? Do I have to usually update firmwares multiple times? Unless maybe a new version just got pushed out between yesterday and today coincidentally?

 

[NickD_3CX]

Hi!

No, 3CX will give you the latest supported firmware that 3CX has available at the time. It just so happened though that yesterday we made a new Fanvil firmware available for certain models (fw v2.4.7), that is probably why you saw a new firmware again.

 

[ThomasLeeIV]

Hi!

No, 3CX will give you the latest supported firmware that 3CX has available at the time. It just so happened though that yesterday we made a new Fanvil firmware available for certain models (fw v2.4.7), that is probably why you saw a new firmware again.

Are there release notes or is there a changelog for new firmware releases?

 

[NickD_3CX]

For a precise changelog you will have to contact the vendor.

From a 3CX perspective there were a few fixes relating to BLFs, which we updated a few posts earlier for.

 

[3CXfan]

I can confirm that after upgrading to latest firmware on my 7 different Fanvil phones, all issues have been resolved.

 

[ThomasLeeIV]

This is a 3CX specific firmware update as the vendor did not release this update in their main branch, so I can't imagine 3CX approves this without documentation of the changes.

All our Fanvil devices get flagged in red and shown as "Not Supported" which implies an urgency to update that may or may not be supported by the quantity and type of firmware changes (i.e. features vs bugs vs security patches).

As an example, the only visible update we have found is a change to the number of BLF screens available on an X6u -- a valuable feature, but a confusing one for users who are familiar with only having 2 pages.

I'm not trying to sound whiny, but it's hard to cross my fingers and blindly update 75-100 users to an unknown firmware.

 

[cobaltit]

Then don't?

Feel free to update one or two users and monitor. At the end of the day even if there was a change log that doesn't imply some other undocumented bug didn't show up. So test by whatever testing methodology makes you feel comfortable. If everything works as-is, then leave it be. But if you contact support step one will be to ask you to update firmware.