Emergency Locations, Port Data, and physical phones

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.....

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.  

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.

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.

doumis 

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?

radz 

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"

doumis 

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.

radz 

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!

doumis 

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.

hi radz and jangliss 

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?

doumiswhen you create your log files (ctrl+alt+shift+1) you'll want to look at the log file without the suffix, just the date.  For example "MSTeams Diagnostics Log 6_23_2021__2_03_19_PM.txt".  In that log file, search for "Location", "getLocation" or "e911". There's usually a few entries, an example of mine connected to wireless looks like:

2021-05-25T19:47:50.972Z Inf LocationCache: [e911][getLocationResponseFromCache][cacheHit=false][key={"bssid":"aa-bb-cc-dd-ee-ff","ipv4":"10.10.10.10","mac":"ff:ee:dd:cc:bb:aa","ssid":"MySecretSSID","subnetLengthIpv4":"24","isCallingPlanUser":false}][context=e911InfoChanged::emergencyService][cachedItem=undefined]

I don't have the logs currently for a switch connected device, but I believe it has "chassisid" in it.

Hope that helps.

jangliss We have checked the _calling.txt log file  on LAN-connected devices and it shows no network information regarding switch or switch port so its as if Teams client is not seeing the switch info at all.

It only shows the bolded information below (IP/Mac has been removed for security), it does report the correct client IP and client MAC address however nothing about the switch or port.  

doumis 

I've done switch and port level for multiple customers, and not had an issue with it except with physical phones (Yealink, Poly, Audiocodes). This appears to still be in question.

Have you looked over my previous responses at grabbing the log files to look at what's being sent to Teams from the desktop client, and ensured it matches?