Forum Discussion
Emergency Locations, Port Data, and physical phones
From my the last update from Microsoft, the next update will be in June should have fixes for the phones.
As for the MS Teams client itself, that should work assuming you have the correct information in Teams. I'd double check the values being sent in the LLDP packets to make sure you're using the right values for chassis ID and port ID. Some switches will send extra information (TLVs) so it's important to grab the right fields.
If you connect a computer with Win10 and the Teams client on, give it some time to verify the networks. Go to Settings > Calling and see what location is showing up. If you see a location, close the settings window, and hit ctrl+alt+shift+1. It'll dump a bunch of log files into your Downloads\ folder. If you look at the file named "MSTeams Diagnostics <datetime>.txt" and search for chassisId, you should see what the Teams client is sending to Microsoft. You could confirm this is what you have configured.
As of Teams Version 1.4.00.26376 (64-bit) on PC, I am now able to identify ChassisID values correctly! MS has confirmed this fix is being ported over to the Device App and should be released "soon" to devices like Yealink MP54 etc. Slow progress but progress nonetheless!
One additional note: the refresh of the client to query its network identifiers is also now fixed so if I moved my PC around the building now to WIFI or other switches it queries and updates my new location based on the configured parameters where previously the client would hang on to the old location value.
For win11 I tried two systems with my username logged in and both would only detect by subnet and not lldp. I plugged in a win10 laptop with same teams client version and it picked up right away.
Microsoft had been promising me info for a week but got nothing for me yet.