Forum Discussion
Emergency Locations, Port Data, and physical phones
- May 22, 2021
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.
I have an open ticket since December regarding both. A Win10 laptop plugged into the same port gets the Port ID fine, but two Win11 computers as well as a Teams Phone fail to use the port-based location/chassisID.
- iroutepacketsMay 10, 2022Copper Contributor
Greg Whitworth
What vendor/model switches do you use? - Greg WhitworthApr 15, 2022Copper Contributor
Poly CCX 500 - Firmware Version: 7.2.1.1971 - Teams App Version: 1449/1.0.94.2022041102.
Location Identification not working using LLDP via ChassisID. Windows 11 PC (Build 22598) running Teams client (1.5.00.9463) works just fine. - doumisFeb 02, 2022Copper Contributor
ph_ly Finally with the latest version of Teams app (1449/1.0.94.2021121302) on MP54 phone I am able to get LLDP chassis id on the phone. We use WIn10 only so no experience with Win11 on the PC side. That said even with PC now and Win10 the e911 location information is sporadic from time to time in our sites and PCs in terms of if the client picks it up or not so still not working as reliably as it should for an e911 service.....