Forum Discussion
JohnBuch
Jan 24, 2023Copper Contributor
Teams Call Ringing Continues After Answering
Hi there Community, We're running Teams 533356 and 531156 on Apple macOS 12.6.1 Monterey. In the last 2 weeks we're seeing many internal Teams calls continue to ring after answering. Only way to ...
harleyburt
May 15, 2023Copper Contributor
Apparently it was patched months ago, but we are still seeing the problem. It doesn't seem to matter who (or what device) is calling who. Clients who have the issue will see this behavior both calling out and receiving calls. The ring will continue after the call is answered. Deleting cache "seems" to help some users, but not all. Even a full purge and reinstall only ever helps temporarily.
We've been seeing this for more than a few months now, and it's highly disruptive. The only way to stop the ring in to kill the client and re-launch, and sometimes users are having to do that several times while attempting to setup meetings and conference calls.
Did we all jump on to Teams VoIP before it was actually ready for prime time?
We've been seeing this for more than a few months now, and it's highly disruptive. The only way to stop the ring in to kill the client and re-launch, and sometimes users are having to do that several times while attempting to setup meetings and conference calls.
Did we all jump on to Teams VoIP before it was actually ready for prime time?
HubBugFinder
May 15, 2023Copper Contributor
I'd log a job with MS Support. They had to do something to our tenant manually 🙂
- BrightFrankOct 04, 2023Copper Contributor
Still suffering here and it's October! Slow fix
HubBugFinder
- harleyburtOct 04, 2023Copper Contributor
We created a ticket with Microsoft Support. Every few days I had to ask for updates. Every time I did they told me that the problem was my PC (even though everyone with the problem has it on every pc they use) and each time they had me generate support files for them again. At some point my test system stopped having the problem, and they told me that they could no longer help unless I bothered one of my users every few days to get support files (the support files that I had provided many times) and when I told them I didn't want to do that they insisted there was nothing they could do. We got our Account Rep involved and they got more active, but still never found a solution. They just kept insisting that the problem was on the PCs, and not related to Teams.
Later I talked to a Microsoft Partner, who I won't name, and he explained that the way the Support system is structured, it benifits the first level support provider (who isn't Microsoft) to keep the tickets open as long as possible because they are paid based on the time they spend on each incident.
All that to say, Microsoft Support is only useful for burning your own time. I certainly wouldn't expect to get any help from them.
Edit: I forgot to mention that even having A5/E5 licensing, that costs hundres of thousdands, doesn't get you "premium support." Microsoft will sell you that seperately. This is just my opinion, but that model seems to encourage the not-premium support to be less than helpful. If it was useful people probably wouldn't pay for "premium," right?
If I sound salty, yeah.
- BrightFrankOct 04, 2023Copper Contributor
What awful service! I appreciate the update, although I won't hold out hope of this fixing itself anytime soon and will hunt about for other call solutions.
Funny that they tried to pin it on blue tooth headsets and PCs - I'm on a Macbook Air and have the same issue, using plug-in old school Wantek headset mostly. Every call I get this, I've had this since first using Teams (6 months ago). Originally I was using a full Mac and had the same issue - I've even tried my bluetooth headset from home with the same results!