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.
I'm not sure if you noticed, but the firmware updated (122.15.0.36) which was released at the beginning of last week had 1449/1.0.94.2021022403. Microsoft released a new firmware over the last day or two 1449/1.0.94.2021033002. I'm assuming this is the firmware that has the LLDP fixes in it. I've got it rolling out to a handful of test phones to see how it plays out, including the MP56 phones.
If you have chassis IDs it should be fine to that level, assuming that's as granular as you want to get it. Double check the firmware you're on, and then retest.
- Testing with Yealink T55a, T56a, and MP56, also Poly CCX 400, 600, and 700, with the latest firmware and Teams App version, I have yet to get it working. I'm still doing testing and working with our contacts at both Yealink and Poly to see if we can dig into where the issue might be.