Wi-Fi Calling Not Working With a VPN? Fixes for Android, iPhone and Routers (2026)

Date:

If Wi-Fi Calling stops working the moment you connect a VPN, or your phone falls back to weak cellular signal whenever the VPN is on, you’re not imagining it. Wi-Fi Calling is a carrier service that builds its own encrypted connection to your carrier, and a VPN app or VPN router can get in its way. This guide explains when that happens on Android, iPhone and VPN routers, and how to fix it, using Apple, Google, carrier and VPN-provider documentation. We did not run our own lab tests for this page; every claim is linked to its source.

This article contains no affiliate links. See our affiliate disclosure and how we review. Updated: November 2026

Bottom line: first prove the VPN is the cause by testing with it off, then exclude Wi-Fi Calling from the tunnel instead of dropping the VPN entirely.

  • Android: exclude the phone and carrier system apps with your VPN’s split tunneling, or disconnect for calls.
  • iPhone: iOS keeps Wi-Fi Calling out of all-traffic VPN tunnels by default, so check the Wi-Fi network and carrier first.
  • VPN router: Wi-Fi Calling needs IPsec on UDP 500 and 4500; route the phone outside the tunnel if calls fail.
  • Still broken with the VPN off? It isn’t the VPN. Follow Apple’s or Google’s steps and call your carrier.

Why a VPN can break Wi-Fi Calling

Wi-Fi Calling isn’t an ordinary app. Your phone opens a secure tunnel of its own to your carrier and sends calls and texts through it. AT&T says its Wi-Fi Calling requires IPsec pass-through and uses UDP ports 500 and 4500 (IKEv2), and T-Mobile lists the same two ports for IPsec authentication and encrypted voice traffic. In other words, it’s already a VPN-like connection.

When you add a consumer VPN, that carrier tunnel may have to travel inside your VPN tunnel, through a VPN server, to the carrier. Depending on the phone, the VPN app and the network, the result can be:

  • Wi-Fi Calling never registers, so calls go over cellular (or fail where cellular is weak).
  • Calls connect but drop, or texts and voicemail arrive late.
  • The phone turns Wi-Fi Calling off on its own after detecting problems.

Google’s own carrier says it plainly: Google Fi Help warns that Wi-Fi calling may not work if you have a VPN turned on, and says to turn off the VPN or update its settings so the Google Fi app can bypass it.

Step 1: Confirm the VPN is really the cause

Before changing VPN settings, make one test call on the same Wi-Fi network with the VPN disconnected, then one with it connected. If both fail, the VPN isn’t your problem. Check these basics first:

  • Wi-Fi Calling is on and supported. On iPhone, Apple puts it under Settings > Cellular > (your line) > Wi-Fi Calling. On Android phones using Google’s Phone app, Google lists Settings > Network & internet > SIMs > (carrier SIM) > Wi-Fi calling, and says that if you don’t find the option, your carrier doesn’t support it. Menu names can differ on other Android brands.
  • The phone shows it’s using Wi-Fi Calling. Apple says you’ll see “Wi-Fi” in the status bar while viewing Control Center. Google says you’ll see “Internet Call” or “Wi-Fi calling” on the notification screen.
  • The Wi-Fi network allows it. Apple notes that not all Wi-Fi networks work with Wi-Fi Calling and suggests trying a different network. Hotel and office networks often block the ports listed above; see our hotel Wi-Fi VPN guide for how restrictive networks behave.

If calls work with the VPN off and fail with it on, continue with the fix for your device.

Fix on Android: exclude calling from the VPN with split tunneling

Android VPN apps usually route every app through the tunnel. The fix is split tunneling, which lets chosen apps bypass the VPN. Proton VPN offers it in the Android app under Settings > Split Tunneling (Exclude mode) on paid plans, and NordVPN offers it under Profile > Settings > Split tunneling on Android, Android TV and Windows.

