Why Your Phone System Stops Working After Network Changes

VoIP down after a network change is one of the most common calls we get in the field. You swap a router, the internet provider upgrades your modem, an IT contractor "tidies up" the network on Friday afternoon, and by Monday morning the phones are dead. The good news: this is almost never a broken phone system. It is almost always a settings mismatch between your new network and the phones that were quietly depending on the old one.

Problem Overview

Here is the scenario we see again and again. Everything was working fine. Then something on the network changed, and now your desk phones won't make or receive calls, show "no service," or keep registering and dropping. The change might have been obvious (a new router) or invisible to you (your provider pushed a firmware update overnight).

VoIP phones are picky about their environment in a way that a laptop or a TV is not. A laptop just needs to reach the internet. A VoIP phone needs to reach the internet and get a valid local IP address, and have a specific kind of voice traffic (called SIP and RTP) allowed through the firewall, and ideally be prioritized so a big download doesn't crush your call quality.

When a network change resets or overrides any one of those four things, the phones go quiet. The fix is rarely complicated once you know where to look, and most of it is safe to do yourself before you ever call your provider.

Common Symptoms

• Phones show "No Service," "Not Registered," "Network Down," or a flashing line key
• You can hear the other person but they can't hear you, or vice versa (one-way audio)
• Calls connect and then drop after a fixed amount of time (often around 30 seconds)
• Incoming calls go straight to voicemail even though the phone looks fine
• Some phones work and others don't, even though they're side by side
• The phone's screen is on and the internet works on computers, but the phone still can't make a call

Most Likely Causes

Listed most-to-least common, based on what actually turns out to be the problem in most offices:

• The phones got new IP addresses (or none at all). A new router hands out addresses on a different range, so phones holding the old address can no longer talk to anything.
• The new firewall or router is blocking VoIP traffic. Many routers ship with settings (like an SIP ALG feature) that interfere with phone calls, or simply don't allow the voice ports the old network permitted.
• Quality of Service (QoS) and call-priority settings were wiped. The old router prioritized voice; the new one treats a phone call the same as a video stream, so audio breaks up under load.
• The phones are pointed at the old network's settings. A static IP, a hard-coded DNS server, or a saved gateway address that no longer exists after the change.
• A cable, port, or power source moved. Phones powered over the network cable (PoE) go dead if they got plugged into a switch port or injector that doesn't supply power.
• The provider's account or registration needs a refresh. Less common, but some hosted phone systems need to re-authenticate after the public IP address changes.

Step-by-Step Troubleshooting

Work through these in order. Each step is safe, reversible, and written so anyone in the office can do it. Stop as soon as the phones come back.

1. Confirm what changed, and when. Ask: did anyone swap a router or modem, move cables, or did the internet provider visit or push an update? Knowing the trigger points you straight at the cause. Write it down before you touch anything.
2. Power-cycle in the right order. Order matters. Turn off the phones, then the router, then the modem. Wait one full minute. Power the modem back on and let its lights go solid (usually one to two minutes). Then power on the router and wait for it to settle. Then power the phones back on last. This lets each device hand out fresh, matching addresses from the top down.
3. Check that other devices have internet. On a computer or phone connected to the same network, open a website. If nothing has internet, this is an internet outage, not a phone problem, and you should treat it as that first.
4. Look at the phone's screen for a clue. "No Service" or "Not Registered" points to the phone not reaching your provider (a firewall or registration issue). A blank or dead screen points to a power or cabling problem (jump to step 7).
5. Re-check the cabling and ports. Make sure the phone's network cable is in the correct port (most phones have a port marked for the network and a separate one for a passthrough computer). Confirm it's plugged into the same switch or router that other working devices use, not an old or disconnected one.
6. Reboot one phone on its own. Unplug a single problem phone for ten seconds and plug it back in. On reboot it will ask the network for a fresh address. If that one phone comes back, reboot the rest the same way.
7. If a phone is completely dead, test its power. If your phones are powered through the network cable (PoE), plug the phone into a port you know supplied power before, or use the phone's original power adapter if it has one. A dead screen after a switch change is almost always a power-delivery issue, not a broken phone.
8. Note whether it's all phones or just some. All phones down points to the router, firewall, or internet. One or two down points to those specific phones, cables, or ports. This single observation saves enormous time and is the first thing support will ask.
9. Look for an "SIP ALG" setting in the new router. If you're comfortable logging into the router with the credentials on its label, find a setting called SIP ALG and turn it off. This feature is meant to help VoIP but in practice breaks it on many routers, and turning it off is a safe, well-known fix. If you can't find it or aren't comfortable, leave the router alone and note it for support.
10. Do not start disabling security. Never turn off your firewall, open every port, or share router passwords to "make it work." Those are unsafe shortcuts. The correct fix is allowing the specific voice settings, which your provider can confirm for your exact system.
11. Give it a few minutes after each change. Phones can take two to three minutes to re-register after a reboot or setting change. Make one change, wait, then test, so you know which change actually fixed it.

