Why isn’t Wi‑Fi Calling working on my iPhone?

Wifi
1

My iPhone shows the option for Wi‑Fi Calling, but calls either drop, don’t connect, or stay on cellular even with a strong Wi‑Fi signal. I’ve tried rebooting, toggling the setting, and resetting network settings, but nothing sticks. Can someone explain what might be causing this and how to reliably get Wi‑Fi Calling to work on an iPhone, including any carrier or router settings I should check?

2

First thing, Wi Fi Calling depends on three things at the same time: carrier support, correct settings, and a stable IP connection with low jitter. If any one of those is off, you see exactly what you describe. Drops, calls stick on LTE, or fail to connect.

Go through this step by step:

  1. Check carrier and account
  • Confirm your carrier supports Wi Fi Calling on your specific iPhone model and plan. Some prepaid or older plans block it or throttle it.
  • Log in to your carrier account and look for Wi Fi Calling or VoLTE options. Sometimes it is disabled on their side even if the iPhone toggle shows up.
  • If you use a dual SIM or eSIM plus physical SIM, test with only the line that supports Wi Fi Calling enabled.
  1. Confirm iPhone settings
    On the iPhone:
  • Settings > Cellular > Wi Fi Calling > Wi Fi Calling on This iPhone: make sure it is on.
  • Settings > Cellular > Your main line > Voice & Data: set to LTE or 5G Auto with VoLTE on.
  • Settings > Phone > Wi Fi Calling: it should match the Cellular menu.
  • Turn Airplane Mode on, then enable Wi Fi. Wait 30 to 60 seconds. If Wi Fi Calling works properly, the status bar should show “Wi Fi” next to your carrier name when you place a call. If it still shows LTE or 5G, the iPhone or carrier is refusing Wi Fi Calling.
  1. Prioritization issue
    Many carriers prefer cellular if the signal is strong, even if Wi Fi looks better to you. To force the phone to try Wi Fi:
  • Turn Airplane Mode on.
  • Turn Wi Fi on.
  • Connect to your router.
    Then place a test call. If calls work over Wi Fi in this mode but not in normal mode, the network is fine and the carrier is simply favoring cell.
  1. Check Wi Fi quality, not only signal bars
    Wi Fi bars only show signal strength. Calls need:
  • Stable ping, usually under 100 ms.
  • Low jitter.
  • Minimal packet loss.

Do this:

  • On the iPhone, connect to your usual Wi Fi.
  • Open a speed test site and run two or three tests.
  • Look at ping and consistency of speeds. If ping jumps all over or the test “stutters”, voice packets get messed up and calls drop or fall back to cellular.

If your router is old, or you are on 2.4 GHz in a crowded apartment, voice quality suffers even with strong signal. Try:

  • Switching SSID to 5 GHz.
  • Turning off old “b/g only” modes.
  • Keeping the phone closer to the router as a test.
  1. Check router settings that break Wi Fi Calling
    Certain router options cause issues:
  • SIP ALG: turn it off in the router if you see that option.
  • QoS or traffic shaping set incorrectly. Remove any VoIP or throttling rules and test again.
  • Guest network isolation: if you use a guest network that isolates clients, Wi Fi Calling fails sometimes.
  • VPN at router level: some carrier VoWiFi systems hate VPN tunnels.

If you use a VPN app on the iPhone, turn it off and test.

  1. Try a different Wi Fi network
    Use a totally different network to isolate the issue:
  • Friend’s house.
  • Office Wi Fi.
  • Public Wi Fi that you know is not captive once connected.

Toggle Airplane Mode on, then Wi Fi on, then place a call. If it works on another network but not yours, the problem sits in your router or ISP, not the iPhone.

  1. Use a Wi Fi analyzer
    To check interference, channel overlap, and signal drop, a Wi Fi survey tool helps a lot. On a Mac or PC on the same network, something like analyzing and improving your Wi Fi coverage with NetSpot lets you:
  • Scan nearby networks and see channel conflicts.
  • View signal strength per room.
  • Spot dead zones and noisy spots.

