08 · Emergency, LBR, survivability
A laptop moves. The address you shouted at install time does not.
Dynamic emergency calling uses the network Teams can see. In the usual design that means trusted IPs, sites, and subnets tied to validated civic addresses. A dispatchable location is specific enough for responders. One address for five buildings is not.
Trusted IPs mean ‘this client is inside our network.’ If you list the VPN concentrator, every remote user looks internal. Give the VPN pool no dispatchable headquarters address. The same subnet list should later feed location-based routing and CQD, or the three maps will disagree.
Map trusted IPs, subnets, and civic addresses. Do not give VPN users the headquarters address.
Trusted IP, subnet, civic address. The VPN pool is not headquarters.
If it fails: Remote users inherit the HQ floor because the VPN range was trusted as internal.
A colleague reports: The PSAP gets a city and no building. Where do you start?
The PSAP gets a city and no building. Validate the address and tie subnets to places inside it. Source: https://learn.microsoft.com/en-us/microsoftteams/what-are-emergency-locations-addresses-and-call-routing accessed 2026-10-14.
Which description of Trusted IP is accurate?
An address that means ‘this client is inside our network.’ It is how Teams decides the client is on a site you mapped. If the trusted IP is the VPN concentrator, every remote user looks internal. Source: https://learn.microsoft.com/en-us/microsoftteams/what-are-emergency-locations-addresses-and-call-routing accessed 2026-10-14.
A colleague reports: Remote users inherit a building. Where do you start?
Remote users inherit a building. List the real internet egress addresses, not the VPN pool, unless you mean to. 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.
Remote users inherit the HQ floor because the VPN range was trusted as internal.
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.
