08 · Emergency, LBR, survivability
Some countries treat toll bypass as a regulatory problem. Location-based routing is the Teams control.
Location-based routing stops a user in a regulated site from placing or receiving PSTN through a gateway in another site. It uses the same kind of network topology as emergency location. A traveler’s laptop should not egress through another country’s SBC.
Media bypass can fight this if the media path would egress in the wrong place. Read the current LBR article before you enable bypass at a regulated site. Do not invent an exception in a workshop.
Location-based routing stops toll bypass by tying users to local gateways. Check it before you enable media bypass.
LBR keeps PSTN in-country. I will re-read it before I enable media bypass there.
If it fails: A laptop in one country places PSTN through another country’s SBC.
A colleague reports: 999 matches an international route via another country. Where do you start?
999 matches an international route via another country. Build an emergency voice route that prefers the local SBC. Source: https://learn.microsoft.com/en-us/microsoftteams/what-are-emergency-locations-addresses-and-call-routing accessed 2026-10-14.
Which description of Calling Plan emergency is accurate?
With Microsoft Calling Plans in supported countries, Microsoft’s emergency calling service is part of the plan. You still configure locations. Direct Routing habits do not apply unchanged. Source: https://learn.microsoft.com/en-us/microsoftteams/what-are-emergency-locations-addresses-and-call-routing accessed 2026-10-14.
A colleague reports: A Calling Plan user is sent to your SBC for 911 by a copied route. Where do you start?
A Calling Plan user is sent to your SBC for 911 by a copied route. Assign the Calling Plan and the emergency addresses for those users. Source: https://learn.microsoft.com/en-us/microsoftteams/what-are-emergency-locations-addresses-and-call-routing accessed 2026-10-14.
Around the call: compliance recording, workforce management, emergency location, analytics, CRM screen pop, and an agent with a human escape. Each one has its own failure.
A laptop in one country places PSTN through another country’s SBC.
Cisco CUBE is one of the SBC families named in this lab’s certification lesson. A certified release can be the Direct Routing SBC between Unified CM and Teams.
The tenant still needs a verified domain on the SBC FQDN, and the user still needs Teams Phone. The studio translator does not open a live AXL session. Confirm the current certified release before you build.
Teams Phone and Webex Calling are separate clouds. This lab does not describe a feature that registers a Webex Calling user into a Teams tenant.
A number move is usually a carrier port, a certified SBC, or a meetings interop product. Confirm before relying.
Unified CCE stays the ACD until you migrate it. Microsoft’s contact-center articles name Connect, Extend, and Unify. They do not name a UCCE connector in the notes this lab cites.
Voice into Teams is still Direct Routing or Operator Connect. The routing script stays on the contact-center product you bought. Confirm the vendor’s current model. Source: https://learn.microsoft.com/en-us/microsoftteams/teams-contact-center.
Copilot Studio, Azure Communication Services, and Graph are later tracks in this lab. Treat any uncited limit as confirm before relying.
Opened 2026-10. A row marked confirm did not open. Wikipedia is background. The Teams blog row is the community index.
