Calls that fail on WhatsApp while normal phone calls work fine are not a network outage. They mean WhatsApp itself is blocked, starved of background permission, or fighting a battery saver that kills its connection the moment the screen sleeps. This guide shows how to fix WhatsApp calls not working by separating a WhatsApp permission problem from a genuine connection problem, because the two demand opposite fixes and only one of them is in your hands.
The cleanest test is a message. If text messages arrive instantly but calls fail, the connection is fine and the calling path is the problem. If messages also stall, the network or the background restriction is the problem. That one comparison, made in under a minute, points the whole troubleshooting effort in the right direction.
Reading the Symptom Before You Change Anything
Before the steps, it helps to know that this fault rarely has a single cause, and the table below separates the likely causes by the sign you actually see, so you can start at the row that matches your situation rather than at the top of a generic list. Working out how to fix WhatsApp calls not working starts with that match, because the right first step depends on the symptom in front of you.
| Likely cause | Sign you will see | First check |
|---|---|---|
| No internet or weak signal | Calls fail to connect at all | Test browsing and move to stronger signal |
| Microphone or camera permission off | Other side cannot hear or see you | Check app permissions |
| Battery saver blocking calls | Calls drop when screen locks | Exempt WhatsApp from battery optimisation |
| Other device or contact fault | Calls fail to one contact only | Test with another contact |
| Outdated app | Calls fail after an app update | Update WhatsApp |
| Account or server fault | Calls fail to every contact | Check with another device |
Note what changed before the fault began, what still works, and what you have already tried, because those three facts turn a frustrating afternoon into a short sequence of tests. A short note on those points, written before you start, also makes any later conversation with support far shorter, since you can describe what you have ruled out instead of repeating the symptom.
Before You Place Another Call
Read the whole guide once before changing anything, because the order matters, and a step skipped early often returns as a larger problem later. Where a price or a feature is given, check it on the vendor page before you commit, since pricing and features change, and the right choice depends on your situation and your existing setup.
When you approach fix WhatsApp calls not working, keep a simple log of each test and its result, even a few lines on paper. Change one thing, test, and note the result before moving on, because changing three things at once and seeing an improvement leaves you unsure which change helped, and the fault returns when the unhelpful changes are undone.
Back up anything important before the later steps, even if you do not expect to reach them. A backup made while the device still works is worth far more than a backup attempted after a destructive step, and it removes the fear that keeps people from taking a legitimate last resort step. Check that the backup completed, rather than assuming it did, since a backup that never finished offers no protection at all.
How to fix WhatsApp calls not working in the Right Order
Working through fix WhatsApp calls not working in this order keeps the least disruptive tests first, so a simple settings fault is found before anyone considers a reinstall, a replacement, or a repair booking, and each step below ends with what a success looks like, so you know when to stop.
- **Confirm internet works on the phone.** Open a web page or a video with Wi-Fi off and on, testing mobile data and Wi-Fi separately. WhatsApp calls need a stable connection, and a phone that browses slowly may still fail calls, since calls need steady low delay traffic. Fix the connection first, since no call setting can compensate for no internet. If this step restores normal behaviour, stop here and note what worked, because continuing past a working fix only adds risk.
- **Test with another contact.** Try a voice call and a video call with a second contact. Calls that fail to one contact only point at that contact device, network, or block state, while calls that fail to every contact point at your phone or connection. Test both voice and video, since they use different permissions and bandwidth. If this step restores normal behaviour, stop here and note what worked, because continuing past a working fix only adds risk.
- **Restart the phone.** Power the phone fully off, wait about thirty seconds, and power it on again. A restart clears a stuck call service and refreshes the network connection in one move. Test a call immediately after restart, before opening other apps, so a background app cannot seize bandwidth first. If this step restores normal behaviour, stop here and note what worked, because continuing past a working fix only adds risk.
- **Check microphone and camera permissions.** On Android, open Settings, Apps, WhatsApp, Permissions, and confirm Microphone and Camera are allowed. On iPhone, open Settings, WhatsApp, and confirm the same toggles. A denied microphone permission leaves the other side hearing nothing, while a denied camera permission leaves video black, even when the call connects. If this step restores normal behaviour, stop here and note what worked, because continuing past a working fix only adds risk.
- **Check Do Not Disturb and notification settings.** Review Do Not Disturb, call notification settings, and any silence unknown callers option that may block incoming calls. A call that never rings may be a notification fault rather than a call fault, especially when outgoing calls work. Test an incoming call from a second phone after changing these settings. If this step restores normal behaviour, stop here and note what worked, because continuing past a working fix only adds risk.
- **Turn off VPN and check data saver settings.** Turn off any VPN for the test, and check data saver or Low Data Mode settings that may restrict background data for WhatsApp. A VPN can add delay or block call traffic, while a data saver can pause WhatsApp when the screen locks. If calls work with the VPN off, the VPN configuration is the fault. At this stage of fix WhatsApp calls not working, a success here is especially valuable, because it proves the fault sat in the middle of the sequence rather than at either end. If this step restores normal behaviour, stop here and note what worked, because continuing past a working fix only adds risk.
- **Exempt WhatsApp from battery optimisation.** On Android, open Settings, Apps, WhatsApp, Battery, and set it to Unrestricted or exempt it from optimisation, following your phone maker wording. Battery optimisation can kill WhatsApp in the background, which drops calls when the screen locks or after a period of idle time. Test a longer call after changing this setting. If this step restores normal behaviour, stop here and note what worked, because continuing past a working fix only adds risk.
- **Update WhatsApp.** Update WhatsApp through the Play Store or App Store, and restart the phone after updating. Call faults that appear after an app update are often fixed in a following release, and an outdated app can lose compatibility with newer call servers. Test both voice and video after the update, since they exercise different code paths. If this step restores normal behaviour, stop here and note what worked, because continuing past a working fix only adds risk.
- **Clear cache on Android.** On Android, open Settings, Apps, WhatsApp, Storage, and choose Clear cache, which removes temporary files without deleting chats. A corrupted cache can break call setup while messages still work. Do not choose Clear data at this stage, since that signs you out and removes local settings unnecessarily. If this step restores normal behaviour, stop here and note what worked, because continuing past a working fix only adds risk.
- **Check storage and system updates.** Free storage if the phone is nearly full, and install any available system update. A full storage can stall call setup, and a system update can fix audio routing faults that affect calls. Test a call after each change, so you know which change actually helped. If this step restores normal behaviour, stop here and note what worked, because continuing past a working fix only adds risk.
- **Reinstall WhatsApp as a later step.** Back up chats to the cloud account first, then uninstall and reinstall WhatsApp, restore the backup, and test a call. A reinstall clears corrupted app files and forces fresh permission requests. Verify the backup completed before uninstalling, since chats without a backup cannot be restored. If this step restores normal behaviour, stop here and note what worked, because continuing past a working fix only adds risk.
- **Test with another device or network.** Sign in on a second device if possible, or test calls on a different network, such as switching from Wi-Fi to mobile data. Calls that work on another network point at the original network or router, while calls that fail everywhere point at the account or the app. Note the result, since it decides whether to pursue network help or app help. If this step restores normal behaviour, stop here and note what worked, because continuing past a working fix only adds risk.
The Checks Most Guides Skip
WhatsApp call faults divide into connection faults, permission faults, and background killing, and each division needs a different repair. A call that never connects points at network, a call that connects without audio or video points at permission, and a call that drops when the screen locks points at battery optimisation. Naming the division before changing settings keeps the repair short. This distinction shapes how you should approach fix WhatsApp calls not working.
Battery optimisation is the most overlooked cause, because it acts after a call starts rather than before it. A call that works for a minute and then drops, or a call that never rings when the phone is idle, often traces to the system killing WhatsApp in the background. Exempting WhatsApp from optimisation is a targeted fix, not a general battery sacrifice, and it belongs before any reinstall.
Voice and video calls are not the same test, even though they share the WhatsApp name. Voice calls need microphone permission and steady audio traffic, while video calls add camera permission and far more bandwidth. A fault that affects only video points at camera or bandwidth, while a fault that affects both points at network or the app itself. Testing both gives the diagnosis for free.
The checks that matter most, in brief, are the first five steps of the sequence, and they deserve a second pass if the fault survives them.
- Confirm internet works on the phone
- Test with another contact
- Restart the phone
- Check microphone and camera permissions
- Check Do Not Disturb and notification settings
WhatsApp publishes calling and permission guidance through its official help pages, and the permission paths in this guide follow those pages. See the official WhatsApp help centre for the current calling steps for your phone.
Testing one change at a time is the habit that separates a quick repair from a long afternoon of guessing. Change a single setting, run the same test you ran at the start, and write down the result before you touch anything else. When a later step appears to work, that note tells you whether the improvement came from the latest change or from an earlier one that only needed time to take effect. Support teams ask for the same log, so the habit pays twice.
A short note made before you start will save time later, especially if the fault returns or if someone else has to finish the job. Record what changed just before the fault appeared, which tests you have already run, and what each test showed. A fault that began after an update, a new accessory, or a move points in a different direction from a fault that appeared out of nowhere, and that single detail often narrows the search more than any single setting.
Do not judge a fix by the first few seconds after you apply it. Some settings need a restart, some connections need a fresh pairing attempt, and some apps need a full close before a change takes effect. Run the same real world test you used at the start, such as opening the feature, making a test call, or playing a short clip, and give the result a full minute before you declare the step a failure and move on.
If the same fault has appeared before, look for the pattern rather than treating each occurrence as new. A fault that returns after every update, every long trip, or every period of heavy use usually has a trigger that the ordered steps can expose. Fixing the trigger, such as a worn cable, a full storage, or an app that hogs resources, prevents the next occurrence far better than repeating the same quick fix.
Keep the accessories you use for testing in a known good state. A spare cable, a charged spare remote battery, or a second pair of earbuds turns a vague suspicion into a clear answer in under a minute. When the fault follows the accessory to another device, the accessory is the problem. When the fault stays with the original device, the device or its settings deserve the attention.
Before any step that erases data or resets settings, confirm where your important content lives. Photos, messages, and documents that sync to a cloud account usually return after a reinstall, while local downloads and unsaved work may not. A quick backup takes a few minutes and turns a last resort step from a risk into a routine procedure.
When a fault may end in a warranty claim, preserve evidence as you go rather than reconstructing it later. Keep dated notes, keep the original accessory that failed, and avoid opening a sealed device, since an opened device can complicate a claim even when the fault is genuine. A repair centre that receives a clear timeline and untouched hardware can usually decide faster than one that receives only a description.
After any system or app update, retest the feature that previously failed, even if the update notes do not mention it. Updates change drivers, permissions, and background behaviour in ways that release notes rarely capture fully, and a fault that an update quietly fixed can return with the next update just as quietly. A two minute retest after each update turns that uncertainty into a known result.
A second device is the cheapest diagnostic tool you can own for this kind of fault, because it answers the device versus environment question in a single test. Borrow a second phone, headset, remote, or monitor for ten minutes, and run the same test on both. When the fault follows the accessory, replace the accessory. When it stays with the original device, focus the repair there and stop buying accessories.
Monitor the fix for a full week of normal use before declaring it permanent, since some faults return only under specific conditions such as heat, low battery, weak signal, or heavy load. Keep the log going through that week, noting any recurrence and its conditions, because a recurrence pattern is itself diagnostic evidence. A fix that survives a normal week has earned your confidence, while a fix that fails in that week still has a fresh trail to follow.
Ways People Accidentally Prolong This Fault
The following errors do not cause the original fault, but they regularly turn a short repair into a long one, and they are worth naming before you start.
- Reinstalling WhatsApp before checking permissions and battery settings, which risks chats for a settings fault.
- Choosing Clear data instead of Clear cache on Android, which signs you out unnecessarily.
- Testing only with one contact, which leaves a contact side fault disguised as your fault.
- Leaving a VPN running during every test, which hides whether the network or the VPN blocks calls.
- Ignoring battery optimisation, which drops calls that start perfectly and then fail.
Avoiding those errors keeps fix WhatsApp calls not working short and calm, because every wasted reset or repeated test adds frustration without adding evidence, and a calm repair is a faster repair.
Signs That Point to a Repair
Contact WhatsApp support when calls fail to every contact on every network after a reinstall and a permission check, or when the account shows other faults alongside call failure. Check with your network provider when calls fail on one network but work on another. Take notes on voice versus video results, and on which contacts and networks you tested.
Take your notes with you when you seek help, including which tests passed and which failed, and the exact conditions where the fault appears. Support moves faster with ruled out causes than with a repeated symptom description, and a clear log often leads to a faster repair or a correct replacement part on the first visit.
Keeping This Fault From Coming Back
Keep WhatsApp updated, review microphone and camera permissions after any system update, and keep WhatsApp exempt from aggressive battery optimisation. Test a call after switching networks or travelling, since a new network can introduce call faults that a quick test would expose. A short monthly check of permissions, battery settings, and app version prevents most call faults.
A ten minute monthly check of updates, storage, cables, and permissions catches most problems while they are still small, and it builds a baseline so a future change stands out immediately. Prevention is not extra work on top of the repair, it is the same discipline applied before the fault appears, and it pays for itself the first time it saves a repeat repair.
More Reading on Stratilyze
More Reading on Stratilyze. If this guide helped, the related guides on this site cover the neighbouring faults that often appear alongside this one, including Fix Whatsapp Not Sending Photos, Fix Whatsapp Backup Not Restoring and Fix Whatsapp Not Downloading Media. Reading the closest match first usually saves a second round of troubleshooting, because a fault in one feature often shares a cause with a fault in another. Keep this guide open while you check the related one, and compare the symptom tables before changing any setting, since the right fix depends on matching your exact symptom rather than the closest headline.
A Second Attempt With Better Notes
A second pass is not a repeat of the first pass, it is a different kind of test. The first pass rules out the common causes in order, while the second pass looks for a cause that was masked during the first, such as a second device interfering, a setting that reverted after a restart, or a fault that only appears under load. Work the second pass slowly, and change only one variable at a time, since a second pass done hastily produces the same confusion as the first pass done at random.
During the second pass, test under the exact conditions where the fault originally appeared, with the same app, the same accessory, and the same network or location. A fault that cannot be reproduced under test conditions has not necessarily been fixed, it may simply be waiting for its trigger. If the second pass still fails, the notes from both passes together give support a far stronger starting point than either pass alone, and they often reveal a pattern that a single pass hides.
Testing in Real Conditions Before You Finish
Return to the first step and confirm it properly before moving on, because a step that was rushed the first time often looks like a failure when it was really an incomplete test. Give it the full time it needs, watch for the result described in the main sequence, and only then move to the next step. This habit of retesting the early steps, rather than jumping to the later and more disruptive ones, saves most of the time that troubleshooting usually wastes.
The diagnosis table at the start deserves a second look once the main steps are done, because a cause that seemed unlikely at the start can become the leading explanation once the obvious ones are ruled out. Compare what you observed with the sign described for each row, and if your observation matches a row you dismissed earlier, work that row again with fresh attention. Diagnosis improves when the table is treated as a checklist to revisit, not as an introduction to skip.
Test again the next day under normal use, not just in the moment after the fix. Some faults return when the device warms up, when a background app updates, or when the original trigger recurs, and a next day test catches those returns while the repair is still fresh in your mind. If the fault returns, note exactly what changed since the fix, since that change is the most likely trigger.
Frequently Asked Questions
Why did this problem start suddenly?
The commonest trigger is a change just before the fault, such as an update, a new accessory, a move, or a period without use. Tracing that change usually points at the cause faster than testing parts at random. Note the last change first, then work through the ordered steps, because a fault with a clear trigger often has a short fix and a fault without one needs the full sequence. Retest the exact action that failed before, not an easier one.
How long should each fix take before I move on?
Give each simple step a proper test rather than a glance, because a restart, a cable swap, or a permission change needs a minute or two to show its result, while a reinstall or a restore needs longer. If a step shows no change after a fair test, move on and note the result, because the log of failed steps is what narrows the remaining causes for the steps that follow. Retest the exact action that failed before, not an easier one.
Will clearing data or resetting settings delete my content?
Clearing a cache removes temporary files only, while clearing data or storage signs you out and removes local settings, so check where your content lives before the stronger step. Content that syncs to a cloud account usually returns after a reinstall, while local downloads and unsaved work need a backup first. Never take a destructive step on a device that holds the only copy of something important. Retest the exact action that failed before, not an easier one.
What if the fault affects only one app, one device, or one connection?
That pattern is useful evidence, because a fault tied to one app points at that app and its permissions, while a fault that follows the device points at the device itself. The ordered guide for fix WhatsApp calls not working helps separate those two cases before you change settings everywhere, and testing with a second app, a second device, or a second connection is the fastest way to draw that line. Retest the exact action that failed before, not an easier one.
When should I contact support instead of trying more fixes?
Contact support after the ordered steps fail, or immediately if you see danger signs such as heat, swelling, liquid damage, or a burning smell, and take your notes on what you tried. Support moves faster when you can list the causes you have ruled out, and continuing to guess after that point risks making a repairable fault worse or turning a warranty claim into a dispute. Retest the exact action that failed before, not an easier one.
How do I stop this happening again?
Keep updates current, keep comfortable free storage, check cables and permissions monthly, and note any change before a fault appears, because most repeats come from the same neglected basics. A ten minute monthly check is cheaper than another afternoon of troubleshooting, and it builds a baseline that makes future changes obvious before they become faults. Retest the exact action that failed before, not an easier one.
Closing the Case Properly
Work through fix WhatsApp calls not working in order, stop at the step that works, and keep the notes on what you tried, because that discipline turns a frustrating fault into a short sequence of tests, and it also means the next fault starts from a known baseline instead of from scratch.
Start with the first step today, test one change at a time, and let the result of each test decide the next move, because a calm ordered approach beats a fast random one, and the time saved by not repeating failed steps is time you get back for the work itself.
