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 .....
- Assign a subnet to that civic address
Set-CsOnlineLisSubnet -Subnet 1.2.3.0 -LocationId $civAddress.DefaultLocationId
- Add a location for a room at that civic address
$loc = New-CsOnlineLisLocation -CivicAddressId $civAddress.CivicAddressId -Location 'Boardroom'
- Assign a port to that location using LLDP information from the switch
Set-CsOnlineLisPort -LocationId $loc.LocationId -PortId 'Gi-0/0/14' -ChassisId 'AA-BB-CC-DD-EE-FF-'
- Plug in physical phone device (such as any of the ones listed above)
- Dial 911 (or 933 if you have testing setup)
- Observe phone pulls the location up for the Civic Address, and PIDF-LO data sent to the 911/933 operator (such as Intrado) is the Civic Address only.
- Unplug physical device, and plug in laptop
- Dial 911 (or 933 if you have testing setup)
- Observe Teams client address shows the room information you defined earlier, and PIDF-LO data also includes that room data
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?
Thanks
