If you need to handle a Fanvil phone setup on Viirtue, the fastest path usually comes down to two methods. Use DHCP Option 66 when you control the customer LAN and want zero-touch deployment, or log into the phone and enter the Viirtue provisioning URL manually under Fanvil's static provisioning settings.
The important qualifier most guides miss: Viirtue's current NDP provisions Fanvil phones that use the NC configuration format, which covers Fanvil's current XU and XS series and a portion of the X series with the right firmware. Fanvil's own auto provisioning documentation describes DHCP Option, Static Provisioning Server, SIP PnP, and TR069 as supported provisioning methods, and its current Download Center lists active Fanvil phone families across the portfolio.
Jump to a Section
TL;DR
Viirtue provisions Fanvil phones that use the NC configuration format. That scope covers Fanvil's current XU and XS series natively, and supports X series handsets when special NC firmware is requested directly from Fanvil. Older Fanvil models, A series Android phones, and the H and I series are not currently supported on Viirtue's NDP, so confirm the model is in scope before you order hardware.
Once you have a supported NC-format phone, the workflow is straightforward: if you manage local DHCP, point Option 66 to the Viirtue-supplied provisioning location and reboot the phones for zero-touch onboarding. If you would rather not touch DHCP, use the phone web interface and set the Static Provisioning Server to the Viirtue NDP URL instead. Both approaches fit Fanvil's documented provisioning model.
Which Fanvil models are supported on Viirtue?
This is the question every MSP should answer before ordering hardware. Fanvil publishes a broad handset portfolio across A, V, X, XU, XS, X300, and H series, but Viirtue's current v42 NDP only provisions phones that use Fanvil's NC configuration format. Here is the honest breakdown.
Supported natively (NC format)
Fanvil's current XU and XS series phones ship with NC-format configuration support and provision cleanly on Viirtue's NDP. This is the safest tier for standardized partner rollouts because no firmware gymnastics are involved. The XU family covers business desk phones such as X3U through X6U, and the XS family extends into enterprise and call-center handsets. For most MSPs standardizing on Fanvil, the XU and XS series are the path of least friction.
Supported with special firmware (X series)
Fanvil's X series handsets do not ship with NC format as standard. To provision them on Viirtue, you need to request special NC-format firmware from Fanvil directly. That firmware is not available in the public Fanvil Download Center and requires opening a request with Fanvil support. If you plan to standardize on an X series model, build this firmware request into your procurement workflow so it does not surprise you at deployment time.
Possibly supported (V series)
Fanvil's V series business phones (V50P through V67) may also support NC format, but they are not part of Viirtue's explicitly confirmed supported list. If you are considering a V series rollout, contact Viirtue support to confirm compatibility for the specific model and firmware version before you commit to the hardware. The conservative approach is to verify compatibility for one unit, then standardize.
Not currently supported
A few Fanvil families fall outside current Viirtue provisioning coverage, and partners should know this before committing to hardware.
- A Series (Android phones). Fanvil's A330, A320, and related Android touchscreen handsets are not currently supported on Viirtue because the underlying Netsapiens platform has not added device coverage for these models yet. If you need Android-style Fanvil hardware, contact Viirtue for a timeline before deployment.
- H Series and I Series. Hotel, compact, and specialty handsets in the H and I families are not currently tested for provisionability on Viirtue's NDP. That does not mean they will never work, but it does mean you should not assume they will provision out of the box. Contact Viirtue support before planning a hospitality or common-area deployment around these models.
- Older Fanvil hardware. Legacy Fanvil phones predate the NC configuration format and will not provision on Viirtue. If you inherit older Fanvil stock from a prior deployment, treat it as replacement candidates rather than Viirtue assets.
Standardize your Fanvil lineup around the XU and XS series for the fewest surprises. Use X series when the form factor or price point justifies the extra step of requesting NC firmware from Fanvil. Avoid A, H, and I series unless Viirtue support confirms current support for your specific model.
When to use DHCP Option 66 vs a provisioning URL
Once your hardware is confirmed as supported, the next decision is how the phone learns the Viirtue provisioning location. You have two practical choices, and they fit different scenarios.
Use DHCP Option 66 when you want true zero-touch deployment on a customer site, especially when many phones are landing on the same LAN and you control the DHCP scope. Fanvil documents DHCP Option as one of the standard ways a handset learns the provision URL during boot, and it scales cleanly for office cutovers and multi-phone rollouts.
Use a direct provisioning URL to Viirtue's NDP when you are staging phones ahead of shipment, working one handset at a time, or dealing with an environment where changing DHCP is slow, risky, or owned by someone else. This is also the better choice when the customer LAN is managed by a third party and you do not have DHCP access.
| Decision Factor | DHCP Option 66 | Manual Provisioning URL |
|---|---|---|
| Number of phones | 5+ phones on the same LAN | 1 to 4 phones, or staged off-site |
| DHCP access | You control the DHCP server | Third party owns DHCP or you cannot touch it |
| Deployment style | Zero-touch at the customer site | Bench staging or per-device repoint |
| Technician time per phone | Minimal after DHCP is set | Higher (web UI per phone) |
| Best fit for | New site cutovers, full refresh projects | Pre-shipment staging, one-off repoints, hosted-only sites |
Option 66 scales. Manual URL is the safety net. Most partners running a serious Viirtue practice end up using both: Option 66 for fresh customer sites where they own the network, and the manual URL path for drop-ship deployments, warehouse staging, and repoints on networks they do not control.
Prerequisites before you provision
Before you touch the phone, make sure three things are true. The device has network access and can reach the internet, you know whether the deployment will use DHCP-driven onboarding or manual URL entry, and you have the Viirtue NDP value from partner certification. Fanvil's provisioning documentation also notes that a phone can have multiple provisioning methods configured at once, which means stale provisioning data from a previous deployment can block a repoint to Viirtue.
On the transport side, Fanvil's provisioning framework natively supports FTP, TFTP, HTTP, and HTTPS. Viirtue only supports HTTP and HTTPS for provisioning on the NDP. When you select the protocol type on the phone, choose HTTP or HTTPS, not FTP or TFTP, regardless of what the Fanvil manual lists as available. This is one of the most common setup mistakes during first-time Fanvil deployments on Viirtue.
Method 1: Provision Fanvil phones with DHCP Option 66
This is the zero-touch path. The DHCP server hands the phone the Viirtue provisioning location at boot, and the phone pulls its configuration automatically. It is the right choice for sites with several NC-format Fanvil phones landing on the same LAN.
- Confirm the phone is set to DHCP for its network mode. This is the Fanvil factory default, so freshly unboxed units are already there. Reset units coming from prior deployments.
- In the site's DHCP environment, configure Option 66 with the Viirtue provisioning URL or path supplied during partner certification.
- Connect the phones to the network and power them on, or reboot any phones that are already connected so they request fresh DHCP data.
- Let each phone pull its configuration from Viirtue's NDP and apply settings. On most Fanvil models, the phone will reboot once after applying the new config.
Fanvil's own Auto Provision Description documentation describes this as a boot-time workflow where the handset requests network information, receives the Option 66 value from DHCP, parses the provisioning URL, and downloads the corresponding configuration from the server. In plain English, Option 66 is the best fit when you want the network itself to tell every Fanvil phone where to go. It scales well for office cutovers, new-site rollouts, and hardware refresh projects where you want phones to self-locate the provisioning target without a technician logging into every handset.
If you are standardizing your Fanvil lineup across multiple customer sites, this is also the workflow that keeps your hardware strategy aligned with the best VoIP phones to resell as an MSP: Option 66 lets you ship pre-labeled phones to a site, have someone on the ground plug them in, and walk away.
Method 2: Provision Fanvil phones with a direct URL to Viirtue's NDP
Use this path when you are staging phones off-site, running a one-off repoint, or working on a network where DHCP is not yours to change. It is slower per phone, but it gives you full control and works in environments where Option 66 is not practical.
- Find the phone's IP address. On most Fanvil models, press the OK or Menu button and navigate to the status screen, where the IP address is displayed.
- Open the phone's web interface in a browser on the same network. Sign in with admin credentials.
- Navigate to System > Auto Provision > Basic Settings > Static Provisioning Server (menu path may vary slightly by model and firmware).
- Paste the Viirtue NDP provisioning URL into the Server Address field exactly as provided.
- Set the Protocol Type to HTTP or HTTPS, matching what your Viirtue NDP workflow expects. Do not select FTP or TFTP.
- Leave the Configuration File Name empty unless your Viirtue onboarding instructions specify a value. Fanvil phones will request common and device-specific files based on the server's naming logic when this field is blank.
- Save the change. Reboot the phone or trigger the Auto Provision Now control to force an immediate pull.
Fanvil's official static provisioning documentation confirms this menu path and field structure. The provisioning server address can be an IP address or a domain, so Viirtue's NDP URL works as written.
Model-by-model guidance for supported Fanvil families
Here is how the provisioning workflow lines up with Fanvil's active families that you might actually deploy on Viirtue.
XU Series business phones
The XU family (X3U, X4U, X5U, X6U) is Fanvil's mainstream NC-format desk phone lineup and is fully supported on Viirtue out of the box. These are the phones most MSPs should standardize on for new customer rollouts. Provision them with Option 66 for mass rollouts or the Static Provisioning Server path for individual staging. No special firmware request is required.
XS Series enterprise and specialty phones
Fanvil's XS series extends into higher-end business and call-center handsets and also ships with NC format. The provisioning workflow is identical to the XU series. If you have customers who need an executive phone with a larger display or a receptionist console, the XS series is your upgrade path within Viirtue-supported hardware.
X Series (requires special NC firmware)
The X series includes models like X1, X3, X4, X7, and X210. These phones do not ship with NC format as standard, and the standard firmware in the Fanvil Download Center will not provision cleanly on Viirtue. To deploy X series hardware on Viirtue, you need to request special NC-format firmware from Fanvil directly. Open the request with Fanvil support before you ship phones to a customer site so you are not installing firmware on the ground.
V Series business phones (verify first)
Fanvil's V series business phones run from V50P through V66, V66 Pro, and V67. Some V series models may support NC format, but this is not part of Viirtue's explicitly confirmed supported list. Before you standardize on a V series model for a Viirtue deployment, contact Viirtue support to verify compatibility for the specific model and firmware version. The five-minute verification call is cheaper than a failed rollout.
XU and XS series are the green light. X series is yellow light with a firmware request. V series is check-before-you-commit. A, H, and I series are currently off the list. Build your standard Fanvil SKU around XU or XS to keep your deployment process predictable.
Troubleshooting Fanvil provisioning on Viirtue
If a Fanvil phone does not pull its configuration after reboot, check the obvious items first before digging into packet captures. The three most common failures account for the majority of first-time setup problems.
- Wrong configuration format. The phone is not running NC-format firmware. This is the number one cause of silent provisioning failures on X series hardware. Verify the firmware version matches Viirtue's NC-format requirement, and request NC firmware from Fanvil if the phone shipped with the standard image.
- Wrong protocol selected. The phone is set to FTP or TFTP instead of HTTP or HTTPS. Viirtue only supports HTTP and HTTPS on the NDP, so any other selection will fail. This is a one-field fix in the phone's Auto Provision menu.
- Stale provisioning targets. The phone still has DHCP enabled when you are using manual URL entry, or it still points at an old provisioning server from a prior deployment. Factory reset, then set only the Viirtue provisioning path.
Fanvil's provisioning documentation makes clear that a phone chooses its provisioning approach at boot based on the methods configured and their priorities, so a forgotten legacy entry can easily win out over your new Viirtue configuration. Clear the stale entries before you troubleshoot anything else.
If you are running into broader call quality or registration issues after the phone successfully provisions, the problem has usually moved from provisioning to network behavior. Router-level features like SIP ALG can silently rewrite SIP headers and break call flow in ways that look like phone problems, and that is a separate troubleshooting track. Viirtue's guide to solving SIP ALG problems in 2026 walks through how to test for ALG interference and disable it on common firewalls.
Why Fanvil phone setup matters for MSPs and resellers
The current search landscape for Fanvil setup is dominated by technical docs, provisioning knowledge bases, and support articles from PBX vendors and hosted voice providers. That tells you something about the intent behind the query: the person searching usually has the phone in hand and needs to make it work right now, not next quarter. For a Viirtue partner, that means getting this workflow right is a margin protection exercise as much as a technical one.
Most of the pages ranking for Fanvil provisioning queries are technical support articles, not thought-leadership content. The person searching is a technician with a phone on their desk, not a prospect evaluating a platform. Partners who publish clear, procedural guidance capture both the search click and the trust that follows it.
There is also a clear content gap in the current ranking pages. Most focus on a single platform's provisioning portal or a narrow manual configuration path. Almost none address the NC format requirement that actually determines whether a given Fanvil phone will work on a given PBX platform. That is the detail that separates a smooth rollout from a two-day troubleshooting session, and it is the detail most MSPs learn the hard way.
For partners building a serious VoIP reseller program, standardizing on the right Fanvil SKU is the first step in a longer workflow: accurate quoting, predictable provisioning, and clean handoff to billing. When the provisioning step is unpredictable, every downstream step in quote-to-cash inherits that uncertainty. Standardizing on Viirtue-supported NC-format hardware removes that variable from your rollout playbook entirely.
Final takeaway on Fanvil phone setup with Viirtue
If you are deploying Fanvil phones on Viirtue, think in terms of supported hardware first and deployment method second. Start with Fanvil's XU or XS series for native NC-format support, use DHCP Option 66 when you control the network and want zero-touch rollouts, and use the manual provisioning URL path when you need control or the customer LAN is not yours to change. HTTP or HTTPS only. Reset phones inherited from other deployments before you repoint them. And when in doubt about a specific model, confirm with Viirtue support before you order hardware.
The upside for MSPs and telecom resellers standardizing on Fanvil is real. Fewer support tickets, cleaner site cutovers, and a repeatable deployment SOP that new technicians can execute without hand-holding. That predictability feeds directly into the ViiBE quote-to-cash engine, your billing flow, and the customer experience your brand sits on top of.
If you are building or expanding a white-label voice practice and want a platform that treats partners like operators instead of commissions, take a look at the Viirtue Partner Program. You can also explore the full Viirtue solutions hub to see how white-label UCaaS, AI voice agents, and telecom compliance infrastructure fit together under one roof. Viirtue ranked first on the best wholesale VoIP providers list for 2026 because of exactly this kind of operational clarity: the workflows that protect your margin at scale are documented, supported, and built into the platform.
Ready to sell branded voice and AI under your own brand? Learn more about how to sell VoIP and UCaaS as a Viirtue partner, or become a Viirtue partner and get access to the Learning Center, NDP provisioning details, and partner certification.
FAQ: Fanvil Phone Setup
How do I set up a Fanvil phone on Viirtue?
Use DHCP Option 66 if you control the site DHCP and want zero-touch provisioning, or log into the phone web UI and point the Static Provisioning Server to the Viirtue NDP URL if you prefer manual provisioning. Fanvil supports both approaches in its provisioning framework. (Fanvil)
Where do I enter the provisioning URL on a Fanvil phone?
Fanvil’s static provisioning guide places it under System > Automatic Provision > Basic Settings > Static Provisioning Server, in the Server Address field. (Fanvil)
Does this work across different Fanvil models?
Yes. Fanvil’s current active SIP phone families include A, V, X, XU, X300, and H series, and Fanvil’s DHCP Option 66 guide states the process applies to all Fanvil phone models. (Fanvil)
Should I use Option 66 or a manual provisioning URL?
Use Option 66 for large, on-site rollouts where DHCP is under your control. Use a manual URL when staging devices individually or when you do not want to change the client’s DHCP settings. Fanvil supports both methods. (Fanvil)
Where do Viirtue partners get the NDP address?
Viirtue partners obtain the current NDP address in the Viirtue Learning Center during partner certification.
