08 · Emergency, LBR, survivability
Responders at the wrong door, and a test that called the real emergency service, are both failures.
Assign the emergency calling policy that notifies the people who can meet responders. Test the notification. A policy that exists and is not assigned notifies nobody.
Use the carrier’s test number or process. Do not dial the real emergency number from a lab because you were curious. Record the result: location shown, SBC used, who was notified.
Assign the notification policy and test emergency calling with the carrier’s process, not a real emergency call.
I test emergency with the carrier’s process and I check that on-site notification fired.
If it fails: The notification policy exists and is assigned to nobody.
A colleague reports: The office loses the WAN and nobody can call emergency services. Where do you start?
The office loses the WAN and nobody can call emergency services. Deploy a supported appliance, point the local clients at it, and test a WAN cut. Source: https://learn.microsoft.com/en-us/microsoftteams/direct-routing-survivable-branch-appliance accessed 2026-10-14.
Which description of PIDF-LO is accurate?
A location object that can be carried in a SIP INVITE for an emergency call so the far end sees where the caller is. It does not replace a carrier who knows how to route emergency calls in that country. Source: https://learn.microsoft.com/en-us/microsoftteams/what-are-emergency-locations-addresses-and-call-routing accessed 2026-10-14.
A colleague reports: The location is stripped at the SBC and the PSAP gets the trunk’s address only. Where do you start?
The location is stripped at the SBC and the PSAP gets the trunk’s address only. Confirm the SBC passes it and the carrier reads it. 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.
The notification policy exists and is assigned to nobody.
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.
