Phones Not Ringing for Incoming Calls

When Your Phones Sound Bad: Part 8 of 12

This problem overlaps with the calls going to voicemail post, but there's an important distinction. In that post, we covered situations where the call is being diverted before it reaches the phone (registration failure, DND, forwarding, routing issues). This post covers the scenario where the call appears to be reaching the phone but the phone doesn't ring, or where specific phones in a group should ring but don't.

The phone is sitting on the desk. It's powered on. It looks registered. But when someone calls, it stays silent while other phones in the office ring, or no phones ring at all.

The phone is registered but not ringing

If the phone shows as registered and appears to be connected, but incoming calls don't make it ring, there are several things to check.

Ring volume. This seems obvious, but it's a real issue. Most VoIP phones have a ring volume control, and it can be turned all the way down without the phone showing any obvious indication that it's muted. Some phones have a physical ringer switch (often on the bottom or back of the phone) that silently disables the ringer.

Pick up the handset and have someone call the extension. If you hear the call coming through on the handset, the phone is receiving the call and the ringer is the issue. Turn the ring volume up or check for a ringer mute switch.

Ringtone file. If the phone is configured to use a custom ringtone file and that file is missing, corrupted, or in a format the phone can't play, the phone might fail silently. It receives the call notification but can't play the associated sound. Some phones fall back to a default tone in this situation. Others just stay silent.

Try resetting the ringtone to the phone's default tone and test. If the default tone works, the custom ringtone file was the problem.

Phone firmware bug. Certain firmware versions on certain phone models have known bugs where the ringer stops working under specific conditions. This might happen after the phone has been running for a long time without a reboot, after a call with specific SIP characteristics, or after a specific sequence of events on the phone. Rebooting the phone resolves it temporarily, and updating the firmware usually fixes it permanently.

If the problem is intermittent and a reboot always fixes it, firmware is the likely cause. Check the manufacturer's release notes for known issues related to ringing.

Hunt groups and ring groups

If the phone is part of a ring group or hunt group and isn't ringing when the group is called, the issue might be in the group configuration rather than the phone itself.

Ring strategy. Ring groups have different strategies: ring all (every phone in the group rings simultaneously), round robin (phones ring one at a time in sequence), linear (phones ring in a fixed order), and others. If the strategy is round robin or linear and the affected phone isn't early in the sequence, it might not ring if someone answers before the group rotates to that phone. Verify that the ring strategy matches what you expect.

Member status. Some PBX platforms allow ring group members to log in and out of the group. An agent who logged out of the group (intentionally or accidentally) won't receive calls for that group even though their phone is working fine for direct calls. Check the group's member status and ensure the affected phone is logged in.

Ring timeout. The ring time per member in a hunt group determines how long each phone rings before the group moves to the next member. If the timeout is too short, the phone might ring so briefly that the user doesn't notice before the call moves on. Increase the ring time per member to a reasonable value (15 to 25 seconds is common).

Penalty or priority settings. Some queue and ring group implementations have penalty or priority settings that determine which phones ring first. A phone with a high penalty value might only ring after all lower penalty phones have been tried. Check these settings if the affected phone is in a queue.

Internal calls work but external calls don't ring

If calls between extensions ring fine but calls from outside don't ring, the problem is between the SIP trunk and the PBX's internal routing.

Inbound route configuration. The PBX needs to know what to do with an incoming call based on the dialed number (DID). If the inbound route for a specific DID is misconfigured, pointing to the wrong extension or missing entirely, that DID's calls won't reach the intended phone. Check the inbound routing rules on the PBX.

Trunk registration. If the SIP trunk uses registration authentication and the registration has failed, external calls can't arrive at all. Check the trunk's registration status on the PBX. If it shows as unregistered or failed, troubleshoot the trunk connection (credentials, network, firewall) before looking at individual phone issues.

DID format mismatch. SIP trunk providers send the dialed number in a specific format. Some send the full number with country code (+15551234567). Others send just the 10 digit number (5551234567). Others send just the last 4 digits. If your PBX's inbound routing rules expect one format and the trunk delivers another, the PBX can't match the incoming call to a route and the call fails or goes to a default destination.

Check the PBX logs to see exactly what DID format is arriving from the trunk, and ensure your inbound routing rules match that format.

SIP forking and multiple devices

Many VoIP setups allow a single extension to ring on multiple devices simultaneously: a desk phone, a softphone on a computer, and a mobile app. This is called SIP forking, where the PBX sends the incoming call notification to every registered device for that extension.

If one device rings but another doesn't, the non-ringing device might have a registration issue, a network issue, or a configuration difference. Check that all devices for the extension are properly registered and that the PBX is configured to fork calls to all of them.

Some PBX platforms have a "max contacts" setting that limits how many devices can register with the same extension. If you have three devices but the limit is set to two, the third device either can't register or pushes one of the others off. Check the max contacts setting.

Call notification timing

VoIP phones rely on SIP INVITE messages to know that a call is coming in. If there's a delay between the PBX sending the INVITE and the phone receiving it, the phone starts ringing late. If the delay is long enough, the call might have already been answered by another phone in a ring group, or the caller might have hung up before the phone starts ringing.

This delay can come from network latency, DNS resolution delays, or the phone processing the incoming INVITE slowly (which can happen on older or lower powered hardware). If a phone consistently starts ringing a few seconds after the other phones in a group, it has a processing or connectivity disadvantage that should be investigated.

VLANs and network segmentation

If phones are on a separate VLAN from the PBX (which is a recommended configuration for QoS purposes), routing between the VLANs needs to work correctly. A misconfigured VLAN, a missing route between VLANs, or a firewall between the voice and data VLANs can block the SIP INVITE from reaching the phone.

This is a common issue after network changes. A switch reconfiguration, a new firewall rule, or a VLAN change can inadvertently break the path between the PBX and the phones. If phones stop ringing after a network change, check the routing and firewall rules between the relevant VLANs.

When nothing rings at all

If no phones in the office ring for any calls, the problem is almost certainly at the PBX or trunk level rather than individual phone level. Check the PBX itself: is it running? Is it reachable on the network? Is the SIP trunk registered and active? Are there error messages in the PBX logs?

A PBX that's running but overloaded might fail to process incoming calls. A PBX with a full disk might stop writing logs and eventually stop processing calls. A PBX with a certificate expiration might fail TLS connections to the trunk provider. These are system level issues that affect all calls, not just specific phones.

If the PBX checks out, look at the network path between the outside world and the PBX. A firewall rule change, an ISP outage affecting only certain ports, or a DNS change that broke the trunk provider's ability to reach your PBX can all cause a complete inbound call failure.

Next up: Call Quality Is Fine in the Morning But Bad in the Afternoon, exploring the daily pattern that points to a specific set of causes.