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.
ChrisHoardMVP jangliss Sorry, but I've not tested this but all I can say it is listed as supported as long as the firmware been updated (from May 2020).
Configure dynamic emergency calling - Microsoft Teams | Microsoft Docs
Yep, but doesn't list the level of support though. I have a case open with Microsoft, which is going very slowly, with the obvious first step being to say "did you check with <vendor>?"
Thank you and ChrisHoardMVP for at least chiming in.
Wonder if Ilya Bukshteyn, jeffschertz, Adam Jacobs or Carolyn Blanding (MS TEAMS) knows more details about this.
- Ilya Bukshteyn
Microsoft
LinusCansby so this is about location info for Teams Phones for E911 yes? SandhyaRao and KruthikaPonnusamy thoughts?