Which apps to exclude isn’t documented by Google or the VPN providers we checked, because Wi-Fi Calling is handled by Android system components rather than one app. What we found:

  • In a Tailscale GitHub issue, a Google Fi user on a Pixel reported that Wi-Fi Calling stopped whenever the Tailscale VPN was on. A Tailscale engineer suggested excluding telephony-related apps in split tunneling, noted that Wi-Fi Calling “is handled entirely by the OS,” and the user later reported it was working consistently.
  • On Google Fi, Google names the Google Fi app as the one to let bypass the VPN.
  • On other carriers, look in your VPN’s app list for system entries related to phone, calling, carrier services or IMS, and exclude those. Show system apps if your VPN hides them by default.

Two cautions. First, excluded apps use your normal connection, not the VPN; NordVPN also warns that excluded apps can still use the VPN’s DNS servers, which can confuse apps that check location. Second, Proton VPN says split tunneling isn’t compatible with its kill switch on most platforms, so turning one on may mean turning the other off. Our kill switch guide explains that trade-off.

After changing settings, reconnect the VPN, wait for the Wi-Fi Calling indicator, and place a test call. Google says that if your phone detects Wi-Fi calling issues it turns the feature off until the problem is fixed, so you may need to switch it back on or restart the phone. For other Android VPN problems, see VPN not working on Android.

Fix on iPhone: check the network and carrier first

On iPhone, the VPN is less often the culprit. Apple’s developer documentation says that when a VPN uses includeAllNetworks to send all traffic through the tunnel, the excludeCellularServices setting keeps cellular services such as Wi-Fi Calling, MMS, SMS and Visual Voicemail out of the tunnel, and that its default value is on. Apple also says the system always excludes cellular-only services such as VoLTE.

That doesn’t guarantee every VPN app behaves well, and you can’t change it yourself: NordVPN says it doesn’t offer split tunneling on iOS or macOS. If Wi-Fi Calling only fails with one VPN connected, disconnect it before calls or try another protocol in the app. Otherwise, work through Apple‘s steps, waiting two minutes between each:

  1. Confirm your carrier offers Wi-Fi Calling and the iPhone has the latest software; if both are true and it still fails, contact your carrier.
  2. Settings > Cellular > (your line) > Wi-Fi Calling: make sure it’s on.
  3. Restart the iPhone.
  4. Connect to a different Wi-Fi network.
  5. Turn Wi-Fi Calling off and on again.
  6. As a last step, Settings > General > Transfer or Reset iPhone > Reset > Reset Network Settings. It resets your saved Wi-Fi networks and other network settings, so have your Wi-Fi passwords ready.

If your VPN on iPhone has other problems, see VPN not working on iPhone.

Fix on a VPN router: let calls bypass the tunnel

A VPN router sends every device’s traffic through the VPN, including your phone’s Wi-Fi Calling tunnel. Carriers publish what that traffic needs: AT&T requires IPsec pass-through, UDP 500 and 4500, TCP 143 for IMAP, and recommends an MTU of 1500, listing epdg.epc.att.net, sentitlement2.mobile.att.net and vvm.mobile.att.net as hosts that must be reachable. T-Mobile lists UDP 500 and 4500 for the address block 208.54.0.0/16.

If calls fail only when the router’s VPN is on, your options are:

  • Exclude the phone. Many VPN-capable routers support policy-based routing that sends chosen devices outside the tunnel. Check your router’s documentation for the exact feature name.
  • Exclude the carrier’s addresses. Route the hosts or address block your carrier publishes (such as T-Mobile‘s 208.54.0.0/16) outside the VPN.
  • Use a separate network. T-Mobile recommends a dedicated SSID for Wi-Fi calling on multipurpose business networks; at home, a guest network that skips the VPN does the same job.

If the router’s VPN also drops for other devices, see why a VPN keeps disconnecting.

Do you lose privacy by excluding Wi-Fi Calling?

Less than you might think. Wi-Fi Calling already travels over IPsec, which AT&T describes as a method of encrypting traffic to provide a secure voice and data path. Your carrier handles your calls and texts whether or not a VPN is on, so a VPN wasn’t hiding them from your carrier anyway. What you give up is narrower: excluded traffic leaves through your real IP address on the local network. Everything else on the phone can stay on the VPN, and you can check that it does with our VPN leak test. If a VPN also breaks banking apps, see why a VPN blocks banking apps.

FAQ

