A call that never rings is worse than a dropped one. You don’t even know you missed it until the voicemail or the chat message lands, and by then the caller has moved on. “Teams calls not ringing” shows up as a few different symptoms — no ring at all, a silent visual toast, calls dropping straight to voicemail, or ringing on the phone but not the desktop — and they trace back to a small set of settings.
Most of the time it’s not a Teams Phone or PSTN problem. It’s your presence sitting on Do Not Disturb, a call forwarding rule you forgot you set, or the ringer pointed at a device that’s switched off. Those are quick to check and quick to fix.
Work through the settings below in order, from your own presence and call rules down to audio devices and Windows, and only escalate to admin policy if the behavior hits more than one person.
Step 1: presence and Do Not Disturb
Your Teams presence directly affects whether calls ring. Do Not Disturb silences call toasts and notifications unless the caller is on your priority access list. Presenting or screen sharing can flip you into DND automatically, and sometimes it sticks after the meeting ends.
Set your status back to Available. If you genuinely want DND but still need certain people to get through, open Settings > Privacy > Manage priority access and add them — calls from those contacts ring even in DND.
While you’re there, confirm you’re actually signed in and online on the device you expect to ring. A desktop that’s signed out won’t ring no matter what.
Step 2: call answering rules and forwarding
This is where calls quietly get sent somewhere other than your ringer. Open Settings > Calls and look at how calls are handled.
Call answering settings to check
| Calls ring me | Should be selected if you want your devices to ring. If 'Forward my calls' is on instead, you won't ring at all. |
|---|---|
| Forward to voicemail | If forwarding is set to voicemail, callers go straight there with no ring. |
| Also ring (simultaneous ring) | Can ring another number/person too — useful, but check it's pointed where you expect. |
| If unanswered | The timeout before a call is treated as missed. Set very short, calls barely ring before going to voicemail. |
The two classic faults here: call forwarding left on from a day you were out, so nothing rings locally; and an if-unanswered timer set so short the call rolls to voicemail almost immediately. Reset forwarding to “Calls ring me” and give the unanswered timer a reasonable window (20 seconds or so).
If you use delegation or call groups, confirm those are set the way you think — a delegate setup can route calls in ways that look like “not ringing” from your seat.
There’s also a quieter setting people overlook: block calls with no caller ID. If that’s enabled and an inbound call arrives without caller information, Teams can suppress it silently. That’s fine if you want it, but if you’re missing some calls and not others, this is worth checking — it can look exactly like an intermittent ringing fault.
Step 3: audio device and the secondary ringer
A call can ring visually while you hear nothing, because the ringtone is routed to a device that’s off, unplugged, or turned down. Teams separates your main call audio from the ringer, which trips people up.
Open Settings > Devices and check:
- The audio device Teams is using for calls.
- The secondary ringer — a separate setting that can play the ring on, say, your laptop speakers even when your headset is your main device. If your ringtone is routed only to a headset that’s switched off, you’ll never hear it.
Set the secondary ringer to your laptop or desktop speakers so an incoming call rings out loud regardless of whether your headset is on your head.
Ringing checklist
- Presence is Available, not Do Not Disturb
- Call handling is set to 'Calls ring me', not forwarded
- The 'if unanswered' timer isn't set too short
- The correct audio device and a working secondary ringer are selected
- You're signed in and online on the device that should ring
Step 4: Windows notifications and Focus
Even with Teams configured perfectly, Windows can suppress the call notification. The same OS-level gates that block chat banners also affect calls.
Check Settings > System > Notifications and confirm Teams is allowed, then make sure Do not disturb / Focus assist isn’t running (it can be set to Priority only, or triggered automatically while you present or use a second display). The detailed walkthrough for the notification side is in fix Teams notifications not working — the same fixes that restore message banners also restore the incoming-call toast.
Step 5: restart, update, and clear the cache
If the settings are all correct and calls still don’t ring, treat it like any other client glitch. Quit Teams fully and relaunch. Force an update from the … menu > Check for updates, since call and notification bugs are frequently fixed in newer builds. If it persists, clear the Teams cache — corrupted local state can break call notifications specifically — using the steps in clear the Microsoft Teams cache on Windows.
A quick cross-check: have someone call you while you’re signed in to Teams on the web or the mobile app as well. If those ring but the desktop doesn’t, the problem is isolated to the desktop client — cache, Windows settings, or the install.
When it’s a policy, not a person
If ringing behavior changed for several people at once, stop debugging individual clients and look at the Teams admin center. Calling policies (Voice > Calling policies) control features like call forwarding, simultaneous ring, delegation, and where calls are allowed to route. A tightened calling policy can change call delivery for a user or a whole group.
For organizations using Teams Phone, also confirm the user’s phone setup is intact — licensing, number assignment, and voice routing all have to be in place for PSTN calls to land. The related setup is covered in assign phone numbers to Teams users and, for routing inbound calls through menus and queues, set up call queues in Microsoft Teams. If inbound PSTN calls specifically aren’t ringing while internal Teams calls do, the issue is more likely in the voice routing or number assignment than in the client.
Internal calls vs PSTN calls: a useful split
When you’re narrowing down a ringing problem, separate the two kinds of call. An internal Teams-to-Teams call never touches the phone network — it’s pure Teams, so if those don’t ring, the cause is almost always on the client or in your own settings (presence, forwarding, devices, Windows notifications). A PSTN call from an outside phone number depends on Teams Phone being fully provisioned, so if internal calls ring fine but external ones don’t, shift your attention to the voice side.
Where to look based on what doesn't ring
| Internal Teams calls don't ring | Client and user settings: presence/DND, forwarding, devices, Windows notifications, cache |
|---|---|
| PSTN (external) calls don't ring | Teams Phone: licensing, number assignment, voice routing, calling policy |
| Nothing rings on desktop, mobile rings | Desktop is signed out, on DND, or notifications suppressed by Windows/Focus |
| Rings but no sound | Audio device / secondary ringer pointed at the wrong or muted device |
This split saves a lot of wasted effort. People often dig through PSTN voice routing when the real problem was Do Not Disturb, or tweak client settings endlessly when the number was never assigned correctly. Confirm which category your problem falls into before going deep.
Wrapping up
Teams calls not ringing comes down to a short checklist: presence off Do Not Disturb, call handling set to ring you (not forward), the unanswered timer reasonable, the ringer routed to a device you can actually hear, and Windows notifications allowed. That covers the large majority of cases, and all of it you can fix from your own settings in a couple of minutes.
If it survives the settings, restart, update, and clear the cache. And when several people lose ringing at once, the cause is almost always a calling policy or voice configuration change in the admin center, not the desktop app.
