Source record · tier 2 current vendor documentation

Considerations for Direct Routing

Publisher: Microsoft
URL: https://learn.microsoft.com/en-us/microsoftteams/considerations-direct-routing
Published: 2026-09-10
Updated: unknown
Accessed: 2026-09-24
HTTP status: 200
License: Microsoft Learn terms of use; no-redistribution; short excerpts and locators only

Source notes citing this source

Outside the US and Canada, the documented Teams Direct Routing (ELIN) and Zoom Phone mechanisms both deliver caller location through the calling number and a carrier or national address-of-record lookup, not through PIDF-LO in the SIP signalling. inferred in context
For Teams Direct Routing users, Microsoft documents dynamic location for routing emergency calls in the United States, and in Canada with the same behaviour except that all calls are screened nationally before transfer to the PSAP. in context
With an SBC ELIN application under Teams Direct Routing, the SBC matches the caller's dynamic emergency location to an ELIN record, replaces the caller's number with the ELIN, and routes the call to the PSAP, which gets the location from the ELIN record uploaded to the PSTN emergency database. On a callback to the ELIN, the application reverses the substitution. in context
Under Teams Direct Routing, a Teams client that cannot obtain an emergency call routing policy from either its network site or the user account is not enabled for emergency calling. in context
Microsoft lists two ways to dynamically route Direct Routing emergency calls: Emergency Routing Service Providers and ELIN applications on the Session Border Controller. in context
Microsoft's Direct Routing considerations page labels Emergency Routing Service Providers as a US-only solution. disputed in context
For Direct Routing in Canada, dynamic emergency location works as in the US except that all emergency calls are screened nationally before being transferred to the PSAP. in context
With an SBC ELIN application, the SBC matches the caller's location to an ELIN record, replaces the caller's number with the ELIN, and routes to the PSAP. The ELIN records must be uploaded to the PSTN emergency database, and callbacks are reverse-substituted. in context
With an Emergency Routing Service Provider integrated into Direct Routing, calls with a dynamically acquired location route automatically to the PSAP for that location, and calls without one are first screened to confirm the caller's location. in context
Microsoft names two ways to route Direct Routing emergency calls dynamically: Emergency Routing Service Providers, which are US only, and SBC-based ELIN applications. in context
Teams clients no longer prepend '+' to emergency numbers, so Direct Routing voice routes toward an emergency provider must match 911 rather than +911. in context
For Direct Routing users, dynamic location for routing emergency calls is supported only in the United States, and in Canada with all calls screened nationally before transfer to the PSAP. in context
For Direct Routing, emergency numbers and their routing are defined in a Teams emergency call routing policy, which can be assigned to a user, a network site or both, and the site policy takes precedence when the client is at a site that has one. in context
The Direct Routing emergency call routing policy references an online PSTN usage, and there must be an online voice route for the emergency dial string. in context
If the Teams client cannot obtain an emergency call routing policy, the Direct Routing user is not enabled for emergency calling. in context
Teams clients no longer prepend a plus sign to emergency numbers, so Direct Routing voice route patterns must match 911 without a leading plus. in context
If a US Direct Routing user's Teams client does not dynamically acquire a US emergency address, the registered emergency address is used and the call is screened to determine whether an updated address is needed before connecting to a PSAP. in context
For Direct Routing, dynamic location for routing emergency calls is supported in the United States, and in Canada in the same way except that all emergency calls are screened nationally before transfer to the PSAP. in context
For Direct Routing, a client uses the site's emergency call routing policy; it falls back to the user's policy if the site has none, the site is undefined, or the dialed number matches none of the site policy's emergency numbers; if no policy is obtained the user is not enabled for emergency calling. in context
With an SBC ELIN application, the emergency addresses and associated telephone numbers are configured in the ELIN application and the ELIN records uploaded to the emergency calling database of the respective PSTN, and Teams emergency locations carrying an ELIN identifier must match those in the ELIN application. in context
On an emergency call with a dynamic location, the SBC ELIN application matches the location to an ELIN record, substitutes the caller's number with the ELIN number and routes to the serving PSAP; on a call-back to the ELIN it reverses the substitution to reach the original caller. in context
With an Emergency Routing Service Provider integrated into Direct Routing, emergency calls carrying a dynamically acquired location are routed automatically to the serving PSAP, and calls without one are first screened to determine the caller's current location. in context
The emergency call routing policy references an online PSTN usage that must have Direct Routing configuration to reach the right PSTN gateways, and in particular there must be an OnlineVoiceRoute for the emergency dial string. in context
Microsoft's two pages disagree on where Direct Routing Emergency Routing Service Providers apply: the configuration page says the United States and Canada, while the Direct Routing considerations page labels them US only. disputed in context
For Direct Routing, Teams clients no longer send emergency calls with a '+' before the emergency dial string (for example +911), so voice route patterns for emergency numbers must match without the '+'. in context
The Direct Routing emergency call routing policy references an online PSTN usage, and there must be an OnlineVoiceRoute for the emergency dial string that reaches the right PSTN gateways. in context
For Direct Routing, Teams uses the network site's emergency call routing policy if one exists; it falls back to the user's policy if the site has none, the client is at an undefined site, or the dialed number matches none of the site policy's emergency numbers; if no policy can be obtained, the user is not enabled for emergency calling. in context
With an SBC ELIN application, emergency addresses and ELIN numbers are configured in the application and uploaded to the PSTN emergency database; on an emergency call the application matches the caller's location to an ELIN record, substitutes the ELIN as the calling number, and reverses the substitution when the PSAP calls back. in context
The Direct Routing considerations page lists Emergency Routing Service Providers as a United States-only option for dynamically routing Direct Routing emergency calls, with ELIN applications as the other option. disputed in context
Teams clients no longer put a '+' in front of emergency numbers (for example +911) on Direct Routing, so voice route patterns for emergency dial strings must match the number without '+'. in context

Cite this source record

APA

WarmTransfer. (2026, September 10). Considerations for Direct Routing. WarmTransfer. https://warmtransfer.net/knowledge/sources/ms-learn-emergency-considerations-direct-routing

BibTeX

@misc{warmtransfer-ms-learn-emergency-considerations-direct-routing,
  title  = {Considerations for Direct Routing},
  author = {{WarmTransfer}},
  year   = {2026},
  url    = {https://warmtransfer.net/knowledge/sources/ms-learn-emergency-considerations-direct-routing},
  note   = {Microsoft, accessed 2026-09-24}
}