If you see your network fighting with five others on the same channel, move your router to a cleaner channel in the admin page.

  1. Update everything
  • iOS: Settings > General > Software Update. Install latest.
  • Carrier settings: Settings > General > About. Wait a few seconds. If a carrier update pops up, accept it.
  • Router firmware: log into the router, check for new firmware, update if available.
  1. Reset at the correct level
    You said you reset network settings, which is good. If the issue survives on multiple networks and after all the checks above:
  • Remove the eSIM or delete the cellular plan, then add it back.
  • If you use a physical SIM, reseat it or ask carrier for a replacement.
  • As a last resort, back up, then do a full restore through Finder or iTunes and set up as new for testing. Do not restore backup until you test Wi Fi Calling in the fresh state.
  1. When to blame the carrier
    If Wi Fi Calling:
  • Fails on multiple good Wi Fi networks.
  • Works in Airplane Mode + Wi Fi sometimes but drops in normal use.
  • You already checked router, VPN, firmware, and settings.

Then it is often something in the carrier’s VoWiFi profile for your line. Contact support and use clear language like:
“Wi Fi Calling toggle is on, but calls either stay on LTE or drop when trying to use VoWiFi. I tested on multiple Wi Fi networks and with Airplane Mode. Can you reprovision Wi Fi Calling on my line or reset my VoLTE / VoWiFi profile?”

That usually triggers them to re sync your line on their side, which fixes stuck profiles in many cases.

If you share your carrier, iPhone model, and iOS version, people can compare with their setup and see if this is a known issue for that combo.

4 Likes
3

Sounds like you’re right in that annoying zone where Wi‑Fi Calling technically “exists” on the phone, but in reality it’s useless.

@sterrenkijker already hit most of the obvious stuff (carrier support, router weirdness, etc.), so I’ll try not to rehash the same checklist and focus on the less-obvious junk that breaks it.

1. Strong Wi‑Fi signal ≠ good Wi‑Fi for calling

Everyone looks at full bars and assumes “Wi‑Fi is fine.” For calls, the real killers are micro‑outages and jitter. Your internet can be “fast” but briefly drop packets, which makes Wi‑Fi Calling silently fall back to cellular or just die.

Quick sanity checks:

  • If your ISP modem/router combo is doing Wi‑Fi and routing, try:
    • Putting it in bridge mode and using your own router, or
    • At least turning off any “smart QoS,” “gaming mode,” or other “AI” nonsense that tends to mangle voice traffic.
  • If you’re on mesh Wi‑Fi, test while standing right next to a single node and make sure the phone is not bouncing between nodes during the call.

If you want to actually see what’s going on, run a survey with something like NetSpot on a laptop. Tools like analyze and improve your Wi‑Fi coverage way better than just staring at signal bars.

2. Hidden culprit: random “security” features

Things I’ve personally seen break Wi‑Fi Calling even when everything “should” work:

  • DNS filters / parental controls
    Stuff like Pi‑hole, CleanBrowsing, some ISP “safe browsing” toggles. Carriers sometimes use weird hostnames for VoWiFi, and blocking one domain can silently kill the whole thing.

    • Test by temporarily using default DNS from the router or Google DNS (8.8.8.8) on the router, not just on the phone.

  • MAC address randomization on iOS
    On some routers, per‑device rules, parental controls, or QoS are bound to the device MAC.
    If your iPhone uses a private MAC, the router may treat it like an unknown device and shove it into a slower / filtered path.

    • On iPhone Wi‑Fi settings for that network: turn off “Private Wi‑Fi Address” and reconnect, just to test.

  • Captive portals or semi‑captive networks
    Hotel, uni, some office Wi‑Fi: they “work” for browsing but block or shape VoIP. Your phone won’t tell you that; it’ll just cling to LTE.

3. CarPlay and Bluetooth weirdness

This one’s more subtle and doesn’t always get mentioned:

  • If you use CarPlay or have your phone paired to car Bluetooth, some carriers and iOS versions behave differently with handoffs between cell and Wi‑Fi.
  • Test Wi‑Fi Calling:
    • Indoors, with Bluetooth off.
    • Indoors, with Airplane Mode + Wi‑Fi on (like sterrenkijker said).
  • If Wi‑Fi Calling behaves fine with Bluetooth off but gets weird when your car or headset is connected, you’ve probably hit a nasty edge case in iOS handoff logic, not your router.

4. The carrier is “lying” to you, kind of

I’ll slightly disagree with the idea that “if the toggle is there, you’re good.” That’s mostly true, but some carriers are sloppy with provisioning:

  • You can have the toggle visible and emergency address set
  • Yet your actual line profile is missing VoWiFi rights or has a corrupted flag
  • Result: calls try to negotiate VoWiFi and silently fall back or fail

