VoIP Phone Keeps Rebooting? How to Stop Boot Loops

A VoIP phone stuck in a reboot loop is completely useless. It powers on, begins its startup sequence, gets partway through — then restarts. Over and over. Meanwhile, calls go unanswered and your team is left without a working phone.

Boot loops can be caused by hardware faults, power issues, network problems, or firmware corruption. This guide covers every common cause and walks you through fixing each one.

Understanding the Boot Process

When a VoIP phone powers on, it goes through several stages:

1. Hardware initialisation — the phone tests its internal components
2. Boot loader — loads the firmware from internal memory
3. Network connection — obtains an IP address via DHCP
4. Provisioning — downloads its configuration from a provisioning server (if configured)
5. SIP registration — connects to the VoIP server and registers its extension

The stage at which the phone reboots tells you a lot about the cause. Watch the phone carefully during its boot sequence and note when exactly it restarts.

Cause 1: Power Supply Problems

Insufficient or unstable power is the most common cause of VoIP phone boot loops.

Power over Ethernet (PoE) Issues

Most business VoIP phones are powered via PoE from a network switch. Problems occur when:

• The switch PoE budget is exceeded — each PoE switch has a maximum total wattage it can deliver. If you add too many devices, some phones do not get enough power. They start booting, draw peak power, and the switch cuts them off.
• Wrong PoE standard — older switches may support 802.3af (15.4W per port) while newer phones require 802.3at (25.5W). The phone gets enough power to start but not enough to complete boot.
• Damaged Ethernet cable — PoE requires all eight wires in the cable to be intact. A cable with broken pairs may pass data but fail to deliver sufficient power.
• Long cable runs — PoE power drops over distance. Cables over 80-90 metres may not deliver enough wattage.

How to Fix Power Issues

• Test with the manufacturer AC adapter — bypass PoE entirely. If the phone boots normally on AC power, the PoE supply is the problem.
• Check your switch PoE budget — log into the switch management interface and verify total PoE consumption versus capacity
• Try a different switch port — individual ports can fail
• Replace the Ethernet cable — use a known-good Cat5e or Cat6 cable
• Use a PoE injector — a midspan PoE injector provides power independently of the switch, useful for diagnosing and as a permanent fix

Cause 2: Firmware Corruption

Corrupted firmware prevents the phone from completing its boot sequence.

How Firmware Gets Corrupted

• Interrupted firmware update — if power is lost or the network drops during a firmware upgrade, the firmware image can be left in a partially written state
• Storage degradation — flash memory in older phones can develop bad sectors over time
• Failed provisioning — some provisioning servers push firmware updates automatically. If the file is incomplete or incompatible, the phone can brick itself.

How to Fix Firmware Issues

1. Access the phone web interface — if the phone stays up long enough, try reaching its web UI (find its IP from your DHCP server). Some phones allow firmware upload via the web interface even during boot loops.
2. Use TFTP recovery mode — most VoIP phones (Yealink, Polycom, Cisco, Grandstream) have a built-in recovery mode that allows firmware to be loaded via TFTP. Consult your phone manufacturer documentation for the specific key combination or procedure.
3. Factory reset — a hard reset clears the configuration and may allow the phone to boot with default firmware. Usually triggered by holding a button combination during power-up.

Cause 3: Provisioning Loop

If your phone is configured to download its settings from a provisioning server, a misconfigured provisioning file can cause repeated reboots.

How Provisioning Loops Happen

• The provisioning file instructs the phone to update firmware, but the firmware file is missing or corrupt — the phone downloads, fails, reboots, tries again
• The provisioning file contains invalid settings that crash the phone software
• The provisioning server responds with an error, and the phone interprets this as "try again" indefinitely

How to Fix It

• Temporarily disable provisioning — if you can access the phone settings, point the provisioning URL to a non-existent server or clear it entirely
• Fix the provisioning file — check your provisioning server for errors in the configuration template
• Check the firmware file — ensure the firmware file on your provisioning server matches the phone model and is not corrupted (verify the checksum)
• Factory reset the phone — this clears the provisioning URL, stopping the loop

Cause 4: DHCP and Network Issues

Network configuration problems can trigger reboots during the network connection phase.

• DHCP server not responding — if the phone cannot obtain an IP address, some models reboot after a timeout period
• IP address conflict — if the DHCP server assigns an IP that is already in use, the phone may detect the conflict and reboot
• VLAN misconfiguration — if the phone is on the wrong VLAN and cannot reach the DHCP server, it loops
• Network switch port issues — a failing switch port may cause intermittent connectivity that triggers reboots

How to Fix Network Issues

• Check your DHCP server is running and has available addresses in its pool
• Verify VLAN assignments on the switch port the phone is connected to
• Try a static IP configuration on the phone to bypass DHCP entirely (for testing)
• Connect the phone directly to the router, bypassing any switches, to isolate the problem

Cause 5: Hardware Failure

Sometimes the phone itself has failed.

• Overheating — phones in direct sunlight, near heat sources, or in enclosed spaces with poor ventilation can overheat and reboot
• Component failure — RAM, flash storage, or processor issues cause crashes during boot
• Physical damage — liquid spills, drops, or power surges can damage internal components
• Age — VoIP phones typically last 5-7 years. Beyond that, component degradation increases

Diagnosing Hardware Failure

• Swap test — put the suspect phone on a known-working port and cable. Put a known-working phone on the suspect phone port. This tells you whether the problem follows the phone or the infrastructure.
• Check for heat — is the phone unusually hot to the touch?
• Look for visual damage — bulging capacitors, burn marks, or corrosion on the circuit board (if accessible)
• Try a factory reset — if the phone boots after a reset, the hardware is likely fine and the issue was software/configuration

Step-by-Step Troubleshooting Checklist

Work through this systematically:

1. Note when in the boot process it restarts — during logo, during network setup, or after connecting
2. Try a different power source — AC adapter instead of PoE, or a different PoE switch port
3. Try a different Ethernet cable
4. Connect directly to the router — bypass switches to isolate network issues
5. Factory reset the phone — clears configuration and provisioning
6. Attempt firmware recovery via TFTP
7. Swap with a known-working phone to confirm hardware failure

If you need help choosing reliable VoIP hardware that is fully managed and supported, our guide to hosted VoIP solutions covers providers that include handsets as part of the service.