When to Call Support

You've done your part once you've power-cycled in order, confirmed the internet works, checked cables and power, and rebooted the phones. If the phones are still down after that, it's time to escalate, and you'll be a great caller because you can tell them exactly what changed and what you tried.

• Call your phone (VoIP) provider if phones show "Not Registered" but the internet works. They can see whether your phones are reaching their servers and confirm the exact ports and settings your firewall needs to allow. This is the most common escalation for VoIP down after a network change.
• Call your internet provider (ISP) if no device has internet, or if they were the ones who changed the modem or router and you can't get into it.
• Call your IT person or installer if the change involved a new firewall, managed switch, or business router with settings you're not comfortable editing, especially QoS or port rules.

Tell whoever you call three things: what changed, whether it's all phones or some, and what the phone screens say. That turns a long diagnostic call into a quick one.

Prevention Tips

• Write down your phone settings before any network change. Take a photo of each phone's network screen and note any static IP addresses. If the new setup needs them, you'll have them.
• Tell your VoIP provider before you swap hardware. A quick heads-up lets them give you the exact firewall and port settings the new router needs, so you transfer them instead of rediscovering them.
• Keep voice priority (QoS) on your checklist. When a new router goes in, make sure call priority is re-applied. It's the difference between clear calls and choppy ones under load.
• Label your cables and ports. Knowing which port carries phones, which supplies power, and which is the internet line prevents most "dead phone after a change" problems.
• Schedule changes for low-call times. Doing a router swap before opening or after closing gives you a window to test the phones before customers are trying to reach you.
• Keep a simple network map. Even a hand-drawn sketch of modem, router, switch, and what plugs in where makes every future change and every support call faster.

Frequently Asked Questions

Why is my VoIP phone not working after installing a new router?

Almost always because the new router hands out different IP addresses or blocks the voice traffic the phones need. Power-cycle the modem, router, and phones in that order, wait a few minutes, and check whether the phone screen says "Not Registered." If it does, your provider can confirm the exact settings the new router must allow.

Why can I make calls but not receive them after a network change?

One-way problems like this usually trace back to a firewall or a router feature (often SIP ALG) interfering with incoming voice traffic. Try turning SIP ALG off in the router if you can find it, and if calls still won't come in, your VoIP provider can verify your phones are reachable from the outside.

Do I need a special router for VoIP phones?

No. Most business routers handle VoIP fine. What matters is that voice traffic is allowed through and given priority (QoS). A more capable router helps in busy offices, but the usual issue isn't the router brand, it's that the voice settings weren't carried over after the change.

Will rebooting fix my phones, or will I lose anything?

Rebooting is safe and is the right first move, you won't lose any settings or voicemail by power-cycling. The only thing to get right is the order: modem first, then router, then phones, with a short wait between each so everything lines up on the same network.

Related Articles

• Why VoIP Calls Sound Choppy (and How to Fix It)
• Why Devices Stop Connecting After a New Router Installation
• VoIP Troubleshooting Checklist for Small Businesses

NTC publishes plain-English, field-tested tech guides for small businesses. If this saved you a headache, subscribe to follow along for more.