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.
Inf LocationService: [e911][getLocationInternal][requestBody={"networkInformation":{"e911":[{"chassisId":"aa-bb-cc-dd-ee-00","portId":"Gi1/0/13"}]
Checking several machines I see no entries for Chassis ID nor Port ID for LAN connected devices in this log file. - only IP and MAC info of the device itself. We checked a wireshark capture running on the same machines and LLDP information (Switch and Port) for our Cisco switches is being presented to the Windows OS. Teams just doesnt seem to be able to see it.
Unsure where to turn next, please advise if you have any ideas. Is there perhaps a policy on Teams admin center that would block this data from being seen by the client?
Greg Whitworth
What vendor/model switches do you use?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.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.....
- Curious if you (or anyone) ever saw this working on a Teams Phone, or a Windows 11 based computer.
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. - I am still having issues with phones not respecting Lldp, as well as win11 computers.
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. 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.
jangliss, checking in to see if there's been any movement on this. Doing a large migration and we just can't seem to get any Teams Device to get a location at the port level. We do get the main location reported but not the zone.
- Thanks for the information.
RahulJain0509last status update I received was Microsoft acknowledged there was an issue, and fixes will be in the September release. So fingers crossed we get the actual fixed update this month.
- Hi radz .. would like to know if you have any new update from MS?
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.
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?
Status update so far from Microsoft is a Britney Spears hit song; "Ooops, we did it again". As of Friday 9th:
The fix was not successful in the deployment regardless of the notes that were displayed. The last comment on it was Friday that they are still trying to determine what is wrong, so it is actively being worked on at this time. I have brought this up to my Team lead to discuss in an upcoming meeting with some higher-ups.And the status update I got this morning was "Still monitoring the case, no ETA"
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.
Not yet unfortunately, though I just reached out again. I got a new case created and assigned to the original agent I had before, and they reported a number of people complaining it still wasn't working. Last time I did observe they were not logging the full Port ID, but that could just be a logging issue. Who knows!
Could you try clearing all the Teams cache data on a test machine, and see if that forces a rediscovery? That is, with Teams closed (actually exit, don't just minimize) go to %AppData%\Microsoft\ and rename Teams to Teams.old, relaunch Teams and sign back in. Give it a bit of time, then hit ctrl+alt+shift+1 and take a look at the logs, also check in Settings > Calling to see if the location is set in there.
I've had issues previously with the Teams client not picking up some changes until the cache was cleared out completely, and the client itself didn't seem content with doing it itself.
