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.
version 1.4.00.8872 is giving me this issue
I can confirm 1.4.00.8755 fixed it.
A new build was spotted in the wild, 1.4.00.10658, which was released on 4/16/2021, and can be downloaded from https://statics.teams.cdn.office.net/production-windows-x64/1.4.00.10658/Teams_windows_x64.exe
I actually managed to grab this particular build from https://raw.githubusercontent.com/ItzLevvie/MicrosoftTeams-msinternal/master/defconfig, and the builds list is seemingly updated every day or so.
It appears to be fixed in this version (until they break it again on the next version!)
For me it is fixed with the latest x64 Windows Client Version...have a look in the last comment from user fudgi in my bug report:
There you'll find the link to the long-awaited Version :-D
Having the same issue on Linux client. Very annoying to wait for the call attempt to end and finally see who was calling you in "activity" afterwards.
**** I reissued the annoying problem...please push!!! *****
Having the same problem when I'm using a laptop + monitor "Extend These Displays" setup. I can hear the incoming call ringing, but the notification for me to pick up is nowhere to be seen.
I have to wait until the call ends then call back.
Being able to accept calls is a critical part of this software, we really need a fix for this.
Todd A commented
With the last couple of Android and iOS updates, we are getting very intermittent incoming call notification dialog boxes. I could make 40 calls and never see this happen. However, we're getting many calls on this and I've been able to see it with my own eyes. We have opened a ticket up with Microsoft. i will update this thread if anything promising comes of it.
Thomas Jeavons commented
MacBook Pro, have had the issue of no call notifications whatsoever. It only tells me when I have missed a call. The call used to ring on both my laptop and my phone, now I'm none the wiser.
I have the same issue and I tried several things. I use my laptop and have an external monitor connected. In Display Settings if I use "duplicate the displays" it works and the answer call dialog appears and I can pick up. If I use "Extend these displays" it stops working. Teams is such an advanced program but the simple things don't work.
We need a fix. User using remote desktop to access office computer can not pick-up a Teams call locally. The Teams call just rings and they must wait until the ringing stops to see who called.
**** I reissued the annoying problem...please push!!! *****
@Phil Grenfell, I have PROBLEM #2 but neither of workarounds 2 or 3 work for me. I simply do not see a notification. Also, it's broken and has been for months, not just from December.
Phil Grenfell commented
TEAMS answering calls used to work fine from March to December. However during the last month we have had two notifications problem:
PROBLEM #1: All notifications stop (TEAMS, Outlook, etc.) and you must reboot the PC to fix the notifications.
PROBLEM #2: When working on a remote computer using the combination of a VPN client and "Remote Desktop Connection", when an inbound TEAMS call is ringing we need to minimize the "Remote Desktop Connection" but we don't see a notification pop-up on top (on the local computer) so the user must frantically minimize all their windows to find the notification pop-up
WORKAROUNDS FOR PROBLEM #2
After minimization of "Remote Desktop Connection" (to get back to the local computer) the following workarounds can be used to quickly answer the incoming TEAMS call on the local computer:
1. Press [Control+Shift+S] to answer TEAMS call using keyboard shortcut
2. Press [Windows+M] to minimize all windows then click answer icon in pop-up window
3. Right-click task bar and choose "Show Desktop" then click answer icon in pop-up window
4. Locally use a PC with two monitors, run "Remote Desktop Connection" on the non-primary monitor- you will see the TEAMS pop-up notification 100% of the time.
Did the clear cache option work though?
Or there's the Clear Cache option from answers.microsoft.com
I am V. Arya, Independent Advisor, to work with you on this issue. Assuming you are using Teams app on Wndows - Try to clear cache of Teams
If Teams is already running - Right click on Microsoft Teams app icon and Quit
Press Windows key, hold it and press r
Paste the following into Run Window
Copy everything from this folder to some other place in your computer. Hence, it means that you will have a backup.
Now delete everything within this folder
Open Microsoft Teams app and now check
Workarounds not Fixes. I have the same problem, a reboot brings the notification to the foreground for a few hours but then it only displays when everything is minimised. I'm no expert but I have found there is a shortcut to answer calls without relying on the notification panel. Ctrl+Shift+S answers an incoming calls although your still don't know who it is (just like the good old days before caller display). There are many other key-stroke shortcuts available, in Teams click your profile disc top right and the dropdown menu has the Keyboard shortcuts option, opening this show you the shortcut menu. Alternatively, when a call comes in, right click the taskbar at the bottom of the screen and you get the Show desktop option which minimises all applications to reveal the illusive notification screen, right click again to Show open windows to restore the minimised applications.
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.