Wi-Fi Calling Not Working? Here's the Quick Fix

EP
Erropedia Team
📅 June 20, 2026 📅 Updated Sep 14, 2026 👁 34 views Network & Connectivity Beginner
Wi-Fi calling drops or won't turn on? Usually a router or phone setting issue. Here's how to fix it without calling your carrier.

Quick answer for advanced users

Disable SIP ALG on your router, update your phone's Wi-Fi calling profile, and make sure you have a valid E911 address saved with your carrier. If that doesn't work, manually set DNS to 8.8.8.8 and 8.8.4.4 on your phone's Wi-Fi connection.

Why does Wi-Fi calling stop working?

I've seen this dozens of times. A client calls me saying "my Wi-Fi calling worked yesterday, now it's dead." The culprit is almost always one of three things: your router is messing with the packets, your phone's Wi-Fi calling profile is corrupt, or your carrier needs you to re-confirm your emergency address. Wi-Fi calling runs on SIP (Session Initiation Protocol), which is the same tech used by office phone systems. Routers with SIP ALG enabled will "helpfully" rewrite those packets, and they break everything. Also, a lot of budget routers from ISPs have this setting on by default and it's hidden deep in the menus.

Another common issue: you moved to a new house or apartment, and your phone still thinks you're at your old address. Carriers require a valid E911 address on file for Wi-Fi calling to work. If that address is missing or old, the feature just won't turn on.

I had a client last month whose entire print queue died because of this — well, not the print queue, but her Wi-Fi calling was dead for a week. She was ready to switch carriers. The fix took 10 minutes.

Step-by-step fix for Wi-Fi calling

  1. Disable SIP ALG on your router. Log into your router's admin page (usually 192.168.1.1 or 192.168.0.1). Look for settings like "SIP ALG", "SIP Passthrough", or "VoIP Pass-through". Turn that off. On TP-Link routers, it's under Advanced > NAT Forwarding. On Netgear, it's under Advanced > Advanced Setup > SIP ALG. On ISP routers like Xfinity or Spectrum, it might be called "VoIP ALG" or just "ALG". Turn it off, save, and restart the router.
  2. Update your Wi-Fi calling profile on your phone. Go to your phone's dialer app (the one you actually make calls from). Dial *#*#4636#*#* on Android, or *#31# on iPhone (but that's not a real thing, so just go to Settings > Phone > Wi-Fi Calling on iPhone). On Android, you'll see an option to "Update Wi-Fi Calling status" or "Refresh Wi-Fi Calling profile". Tap that. On iPhone, turn Wi-Fi Calling off, wait 10 seconds, then turn it back on. Also, reboot the phone after.
  3. Re-enter your E911 address. This is the big one people miss. Go to your carrier's website or app. On T-Mobile, it's under Profile > E911 Address. On Verizon, go to My Verizon > Account > Devices > Wi-Fi Calling. On AT&T, go to myAT&T > Wireless > Wi-Fi Calling. Re-enter your current address exactly as it appears in official records. Make sure it matches what Google Maps shows. Some carriers let you do this from the phone itself: on Samsung, go to Settings > Connections > Wi-Fi Calling > Update Emergency Address.
  4. Manually set DNS on your Wi-Fi connection. Your ISP's DNS servers can be slow or block some SIP traffic. On your phone, go to Wi-Fi settings > tap on your network name > modify network > show advanced options > set IP to Static (or DHCP but DNS manual). Set DNS 1 to 8.8.8.8 and DNS 2 to 8.8.4.4. On iPhone, go to Settings > Wi-Fi > tap the (i) icon > Configure DNS > Manual. Add 8.8.8.8 and 8.8.4.4. This fixes about 20% of stubborn cases.
  5. Check if your router has a firewall blocking UDP ports. Wi-Fi calling uses UDP ports 500, 4500, and 3478-3480. Some routers have a "VoIP" firewall setting that blocks these. Look for "SIP" or "VoIP" in your router's firewall settings and make sure it's set to allow or passthrough. If you see an option for "Application Layer Gateway" for SIP, disable it.