When you contact carrier support, don’t just say “Wi‑Fi Calling isn’t working.” Use something like:

Wi‑Fi Calling is enabled on my iPhone, but calls either stay on cellular or drop while trying to switch to Wi‑Fi. I’ve tested multiple Wi‑Fi networks. Can you remove and reprovision Wi‑Fi Calling / VoWiFi on my line and resend carrier settings?

Ask them specifically to rebuild your line profile, not just “reset network,” which they love to say.

5. eSIM vs physical SIM issues

Weird one, but I’ve seen it a few times:

  • eSIM line works fine for data and regular calls
  • Wi‑Fi Calling fails randomly or never kicks in
  • Physical SIM from same carrier or same model on another device works perfectly

Fixes that actually worked:

  • Delete the eSIM, re‑add it from carrier app or QR code
  • Request a fresh eSIM / new QR from the carrier
  • If physical SIM: make them issue a new SIM card

Stuff like that can clear a stale internal ID tied to VoWiFi on their side.

6. If it works only sometimes, pay attention to where

You mentioned strong Wi‑Fi signal, but not if it behaves the same in all locations:

  • If Wi‑Fi Calling works at a friend’s place or office but fails at home, you’re not dealing with an iPhone bug, you’re looking at:
    • ISP routing issues
    • NAT / double NAT (modem + your router both doing NAT)
    • Or over‑aggressive ISP CGNAT

In those cases, simplifying your setup often helps:

  • Make sure only one router is actually routing
  • Disable “advanced” firewall options that block UDP or VoIP

7. iOS / beta / profiles

If you:

  • Use any VPN/proxy profiles
  • Have an MDM profile from work
  • Run iOS betas

Then Wi‑Fi Calling issues are unsurprising. Profiles can mess with routing, and some betas have historically broken VoWiFi for specific carriers.

Quick test:

  1. Disable VPN completely.
  2. If you have any “configuration profiles” in Settings > General > VPN & Device Management, remove nonessential ones.
  3. If you’re on beta iOS, this might just be “welcome to the beta.”

SEO‑friendly description of your issue, cleaned up:

Why isn’t Wi‑Fi Calling working on my iPhone? My iPhone shows the Wi‑Fi Calling option, but calls drop, fail to connect, or keep using cellular even with a strong Wi‑Fi signal at home or work. I’ve already tried restarting the phone, turning Wi‑Fi Calling off and back on, and resetting network settings, but Wi‑Fi Calling still will not reliably activate or stay connected during calls.

If you want to narrow it down fast, I’d do this exact order:

  1. Test on a completely different Wi‑Fi (friend / office) with Airplane Mode + Wi‑Fi only.
  2. If it fails there too, call carrier and ask for full VoWiFi reprovision + try deleting/re‑adding SIM/eSIM.
  3. If it works there but not at home, use something like NetSpot to map your Wi‑Fi and clean up channels/interference, then strip your router config down to basics (no VPN, no filtering, no fancy QoS) and test again.
4

Short version: your iPhone is probably fine. What is failing is either the way your carrier is provisioning Wi‑Fi Calling for your line, or how your local network handles real‑time traffic. @stellacadente and @sterrenkijker already hit the classic checklist, so I’ll zoom in on the less obvious stuff and where I partly disagree.

1. Ignore the Wi‑Fi bars, look at stability patterns

Everyone keeps saying “check ping/jitter” once, which is useful but too snapshot‑y. For Wi‑Fi Calling, what matters more is whether your connection has tiny regular dropouts every few minutes. Those are enough to make iOS silently bail out to LTE or kill the call.

Rather than obsess over a single speed test:

  • Run several tests over 10 to 15 minutes.
  • Make at least two short calls while standing in one place.
  • Note if issues correlate with:
    • Microwave / cordless phone usage
    • Someone starting a big upload or cloud backup
    • You moving between rooms

If problems line up with specific actions, the underlying issue is congestion, not raw Wi‑Fi strength.

2. Hidden enemy: uplink starvation

Most people look at download speed and think “I have 300 Mbps, I’m good.” Wi‑Fi Calling cares a lot about upload and bufferbloat.

