You tap the phone icon in Messenger, and instead of your friend's voice you get… silence. Or "Call failed" flashing across the screen. Or the endless "connecting" ring that never connects. Here's the thing most guides skip: a Messenger call is really three things running at once — your connection, your permissions, and Messenger's servers. Each one has a different fix.
In This Guide:
- Fix 1: Stabilize Your Internet Connection
- Fix 2: Restore Microphone and Camera Permissions
- Fix 3: Force Stop Messenger and Clear Its Cache
- Fix 4: Update Messenger to the Latest Version
- Fix 5: Fix Incoming Calls That Don't Ring
- Fix 6: Reinstall and Check Messenger's Servers
- Special Case: "Call May Be Unavailable" Messages
- Watch: Messenger Calls Fixed Step by Step
- FAQs
Fix 1: Stabilize Your Internet Connection
Messenger messages can squeeze through a weak connection because they retry quietly in the background. Calls can't — a voice call needs a live, steady two-way stream, and video calls need even more. That's why your chats can work perfectly while every call dies. Run this test before touching anything else:
- Switch networks: if you're on Wi-Fi, turn it off and try a call on mobile data. If you're on mobile data, join Wi-Fi. If calls work on one network, the problem is the network, not the app.
- On Wi-Fi, move closer to the router and restart it (unplug for 30 seconds) if calls only fail at home.
- Toggle Airplane Mode on for 30 seconds, then off — this forces your phone to reconnect with fresh network settings.
- Avoid congested public Wi-Fi (cafes, offices, malls) for calls. These networks often deprioritize voice traffic, and some block VoIP entirely.
- If you're on a work or school network and calls always fail, ask the admin whether VoIP is allowed — blocked voice services fail even on a fast connection.
Voice calls want around 1 Mbps in both directions; if a speed test shows far less, fix the connection first.
Fix 2: Restore Microphone and Camera Permissions
The single most common reason a Messenger call starts but nobody can hear or see you: the app lost permission to your microphone or camera. This happens silently — after an update, a restore from backup, or an accidental tap on a permission prompt. Messenger won't always warn you; the call just goes mute:
- Open Settings → Apps → Messenger → Permissions.
- Make sure Microphone and Camera are both set to Allow only while using the app.
- If they already show as allowed, toggle them off and back on — this re-registers the permission, which fixes cases where the setting shows correctly but the system is blocking access underneath.
- Check the phone-wide kill switches in Quick Settings (Mic access, Camera access), and close any other app using the camera — only one app can hold it at a time.
One more spot people miss: inside a call, check that the mute button isn't lit and the volume is up. It sounds obvious, but a surprising number of "they can't hear me" reports end there.
Fix 3: Force Stop Messenger and Clear Its Cache
Messenger keeps a lot of temporary call data — session states, connection tokens, media buffers. When any of it corrupts, calls can fail in weird, inconsistent ways: some contacts work and others don't, calls drop after exactly a few seconds, or the app refuses to place a call until you restart it. Clearing the cache wipes that stale state without touching your account:
- Go to Settings → Apps → Messenger and tap Force stop to shut the app down completely.
- Tap Storage, then Clear cache. This deletes temporary files only — your chats and contacts stay on your account. Do NOT tap Clear data here.
- Restart your phone, then reopen Messenger and try a test call.
- If calls break again hours later, repeat this every few days or free up storage — a full phone corrupts caches faster.
Covers Android 10 through 14 — and it's the step to try when calls fail intermittently, the classic sign of corrupted session state rather than a hard block.
Fix 4: Update Messenger to the Latest Version
Messenger's calling stack changes constantly, and Meta sometimes requires a minimum app version for calls to connect even when messaging still works. If your Messenger hasn't updated in weeks, your calls may be trying to use a protocol the servers no longer fully support. A stale app is also the most common cause of mass "calls broke overnight" complaints:
- Open the Play Store, search Messenger, and tap Update if it's available.
- No Update button? Check profile icon → Manage apps & device → Updates available for anything pending.
- After updating, restart your phone before testing — this clears out any old app processes still running.
- Also check for a system (Android) update: Settings → System → System update. Call audio and camera routing depend on OS-level media libraries, and very old system software can clash with new Messenger versions.
If recent Play Store reviews mention calls breaking, you're in a known buggy version — the next update is the real fix, and waiting beats wiping the app.
Fix 5: Fix Incoming Calls That Don't Ring
Outgoing calls work but you never hear incoming calls ring? That's a notification problem, not a calling problem — and it's the most complained-about Messenger call issue of all. Your phone is silently killing the incoming-call alert:
- Turn off Do Not Disturb: swipe down to Quick Settings and make sure the DND tile is off. DND silences call notifications outright.
- Check Messenger's notification settings: Settings → Apps → Messenger → Notifications — make sure notifications are on, with sound and lock-screen display enabled.
- Exempt Messenger from battery optimization: Settings → Apps → Messenger → Battery → Unrestricted. Samsung (One UI) and Xiaomi (HyperOS) battery savers kill Messenger's background process, so incoming-call signals arrive late or never — also check Samsung's Settings → Battery → Background usage limits sleeping-apps list.
- Allow background data for Messenger: Settings → Apps → Messenger → Mobile data & Wi-Fi → Background data should be on — the incoming-call ping needs to reach the app while it's in the background.
- Inside Messenger, open your profile picture → Notifications & sounds and confirm call notifications are enabled and message previews aren't hiding call alerts.
Note the difference: if you see the incoming call but can't answer (the screen doesn't respond), that's the app being wedged — use Fix 3. If you never see it at all, it's this fix.
Fix 6: Reinstall and Check Messenger's Servers
When everything above checks out and calls still fail, either the app install itself is broken or the problem isn't on your phone at all:
- Reinstall Messenger as a last step: Settings → Apps → Messenger → Uninstall, restart the phone, reinstall from the Play Store. Your messages live on your account and return after sign-in.
- Before reinstalling, search "Messenger down" in your browser. Call infrastructure degrades regionally — and when it does, messages may keep working while calls fail everywhere, because they run on different backend paths.
- Check with the other person too: Messenger calls need a working connection on both ends. If calls fail only with one contact, the problem is almost certainly on their side — ask them to run the same checks, especially their connection and app update.
- If calls fail on both Wi-Fi and mobile data with multiple contacts, after a reinstall, and Messenger isn't down — try messenger.com in a desktop browser as a control test. Browser calls working points at your phone; failing there too points account-side.
One honest boundary: someone who blocked you or disabled calls looks like a calling failure from your end. Calls to one person always failing instantly while everyone else connects is a contact-level situation, not a phone bug.
Special Case: "Call May Be Unavailable" Messages
These are status messages, not app bugs. "Call may be unavailable" usually means the person is unreachable right now — phone off, no internet, or restricted call permissions on their end. "Hasn't answered your calls" means they haven't picked up. Give it a few hours; if it's a close contact, send a regular message first to confirm they receive it, then ask them to check their connection and permissions. (Chats broken too? See our guide on Messenger messages not sending.)
Confusingly, the same "Call failed" banner can mean a network drop (Fix 1), a permission problem (Fix 2), or a server outage (Fix 6) — which is why the ordered checklist above beats guessing from the error text.
Watch: Messenger Calls Fixed Step by Step
If you'd rather watch than read, this video walks through the "Call may be unavailable" and "Call failed" errors on Messenger with the same checks covered above:
Video by Trevor Nace — full credit to the creator of this Messenger fix tutorial on YouTube.
Related Guides:
FAQs
Why do Messenger messages work but calls don't?
Messages retry quietly over tiny packets; calls need a live, steady stream. If your connection is marginal (Fix 1), permissions are off (Fix 2), or the app is outdated (Fix 4), calls fail while chats keep working.
What does "Call failed" on Messenger actually mean?
"Call failed" is a generic message — it can mean a network drop, a permission problem, a buggy app version, or a server-side hiccup. Work through the fixes in order rather than reading into the message: network test first, then permissions, then cache, then the update.
Will clearing Messenger's cache delete my messages?
No. Clear cache only removes temporary files — session data, media buffers, thumbnails. Your conversations are tied to your account and come back after a reinstall or re-login. Just don't tap Clear data, which would sign you out and wipe local app data.
Why can't the other person hear me on Messenger calls?
Almost always the Microphone permission: Settings → Apps → Messenger → Permissions → Microphone → Allow only while using the app. Also check the phone's Quick Settings Mic access toggle and make sure you're not muted inside the call itself.
By Sameer Zehri | App Fix Guru Editor | Last updated: October 2026
