Teams LIS subnet matching calculates a network ID from the client IP and client-reported prefix length, and that network ID must equal a subnet configured in LIS (for example 10.10.10.150/25 yields 10.10.10.128).
Checked 2026-10-01
- Vendor
- Microsoft
- Product
- Teams Phone
- Subsystem
- LIS subnet matching
- 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 dynamic emergency calling > Configure network settings, Note on LIS subnets
Cite this note
APA
WarmTransfer. (2026, October 1). Troubleshooting 911 calls that route with the wrong location: source note e911-routing-failures-teams-lis-subnet-network-id. WarmTransfer. https://warmtransfer.net/knowledge/claims/e911-routing-failures-teams-lis-subnet-network-id
BibTeX
@misc{warmtransfer-claim-e911-routing-failures-teams-lis-subnet-network-id,
title = {Troubleshooting 911 calls that route with the wrong location: source note e911-routing-failures-teams-lis-subnet-network-id},
author = {{WarmTransfer}},
year = {2026},
url = {https://warmtransfer.net/knowledge/claims/e911-routing-failures-teams-lis-subnet-network-id},
note = {Source note e911-routing-failures-teams-lis-subnet-network-id, checked 2026-10-01}
}