Calls Going Straight to Voicemail

When Your Phones Sound Bad: Part 5 of 12

The phone doesn't ring. The caller either gets sent to voicemail immediately or hears a message that the person they're calling is unavailable. The phone is sitting right there on the desk, it looks like it's working, and nobody understands why calls aren't coming through.

This is a different category of problem from audio quality issues. The call isn't happening at all, or it's being redirected before the phone ever has a chance to ring. The causes are usually configuration or connectivity related rather than network quality related, and most of them are straightforward to identify once you know where to look.

Check 1: Is the phone registered?

This is the most common cause of calls going straight to voicemail, and it should be the first thing you check every time.

A VoIP phone has to register with the phone system (PBX or cloud provider) to tell the system where it is on the network. If the phone isn't registered, the system doesn't know how to reach it. When a call comes in for that extension, the system sees that the phone is unreachable and routes the call to voicemail or plays an unavailable message.

Most phones display their registration status on the screen. Look for messages like "No Service," "Not Registered," "Registration Failed," or a missing extension number on the display. Some phones show a small icon or status indicator. If the phone shows any sign that it's not registered, that's your answer.

Common reasons for registration failure:

Wrong credentials. The username, password, or server address configured on the phone is incorrect. This happens after a password change on the PBX that wasn't updated on the phone, after a phone is factory reset, or after an initial provisioning error.

Network connectivity. The phone can't reach the registration server. This could be a disconnected Ethernet cable, a switch port that's down, a VLAN misconfiguration, or a DNS resolution failure (the phone is configured with a hostname for the server but can't resolve it to an IP address).

Firewall blocking. A firewall between the phone and the registration server is blocking the SIP registration messages. This is common when phones are at remote locations or behind routers with restrictive firewall rules.

NAT timeout. The phone registered successfully, but the NAT mapping on the router expired between registration renewals. The system still thinks the phone is registered (the registration hasn't expired yet), but it can't actually reach the phone. This is the sneaky version of this problem because everything looks correct on both sides, but calls still don't arrive. The phone's registration log might show successful registrations, and the server might show the phone as registered, but the network path is broken.

To fix NAT timeout issues, reduce the registration interval on the phone to a value shorter than the router's NAT timeout. A registration interval of 60 seconds usually works for most NAT devices. You can also enable SIP keep alives (often called OPTIONS ping or CRLF keep alive) on the phone, which send periodic small packets to maintain the NAT mapping between registrations.

Check 2: Do Not Disturb

This one catches people more often than you'd expect. Do Not Disturb (DND) is a feature on most VoIP phones that silently rejects all incoming calls. When DND is enabled, the phone tells the system it's unavailable, and the system routes the call to voicemail.

DND is usually activated by a button on the phone or a soft key on the display. Some phones activate DND with a single accidental button press, and the user doesn't realize it happened. The DND indicator might be a small icon on the screen that's easy to overlook.

Check the phone's display for a DND indicator. Try toggling DND off (the button or soft key should deactivate it) and test an incoming call. If that resolves it, the fix is awareness. If accidental DND activation is a recurring problem, some PBX platforms allow administrators to disable the DND feature on specific phones or to require a confirmation step before activating it.

Check 3: Call forwarding

Similar to DND, call forwarding might be active without the user realizing it. If call forwarding is configured to send all calls to an external number or directly to voicemail, the desk phone won't ring.

Check the phone's forwarding settings and check the PBX configuration for that extension. Call forwarding can be set at the phone level (the phone itself redirects calls before they ring) or at the PBX level (the PBX redirects calls before sending them to the phone). Both need to be checked.

Some PBX platforms have a "find me/follow me" feature that routes calls to a series of numbers in sequence. If this is misconfigured, calls might be sent to the wrong destination before the desk phone has a chance to ring.

Check 4: Ring group or queue configuration

If the phone is supposed to receive calls through a ring group, hunt group, or call queue, the configuration of that group determines which phones ring and in what order. A phone that's been accidentally removed from the group, or a group whose ring strategy has been changed (from "ring all" to "round robin," for example), can result in certain phones not ringing for calls they used to receive.

Check the ring group or queue configuration on the PBX. Verify that the affected extension is a member of the correct groups and that the ring strategy matches what's expected.

Check 5: Time based routing

Many PBX systems have time conditions that route calls differently based on the time of day, day of week, or holiday schedule. If calls go to voicemail only at certain times, check the time conditions in the PBX configuration. A common issue is a time condition with the wrong timezone set, causing business hours routing to kick in at the wrong times. Another common issue is a holiday schedule that hasn't been updated and is still active past the actual holiday.

Check 6: DNS resolution

If phones are configured to connect to the PBX or VoIP provider using a domain name (like sip.provider.com) rather than a direct IP address, DNS resolution failure will prevent registration. The phone can't translate the domain name to an IP address, so it can't send registration messages, so it can't receive calls.

DNS issues can be intermittent. If your DNS server is slow or occasionally unresponsive, phones might register successfully most of the time but fail during periods when DNS is flaky. This creates an intermittent pattern where calls sometimes go to voicemail and sometimes ring normally.

Check the phone's configured DNS server. Try manually resolving the PBX hostname from a computer on the same network to verify DNS is working. If the phone's DHCP assigned DNS server is the router itself, try pointing it to a reliable external DNS server instead, to rule out router DNS issues.

Check 7: The phone is ringing but the user doesn't hear it

Sometimes the phone is actually ringing but the user doesn't notice. This sounds silly, but it's worth checking. The ring volume might be turned down to zero. The ringer might be muted (some phones have a physical ringer switch on the bottom or side). The phone might be configured with a custom ringtone that isn't playing correctly.

Pick up the phone's handset during a test call to see if the call is actually arriving at the phone. If you can answer the call, the phone is receiving it but the ringer isn't alerting the user.

Check 8: Inbound routing from the SIP trunk

If no phones in the office are ringing for external calls, but internal calls (extension to extension) work fine, the problem is likely in the inbound trunk routing. The SIP trunk delivers incoming calls to the PBX, and the PBX needs to know what to do with them based on the dialed number (the DID).

If the DID mapping is missing or incorrect, the PBX receives the incoming call but doesn't know which extension to route it to. Depending on the configuration, it might send the call to a default destination (which might be voicemail), play a "number not in service" message, or simply reject the call.

Check the PBX's inbound routing rules. Verify that each DID number is mapped to the correct extension, ring group, or auto attendant. If the trunk provider recently changed their configuration (moved to new equipment, changed the format of the calling/called numbers), the DID format in the incoming SIP message might not match what your PBX is expecting.

The pattern tells the story

The most useful diagnostic step for calls going to voicemail is identifying the pattern. Does it happen to all phones or just one? All calls or just external calls? All the time or just certain times? Every answer eliminates possibilities.

One phone affected: probably phone registration, DND, or forwarding on that specific phone. All phones affected: probably PBX configuration, trunk routing, or a network issue between the phones and the PBX. Only external calls: trunk routing or trunk registration. Only at certain times: time conditions or NAT timeout. Intermittent: NAT timeout, DNS issues, or network instability.

Next up: Caller ID Not Showing or Showing the Wrong Number, explaining why the display says "Unknown" or shows a number you don't recognize.