VoIP and Wi-Fi calling on Starlink: what to try, in order

Bandwidth a voice call needs

Small (Teams audio: 58 kbps)

First call for Wi-Fi calling

Your mobile carrier

Starlink router settings for VoIP

None to change

Most common VoIP fix

SIP ALG off (own router)

Wi-Fi calling not working: fixes in order

Wi-Fi calling sends your phone’s calls through an encrypted tunnel to your carrier over the internet. Starlink can carry that tunnel, but the carrier decides whether to accept it. Starlink’s own troubleshooting says the cause may be device settings, network glitches or carrier restrictions, and that Wi-Fi Calling is sensitive to IP geolocation (checked Oct 5, 2026).

1. Call your carrier first. Starlink’s advice is to contact the carrier before Starlink: share your IP address and its location, the symptoms and any error message, and mention Starlink in case they need to allow it. Ask them to confirm Wi-Fi Calling is turned on for your line and that a valid emergency address is on file. Without that address, many phones won’t offer Wi-Fi calling at all.
2. Check where your IP address appears to be. On the phone, connected to your Wi-Fi, search “what is my IP location”. If it shows a different city or state, that’s the geolocation problem Starlink describes. Give the carrier that result; it’s their system that decides.
3. Reset the phone side. Turn Wi-Fi Calling off and on, install system and carrier-settings updates, and restart. On Android, set calling preference to “Wi-Fi preferred” if your phone offers it.
4. Turn off VPN and privacy-relay apps on the phone. They change your apparent location and wrap the carrier’s tunnel inside another one.
5. Try a different Wi-Fi band or move closer to the router. Weak Wi-Fi at the far end of the house drops calls even when the line is fine.
6. If it still fails, test the line and open a Starlink ticket. Starlink’s steps: run a short ping test (about half a minute), and note any latency over 200 ms or any loss. Send Starlink your IP and those ping results.

VoIP phones and adapters: fixes in order

A VoIP service (a desk phone, an analog phone adapter, or an app from a phone provider) registers outward to the provider and keeps that connection open. That works behind Starlink’s CGNAT, which blocks inbound connections (checked Oct 5, 2026) but lets the phone’s own outbound connection carry calls in both directions.

1. Plug the adapter or desk phone into the router with Ethernet. Not into a Wi-Fi extender, and not into a powerline adapter if you can avoid it.
2. On your own router, turn SIP ALG off. It rewrites call setup messages and is a classic cause of one-way audio and dropped calls. The Starlink router has no such settings: it has no port forwarding or firewall rules at all (checked Oct 5, 2026). If you use your own router, Starlink’s bypass mode turns off the Starlink router’s Wi-Fi so yours does the routing.
3. Fix calls that never ring. If outgoing calls work but incoming calls don’t arrive, the opening in the NAT is timing out between registrations. Ask the provider to shorten the registration or keepalive interval, or to switch to a TCP or TLS connection. Don’t try to port forward: on CGNAT it can’t work.
4. Give calls priority on your own router. Turn on QoS or smart queue management and set an upload limit a little below what your line delivers. That stops a backup or photo upload from crowding out voice packets. How upload limits work.
5. Count your connections. CGNAT plans are limited to 1,200 sessions open connections at once, and Starlink says hitting it can drop VoIP calls or stop them connecting (checked Oct 5, 2026). A small office with many phones, computers and cameras can get there.

Choppy audio, gaps and one-way sound

Voice uses very little bandwidth: Microsoft recommends 58 kbps for Teams audio and Google lists about 100 kbps each way for Meet audio (vendor figures, checked Oct 5, 2026). So a choppy call is almost never “not enough speed”. It’s delay, jitter or lost packets.

The ITU’s planning guide says keeping one-way delay under 150 ms makes a conversation feel natural (checked Oct 5, 2026). Starlink’s normal delay is well inside that: it reports 25.7 ms median peak-hour latency in the US, and that’s a round trip. The trouble is short gaps: an obstruction, a busy upload, or weak Wi-Fi drops a few packets and you hear a word cut out. Call quality is often scored as a MOS, an average of listener ratings where Bad is the lowest and Excellent scores 5 (ITU, checked Oct 5, 2026).

• Words cut out now and then, at random: short outages. Check the Starlink app’s Statistics page for outages at those times, and use the app’s obstruction check.
• Audio breaks up when someone uploads or streams: upload saturation. Set an upload limit (step 4 above).
• You hear them, they don’t hear you (or the reverse): SIP ALG or a NAT timeout. Steps 2 and 3.
• Only on Wi-Fi, never on Ethernet: your Wi-Fi, not the satellite.