What to try if the main fix doesn't work

If you've done all the above and Wi-Fi calling still won't turn on, try these alternative fixes:

  • Switch to 2.4GHz Wi-Fi only. I've seen 5GHz bands cause issues with Wi-Fi calling on some phones, especially older ones. Go to your router settings and create a separate 2.4GHz network (or temporarily turn off the 5GHz band) and connect your phone to that. If it works, you know the problem is the 5GHz band or channel width settings (try setting 5GHz channel width to 40MHz instead of 80MHz).
  • Factory reset the phone's network settings. On Android: Settings > General Management > Reset > Reset Network Settings. On iPhone: Settings > General > Transfer or Reset iPhone > Reset > Reset Network Settings. This wipes saved Wi-Fi networks and Bluetooth pairings, so write down your Wi-Fi password first. But it clears any corrupt SIP cache or DNS settings that the carrier pushed.
  • Try a different router. If you're using a router your ISP gave you, it's likely a piece of junk. I've seen ISP routers that simply don't support Wi-Fi calling properly even with SIP ALG off. Borrow a friend's router or buy a $40 TP-Link Archer A6. That fixed a case for a client in a small office who had Comcast's gateway — it just wouldn't pass SIP traffic correctly.
  • Contact your carrier and ask them to reprovision Wi-Fi calling. This is last resort. Call your carrier's tech support and say "please reprovision Wi-Fi calling on my line." They can push a refresh from their end. I've seen this fix cases where the phone itself was fine but the carrier's database was out of sync.

How to prevent Wi-Fi calling issues in the future

Once you get it working, do these two things to keep it working:

  • Keep your E911 address updated whenever you move. Set a calendar reminder every 6 months if you rent. Carriers will silently disable Wi-Fi calling if your address doesn't match their records.
  • Don't let your router auto-update firmware without checking. Router manufacturers sometimes re-enable SIP ALG or change firewall settings in updates. I've seen a Netgear update turn SIP ALG back on three times in one year. Disable auto-update and only install new firmware manually after checking the release notes for any mention of VoIP or SIP changes.
  • Stick with a known-good router brand. I've had the least issues with Asus routers (especially the RT-AC68U and newer models) and TP-Link Deco mesh systems with SIP ALG disabled. Avoid cheap no-name routers from Amazon — they often have broken SIP implementations.

Note: If you use Wi-Fi calling for work, like taking client calls over it, set up a separate guest network on 2.4GHz just for your phone. That way, even if your main network has issues, Wi-Fi calling stays up. I do this for all my small business clients who rely on Wi-Fi calling.

That's it. Nine times out of ten, turning off SIP ALG and updating the E911 address fixes it. If not, the DNS trick or the 2.4GHz band swap will get you there. Don't waste time with carrier support until you've tried these — they'll just tell you to restart your phone and router anyway.

Related Errors in Network & Connectivity
0X00003B03 Fix 0x00003B03: UI language install fails on Windows 0XC00002CC STATUS_ONLY_IF_CONNECTED (0XC00002CC) – Fix When Offline Modem Online But No Signal Light? Here's the Fix 0X0000233A DNS_ERROR_RCODE_BADTIME (0X0000233A) – DNS Signature Expired
Wi-Fi calling not working Wi-Fi calling fix turn on Wi-Fi calling Android Wi-Fi calling iPhone router settings for Wi-Fi calling Wi-Fi calling not connecting E911 address Wi-Fi calling DNS settings Wi-Fi calling SIP ALG disable Wi-Fi calling troubleshooting

Was this solution helpful?

EP
Erropedia Team
Tech Support Editors
The Erropedia editorial team researches and documents real-world tech errors from across Windows, Linux, macOS, networking, databases, cloud platforms, and more. Every solution is reviewed for accuracy and updated as software and systems evolve.