Does a VPN block Wi-Fi Calling?
It can. Google says Wi-Fi calling may not work on Google Fi if you have a VPN turned on, and recommends turning the VPN off or letting the Fi app bypass it. On iPhone, Apple’s VPN framework excludes Wi-Fi Calling traffic from all-traffic tunnels by default, so failures there more often come from the Wi-Fi network or carrier setup.

How do I keep my VPN on and still use Wi-Fi Calling on Android?
Use your VPN’s split tunneling to exclude the phone and carrier system apps. Proton VPN and NordVPN both offer app-based split tunneling on Android. In a Tailscale support thread, excluding telephony-related apps restored Wi-Fi Calling for a Google Fi user. If your VPN has no split tunneling, disconnect it for calls.

Can I exclude Wi-Fi Calling from a VPN on iPhone?
Usually there’s nothing to exclude. Apple’s developer documentation says that when a VPN routes all traffic, the excludeCellularServices setting, which is on by default, keeps Wi-Fi Calling, MMS and Visual Voicemail traffic out of the tunnel. NordVPN says it doesn’t offer split tunneling on iOS, so if a VPN still causes problems, disconnect it before calls.

Why does Wi-Fi Calling fail when my router runs a VPN?
A router VPN carries every device’s traffic, including the phone’s Wi-Fi Calling connection. AT&T and T-Mobile say Wi-Fi Calling uses IPsec on UDP ports 500 and 4500, and AT&T says IPsec pass-through must be allowed. If the VPN path interferes, route your phone or your carrier’s Wi-Fi Calling addresses outside the router’s tunnel, if your router supports that.

What ports does Wi-Fi Calling need?
AT&T lists UDP 500 and 4500 (IKEv2) and TCP 143 (IMAP), recommends an MTU of 1500, and names epdg.epc.att.net among the hosts. T-Mobile lists UDP 500 and 4500 for its current Wi-Fi Calling, plus TCP 443 and 993 for authentication and visual voicemail. Other carriers publish their own requirements.

Is it safe to make Wi-Fi calls without a VPN?
Your VPN doesn’t need to carry Wi-Fi calls for them to be protected in transit. AT&T and T-Mobile describe Wi-Fi Calling as running over IPsec, which AT&T calls a method of encrypting traffic for a secure voice and data path. A VPN still protects your other apps on public Wi-Fi.

Related guides: VPN not working on Android · VPN not working on iPhone · VPN blocks banking app · VPN kill switch not working

Sources: Apple Support: Make a call with Wi-Fi Calling, Apple Developer: includeAllNetworks, Apple Developer: excludeCellularServices, Google Phone app Help: Make calls over Wi-Fi, Google Fi Help: Make calls over Wi-Fi, Proton VPN: How to use split tunneling, NordVPN Support: split tunneling, NordVPN Support: CarPlay, Android Auto and casting, Tailscale GitHub issue #13189, AT&T: Wi-Fi Calling LAN and VPN configuration, T-Mobile: Wi-Fi Calling on a corporate network. Checked November 18, 2026.

Impulsblog Editorial
Impulsblog Editorial
The Pulsblog editorial team.

LEAVE A REPLY

Share post:

Subscribe

spot_imgspot_img

Popular

More like this
Related

VPN Not Working on Nintendo Switch? Setup, NAT and eShop Fixes (2026)

Nintendo Switch and Switch 2 can't run VPN apps. Here's why a router or PC-shared VPN fails, how to fix NAT Type D/F, what smart DNS does, and why the eShop won't change.

How to Turn Off Ad Tracking on iPhone and Android (Every Setting, 2026)

Step-by-step settings to stop ad tracking on iPhone and Android: App Tracking Transparency, Apple Personalized Ads, deleting the Android advertising ID, Ads privacy and Google's My Ad Center.

VPN Not Working on PS5 or Xbox? Setup Fixes and NAT Problems (2026)

PS5 and Xbox can't run VPN apps. Here's why a router or PC-shared VPN fails on consoles, how to fix hotspot and strict NAT problems, and which ports to open.

How to Turn Off ACR on Your Smart TV (Samsung, LG, Vizio, Roku, Fire TV, Google TV)

Step-by-step menu paths to turn off ACR viewing-data tracking on Samsung, LG, Vizio, Roku TV, Fire TV, Google TV and Hisense smart TVs, and what it won't stop.