Teams meeting disconnect

%3CLINGO-SUB%20id%3D%22lingo-sub-1622592%22%20slang%3D%22en-US%22%3ETeams%20meeting%20disconnect%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1622592%22%20slang%3D%22en-US%22%3E%3CP%3EFrom%20time%20to%20time%20our%20users%20experience%20disconnects%20when%20in%20meetings.%20The%20disconnect%20is%20frequent%20and%20usually%20occur%20anywhere%20between%2020%20to%2060%20seconds%20after%20joining.%20Upon%20reconnect%20they%20are%20able%20to%20stay%20connected%20for%20another%2020-60%20seconds..%20We%20have%20experinced%20this%20issue%20with%20Skype%20online%20aswell%20before%20migrating%20to%20Teams.%20Sometimes%20it%20works%20fine%20for%20a%20month%20or%20two%20and%20then%20suddenly%20it%20happends%20again..%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EIn%20attached%20screenshoot%2C%20we%20can%20se%20that%20the%20first%20meeting%20from%20conference%20PC%201%20was%20working%20fine%20for%209%20min.%20After%20that%20they%20had%20to%20change%20conference%20room%20and%20instead%20use%20conference%20PC%202%20and%20every%20attempt%20to%20join%20the%20meeting%20ended%20up%20with%20a%20disconnect%20after%2040%20something%20seconds..%20They%20even%20tried%20to%20use%20the%20call%20function%20instead%20but%20as%20shown%20on%20the%20screenshot%2C%20that%20failed%20aswell.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAs%20seen%20on%20the%20second%20screenshot%2C%20the%20reason%20for%20meeting%20%2F%20call%20ending%20is%20%22CallEndReasonLocalUserInitiated%22%20-%20No%20idea%20why%20though%2C%20the%20user%20was%20in%20presentation%20mode%20and%20I%20was%20in%20the%20room%20when%20it%20happen%2C%20the%20user%20did%20NOT%20end%20the%20call..%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAfter%20several%20attempts%20they%20gave%20up%20and%20postponed%20the%20meeting.%20I%20logged%20in%20to%20the%20same%20PC%20and%20had%20no%20issues%20connecting%20to%20a%20meeting%20and%20stay%20connected..%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EIn%20the%20third%20screenshot%20we%20have%20another%20example%20from%20just%20a%20few%20hours%20ago..%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWe%20are%20running%20Windows%2010%201909%20%2F%202004%20on%20all%20computers.%20Teams%20is%20auto%20upgrade%20and%20currently%20on%20version%201.3.00.21759%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-1622592%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EMeetings%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EMicrosoft%20Teams%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1622756%22%20slang%3D%22en-US%22%3ERe%3A%20Teams%20meeting%20disconnect%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1622756%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F241077%22%20target%3D%22_blank%22%3E%40Henric%20Appelgren%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThis%20sounds%20like%20it%20could%20be%20a%20local%20networking%20issue.%26nbsp%3B%20Have%20you%20tried%20joining%20Teams%20meetings%20from%20some%20other%20locations%20to%20see%20if%20there%20are%20any%20differences%2C%20or%20does%20this%20happen%20no%20matter%20where%20the%20attendees%20are%20working%20from%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1622785%22%20slang%3D%22en-US%22%3ERe%3A%20Teams%20meeting%20disconnect%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1622785%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F616707%22%20target%3D%22_blank%22%3E%40PeterRising%3C%2FA%3E%26nbsp%3BSorry%20I%20missed%20to%20include%20that%20part%2C%20users%20have%20experienced%20this%20issue%20while%20working%20from%20home%20%2F%20different%20locations%20as%20well.%20If%20it%20only%20occured%20at%20other%20locations%20I%20would%20to%20have%20assumed%20network%20issues.%20But%20when%20the%20disconnect%20always%20happens%20within%2060%20seconds%20or%20less%20and%20both%20at%20office%20network%20and%20home%20I%20dont%20belive%20it%20should%20be%20an%20issue.%20Besides%2C%20shouldnt%20you%20see%20that%20in%20the%20%22debug%22%20in%20Teams%20admin%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E
New Contributor

From time to time our users experience disconnects when in meetings. The disconnect is frequent and usually occur anywhere between 20 to 60 seconds after joining. Upon reconnect they are able to stay connected for another 20-60 seconds.. We have experinced this issue with Skype online aswell before migrating to Teams. Sometimes it works fine for a month or two and then suddenly it happends again..

 

 

In attached screenshoot, we can se that the first meeting from conference PC 1 was working fine for 9 min. After that they had to change conference room and instead use conference PC 2 and every attempt to join the meeting ended up with a disconnect after 40 something seconds.. They even tried to use the call function instead but as shown on the screenshot, that failed aswell.

 

As seen on the second screenshot, the reason for meeting / call ending is "CallEndReasonLocalUserInitiated" - No idea why though, the user was in presentation mode and I was in the room when it happen, the user did NOT end the call..

 

After several attempts they gave up and postponed the meeting. I logged in to the same PC and had no issues connecting to a meeting and stay connected..

 

In the third screenshot we have another example from just a few hours ago..

 

We are running Windows 10 1909 / 2004 on all computers. Teams is auto upgrade and currently on version 1.3.00.21759

2 Replies

@Henric Appelgren 

 

This sounds like it could be a local networking issue.  Have you tried joining Teams meetings from some other locations to see if there are any differences, or does this happen no matter where the attendees are working from?

@PeterRising Sorry I missed to include that part, users have experienced this issue while working from home / different locations as well. If it only occured at other locations I would to have assumed network issues. But when the disconnect always happens within 60 seconds or less and both at office network and home I dont belive it should be an issue. Besides, shouldnt you see that in the "debug" in Teams admin?