Mar 14 2019 07:47 AM
Mar 14 2019 07:47 AM
We were in a video meeting, the host was sharing his desktop and the call was running for over 30 minutes until microsoft teams ended the meeting by itself?
How could this happen?
Where can i find a logfile or anything that could explain why this happened?
Mar 14 2019 07:55 AM
In the Team admin center look up one of the users then look at their call history to identify this meeting. You can see when each of the participants joined and left the meeting, and through the debug tab you can see down to the specific actions and reasons.
If detained data is absent that normally mean that network connectivity was lost at the end of the call, so it can't report call data, which would be your answer.
From personal experience you'll investigate lots of these and the answer is always either 1. Network loss or 2. It didn't happen, users pressed a wrong button.
Mar 14 2019 08:11 AM
Mar 14 2019 10:41 AM
Unless you have a repeatable issue it's pretty unlikely you will diagnose any kind of issue. Things happen, maybe your network switch reset the port, maybe your firewall had some IDS that became suspicious, maybe the local machine installed a patch at that moment, any one of millions of small randoms could create a one off random event.
Mar 28 2019 02:36 PM
These are not so random from what I have seen. We have 4-6 Teams meetings going on at any given time. Around 1/3 of those will just randomly end the meeting which is seen because the chat gets a message saying recording has stopped. You can quickly join the meeting again to get it going, but someone has to be paying attention to know that it stopped. I can replicate this problem all day, and even had 3 today that dropped mid-meeting. We are running Teams in a pilot and will probably have to revert back to Go To Meeting as these meetings must be recorded. Not a single thing shows up in the logs about updating, authentication, disconnects, etc. The only thing you see is that the status changed from Presenting to Available.
Mar 29 2019 05:59 AM
I plan on getting one opened today. We have been running these Teams meetings for 2 weeks and have confirmed that the logs contain no information. I was able to attend two of these meetings yesterday to confirm. There is a 99% chance that this ticket will never get resolved or will be a "known issue" so I am not giving my hopes up. Unfortunately, everything is "open a ticket" and almost all of them end up with the same no-resolution available and/or wait until the next update.
Mar 29 2019 07:55 AM
@Jacob Heinikel my org is Teams Only, we have hundreds of meetings each week, and they don't end early. I would strongly suggest checking that your network is allowing the right protocols and there isn't some security device that breaks you network connection.
The call records in the Team admin centre will show you why each user disconnected from the meeting.
Mar 29 2019 07:57 AM
Mar 29 2019 08:09 AM
I have been running through the diagnostics to see what the deal is. These meetings clearly show that the meeting ended. No timeouts, disconnects, audio quality shows good, etc. Even the Teams log on the client only shows that the status changed from Presenting to Available. I have daily meetings that run for an hour or so and never fail, but these other meetings fail pretty regularly around 1.5-2 hours in. Firewalls show no blocks either. (I assumed this was the problem, but turned out no connections were blocked) I'll open a ticket and respond here with what comes out of that.
Jul 10 2019 01:50 PM
We had two reports of this today. Did you ever determine the cause?
Our report was when two people connected, Person B started recording then left the meeting. The recording should continue until Person A stops the recording or leaves the meeting, but the meeting terminated "on its own", which then correctly stopped the recording.
Sep 20 2019 07:31 AM - edited Sep 20 2019 07:32 AM
@Roy Faltesek We had a Mac user experiencing a similar problem. Teams calls were dropping after 30-45 seconds.
After a restart, when you started a call you would hear the dial tone over people speaking.
Turns out there was some conflict with the Lync 2010 client (we're currently going through migration).
After exiting Lync the issue was resolved.
Check any possible conflicting applications.
Sep 20 2019 08:59 AM
@Rzel99 The problem you reference sounds legit but different.
We confirmed our problem is an idle timeout of Teams; it happens right at 30m. It only happens when no one interacts with Teams for 30m. They go into a room, someone joins from their laptop to record the meeting and present their desktop, they work in PowerPoint or Word or Excel or whatever, 30 minutes later, with no one having touched Teams, the meeting ends. If you click around within Teams at some point, I believe it will reset the 30m timer.
Sep 20 2019 10:01 AM
Solid feature there. /s
An "Are you still in the meeting" prompt be way more elegant rather than an undisclosed 30 minute timeout. Maybe something like Netflix, Pandora, YouTube, etc do to ensure something is still going on. Luckily, our meetings have been more hands-on and people presenting content rather than just voice.
Sep 30 2019 08:59 AM
We have the same issue but not on meetings, but on regular phone calls. During a longer phine session you normally do not click around in your teams client and these phone calls are exactly terminated after 30 minutes. So this timer seems to be active for all calls. So what possibilities do we have to extend this timer to minimum 2 hours?
Sep 09 2020 10:15 AM
Your responses imply that TEAMS is not a product that anyone can rely on, the typical accept the failing as designed acceptance mindset. I know that I am having issues with TEAMS not allowing me to receive or make calls while other platforms have no issues, it is from a WINDOWS 10 OS PC where Jabber has no issues and other software we use can make and received calls. Based on your logic there is no reason to use TEAMS as it will not have a resolution and it is currently dysfunctional as it stands.