Dec 09 2020 12:33 PM
Dec 09 2020 12:33 PM
TLDR; Has anybody had any luck with Teams devices, such as a Poly CCX 400, Yealink MP56, or AudioCodes HD450 in getting location data when you have port level data defined?
I've seen this come up a couple of times, and have opened a case with Microsoft. First thing they did was point the fingers at the hardware vendors, but they all say they're just running the Teams client, so it has to be a Microsoft issue. Setup goes something like this:
$civAddress = New-CsOnlineLisCivicAddress .....
Set-CsOnlineLisSubnet -Subnet 188.8.131.52 -LocationId $civAddress.DefaultLocationId
$loc = New-CsOnlineLisLocation -CivicAddressId $civAddress.CivicAddressId -Location 'Boardroom'
Set-CsOnlineLisPort -LocationId $loc.LocationId -PortId 'Gi-0/0/14' -ChassisId 'AA-BB-CC-DD-EE-FF-'
So this seems like the Teams client on a Windows workstation works fine, but physical phone device does not appear to be pulling the location properly. Anybody successfully been able to get port level location data working with physical devices?
Dec 28 2020 08:21 AM
Dec 28 2020 11:39 AM
Dec 28 2020 11:43 AM - edited Dec 28 2020 11:45 AM
Dec 28 2020 11:59 AM
Dec 28 2020 01:28 PM
Jan 04 2021 01:41 PM
Jan 05 2021 05:06 PM
Thanks for the information. Is there any details documented anywhere? I'm at nearly a month on the case, and they're still going backwards and forwards with the product group and it seems like nobody has a clue.
Feb 02 2021 08:53 AM
I, too, have not been able to get Teams to recognize LLDP data, though it can discover subnets perfectly fine.
Feb 03 2021 12:44 PM
I spoke to somebody at Microsoft and got additional details on this. Currently the port level mapping only works on the Windows Teams client. There is an additional application that can be acquired through support for MacOS. For other devices such as Yealink/Poly/AudioCodes phones, support is coming soon.
Are you able to get the Windows clients to correctly locate themselves? If not, I can certainly help there, I've had no issues with that.
Apr 01 2021 11:18 AM
I'm working on this issue currently, Teams windows client pulls location and routes to local PSAP, but Yealink MP56 is still going out to the national ECC.
I've provided a link to Microsofts latest release for Teams phone software, which does call out LLDP for E911 Updates. Unfortunately after updating my phones it still does not seem to make a difference. I've set up everything up to switch chassis ID#s, did not do Port ID #s. But now i'm wondering if i need to go down that rabbit hole to make this actually work?
Apr 02 2021 07:00 PM
Apr 05 2021 08:31 AM
Apr 27 2021 06:05 AM
Apr 27 2021 12:45 PM
Apr 29 2021 09:14 AM
May 04 2021 02:28 PM
Not a good response from support today, on this "new feature".
I just wanted to inform you that Product Group has already finished their initial investigation and this has been accepted as a bug ― the product group will work on identifying the faulty code, restoring the functionality and patching it in to all branches of Office.
The engineering team will go through the process of developing, testing, and then deploying the fix globally however their is no tentative ETA for has been setup till now for fixing the issue. Once the fix is complete it will be deployed to your tenant and no further action is needed on your end.
Sounds like out the gate, they didn't even get it working right.