Unsupported Fanvil i16sv Video Door Intercom Won't Provision

[Rich1236584]

Hi all, we have a Cloud-hosted 3CX instance and can't get the Fanvil i16SV intercom to provision.

Local SBC deployed on-prem/ Firewall all checks out with no issues. All other phones are provisioned with no problem.

The Intercom show's up within the phone tab however the options to "Add Ext" or "Assign Ext" won't select/greyed out as shown in the attached screenshot.

Any idea's how to get this working?

Thanks
Rich

 

[JohnS_3CX]

Hi Rich,

I'm afraid that is not an i16SV or i16S (the models we support).

You have an i16V apparently, and we do not support that model (hence why "Add Ext" or "Assign Ext" won't are greyed out).

Also, I see it being reported with non RFC1918 IP address, that might mean you also have some network issues to figure out, but that would be a different discussion altogether.

 

[Rich1236584]

Ah ok. I will look into that, Thanks.

 

[fibreplus]

I just purchased the Fanvil i16S with our server in-house on the local LAN, we found the device it is using DHCP and accepted the correct IP in our range with no conflict. We found under phones although reported Firmware is not (all text on row are in RED) supported i.e. 2.12.44.6 as per Fanvil site. it shows under PHONES as a green. What would you guys propose? I have considered rolling back the firmware to an older version! however not sure if this will take!

 

[jed]

I just purchased the Fanvil i16S with our server in-house on the local LAN, we found the device it is using DHCP and accepted the correct IP in our range with no conflict. We found under phones although reported Firmware is not (all text on row are in RED) supported i.e. 2.12.44.6 as per Fanvil site. it shows under PHONES as a green. What would you guys propose? I have considered rolling back the firmware to an older version! however not sure if this will take!

Just Installed 50 pcs. i16S, and they all provisioned perfectly. The Doorphone hardware version 1.0 came with FW 2.12.3 and we updated all through 3CX to 2.4.7, without any issues.
So my advice would be to roll back to 2.12.3 and do the update through 3CX to 2.4.7 and it should work.