May 02 2018 04:20 PM
May 02 2018 04:20 PM
we are seeing increasing instances where you have an incoming call you get the audio notification but nothing visual so you have no way to pick up the call. If you bring the teams client to the front as well there is no obvious sign of the call.
We are also seeing cases where although the desktop client is up and running and you are actively working on the machine it is only the mobile client that rings
Jul 26 2018 09:48 PM
Agree. Moving from Slack which just works to be forced onto Teams, the missing functionality of knowing that someone is calling me on Teams is just pathetic.
Aug 13 2018 10:39 AM - edited Aug 13 2018 10:44 AM
I am seeing this consistently and have to call other people
I get the audio ring but no visual notification (pop up window to answer call) nor visual tag (phone icon) on a chat group that I can see then open the chat window and click on join call. None of this works.
I even have had people in the call try to re-add me to the call but that doesn't work either - same result
Aug 24 2018 08:11 AM - edited Aug 24 2018 08:23 AM
I didn't get any notifications until a Voice mail was left. No visual or ringing when the Teams Desktop app was running and Skype for Business was not. I have the settings in the Admin Portal to Run in Islands mode so the call should have been directed properly.
Well this explains it;
I am really not sure about unleashing Teams on my teams. It seems like more trouble than it is worth.
Aug 24 2018 10:11 AM
@Scott Klein I think you ought to raise a support ticket as you explained you aren't getting any notifications, and that was some time ago now. It's certainly not my experience. Support will be able to look through your clients logs to see what it's doing.
Aug 24 2018 10:27 AM
It was from and outside caller over PSTN to my SfB provisioned number. I assumed that since MS was eventually moving everyone to Teams and away from SfB the paths were in parallel but that is not the case. I really wanted to eat our own dog food and use only Teams so I was not running SfB at the time. Seems I cannot do that and need to have both apps running. I have to have SfB for a Polycom endpoint when in the office, so I cannot make the policy change. I also have some other staff that have SfB calling plans so I cannot force the policy on everyone.
Aug 26 2018 03:11 AM
@Forrest Hoffman when you are in islands mode incoming PSTN calls will go to Skype. If you switch to Teams only mode they will come to Teams. Polycom VVX phones will work with Teams, but I can't really see when that will be, sometime soon I'm sure.
It's easy to change and change back, so it's worth giving it a go, using a headset etc.
Sep 10 2018 12:07 PM
Same issue right now only 1 user of 30 has reported it. No notification for Teams to Teams calls. we do not use PSTN calling with Teams or S4B, we have another provider for that.
Sep 12 2018 08:34 PM
Having the same issue.
1 user across about 20 users.
Have done a full uninstall / reinstall. Issue stays with that user.
Sound card or app related I wonder? Maybe windows update related?
Dec 11 2018 06:15 AM - edited Dec 11 2018 06:22 AM
One of my colleague has the same issue.
He cannot see incoming calls (no notification).
It works for everyone else (15 people). The other features of Teams works for him.
UPDATE: at first, I thought that he couldn't initiate calls, but he can. Also, he sees, in the application, that someone is calling and can accept, but he hasn't the call notification.
May 09 2019 02:33 PM
This problem just appeared for me yesterday. Didn't adjust any settings in Teams and now I can't answer calls on my PC, all calls go to my Mobile Phone. I deleted Teams from my phone to try and force the PC to ring but alas, it didn't work. Did anyone every find a fix for this issue? It's really, really frustrating.
Jul 10 2019 08:59 AM
Jul 31 2019 05:04 AM
@Jon Greavesand everyone, I don't know if this helps, but we were having similar problems with a couple of users. They could make Teams calls but when someone called them, it either only rang their mobile app, even when sitting in front of their active desktop, or it wouldn't notify the at all, after removing the mobile app. They would simply see a missed call in their activity feed. Then by accident, we found out the users had quiet hours or what Windows 10 now calls Focus Assist turned on. I've never even heard of that feature, but it is essentially a do not disturb function in Windows 10. Once they toggled that to "off" they could make and receive Teams calls just fine. They swear they never turned Focus Assist on, so that still remains a mystery, but it definitely fixed their Teams issue. I hope that helps.
Aug 01 2019 11:38 AM
I was hoping the Focus Assistance would fix this issue, but it was already turned off for our users. We still have not found a solution for this most basic of issues for a communication platform.
Aug 06 2019 09:20 AM - edited Aug 06 2019 09:20 AM
We've been having issues with this at my company as well. We'll check for Focus Assist to see if that helps. Thanks for the tip!