Wi-Fi Calling Not Working on Android? Carrier Fixes

If Wi-Fi calling isn't working on your Android phone, check three things first: the Wi-Fi calling switch is on for the right SIM, your carrier has a 911 (E911) address on file, and the Wi-Fi network actually has internet. Then turn on airplane mode, turn Wi-Fi back on, and place a test call. If it still fails, the usual culprits are a router or VPN blocking the encrypted connection your carrier uses (UDP ports 500 and 4500), HD Voice turned off on your line, or a phone your carrier doesn't support for Wi-Fi calling.

Also in this topic: Android Guides hub.

Jump to: match your symptom · turn it on (Pixel and Galaxy) · E911 address · airplane mode test · T-Mobile, Verizon, AT&T rules · router ports and VPNs · switch missing or grayed out · reset and carrier help · abroad · FAQ

Quick answer: Wi-Fi calling needs four things at once: carrier support for your phone and plan, a registered 911 address, HD Voice (VoLTE) on your line, and a Wi-Fi network that lets the call's encrypted tunnel through. Most failures are one of those four. A missing switch almost always means the carrier hasn't enabled the feature for that phone, not that the phone is broken.

How we put this together: The menu paths, requirements, and port numbers below come from Google's Phone app and Pixel help pages, Samsung US support, Android's developer documentation, and the Wi-Fi calling pages of T-Mobile, Verizon, and AT&T, all linked in place and checked on October 24, 2026. We haven't tried every fix on every phone or carrier, and menu names can differ by phone maker and software version.

Why Is Wi-Fi Calling Not Working? Match the Symptom

Wi-Fi calling is a carrier feature that sends your normal calls and texts over a Wi-Fi internet connection instead of a cell tower, using your regular phone number. Because it depends on your carrier, your phone, and the Wi-Fi network, the fix depends on where it breaks. Find your symptom here first.

What you see	Most likely cause	Start here
No Wi-Fi calling option in Settings	Carrier doesn't enable it for this phone or plan	Switch missing
Switch turns on, then a message says to contact your carrier	No E911 address, or the feature isn't active on your account	E911 address
Switch is on, but calls still use cell signal	Calling preference is set to mobile, or the phone thinks Wi-Fi is too weak	Airplane mode test
Works on other Wi-Fi, fails at home or work	Router, firewall, or network blocking ports 500 and 4500	Router ports
Fails only with a VPN on	The VPN is carrying or blocking the call's tunnel	Router ports and VPNs
Calls connect but drop or sound choppy	Slow or unstable Wi-Fi	Carrier speed rules
Pixel shows "Wi-Fi calling has been turned off"	The phone detected a problem and switched it off	Reset and carrier help

How to Turn On Wi-Fi Calling on a Pixel or Samsung Galaxy

Turn the feature on in Settings and accept any terms and address prompts the carrier shows. The menu is in a different place on Pixel and Samsung phones, and on dual-SIM phones it's set per SIM, so make sure you're on the SIM that holds your carrier line.

Pixel and phones using Google's settings

1. Open Settings and tap Network & internet > SIMs.
2. Tap your carrier SIM, then Wi-Fi calling.
3. Turn on Use Wi-Fi calling, and accept the terms and enter your emergency address if asked.

Google's Wi-Fi calling help page is blunt about a missing option: "If you don't find this option, your carrier doesn't support this feature." Its Pixel connectivity page adds that when Wi-Fi calling is on, the phone routes calls over Wi-Fi or your carrier's network "based on your preference or signal strength." When a call is going over Wi-Fi, Google says you'll see "Internet Call" or "Wi-Fi calling" in the notification.

Samsung Galaxy

1. Open Settings and tap Connections > Wi-Fi Calling.
2. Turn on the switch. If a popup asks for emergency information, fill it in and tap Save.
3. Tap the words Wi-Fi Calling (not the switch) to set Calling preference to Wi-Fi preferred if you want Wi-Fi used even when you have some signal.

Samsung's Wi-Fi Calling setup page says you need to be connected to Wi-Fi and have active service on a SIM or eSIM to turn it on, and that on some phones there's also a Wi-Fi Calling tile in Quick settings. It has one carrier-specific note worth reading twice: on AT&T phones, VoLTE must be turned on before Wi-Fi Calling will activate.

Add or Fix Your E911 Address

All three major US carriers require a registered 911 address before Wi-Fi calling will work, and a missing one is the most common reason the switch won't stay on. Verizon's Wi-Fi Calling FAQ explains why: the FCC requires carriers that offer voice over the internet to support 911 calls and collect a registered location, because a Wi-Fi call can't always be located the way a cell call can.

• On the phone: The address is usually in the same menu as the switch. On a Galaxy, tap the words Wi-Fi Calling, then Emergency address. On a Pixel, open the Wi-Fi calling screen under your SIM and look for the emergency address entry. Ting's Wi-Fi calling troubleshooting page gives the same paths.
• T-Mobile: Its troubleshooting page names the error: REG09 means the 911 address is missing. T-Mobile says you can update the address in your T-Mobile account online or through Customer Care.
• Prepaid and smaller carriers: Some want the address entered in your online account, not just on the phone. Tello, for example, says the Android message "To allow Wi-Fi Calls on this account, contact your carrier" means you need to add the E911 address in your Tello account first.

