08 · Emergency, LBR, survivability
The client is Teams in both designs. The carrier is not.
On Calling Plans, Microsoft’s emergency calling path is in play in supported countries, and your job is accurate locations. On Direct Routing, the emergency voice route must prefer the local SBC, and the carrier must accept the call. PIDF-LO can ride in the INVITE. If the SBC strips it, the far end may only see the trunk.
An emergency calling policy controls notification and lookup. It is not a substitute for the route. On-site security who are not notified will meet responders at the wrong door.
Say who routes the emergency call. Microsoft’s path for Calling Plans, your SBC and carrier for Direct Routing.
Calling Plan emergency and Direct Routing emergency are different owners. I will not copy one route onto the other.
If it fails: A Calling Plan user’s 911 is forced out a foreign SBC.
Which description of Emergency calling policy is accurate?
Controls notification and how the client looks up location. It is not the PSTN route. You can have a perfect policy and still send the call to the wrong SBC. Source: https://learn.microsoft.com/en-us/microsoftteams/what-are-emergency-locations-addresses-and-call-routing accessed 2026-10-14.
A colleague reports: Security is notified for a test call and the route still left the country. Where do you start?
Security is notified for a test call and the route still left the country. Pair the policy with a routing policy and a tested number from the carrier. Source: https://learn.microsoft.com/en-us/microsoftteams/what-are-emergency-locations-addresses-and-call-routing accessed 2026-10-14.
Which description of Direct Routing emergency is accurate?
You, the SBC, and the carrier deliver the emergency call. Microsoft does not become the emergency carrier because Teams is the client. PIDF-LO may be present. The carrier still has to accept the call. 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 Calling Plan user’s 911 is forced out a foreign 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.
