A Teams user working from home on a network not in the tenant's trusted IPs and without LLDP or BSSID entries will not get an LIS match, so the call relies on user-confirmed, OS-suggested or static addresses, and a static-only address is screened.
inferred · Checked 2026-10-01
- Vendor
- Microsoft
- Product
- Teams Phone
- Subsystem
- Remote worker location
- Deployment
- multi-tenant
- Region
- us
- Release range
- current as of 2026-10-01
- Status
- inferred
- Checked
- 2026-10-01
Sources
- Emergency addresses for remote locations — Microsoft · tier 2 current vendor documentation · Location precedence and Emergency address classification and routing; combined with Configure dynamic emergency calling > Configure network settings
Cite this note
APA
WarmTransfer. (2026, October 1). Troubleshooting 911 calls that route with the wrong location: source note e911-routing-failures-inf-remote-falls-to-static. WarmTransfer. https://warmtransfer.net/knowledge/claims/e911-routing-failures-inf-remote-falls-to-static
BibTeX
@misc{warmtransfer-claim-e911-routing-failures-inf-remote-falls-to-static,
title = {Troubleshooting 911 calls that route with the wrong location: source note e911-routing-failures-inf-remote-falls-to-static},
author = {{WarmTransfer}},
year = {2026},
url = {https://warmtransfer.net/knowledge/claims/e911-routing-failures-inf-remote-falls-to-static},
note = {Source note e911-routing-failures-inf-remote-falls-to-static, checked 2026-10-01}
}