teams.microsoft.com - Call freezes after 15-20 seconds

[webcompat-bot]

URL: https://teams.microsoft.com/v2/

Browser / Version: Firefox 124.0 Operating System: Ubuntu Tested Another Browser: Yes Other

Problem type: Something else Description: Calls are possible but freeze in "new teams" Steps to Reproduce: Have switched to "new teams" adn as far as I understand firefox is supported and is possible to initiate calls but the call freezes every 10-20 seconds. Switched to chromium and was able to perform call without any issues.

Browser Configuration

• None

From webcompat.com with ❤️

[ailioaie]

Thank you for reporting this issue, I wasn't able to reproduce it yet. I've tried to test the issue but unfortunatelly i can't even connect to teams as expected using the link provided:

I also try to connect searching on google for Teams but also not succesfully:

Tested on: • Browser / Version: Firefox Nightly 127.0a1 (2024-04-16) / Firefox Release 125.0.1/ Chrome 123.0.6312.122 • Operating System: Linux

Notes:

1. Chrome asking me to upgrade Teams when I try to reproduce. It seems the test account is not working and we need a subscription

Moving to Needsdiagnosis.

[qa_16/2024]

[ailioaie]

@denschub Can you take a look, please?

[inv_16/2024]

[ailioaie]

"More users seems to reproduce this issue, check: https://github.com/webcompat/web-bugs/issues/118070#issuecomment-2058998360 "

[inv_16/2024]

[dev-nicolaos]

I've experienced this same issue. Both on "teams.microsoft.com" and "teams.microsoft.com/v2/". On "old teams" it was annoying for a while, but not unusable. For the first 5-10 minutes of any meeting the call would freeze up for a few seconds every 30 seconds or so before auto-reconnecting. Several weeks ago the issue became significantly worse, and I had to switch to taking teams meetings in a chromium based browser. During that time my user (and/or org, not really sure which) was prompted to "switch to the new teams" (/v2) so I thought I'd try a meeting in Firefox again. I experienced one or two "freezes then reconnect" cycles shortly after joining, but after that the meeting went forward with no issues.

This is all using the latest stable versions of Firefox on Windows 11 Enterprise and Windows 10 Enterprise.

[Bitals]

I've also had the same issue several weeks ago, but it pretty much resolved itself. Like there were several days in a row (less than a week I think) with multiple seemingly random disconnects/freezes during the call, which reconnected after about a minute, but next week they were gone again, even without moving to v2.

Also this was in an unofficial electron app, meaning chromium. So I guess teams just was a bit moody for a while?

[denschub]

Thanks for the report. We're looking into it.

[NoTuxNoBux]

Is this an actual 'freeze' as in you momentarily hear nothing or see no webcam updates and then the call continues? I had a similar issue before when IPv6 was enabled for some unknown reason - disabling it fixed the problem, but recently I tested again with IPv6 and now it's suddenly not an issue any more.

The issue I had in https://github.com/webcompat/web-bugs/issues/118070#issuecomment-2058998360 is slightly different though, because Teams just ends the call after about 10 seconds of laggy webcam footage (but the call works up until that point). I had this with everyone except one person, and then it evolved to just everyone in one-on-one calls. I now today tried allowing use of the webcam (I usually leave it disabled because I don't turn it on), and today I can do a one-on-one call successfully again with at least one person. I'll try to add an update to this post if this effectively solves the problem.

Everything works fine in other tools such as Jitsi, Google Meet or other browsers such as Chrome, so it still sounds like it's Teams at fault somehow.

EDIT: Giving permissions doesn't fix the issue. Neither does disabling tracking prevention or extensions.

[Bitals]

Is this an actual 'freeze' as in you momentarily hear nothing or see no webcam updates and then the call continues? I had a similar issue before when IPv6 was enabled for some unknown reason - disabling it fixed the problem

It is, both sound and video stopped, after some time a message going something like "trying to reconnect" appeared, stayed for up to a minute and the call reconnected.

No IPv6 in this part of the world ATM.

[NoTuxNoBux]

I created a new issue for my problem since it is distinct from this one here: https://github.com/webcompat/web-bugs/issues/136071 - the call doesn't freeze for me, it just drops entirely.

[jdu]

I've been experiencing this pretty often, it's hit and miss sometimes, but seems to be predominantly an issue when having one-to-one calls. Enough that I have to move calls to Slack because teams is really unusable.

One-to-one calls end up with a major freeze for 2-4 seconds every 15-20 seconds. The video quality is generally pretty poor as well. I'm on a fibre line with 900Gbps and the other person will generally as good of or better than normal connection. I've not waited it out to see if it resolves, but it does seem to be specific to one to one calls as I don't seem to have the problem when having group calls at all.

No VPN in between, no proxies, nothing that would interfere with the call from a networking perspective.

Ending and restarting the call doesn't resolve the issue.

[rettichschnidi]

Similar (same?) issue here. Most recent Firefox (129.0.2, 64-bit) on Linux (Debian 12). Happens every 30-60 seconds.

When it happens, the screen looks like this for around 3 seconds:

During that time, the presenters audio is interrupted because the "warning" jingle gets played.

Every time this happens, the following warning appears on the console:

WebRTC: onaddstream is deprecated! Use peerConnection.ontrack instead.

Sometimes also some errors: