Solved 3CX hosted and Fanvil i18S Direct SIP

[charcoalgray99]

I am having a heck of a time trying to get a Fanvil i18S provisioned with our 3CX hosted instance.

i18S was configured for DHCP, the admin password was changed, then upgraded to the latest 2.8.2.7020 firmware. The phone was added in the phone provisioning tab, Direct SIP was selected, mac address entered, unchecked "disallow use of extensions outside...", BLF button was configured.

Then the i18S was configured for the Static Provisioning Server with the filename as <mac_address>.cfg and extension and voicemail PIN. After the i18S reboots, I see the user/phone join 3CX and calls function. Everything looks great, almost.

Now, after the i18S has rebooted with it's remote config, any attempts to login to the i18S internal website by IP, show a basic authentication prompt. The default password and new admin password are not accepted. After 3 failed attempts at basic authentication, it returns a blank page that says "401 authorization required".

Seeing that this firmware version was showing in 3CX as "unsupported", I reset the i18S config via telnet menu and reverted firmware to the "supported" version listed on this page: i18S2.4.0.6516T20190402180834.z

https://www.3cx.com/sip-phones/fanvil-sip-doorphones/

After performing all the steps above again, with the 2.4 firmware, I had the same result after the phone was configured by 3CX. Oddly, 3CX still complained that this was an unsupported firmware version even though it is listed in the guide above.

I've already tried contacting Fanvil support, and they instructed me that the issue was because I need to use the 2.8.2.7020 firmware with 3CX and to perform a packet capture from the i18S "Tools" page.

Well, I tried everything all over again, resetting the config, upgrading to 2.8.2.7020, all the above configuration steps. The packet capture didn't work across the phone reboot as instructed by Fanvil support (because the internal site starts returning 401 errors) and now I'm back where I started after investing way too much time into this.

While technically the phone does work despite the warning from 3CX, but I need to be able to retain access to the i18S configuration by local IP should we need to change any settings in the future.

Fanvil support is not helpful at this point. I guess I have no support from 3CX. What do I do?

At this point I'm almost ready to return the i18S and find a different IP door station with no keypad, but I can't locate any other similar "supported" devices for hosted 3CX.

Has anyone else experienced similar "401 authorization required" errors from a Fanvil device?

 

[JohnS_3CX]

Hello @charcoalgray99

I think you've become terribly confused here, please forget everything you wrote above and I will guide you.

You have to do exactly as below:

1. The correct version is 2.8.2.7020 - install this one and ignore everything else please
2. Factory reset the device
3. DO NOT change any passwords in the device, leave it as is in its reset state
4. Edit your i18S extension in 3CX, click the provisioning tab, scroll down to where it says "Phone Web Page Password" and read it - this is the password that the device login will use. Now you know where the password is if you need to change it.
5. Then provision it as the guide says here, do not use any extension+config filename, just do this part below that I highlighted:
   

- Your device will now configure itself.
- The username is still admin
- The password is exactly where I showed you


Please let me know if you were successful after you follow these steps, and we can continue from there if you have more questions

 

[charcoalgray99]

Thank you very much for your help. I was able to configure the device correctly now. What is very confusing is that the login prompt on the Fanvil changes from the HTML styled login form, to the basic authentication prompt after configuration. Using admin and the "Phone Web Page Password", I was able to login after configuration.

I also believe the guide link to firmware should be updated as it is out of date, or remove the wording "running the required firmware by 3CX", which makes it sound like 3CX is only compatible with the firmware available for download at the provided link.

 

[JohnS_3CX]

Glad to hear you were able to get it up and running! As for the guide:






Most people today will purchase devices that already come with a way newer firmware than the one that existed when this guide was made, but we want to cover even those that may have found a device with the oldest firmware that has provisioning issues. They need to install the minimum version first.