Incoming Call Notification / Dialog not always appearing
I find after having Teams run for some time (e.g. more than a day) that the Incoming Call notification dialog seems to stop showing on the Windows Desktop version.
I can hear the incoming call sound, there's just no way to accept the call -- I have to use my mobile (which is also ringing and has a notification).
If I quit and re-open Teams, then it shows future incoming calls, so it's purely an issue that the "Incoming Call" dialog doesn't show.
Attached is the dialog I normally see, when it's working, and goes missing.
I have figured it out, if teams is in full screen, the thing will not sure, but when it's minimised, it will show.
So strange that Microsoft apparently ignores this bug, despite so many people experiencing it!?
I'm also experiencing it using RDP.
A VERY POOR WORKAROUND:
If you know who is calling (e.g. see it on phone or remote dekstop), go to activity tab and find them there and double click on their name - instead of initiating a new call, it will answer the incoming call.
Same here. I don't get calls very often, but when i do there is no option to accept them anywhere. Very frustrating. I can't even see who is calling me!
***** I reissued the annoying problem...please push!!! *****
we have the same issue, the teams incoming calls pop up dialogue can't be seen, but its behind all the windows.
Same issue. Can hear calling tone, but there's nothing to click to accept and start call. Keep missing calls.
Win 8.1 - no RDP.
Same here on My MacBook Pro!
Having the same issue on a macbook
I use Teams locally, while I work through VPN/Remote Desktop. Teams is closed on my remote PC. I can hear incoming calls or requests to join meetings , but I cannot answer them because there is no notification. I can't even tell who's calling, unless it also rings on my mobile app. It seems this problem is recurring over the last couple of years in various forms. I would like to see Microsoft prioritize this issue and keep checking that it's not broken before releasing updates, or make the function more robust.
Mark Hogan commented
Same issue here. I RDP over Citrix to my Windows 7 desktop in the office where Teams is installed. I also have Teams on my own laptop and login with that to my company's Teams environment. I also have Teams on my mobile. Incoming calls ring on my office desktop which is pointless as there is no audio support setup over my RCP Citrix session. It rings also on my mobile, which I can answer which might work for audio only, but is useless for any sharing. I can hear it ringing on my own laptop, but there is no where to answer the call. On my laptop I have MS Teams version 1.3.00.30866, last updated 12/4/20 but who can be sure that is December 4th or April 12th? Laptop has Windows 10 Version 2004 (OS Build 19041.746)
Unable to answer calls. No incoming dialog box on screen. Sound of call intact. I have to quickly go into History to see who called and hope they'll answer when I call them back. Persistent and serious issue. Macbook Air running latest Big Sur. Please do something.
Similar issue here. Incoming video chat call rings to my desktop app, but I cannot tell which person/group is calling. If I happen to be in the same chat when the person calls me, I can click to join it. But otherwise I typically have to join from my iOS app on the phone, ask which group chat to go to, then find/join it on the desktop app (and hang up on the phone app). SO FRUSTRATING.
I feel like there used to be a separate notification popup window that I'm not seeing anymore?? But even within the desktop app, could the group/chat name flash or have an obvious "incoming call" icon next to it or move to the top of the list, SOMETHING???
***** I reissued the annoying problem...please push!!! *****
Emma Borkent commented
We have the same issues. Calls cannot be anwsered outside the RDP where they need to be awnsered. You can pick up, but cannot talk, only see and hear the other person. When you go outside the RDS, you don't get a notification, so you can't anwser.
Getting same issue. Microsoft Teams Version 1.3.00.33674 (64-bit). It was last updated on 12/10/20. We have Business Voice though staff say they're getting the issue with both within Teams and external calls to the assigned business voice numbers.
Yes, most of the people in my company working remotely have this same problem. It's been a problem for many months after Microsoft updated Windows 10 / Edge / Teams (I believe it could be a combination of these).
Here's my observations :
1. If you are RDPing into your work PC, and have that RDP open and someone calls...
a) You see the call notification dialog on your remote machine.
b) You also see the notification on your phone if you have Teams app installed
c) You DO NOT have a notification dialog on your local machine, where you need to answer the call. You cannot task switch it into view. It is not hidden, it simply does not appear.
2. If you have an RDP session minimized and you have something focused locally and someone calls, you MAY sometimes see the notification dialog
3. Fully quitting and restarting Teams including all of the places, locally, remotely, on your phone, will not fix the issue.
This is an absolutely ridiculous bug and shows the poor standard of both Microsoft Testing and Bug Fixing. Being able to answer a call via a UI is fundamental to any VOIP service. Search online, you'll see this bug has been reported by literally thousands of users and has been an issue for months without resolution.
This should be a a high priority bug fix, there's no excuse for this inexcusable shoddiness.
I absolutely hate Teams. I get the same problem, no way to answer the call. My company is forcing us to change from Skype to Teams and it's the worst decision ever. Skype worked way better than Teams. What are they doing at Microsoft? This is such a huge issue it should be fixed and updated within the day.
Same here...Using RDP
Same .... no way to answer incoming calls. i have to look through activity to find missed call and call them back, and hope they are able to answer on other end. some can some can't either
You have Microsoft Teams Version 1.3.00.33674 (64-bit). It was last updated on 1/5/21.
Same problem here; incoming calls ring but no way to accept the call is presented - which is really annoying.
This used to work correctly until recently.
(I'm using the Teams client on Linux 20.10, and to be fair it works well aside from this issue.)