Forum Discussion
Teams emergency location sticky
JBoslooper_Magenium so I have received some feedback from Microsoft with an explanation of how this works. The main issue where the emergency location was stuck or not working appears to be resolved. I believe it was a backend fix instead of client update. Anyway around August the client started updating consistently at first a 10 minute window and now consistently at 5 minutes.
Microsoft described to me that a network change would start a timer on the client. At 5 minutes the client will send a request to Teams backend to check for its emergency location. If the Emergency Location is different it will update the client. This is what I'm experiencing at this point in time. If I change from wired to wireless, 5 minutes after this change the location updates. Same goes with other network changes (i.e. BSSID change, leave one building and reconnect in another, disconnect Wi-Fi adapter and reconnect).
Two additional points were made by the Microsoft contact. First, the location is "hashed and cached for 4 hours (or until there is a network change)". Second, if there was no event (Teams startup or network change) for 4 hours, the Teams client will send a new request.
JBoslooper_Magenium so I have received some feedback from Microsoft with an explanation of how this works. The main issue where the emergency location was stuck or not working appears to be resolved. I believe it was a backend fix instead of client update. Anyway around August the client started updating consistently at first a 10 minute window and now consistently at 5 minutes.
Microsoft described to me that a network change would start a timer on the client. At 5 minutes the client will send a request to Teams backend to check for its emergency location. If the Emergency Location is different it will update the client. This is what I'm experiencing at this point in time. If I change from wired to wireless, 5 minutes after this change the location updates. Same goes with other network changes (i.e. BSSID change, leave one building and reconnect in another, disconnect Wi-Fi adapter and reconnect).
Two additional points were made by the Microsoft contact. First, the location is "hashed and cached for 4 hours (or until there is a network change)". Second, if there was no event (Teams startup or network change) for 4 hours, the Teams client will send a new request.
- JustinDonut. I can't say for sure but would believe that would be considered a network change as the ethernet adapter did not have an address before and now does. Probably best to test that theory. With-in 5 minutes you should know. By the way you can check the Microsoft diagnostics file on the local computer, the network information that is matching and which policies are applied to the machine based on your network information. With Teams in the foreground of your screen, press ctrl, alt, shift, 1 keys together and you should see a bunch of files download to your downloads folder. Look in the diagnostics folder that shows up with current date/time in the downloads folder. Open it and check the "web" folder for a .txt file ending with "_calling.txt". Open it and you'd find this information and more.
dwilliamsucb So would that mean if a laptop is being plugged in to ethernet without disconnecting the wireless, the Teams client would not see a network change because the wireless is still connected?
This is happening to our site today DEC 14th, 2022.
even after 15 mins, no change to correct room mapping.
New ticket being started...
- That is GREAT information! Thank you so much for following up on this. While that's not necessarily a perfect solution, at least the explanation of what the client behavior SHOULD be and my customer will be happy knowing there is an answer. I'm going to check this behavior the next time I'm on site. Thank you again!
