Phones
Cricket Wi‑Fi Calling Not Working
Troubleshoot Cricket Wireless Wi-Fi Calling failure on iOS and Android with step-by-step network resets, E911 address verification, and SIM settings adjustments.
Symptoms
- Calls drop immediately when transitioning from Wi-Fi to cellular data
- Error message stating 'Network Error' or 'Wi-Fi Calling Unable to be Activated'
- The Wi-Fi Calling toggle switch is grayed out or automatically turns off
- Incoming calls go directly to voicemail while connected to Wi-Fi
- Emergency 911 (E911) address prompt appears repeatedly and fails to save
- Status bar indicator for 'Cricket Wi-Fi' is missing despite a strong connection
Quick troubleshooting
Step 1
Update and Verify E911 Emergency Address
Open the myCricket app or log into your Cricket Wireless account in a web browser. Navigate to Account Settings and locate the Wi-Fi Calling management section to confirm your E911 emergency address is saved. Cricket automatically disables Wi-Fi Calling feature activation if a valid emergency address is missing.
Step 2
Reset Phone Network Settings
On iPhone, go to Settings > General > Transfer or Reset iPhone > Reset > Reset Network Settings. On Android, navigate to Settings > System > Reset options > Reset Wi-Fi, mobile & Bluetooth. This clears stored network profiles, clears corrupt IMS settings, and forces the phone to re-register with Cricket's towers.
Step 3
Isolate the Wi-Fi Network and Router Ports
Test Wi-Fi Calling on a different Wi-Fi network, such as a friend's router or a work network. If it functions properly elsewhere, log into your home router's admin panel and ensure UDP ports 500 and 4500 are open and SIP ALG (Application Layer Gateway) is toggled off.
Step 4
Re-seat Physical SIM or Re-provision eSIM
Power off your phone and use a SIM ejector tool to inspect your physical SIM card for scratches, oxidation, or dirt. Wipe the gold contacts with an isopropyl alcohol wipe before reinserting. If you use an eSIM, request a new eSIM activation profile through the Cricket app.
Step 5
Check Carrier Settings and OS Updates
Connect your phone to internet-connected Wi-Fi and check for available operating system updates. On iOS devices, navigate to Settings > About to trigger a pop-up prompt if an updated Cricket carrier bundle is pending.
Likely causes
- Unregistered or invalid Emergency 911 (E911) address on the Cricket account
- Corrupted network cache or misconfigured carrier settings bundle
- Router firewall blocking IPsec tunneling (UDP ports 500 and 4500)
- Outdated phone operating system or carrier configuration
- Damaged SIM card or outdated eSIM provisioning profile
- Cricket Wireless account-level feature provision mismatch
- Hardware failure in the phone's wireless baseband modem or Wi-Fi IC
What's going on
Wi-Fi Calling relies on secure IPsec encryption tunnels to route your voice calls and SMS text messages over standard internet routers directly to Cricket Wireless servers. When this feature fails, it usually stems from a breakdown in four main areas: account-level provisioning, address registration, local network security settings, or phone system software.
Because Cricket operates as a Mobile Virtual Network Operator (MVNO) on AT&T's network, feature flags like Wi-Fi Calling require strict alignment between your device's carrier settings, SIM profile, and Cricket's billing server. If any link in that chain drops out, you may run into common problems like grayed-out toggles, silent call drops, or unexpected error pop-ups.
Symptoms people notice
- The carrier label in the status bar says "Cricket" instead of "Cricket Wi-Fi" or "Wi-Fi Calling."
- Calls immediately fail or disconnect the moment your phone steps out of cellular tower range.
- The Wi-Fi Calling switch in your phone's settings menu automatically toggles back to Off after several seconds.
- An error code appears when toggling the setting, such as "Unable to complete setup" or "Contact your carrier."
- Inbound callers are sent straight to voicemail without your phone ringing.
- Poor audio quality or severe lag on voice calls while connected to high-speed home internet.
Likely causes
- Missing or Mismatched E911 Address: Federal regulations require carriers to maintain a verified physical address for emergency routing before enabling Wi-Fi Calling.
- Network Cache Corruption: Corrupted cellular data caches or outdated network preference files prevent proper IPsec tunnel establishment.
- Router Security Restrictions: Firewalls or security suites blocking IPsec traffic (UDP ports 500 and 4500) or aggressive SIP ALG settings on your home router.
- Incompatible Carrier Settings: Pending device updates or outdated carrier bundle files on BYOD (Bring Your Own Device) phones.
- SIM Provisioning Error: An aging physical SIM card that lacks updated IMS/VoLTE keys, or an improperly bound eSIM profile.
- Account Provisioning Mismatch: Cricket account switches or plan changes that accidentally stripped the Wi-Fi Calling feature flag.
Quick checks first
Before taking your phone apart or performing full resets, perform these rapid preliminary checks:
- Toggle Airplane Mode: Turn Airplane Mode ON, wait 10 seconds, connect to Wi-Fi, and see if "Cricket Wi-Fi" populates in the status bar.
- Verify Wi-Fi Quality: Ensure your Wi-Fi signal is strong and internet speed is stable. Wi-Fi Calling automatically disengages if latency is too high.
- Verify E911 Registration: Log into the myCricket app to verify that a full street address (including unit/apt numbers) is saved in your profile.
- Check Device Compatibility: Ensure your specific phone model is officially supported for Wi-Fi Calling on Cricket's BYOD compatibility checklist.
When it's a real repair
If you have completed all software-level troubleshooting, verified your E911 address, tested on multiple Wi-Fi networks, and even swapped SIM cards with Cricket support without success, you may be dealing with a hardware issue.
Common hardware factors that disrupt Wi-Fi Calling include:
- Corroded or Damaged SIM Card Reader: Pins inside the SIM tray that fail to establish stable contacts with the SIM IC.
- Failing Baseband Modem or Wi-Fi Transceiver: Physical damage or solder degradation under the baseband IC or Wi-Fi/Bluetooth chip on the motherboard after a drop.
- Damaged Internal Antennas: Flex cables or coaxial antenna lines that have disconnected after a screen replacement or severe drop.
To explore component replacement procedures and disassembly steps, check out our free guides.
DIY vs professional repair
Software configurations, E911 registration, network resets, and SIM swaps are 100% DIY-friendly and should always be completed first. You do not need specialized tools or technical experience to solve standard service registration failures.
However, if physical symptoms exist—such as your phone overheating near the modem area, failing to connect to Wi-Fi altogether, or losing Bluetooth functionality alongside Wi-Fi Calling—board-level repair or component replacements will be required. Internal antenna replacements are suitable for confident DIYers with standard precision screwdrivers and prying tools. Motherboard baseband repairs require micro-soldering equipment and should be referred to experienced repair technicians or submitted through an official mail-in repair program via LML Experts.
Next steps
If basic troubleshooting hasn't resolved your Cricket Wi-Fi Calling issues, follow this recommended sequence:
- Check your account in the myCricket app and update your emergency location details.
- Execute a full Network Settings Reset on your mobile device.
- Test the feature on an isolated, open Wi-Fi network or guest network to rule out router firewall blocking.
- Contact Cricket Wireless support to re-provision your account's IMS/VoLTE line feature flags, or request a replacement SIM/eSIM.
- Browse our repair community to post your phone model details and get advice from experienced repair builders if hardware damage is suspected.
Next steps
Try the DIY guide if you're comfortable opening the device. Still stuck? Browse related problems for similar symptoms.

