The Vodia PBX streamlines the automatic provisioning of Fanvil phones through methods like zero-touch LAN provisioning, DHCP option 66 and Fanvil RPS. To get started, ensure you reset your Fanvil device by holding the OK button until prompted for a factory reset, then customize it by uploading your logo. For RPS provisioning, register for an account on the Fanvil portal, input your credentials in the Vodia PBX settings and add the phone's MAC address to the respective extensions. This allows the Vodia PBX to register the device in your Fanvil RPS account. Finally, reboot your Fanvil device to connect to the RPS and download its configuration file. For older models like the X4, use "prov/fanvil.xml" as the configuration file name; newer models like the X4U require "prov/fanvil-sysconf.xml." This seamless integration makes managing your Fanvil devices efficient and hassle-free.
The Vodia PBX can automatically provision Fanvil desktop phones through zero-touch LAN provisioning, the DHCP option 66 provisioning URL and Fanvil RPS.
Provisioning
When provisioning a Fanvil phone, you should first set the required settings on the PBX as shown in the provisioning document, Steps Before Provisioning.
Reset X-Fanvil series Phone
To Factory reset a Fanvil phone, make sure you are on the main page of the phone. Press the OK button until a prompt appears.
The phone will show you the Factory reset message, then it will reboot.
Upload a logo
You can now customize the Fanvil X series phones with your own customized logo. Learn how to upload your logo here.
You'll need to register first. Fanvil will then provide you with a username and password - you can apply it on the Vodia PBX under Admin -- Phone -- Settings --Fanvil
Once you have entered your credentials on the Vodia PBX, save the configuration:
Preparing the Extension
For Fanvil's RPS to work, you will need to add the phone's MAC address to the extensions. Vodia will then automatically register the device in your Fanvil RPS account.
Open MAC-based Provisioning
For the PBX to securely provision the phone, you will need to open the MAC-based provisioning:
Navigate to your Domain ---> All Account ---> Extensions.
Click on the extension box and under "Please select an action", choose "Open account for MAC-based provisioning". This will open a window for provisioning the phone:
Final step, reboot the phone
Reboot the Fanvil X device. The phone will contact Fanvil's RPS and send the phone to the Vodia PBX to get its config file. You should see the phone register:
Adding Buttons
To add Buttons to your phone, navigate to your Extension ---> Buttons. Vodia can detect any Fanvil model and button scheme. To add buttons to your phone, choose a type and parameter. Once you're done, save.
Reboot the phone once so it can fetch its new button config. For more information on Buttons, please review our buttons setup
Setup Devices In LAN
If your phone is in the same LAN as the PBX, you can provision your Fanvil devices by visiting (Phones in the LAN) under the Administrator level (Phones→LAN Devices).
Make sure the phone is factory reset (or at least has the default username and password); Vodia is listening on port 20 for device info by default, so make sure it's not blocked.
Make sure Steps Before Provisioning is completed before LAN provision. Choose the Fanvil phone you want to provision and click on the setup button to assign the phone to one of your extensions.
TLS Provisioning
To provision your Fanvil using the TLS protocol, navigate to your domain name -----> General Settings. Scroll down to Provisioning Parameters and choose TLS under the setting, "Proposed SIP transport protocol". For more info, check our domain settings.
Reprovisioning
Vodia Reprovisioning makes it easy for administrators to provision phones on the fly when making changes to the transport protocol (as shown above).
To start the reprovisioning function, click on the start button, then reprovision. The Fanvil phone will reboot and update its new config file within a few seconds.
Fanvil X4 Model Provisioning
The older phone models (e.g., X4, etc.) need the "Configuration File Name" as "prov/fanvil.xml " (this will be found inside RPS --> Group --> Edit button --> Phone Flash section). The old models also may need multiple factory resets at each periodic interval during provisioning (if you don't see the phone doing anything).
Fanvil X4U Model
The newer phone models (e.g., X4U, etc.) need the "Configuration File Name" as "prov/fanvil-sysconf.xml" (this will be found inside RPS --> Group --> Edit button --> Phone Flash section).
Vodia Phone 2 brings business calling directly into your Android smartphone experience. By integrating with Android's native calling framework, work calls ring, answer, and behave like regular phone calls, eliminating the need to switch between separate calling apps. Users can place calls from the standard phone dialer, answer from the lock screen, and take advantage of familiar Android features while still benefiting from business tools such as call history, messaging, voicemail, call forwarding, DND, and custom status settings.
Vodia Sales Engineer Eric Altman will attend HITEC North America 2026 in San Antonio, Texas, where he will discuss V70, the latest version of the Vodia PBX, and its applications for the hospitality industry. Vodia will showcase its AI-driven communications capabilities, hospitality-focused PBX features, integrations with leading property management systems and hotel phones, and solutions designed to help hotels improve guest experiences, streamline operations, and support modern communication requirements.
Modern business communication rarely happens within a single office or PBX environment. With V70 of the Vodia PBX, organizations and service providers can now share presence information between tenants and across separate PBX systems. External Presence Sharing extends BLF visibility beyond a single deployment, helping distributed teams maintain awareness of user availability across locations, departments, and communication environments while supporting more connected and flexible business communications.