The general configuration file is helpful in automatic configuration deployment of a large number of terminals. For example, only a general configuration file F0V00X600000.cfg carrying firmware parameters needs to be placed on the automatic configuration server to automatically deploy firmware for 1000 X6 terminals.
@Dashrender thanks I had totally missed that section of the pdf. Adding the Auto Image Url option, to the F0V0X5U00000.cfg did get the phone to properly upgrade the firmware automatically.
F0V0X5U00000.cfg contents for the test.
<<VOIP CONFIG FILE>>Version:2.0000000000
<AUTOUPDATE CONFIG MODULE>
Auto Image Url :https://URL/x5u-6906-P0.18.23.21-2.2.10-3421T2020-09-27-16.44.21.z
<<END OF FILE>>
Here are the logs of the process, phones starts with firmware 1.0.0 and properly upgrades to 2.2.10
Fanvil is readily available in many regions and the problem people have had is not with the hardware. It's firmware upgrades that breaks things, intermittent problems, provisioning stops working, DSS keys that stops working etc. All related to software.
Consensus among those that deploy both Yealink and Fanvil has been to get Yealink if possible as Fanvil causes a lot more support issues over time.
But hopefully Fanvil is getting better so it will be interesting to see what you guys think in a year or so.
That’s why I am buying one to test. Since warranty/support is supposed to be available now, that means it is time to test.
I don't see a firmware for the T54W nor is the EXP50 available.
These phones are basically new since October or so. They will not be in EPM anytime soon because of how that has traditionally worked. The device manufacturer has to sing an agreement with Sangoma (Schmoozecom) to get a device supported. I assume, but do not know for a fact, that the agrement includes monetary compensation also, as anything in EPM is fully tested by Sangoma also, and testing takes manpower (money).