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.
You're not going crazy, friend. A configuration that has been working for a while, appears to have stopped for me. Same switch, same port, same tenant. I'm doing additional configuration testing. Also observed some odd behavior with Set-CsOnlinePort earlier where it refused to update the location id.
So after a few hours, and multiple 911/933 calls. The Teams client on the desktop did actually pick up the location based on port information. It almost seems like the location lookup the first time did not have the LLDP data to send to Teams, and later on it did. Are you still having issues with this?
jangliss no charge on our end unfortunately still unable to get ChassisID to be found and interpreted by both Soft Client on PC nor Hard Phone. Hard phone logs actually do show the ChassisID MAC address is being reported to device but still does not then report the correct location information on the phone. Soft client logs never show anything about ChassisID.
We started using subnet for now temporarily as the identifier as that works fine on clients and phones but is not optimal for our building geography in terms of reporting accurate locations.
We have MS premier ticket opened for several weeks now and is with PG team but so far no progress. If you don't mind me asking what model switches do you use, we are on Cisco C9300s but I have also seen the exact same issues occurring in my home lab using Unifi Switches... Thanks.