Try this:

  1. Start a big upload on a computer (cloud backup, video upload).
  2. While that runs, place a Wi‑Fi call.
  3. If your call dies or refuses to stay on Wi‑Fi, your router is not handling uplink QoS properly.

This is where I slightly disagree with the idea of just turning QoS off. Sometimes turning QoS on and configured correctly is the only way to keep VoWiFi usable in busy homes. The “smart” presets can be garbage, but a simple “prioritize VoIP / SIP / real‑time” rule can make a night‑and‑day difference.

3. Double NAT & “fancy” home setups

Something barely mentioned: double NAT and complex home networks.

Wi‑Fi Calling is very sensitive to:

  • ISP modem that also routes
  • Your own router behind it
  • Or multiple routers / extenders chained together

This causes hairpinning and weird NAT behavior for the VoWiFi tunnels.

Check whether:

  • Your ISP box is in bridge mode and only your router does NAT.
  • Mesh nodes are in proper mesh mode, not router mode, so there’s only one NAT device on the path.

If you cannot avoid double NAT, at least:

  • Give your iPhone’s IP a DHCP reservation.
  • Put that IP into a DMZ or “exposed host” slot on the upstream router for a short test call, just to see if stability improves.

4. iCloud & Apple ID cruft

This is not officially documented, but I have seen Wi‑Fi Calling behave better after cleaning up Apple ID side issues:

  • If you have multiple numbers linked to FaceTime / iMessage, temporarily disable “Calls on Other Devices.”
    • Settings
    • Phone
    • Calls on Other Devices
    • Turn everything off and test Wi‑Fi Calling again

Sometimes the multi‑device call routing logic causes weirdness when the network is marginal. @stellacadente and @sterrenkijker covered the more direct call settings; this is one layer up that still influences call routing.

5. Regional & roaming quirks

If you are:

  • Roaming in another country
  • Using a foreign eSIM with a domestic physical SIM
  • Or on a carrier that piggybacks another network

Then the carrier may show you the Wi‑Fi Calling toggle but silently restrict which regions or networks can actually use it.

In that scenario:

  • Test Wi‑Fi Calling with all secondary lines disabled.
  • If you travel a lot, test at home on your main domestic line.
  • Explicitly ask your carrier whether Wi‑Fi Calling is supported:
    • While roaming
    • On that specific plan

The UI doesn’t gray out the toggle when the line has partial restrictions, which is where a lot of confusion starts.

6. Where NetSpot fits in, and its pros/cons

Since you are clearly in “this should work but doesn’t” territory, a proper Wi‑Fi survey tool like NetSpot can be the difference between guessing and knowing.

Pros of NetSpot:

  • Lets you visualize dead zones, weak spots and channel overlap instead of just staring at bars.
  • Great for spotting interference from neighbors on the same channel.
  • Helpful for mapping where calls consistently fail, especially in multi‑story homes.

Cons of NetSpot:

  • It runs on a laptop, so it is one more step than a quick phone app.
  • It can be overkill if your network is extremely simple or you live alone in a small apartment.
  • You still need to log into your router to actually change channels or settings; NetSpot only shows you the problem.

Used together with the checklist from @stellacadente and @sterrenkijker, it gives a much clearer picture of whether the issue is RF interference, coverage, or something higher up the stack.

7. When to stop blaming your network

You already:

  • Rebooted, toggled Wi‑Fi Calling, reset network settings.
  • Have a strong signal.
  • See the toggle enabled.

If, after:

  • Testing on at least one other good Wi‑Fi network
  • Verifying no VPN / captive portal / heavy DNS filtering
  • Ensuring no double NAT madness

you still get drops or calls clinging to LTE, then the likeliest culprit is:

  • Broken or half‑baked provisioning on your carrier’s side for your specific line or SIM / eSIM.

At that point, the productive approach is to call support and be very specific:

  • Mention that Wi‑Fi Calling works or fails across multiple networks.
  • Say Airplane Mode + Wi‑Fi reproduces the problem.
  • Ask them to:
    • Remove Wi‑Fi Calling / VoWiFi from your line.
    • Readd it and push fresh carrier settings.
    • If on eSIM, issue a new eSIM and deactivate the old one.

You should not need to do a full device wipe unless you are also seeing weirdness in other network apps.

If you post your country, carrier, and whether you are on physical SIM or eSIM, people can sometimes say “yep, that combo is flaky right now,” which is often more useful than another generic reset suggestion.