Jan 23 2023 08:28 PM
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 stop the ringing is to quit Teams and re-launch. Anybody else seeing this ?
Regards, John B
Jan 24 2023 10:37 AM
Jan 26 2023 04:19 AM
Jan 29 2023 08:37 PM
Feb 06 2023 05:45 AM
Having the same issue, but only when calling certain accounts using Windows 10 devices. Example would be if iPad A gets a call from PC A, PC A continues to ring after answering. But if iPad A calls PC A, no issue at all. Now if iPad A gets a call from PC B, there's no issue. This continues with random users calling iPad A. I've tried reimaging multiple PCs, even tried reimaging iPads. It almost seems account based, but not every account has an issue calling the iPad. Even tried using the browser version of Teams and still have the issue.
Feb 14 2023 01:52 PM
|
|
|
|
Mar 13 2023 08:55 AM
@HubBugFinder Issue remains. Call comes in ringing in primary, pickup in primary, continues to ring into the secondary, picked up in secondary by a different rep, and co-joined to the same call?
Apr 20 2023 05:17 AM
Similar issue here. Everyday more users are reporting it. If primary user desk phone rings, then delegate picks up call, primary user and all other delegates continue to have their desk phones rings for about 10 rings. Most users here have no delegate, some have 1 delegate, but a few folks have 2-3 delegates. Microsoft's documentation says you can have up to 25 delegates. This issue started a few months ago for one user, now I've had 8 people report it in the last 2 weeks. We have reset the physical desk phones, turned off all delegates and set them up fresh, made sure the phone firmware & Teams were updates, swapped out physical desk phones, turned on/off the Enable lightweight calling experience. Nothing is resolving this issue. I believe the problem is in Teams code at this point, not our hardware or configuration.
Does anyone have a resolution yet?
May 08 2023 07:35 AM
May 08 2023 07:47 AM
@Shamiir18 We are still having the issue. I've been sending Teams log files to Microsoft nearly every day. Hope they figure it out soon.
What PSTN are you using? A Teams calling plan? Operator connect or direct routing? We are using Direct Routing so it is hard to tell if it is Microsoft's issue or our SBC.
May 08 2023 02:32 PM
May 15 2023 05:15 AM
May 15 2023 03:24 PM
Oct 04 2023 08:34 AM
Still suffering here and it's October! Slow fix @HubBugFinder
Oct 04 2023 08:46 AM - edited Oct 04 2023 08:51 AM
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.
Oct 04 2023 08:55 AM - edited Oct 04 2023 08:57 AM
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!
Oct 04 2023 09:22 AM
Oct 04 2023 11:53 AM
We were able to work through this with Microsoft support. I did have to train my users to send me diagnostics whenever they had the issue. It took a few weeks but we did get it fixed. I think Microsoft fixed something on their end and didn't own up to it.
Oct 04 2023 12:01 PM
Dec 11 2023 07:56 AM
Hello,
and how did they fix the issue? We are facing same issue.