Aug 12 2020 08:00 AM
Aug 12 2020 08:00 AM
So I am having an issue with Microsoft Teams on a daily meeting. The issue is that one user continually gets dropped from the teams meetings. He's tried both of our wifi networks, his personal network, and a wired connection none of these fix the issue. At first I assumed it was network based as our buildings internet is p2p and can sometimes be a bit difficult to work with. I have a log file but I'm not sure how to exactly read the file and apply any changes accordingly. Thanks for any information on either how to read the log file or with what my root issues might be.
Aug 12 2020 08:08 AM
Hi @js1605 ,
Before delving into logs, especially as there is no nice tool outside of Microsoft to parse it (short of ctrl + f), I would recommend trying the following:
Is the user in question using the web or desktop client? If client:
Has the user enabled the new meeting experience check within their settings, if yes can they turn it off and see if the problem still occurs. If no, can they turn it on and see if the problem still occurs. A restart of the application will need to occur for any changes to that setting to take effect.
Is the same issue present in the web version.
What is the version of their client?
If the web version:
Could they try the desktop version and see if the issue is still present. I know hardly the golden answer but worth a try as that kind of takes the update and version of the desktop application out of the equation somewhat.
Aug 12 2020 09:23 AM
Thanks for the quick reply to answer your questions:
He is on the desktop client.
The new meeting experience isn't checked.
We experience the same issue on the web or desktop versions. (less on web)
Version 1.3.00.19565 (64-bit)
Aug 12 2020 09:40 AMSolution
Aug 12 2020 09:50 AM
I also noticed this setting in settings: Enable logging for meeting diagnostics (requires restarting Teams)
Unable to find any official word on it but it may give you more insights into meetings in the logs, or might just be for the new meeting experience.
Aug 12 2020 09:56 AM
The installation is a standalone installation, I'll try out the new meeting experience and see what shakes out with that.
Feb 11 2021 02:52 AM
@HenryPhillipsNimbitech I have the same issue and found a reason that’s stumping me: Teams calls get dropped when, and I‘m quoting the Teams debug logs here, a cookie is rejected *within Teams* !? (note that this is between desktop clients, not using the web client!)
Full Log entry (two of these entries are created each time a call gets dropped):
Thu Feb 11 2021 10:55:27 GMT+0100 (Central European Standard Time) <15292> -- event -- errorMessage: https://teams.microsoft.com: line 0: A cookie associated with a resource at http://teams.microsoft.com was set with `SameSite=None` but without `Secure`. A future release of Chrome will only deliver cookies marked `SameSite=None` if they are also marked `Secure`. You can review cookies in developer tools under Application>Storage>Cookies and see more details at https://, status: success, scenario: 21a290dc-ae12-4d0d-b299-d0d740ce2d8f, scenarioName: experience-renderer-console-error, name: experience-renderer-console-error, step: start, sequence: 0, delta: 0, scenarioDelta: 0, elapsed: 264788079, stepDelta: 0, ppChannel: Production::DC, distSrc: PROPLUS_O365ProPlusRetail,VisioProRetail, ppInstallMode: UPDATE, autoStartPolicy: undefined, vdiMode: 0, eventpdclevel: 1, Scenario.Name: experience-renderer-console-error, Scenario.Step: start, Scenario.Status: success,
This occurs only with direct 1:1 calls, not when joining a call that’s part of a scheduled meeting. Being just an end user, I don’t know the connection between Teams calls, Chrome, cookies and the reason for why these rejected cookies result in dropped 1:1 calls but not scheduled calls. But I know that multiple colleagues have the same call drop issue, and it’s quite annoying. If you or anyone here knows more about what this issue means and how to fix/workaround it, I‘d me much obliged...
Mar 04 2021 08:08 AM
I've here a pattern that the drops occur somewhere between 2m55s and 3m1s of connection.
@GeorgStoegerI see these two errors on rejected cookies also occur in the log on calls where I didn't have a drop-out each 3mins.
Sometimes I've the drops also when attending scheduled meetings, I can't find a pattern yet.
It looks like it started happening here only recently after the latest teams update.
I'm using a Jabra (Dell made by Jabra) headset - in a similar thread there is a vague suggestion that it may be related to that: https://techcommunity.microsoft.com/t5/microsoft-teams/teams-call-automatically-gets-disconnected-fr...
Mar 05 2021 05:23 AM
In my case, the issue seems to disappear if I use my Dell/Jabra headset not via its USB controller but if I plug it in directly with its 3.5mm jack plug -> looks like this controller somehow triggers an end-of-call - although I used this one already for a year without problems before this suddenly happened. So for my case it looks like issue https://techcommunity.microsoft.com/t5/microsoft-teams/teams-call-automatically-gets-disconnected-fr...
Mar 16 2021 06:59 AM
Jul 15 2021 09:00 AM
Jul 15 2021 09:03 AM
@NIkhilSoni1984 So while my answer wont be very helpful it is what our end answer was and that was our ISP. We were on a Point to point internet that just was ultimately too noisy of a signal for teams phone calls. We replaced our ISP and went to fiber and haven't had any issues.
Jul 18 2021 09:16 PM