Use the street address where you'll use Wi-Fi calling most, and update it when you move. Verizon and AT&T both say 911 calls try the cellular network first whenever it's available. Verizon adds that this happens even in airplane mode, and the registered address is used when the call has to go over Wi-Fi.

Run the Airplane Mode Test

The fastest way to tell whether Wi-Fi calling works at all is to take the cell network out of the picture. Turn on airplane mode, turn Wi-Fi back on, and call someone. If the call goes through, Wi-Fi calling works, and your phone was simply choosing the cell network.

If that's what happened, set the preference instead of living in airplane mode. On a Galaxy, change Calling preference to Wi-Fi preferred. T-Mobile's own Android steps for its Wi-Fi Calling service end with "Tap Wi-Fi Preferred." Ting notes that switching to Wi-Fi preferred can help when your cell signal is low.

If the test call fails, keep airplane mode on for the next sections. It makes it clear that any failure is about Wi-Fi, not the cell network.

What T-Mobile, Verizon, and AT&T Require

Each major US carrier publishes its own requirements, and they're stricter than most guides suggest. T-Mobile, for example, rules out two kinds of internet connection entirely. Here's what each carrier's support pages say.

Requirement	T-Mobile	Verizon	AT&T
911 address on file	Required (error REG09 if missing)	Required; you confirm a US address when you turn it on	Required; set on the same screen as the switch
HD Voice / VoLTE	Not listed as a separate step	HD Voice required (on by default on current phones)	Account must be set up for HD Voice
Wi-Fi speed	At least 2 Mbps up and down	Not published; suggests a Wi-Fi extender if calls are poor	Not published; MTU of 1500 recommended
Connections not supported	Satellite internet and cell phone hotspots	Not specified	Not specified
Router ports to allow	UDP 500 and 4500 (plus 5061 for older WFC 1.0)	Not published	UDP 500 and 4500, IPsec pass-through, TCP 143 (IMAP)
Phones bought elsewhere	Most work, but support isn't guaranteed	Search Settings for Wi-Fi Calling to check	"Compatible" AT&T phone and eligible plan required
How you know it's on (Android)	Wi-Fi Calling icon in the status bar	Wi-Fi icon on the call button	A plus sign (+) next to the Wi-Fi icon

Sources: T-Mobile's Wi-Fi Calling page and corporate network page; Verizon's Wi-Fi Calling FAQ and HD Voice FAQ; AT&T's Wi-Fi Calling page and LAN and VPN configuration page.

Two details here explain a lot of "it just doesn't work" complaints. First, T-Mobile doesn't support Wi-Fi calling over satellite internet or over another phone's hotspot, so using a second phone's hotspot as Wi-Fi isn't a workaround on T-Mobile. Second, T-Mobile's two numbers can look contradictory: it requires 2 Mbps for Wi-Fi calling, but its troubleshooting page only treats speeds under 0.25 Mbps as an internet problem. A connection between those numbers can browse fine and still fail calls. Run a speed test where you make calls, not next to the router.

For Verizon, HD Voice is the one to check on older phones. Verizon says HD Voice is on by default for its current smartphones, but older Android phones may need it turned on manually, usually under Advanced Calling. If you're not sure, search Settings for "HD Voice," "VoLTE," or "Advanced Calling."

Check Your Router, Firewall, and VPN

If Wi-Fi calling works on other networks but not on yours, the network is blocking it. Carrier Wi-Fi calling runs through an encrypted IPsec tunnel to the carrier, and both T-Mobile and AT&T list the same two ports it needs: UDP 500 (IKE) and UDP 4500 (IPsec NAT traversal). Firewalls, office and school networks, and router security features can block them.

On a home router

• Restart the modem and router. T-Mobile's steps: turn both off, wait 30 seconds, turn on the modem, and turn on the router once the modem is online.
• Update the router's firmware. T-Mobile, AT&T, and TP-Link all list this.
• Allow IPsec pass-through and UDP 500 and 4500. AT&T says Wi-Fi Calling "requires IPSec pass-through to be allowed" and that ports 500, 4500, and 143 must be open. It also recommends an MTU of 1500.
• Try turning off SIP ALG. TP-Link's Wi-Fi calling FAQ lists disabling SIP ALG as its second step, before port forwarding. It's a router feature meant to help internet phone services, and the setting is usually under NAT or WAN options.
• Turn off the router's firewall or "security" add-ons briefly to test. T-Mobile's checklist includes making sure you don't have a firewall turned on.

T-Mobile also suggests staying within 15 feet of the router while testing and keeping away from 2.4 GHz baby monitors, cordless phones, and some Bluetooth devices, which can interfere.

On work, school, or hotel Wi-Fi

You can't change these networks, so if the ports are blocked, Wi-Fi calling won't work there. Finish any sign-in page first. If you're the IT admin, T-Mobile's corporate network page lists the IP ranges and ports to allow, and AT&T's lists the hostnames its phones need to reach, including epdg.epc.att.net. If the network itself won't load pages, fix that first with our guide to Android Wi-Fi connected but no internet.

Turn off your VPN

Turn off any VPN app and test again. Ting lists turning off VPNs and firewalls on the phone or router as a step, and a VPN that routes all traffic changes where your phone appears to be. T-Mobile's billing notes add a cost angle: if a VPN connects you through another country, you may get a welcome text and be charged international rates, even if you're in the US. If you need a VPN day to day, our list of the best VPN apps for Android notes which ones have split tunneling, so you can exclude traffic you don't want to send through the VPN.

T-Mobile also says to turn off battery-saving features and uninstall apps that manage or scan Wi-Fi networks, since both can interfere with the connection.

Wi-Fi Calling Switch Missing or Grayed Out?

If there's no Wi-Fi calling option, your carrier hasn't enabled it for that phone, and no setting on the phone will add it. Android decides whether to show the feature from carrier settings built into the phone. Android's CarrierConfigManager reference includes a flag for exactly this, specifying whether Wi-Fi calling "should be available for carrier," along with a separate flag for whether the carrier allows a "Wi-Fi only" mode.

That's why the same phone model can show Wi-Fi calling on one carrier and not another, and why unlocked or imported phones often lack it. What to do:

• Install system updates. Samsung's Wi-Fi Calling troubleshooting page and T-Mobile both list updating the phone's software.
• Check that your SIM or eSIM is active. Samsung says you need a SIM inserted or an active eSIM. If you just moved your number, finish the move first; our mobile data fix guide covers SIM activation and carrier SIM locks.
• Ask your carrier whether your phone is supported. T-Mobile says most phones bought elsewhere work, but it can't guarantee Wi-Fi calling on them. AT&T requires a compatible phone and an eligible plan.

A grayed-out switch usually means the phone isn't connected to Wi-Fi yet or the SIM isn't active. Samsung says you must be on Wi-Fi with active service to turn the feature on.

Restart, Reset Mobile Network Settings, Then Call Your Carrier

If nothing above worked, restart the phone, then reset mobile network settings, and then contact your carrier. Do them in that order, because each step is harder to undo than the one before.

• Restart. Google's Wi-Fi calling page says that if your phone detects Wi-Fi calling problems, it turns the feature off until they're fixed. If the problem continues, you get a notification that Wi-Fi calling has been turned off entirely, and Google says you may need to restart or have your carrier reactivate it. Many guides miss this, so turn the switch back on after you fix the cause.
• Reset mobile network settings first, not everything. On a Pixel, go to Settings > System > Reset options > Reset Mobile Network Settings. On a Galaxy, go to Settings > General management > Reset > Reset mobile network settings. Current Pixel and Galaxy phones list Wi-Fi and Bluetooth as a separate reset, so this one keeps your saved Wi-Fi networks. Samsung warns that you may need to re-enter a custom APN afterward; we keep current values for T-Mobile APN settings and AT&T APN settings.
• Reset Wi-Fi and Bluetooth only if one network is the problem and forgetting and rejoining it didn't help. That reset deletes every saved Wi-Fi password.
• Contact your carrier. Ask them to confirm that Wi-Fi calling and HD Voice are active on your line, that your E911 address is valid, and that your phone is supported. T-Mobile also points to the troubleshooter in its T-Life app. Call from another phone if you can.

Using Wi-Fi Calling Outside the US

Wi-Fi calling is one of the cheapest ways to call home while traveling, but the rules differ by carrier and destination, and some countries block it. Here's what the carriers say.

• Calls to US numbers are free on all three carriers over Wi-Fi calling, even from abroad. Calls to non-US numbers are billed at international rates, depending on your plan or add-on.
• AT&T blocks Wi-Fi Calling in some countries. Its page lists China, Cuba, North Korea, India, Iran, Israel, Pakistan, Saudi Arabia, Sudan, Syria, Turkey, the United Arab Emirates, and Vietnam. T-Mobile says it isn't available where Wi-Fi calling is prohibited by law, "including North Korea, Iran, and Syria."
• Android has an edge on Verizon. Verizon says iPhones must be connected to its network in the US to turn on Wi-Fi Calling and can't turn it on after leaving the country. Android phones can activate it over Wi-Fi.
• Watch for silent switches to roaming. T-Mobile warns that if Wi-Fi drops for a moment, a call can move to a local cell network and cost roaming charges. Its suggested fix: turn on airplane mode, then turn on Wi-Fi and Wi-Fi calling. On Android, also check the roaming preference (sometimes called "When roaming"); Verizon suggests choosing Wi-Fi preferred when you travel.
• AT&T doesn't support 211, 311, 511, and 811 calls over Wi-Fi Calling, so dial those over cell service.

If calls on cell service vanish to voicemail while you're away, that's a different problem; see our guide to Android calls going straight to voicemail.

Bottom Line

Turn Wi-Fi calling on for the right SIM, make sure your carrier has your 911 address, and run the airplane mode test. If it works elsewhere but not at home, open UDP 500 and 4500 and turn off your VPN. If the switch is missing, it's a carrier decision, so update the phone and ask your carrier whether your model is supported.