In brief: The most common Fanvil IP phone issues are no power (check PoE switch port and cable), connectivity failures (verify VLAN tagging and SIP registration credentials), audio quality problems (codec mismatch or QoS misconfiguration), and firmware-related bugs. Most issues can be resolved through the web interface at the phone’s IP address, typically reachable at 192.168.x.x on local networks.
Fanvil IP phones are a popular choice among South African businesses and resellers for their price-to-performance ratio and wide model range — from entry-level desk phones to high-end DSS key models. When issues arise, the troubleshooting methodology is consistent across the range. This guide covers the most common problems in deployed SA environments, their causes, and step-by-step resolutions.
Accessing the Fanvil Web Interface
Most Fanvil troubleshooting happens through the phone’s built-in web interface. Before starting any troubleshooting:
- Find the phone’s IP address: press the OK button (or navigate Menu → Status → Network) to display the current IP
- Enter the IP in a browser on the same network
- Default login: admin / admin (change this on first setup)
- The web interface gives access to SIP accounts, network settings, audio codecs, logs, and firmware
Problem 1: No Power / Phone Won’t Turn On
Symptoms
The phone screen remains dark; no LED activity; no boot sequence.
Causes and Fixes
PoE port not active: Confirm the network switch port has PoE enabled. Most managed switches have PoE enabled per-port — check the switch management interface. Fanvil phones use 802.3af PoE (12.95W max for most models); higher-end models with expansion modules may require 802.3at (25.5W). If the switch port doesn’t provide enough power, the phone may boot partially and shut down.
Cable fault: Test with a known-good Cat5e or Cat6 cable. Fanvil phones require all 8 wires intact for PoE — a damaged pair will prevent power delivery even if data works. Test with a cable tester.
Faulty PoE injector: If using a PoE injector rather than a PoE switch, test with a replacement injector. Fanvil’s X-series and H-series support both PoE and 5V DC adapters — testing with the DC adapter (if available) immediately confirms whether the phone hardware is functional.
Phone in a fault loop: If power was lost during a firmware update, the phone may be stuck in a bootloader loop. Connect via DC adapter, allow full boot, then access the web interface and check firmware status before reconnecting PoE.
Problem 2: Registration Failed / Cannot Make Calls
Symptoms
Phone shows “Unregistered”, “Registration Failed”, or displays account as red/offline. No dial tone; calls fail immediately.
Causes and Fixes
Wrong SIP credentials: Verify the SIP username, password, and server address against the 3CX/Yeastar/hosted PBX management portal. Check that the SIP account line 1 in the Fanvil web interface exactly matches the extension settings. Common error: using the extension number as both the SIP ID and authentication name — these may differ on some PBX platforms.
Network reachability: From the Fanvil web interface, use the built-in ping tool (Network → Ping) to test connectivity to the SIP server IP or hostname. If ping fails, the issue is network routing, not SIP configuration.
VLAN misconfiguration: In SA enterprise environments, voice VLANs are common. If the upstream switch port is configured for a voice VLAN, the Fanvil phone must be configured with the matching VLAN ID (Network → Advanced → VLAN settings in the web interface). Mismatched VLAN prevents SIP registration even when the phone appears connected on the data network.
Firewall blocking SIP: SIP typically uses UDP/TCP port 5060. If there’s a firewall between the phone and the PBX server (common in cloud PBX deployments), verify that SIP and RTP ports (typically UDP 10000–20000) are permitted. For 3CX hosted deployments, outbound UDP 5090 is also required.
DNS resolution failure: If the SIP server is configured as a hostname rather than IP address, confirm the phone’s DNS server settings (usually pulled from DHCP) can resolve the hostname. Test by temporarily switching to the SIP server’s direct IP address.
Problem 3: One-Way Audio or No Audio on Calls
Symptoms
Calls connect but only one party can hear the other; or the call connects but there is no audio at all.
Causes and Fixes
SIP ALG (most common in SA): As above — disable SIP ALG on the router first. This is responsible for the majority of one-way audio issues in SA deployments.
Codec mismatch: The phone and PBX must agree on an audio codec. Standard codec priority for Fanvil in SA deployments:
- G.711a (alaw) — Used on most SA carriers and recommended for fibre connections. Uncompressed; best quality.
- G.711u (ulaw) — North American standard; less common on SA carriers.
- G.729 — Compressed; useful on constrained bandwidth but requires a licence on some PBX platforms. 3CX includes G.729 in the licence; confirm your PBX does too.
Set codec priority in the Fanvil web interface: Account → Account 1 → Codec. Ensure G.711a is at the top of the priority list for SA-carrier termination.
NAT traversal issues: If the phone is behind NAT (most SA deployments), the PBX must be configured with STUN or the correct public IP for RTP. In 3CX, enable STUN on the extension if the phone is behind NAT. In Yeastar, configure the external host in the SIP settings.
RTP port range blocked: RTP audio travels on different ports from SIP signalling. Confirm that UDP ports 10000–20000 (or your PBX’s configured RTP range) are not blocked on the customer’s firewall.
Problem 4: Poor Call Quality (Crackling, Delay, Dropped Words)
Causes and Fixes
QoS (Quality of Service) not configured: Voice traffic must be prioritised over data traffic on the network. Enable QoS on the switch port connected to the Fanvil phone and mark SIP/RTP packets with DSCP EF (46) for expedited forwarding. On the Fanvil phone: Network → Advanced → QoS → enable DSCP and set to 46.
High jitter or packet loss: Use the Fanvil web interface’s built-in network statistics or the 3CX/Yeastar statistics page to check jitter and packet loss on active calls. Acceptable jitter for VoIP: <30ms. Acceptable packet loss: <1%. Values above these cause audible quality degradation. If the LAN is clean but the upstream carrier shows high jitter, raise a fault with your SIP trunk provider.
Load shedding impact: In South Africa, load shedding causes power fluctuations that affect switch PoE delivery and can cause brief network outages. Phones on UPS-backed PoE switches maintain quality during outages; phones directly powered by utility power will reboot and re-register (taking 30–60 seconds). Recommend UPS-backed PoE switches to all business customers.
Problem 5: Display Issues or Keypad Not Responding
Causes and Fixes
Screen unresponsive: Restart the phone (long-press the # key on Fanvil H-series, or pull PoE). If the screen remains frozen after reboot, a factory reset may be required. Factory reset: Menu → Advanced → Factory Reset (admin password required). Note this erases all configuration — ensure provisioning is in place to restore settings.
Keys not registering: Clean the keypad with a dry cloth — liquid ingress under keys is a common cause in office environments. If cleaning doesn’t resolve it, test by provisioning the same extension on a softphone; if calls work on the softphone, the hardware has likely failed.
Screen brightness/contrast: Fanvil phones allow screen brightness adjustment in the phone menu (Settings → Display). In high-ambient-light environments (sunny SA offices), maximum brightness is often necessary for readability.
Problem 6: Firmware Update Issues
Fanvil releases firmware updates regularly, including security patches and bug fixes. Always check the Fanvil official download portal for the latest firmware for your specific model.
Updating Firmware via Web Interface
- Download the correct firmware file for your model (e.g., X4U, X6, H2S — do not cross-load firmware between models)
- Login to the web interface → System → Upgrade
- Select the firmware file and click Upgrade
- Do not power off during upgrade — the process takes 2–5 minutes
- Phone will reboot and return to the login screen with the new firmware version displayed
Bulk Firmware Updates via Auto-Provisioning
For SA resellers managing multiple Fanvil deployments, auto-provisioning via TFTP or HTTP is the recommended approach for bulk updates. Configure the provisioning server URL in 3CX or your DHCP server (Option 66) to point to your provisioning server, then deploy firmware updates centrally without touching each phone individually.
Frequently Asked Questions
What is the default IP address of a Fanvil phone?
Fanvil phones obtain an IP address via DHCP by default. To find the current IP, press the OK button on the phone to display network information, or check your DHCP server’s lease table. If DHCP is not available, the phone defaults to a static IP of 192.168.1.120 (varies by model — check the Quick Installation Guide for your model).
How do I factory reset a Fanvil phone?
Navigate to Menu → Advanced Settings → Factory Reset on the phone itself (admin password required, default: admin). Alternatively, via the web interface: System → Configuration → Factory Reset. Note that this erases all configuration including SIP accounts. Ensure auto-provisioning is configured before resetting deployed phones.
Why does my Fanvil phone keep losing registration?
The most common causes are: SIP ALG enabled on the router (disable it), NAT/firewall blocking SIP keep-alive packets, or a firmware bug (update to the latest version). Also check the SIP registration expiry setting — some carriers require a shorter interval (60–120 seconds) to maintain registration through NAT.
What codecs should Fanvil phones use in South Africa?
Set G.711a (alaw) as the first priority codec for connections to South African SIP carriers — it’s the standard on SA networks. Use G.711u (ulaw) as second priority. G.729 can be added for bandwidth-constrained connections but requires a licence on some PBX platforms.
My Fanvil phone has one-way audio. How do I fix it?
Start with SIP ALG — disable it on the router (this causes the majority of one-way audio issues in SA). Then verify: the RTP port range (UDP 10000–20000) is not blocked on the firewall, NAT traversal (STUN) is configured on the PBX extension, and codec priorities match between phone and PBX.
About the Author
Mechelle Gindra
Mechelle Gindra is the managing editor and lead content strategist at Telecoms-Channel, South Africa's dedicated intelligence platform for telecoms resellers, ICT distributors, and channel partners. She oversees the editorial team's AI-assisted content production pipeline, ensuring vendor news, market analysis, and regulatory updates are accurate, timely, and actionable for the SA telecoms channel community. With deep expertise in the South African telecoms reseller ecosystem, Mechelle directs coverage of vendor partner programmes, ICASA regulatory developments, wholesale market dynamics, and channel business strategy. She is responsible for maintaining Telecoms-Channel's editorial standards, fact-checking processes, and corrections policy.
