Testing my Fanvil X4U
-
First things first, it phsyccially feels good. It does not feel like cheap crap. I get that it is not hard to make plastic not feel cheap, but that is always a concern with lower cost devices.
-
I ordered a single unit off Amazon for fast delivery I did not go through distribution.
It arrived with the original 1.0.0 firmware. That is from November according to the Fanvil site.
The unit did NOT reach out to my PBX on first boot. This was highly disappointing. I have DHCP options setup that specify this information and it has worked with every device I have plugged in. Snom, Grandstream, Yealink, Sangoma, and even an 8 year old Aastra.
-
I upgraded the firmware manually to 2.0.5 and the unit did reach out to the PBX on reboot. I chose 2.0.5 intentionally, because I plan to have an auto provisioning file made shortly and I want to do a firmware upgrade that way.
It looks like the Fanvil phones, like every other brand, look for a generic model config file and then a MAC specific confgil file.
-
Fanvil uses an XML or TXT format for the config. I exported them from the GUI to just see what it looks like.
XML
-
There are two text formats.
Unnamed:
NC:
-
I flashed the firmware back to 1.0.0 and it did reach out to the PBX as per the DHCP options.
So it is possible the unit had some reason to have not done it out of the box. It was an Amazon purchase, so who knows.
-
Heading to the store for a bit. Will continue this later this afternoon.
-
I defaulted the phone and exported the XML version. Then I added my extension and changed a few settings and exported again. I grabbed the
diff
of the files and made a valid XML syntax out of it.Created
0c383e42480e.cfg
and stuck it on my PBX.Defaulted the phone, still on firmware 1.0.0 and boom.
works.
It only tried to pull the MAC.cfg once since it successfully processed it.
If your XML is invalid, it will try 5 times before giving up.
-
This will get you an extension registered.
<?xml version="1.0" encoding="UTF-8"?> <sysConf> <Version>2.0000000000</Version> <sip> <line index="1"> <PhoneNumber>121</PhoneNumber> <RegisterAddr>pbx.bundystl.com</RegisterAddr> <!-- Seriously, I need to say? --> <RegisterPort>5061</RegisterPort> <!-- Port for SIP Registration --> <RegisterUser>121</RegisterUser> <!-- Seriously, I need to say? --> <RegisterPswd>SIPPASSWORD</RegisterPswd> <!-- Seriously, I need to say? --> <EnableReg>1</EnableReg> <!-- Account enabled --> <MediaCrypto>2</MediaCrypto> <!-- Compulsory SRTP, use 0 for disabled --> <Transport>3</Transport> <!-- TLS, use 0 for UDP --> <VoiceCodecMap>G722,OPUS,PCMU</VoiceCodecMap> <!-- Long list by default, I like specific --> </line> </sip> </sysConf>
-
For the DSS key programing there are a lot of options in the web UI to be explored, like any phone.
But this is a basic setup with all three top screen side keys set to a line presense and the first to bottom screen set to normal BLF.
<dsskey> <SelectDsskeyAction>0</SelectDsskeyAction> <MemoryKeytoBXfer>1</MemoryKeytoBXfer> <DSSHomePage>1</DSSHomePage> <SidekeyConfig1 index="1"> <Type>2</Type> <Value>SIP1</Value> <Title>121</Title> <ICON>Green</ICON> </SidekeyConfig1> <SidekeyConfig1 index="2"> <Type>2</Type> <Value>SIP1</Value> <Title>121</Title> <ICON>Green</ICON> </SidekeyConfig1> <SidekeyConfig1 index="3"> <Type>2</Type> <Value>SIP1</Value> <Title>121</Title> <ICON>Green</ICON> </SidekeyConfig1> <internal index="1"> <Fkey index="1"> <Type>1</Type> <Value>101@1/bb</Value> <Title>Test</Title> <ICON>Green</ICON> </Fkey> <Fkey index="2"> <Type>1</Type> <Value>103@1/bb</Value> <Title>Jared</Title> <ICON>Green</ICON> </Fkey> </internal> </dsskey>
-
@JaredBusch how are you liking the Fanvil? Price/performance specs stack up nicely against some of the others, so how is your real-world experience with it?
-
-
-