Your phone says Wi-Fi Calling is switched on. Calls still fail to connect, drop mid-sentence, or never move onto Wi-Fi at all. Your cell signal at home is weak, which is exactly why you need this to work.
Wifi calling not working at home usually points at your router, not your phone. Wi-Fi Calling builds an encrypted tunnel from your phone to your carrier, and a home network can quietly block it. The short answer: allow IPsec pass-through, keep UDP ports 500 and 4500 open, set the MTU to 1500, and make sure no DNS filter is hiding your carrier’s servers.
Most guides stop at toggling the feature and resetting network settings. This one starts on the network side, because your carrier’s own documentation does.
What Your Carrier Actually Needs From Your Router
AT&T’s support article on configuring your LAN and VPN for Wi-Fi Calling is blunt about it. It says “AT&T Wi-Fi Calling requires IPSec pass-through to be allowed.” It also lists the ports to open: “Open data ports 500, 4500, and 143.” Ports 500 and 4500 are UDP, used for IKEv2, the protocol that sets up the encrypted tunnel. Port 143 is TCP, used for IMAP.
The same page asks you to “Set Maximum Transmission Unit (MTU) to 1500.” It explains that Wi-Fi Calling “performs best if the MTU is set to 1500.” Finally, it names three servers your traffic should be able to reach: epdg.epc.att.net, sentitlement2.mobile.att.net, and vvm.mobile.att.net.
Those ports and server names come from AT&T. Other carriers use their own server names, so check your carrier’s support page for the exact list. The general idea still applies everywhere. Your phone needs a clear outbound path to a carrier server, and anything in the way breaks calling while normal browsing keeps working.
Why It Fails Only at Home
Cellular calls never touch your router, so nothing there can interfere. Wi-Fi Calling is different. Every call rides through your modem, router, and any filtering you’ve added. A feature that works at the office and fails at home is the classic sign that something on your home network is the cause.
That also explains why resetting the phone rarely helps. The phone is usually fine. The path it takes to the carrier is the broken part.
Fix 1: Test the Same Phone on a Different Wi-Fi Network
Before you touch your router, confirm the network is the problem. This takes two minutes and saves you from changing settings you didn’t need to change.
How to check:
- Turn on your phone’s personal hotspot from a second phone, or join a friend’s or café’s Wi-Fi
- Make sure Wi-Fi Calling is switched on in your phone’s settings
- Place a test call and watch whether Wi-Fi Calling connects
- If it works there and fails at home, wifi calling not working at home is a network problem, and Fixes 2 through 5 apply
- If it fails everywhere, skip ahead to Fix 6, since the cause is on the phone or your carrier account
Fix 2: Turn On IPsec Pass-Through and Open the UDP Ports
This is the direct fix for wifi calling not working at home when your router is blocking the tunnel. Menu names vary by brand. Look under Advanced, Security, or VPN settings.
How to fix:
- Log into your router’s admin page, usually at 192.168.1.1 or a similar address printed on the router
- Find a setting called IPsec Passthrough or VPN Passthrough, and make sure it’s enabled
- Open the firewall, parental control, or security section and look for rules that block outbound UDP traffic
- Confirm that UDP ports 500 and 4500 can go out to the internet
- Save your changes, reboot the router, and then retest a Wi-Fi call
Many routers allow outbound traffic by default, so you may find nothing to change. In that case, move on to the next fix rather than assuming this one failed.
Fix 3: Set the MTU to 1500
A wrong MTU is a quiet cause of wifi calling not working at home. An MTU that’s too small can break a tunnel that would otherwise work. AT&T asks for 1500, so match that value if your router lets you change it.
How to fix:
- In your router’s admin page, open the WAN or Internet settings
- Find the MTU field
- Set it to 1500, unless your internet provider requires a different value
- Save, reboot, and retest
Some connection types, such as PPPoE, often use a lower default. Check your provider’s guidance before you change it, and write down the original value first so you can undo it.
Fix 4: Test Your DNS Filter Before You Blame It
Encrypted DNS and ad-blocking DNS can interfere with Wi-Fi Calling. The evidence is real but mixed, so test before you change anything.
A thread on TechEnclave describes a Jio user in India who couldn’t run ad-blocking DNS and Wi-Fi Calling together. Mullvad DNS, AdGuard DNS, AhaDNS, and NextDNS all caused trouble at some point. One reply suggested the DNS provider “might be blocking (or simply not receiving) DNS responses for *.3gppnetwork.org or vowifi.jio.com.”
Carrier servers often sit under that 3gppnetwork.org name, and the thread shows examples like epdg.epc.mnc873.mcc405.pub.3gppnetwork.org.
Treat this as a lead, not a verdict. In that same thread, allowlisting the Wi-Fi Calling domains didn’t fix things for the original poster, who ended up turning off private DNS. A separate NextDNS support thread looked like a DNS bug at first. A carrier’s domain failed through NextDNS but resolved through Google’s 8.8.8.8. The poster later wrote, “False alarm. This was an IPv6 problem at the provider.”
How to check:
- On a computer connected to your home network, open Terminal or Command Prompt
- Run nslookup epdg.epc.att.net, and swap in your carrier’s server name if you’re not on AT&T
- Run it again against a public resolver: nslookup epdg.epc.att.net 8.8.8.8
- If the first lookup fails or returns 0.0.0.0 and the second returns a real address, your DNS filter is the cause
- In that case, allowlist your carrier’s domains in the filter, or turn the filter off for your phone
- If both lookups fail or both succeed, DNS isn’t your problem, so move on
Fix 5: Check Firewalls and Double Routers
Wifi calling not working at home often gets worse with a business-grade firewall or two routers in a row. Each one is another place for the tunnel to get stuck.
Fortinet’s community guide on allowing Wi-Fi Calling through a FortiGate lists two details worth knowing. It says “the firewall policy options port-preserve must be disabled to avoid session clash since multiple phones may use the same source port for IKE.” It also warns that the “default UDP idle timer is three minutes” and that reducing it “may cause the IPsec tunnel to the carrier to be torn down.”
You don’t need a FortiGate for that to matter. Any firewall that shortens UDP timeouts or rewrites source ports can cause the same kind of trouble.
How to fix:
- If you have a firewall appliance, allow UDP 500 and UDP 4500 to your carrier’s servers only
- Check that your UDP idle timeout isn’t set below a few minutes
- If you’re running your ISP’s gateway plus your own router, put the gateway into bridge mode so only one device handles traffic. Our Sonos guide walks through the same bridge-mode steps
- Update the firmware on your modem and router, since AT&T recommends keeping them current
Fix 6: Reset the Phone Side Last
Once the network checks out, go back to the phone. Do this last, because it rarely fixes a network block.
How to fix:
- Turn Wi-Fi Calling off, wait ten seconds, and turn it back on
- Restart the phone, then check for a carrier settings update in your system settings
- Confirm Wi-Fi Calling is enabled on your carrier account, not only on the phone
- As a final step, reset network settings. This erases saved Wi-Fi passwords, so keep yours handy
Frequently Asked Questions
Why is wifi calling not working at home but fine at work? Your home network is blocking or interfering with the encrypted tunnel to your carrier. Common causes are disabled IPsec pass-through, blocked UDP ports 500 and 4500, an unusual MTU, a DNS filter, or a second router. A different network that allows that traffic will work immediately.
Which ports does Wi-Fi Calling use? AT&T’s documentation lists UDP 500 and UDP 4500 for IKEv2, plus TCP 143 for IMAP. Other carriers may publish different lists, so confirm yours on your carrier’s support page.
Do I need to forward ports on my router for Wi-Fi Calling? Usually not. The connection starts from your phone and goes outward, so you need outbound traffic allowed rather than inbound forwarding. A reply in a Netgear community thread about an Orbi router made the same point. Firewalls that block outbound UDP are the case that needs attention.
Can ad-blocking DNS break Wi-Fi Calling? Sometimes. Community reports show encrypted and ad-blocking DNS services interfering for some carriers, but the evidence is mixed and at least one case turned out to be an IPv6 problem at the carrier. Run the nslookup test in Fix 4 to find out whether DNS is involved on your network.
Is it safe to change my router’s MTU? Yes, if you note the original value first. AT&T asks for 1500, and you can set the old number back if something else breaks.
The Bottom Line
Wifi calling not working at home is usually a network problem, not a phone problem. Your phone builds an encrypted tunnel to your carrier, and your router, firewall, or DNS filter can stop it. Confirm the cause by testing on another Wi-Fi network first. Then enable IPsec pass-through, keep UDP 500 and 4500 open, set the MTU to 1500, and run a quick nslookup test if you use filtered DNS. Treat DNS blocking as a lead to test, since the evidence for it is mixed. This is the same pattern as Siri’s “Unable to connect to ChatGPT” error, where a network-level filter breaks a feature that looks like a phone problem.