A Windows client with a stateful DHCPv6 address can report a /128 prefix, so Teams LIS computes the full address as the network ID and does not match a /64 LIS subnet entry.
Checked 2026-10-01
- Vendor
- Microsoft
- Product
- Teams Phone
- Subsystem
- LIS subnet matching (IPv6)
- Deployment
- multi-tenant
- Region
- not restricted
- Release range
- current as of 2026-10-01
- Checked
- 2026-10-01
Sources
- Configure dynamic emergency calling — Microsoft · tier 2 current vendor documentation · Configure Location Information Service > IPv6 subnet matching
Cite this note
APA
WarmTransfer. (2026, October 1). Troubleshooting 911 calls that route with the wrong location: source note e911-routing-failures-teams-ipv6-128-mismatch. WarmTransfer. https://warmtransfer.net/knowledge/claims/e911-routing-failures-teams-ipv6-128-mismatch
BibTeX
@misc{warmtransfer-claim-e911-routing-failures-teams-ipv6-128-mismatch,
title = {Troubleshooting 911 calls that route with the wrong location: source note e911-routing-failures-teams-ipv6-128-mismatch},
author = {{WarmTransfer}},
year = {2026},
url = {https://warmtransfer.net/knowledge/claims/e911-routing-failures-teams-ipv6-128-mismatch},
note = {Source note e911-routing-failures-teams-ipv6-128-mismatch, checked 2026-10-01}
}