Voice LabTeams Phone

17 · Ecosystem

E911 as a system of record

Location is data you operate, shared with routing and with quality maps.

Room HTMLAll downloads

Learn it in 5 minutes

Keep one subnet list. Emergency location, location-based routing, and the CQD building map should read it. Three spreadsheets will drift, and then E911 says London, CQD says VPN, and LBR says Manchester.

Configuration is the topology plus the emergency policy plus the route plus the carrier test. Troubleshooting starts with ‘which subnet did the client present,’ not with the SBC firmware. PIDF-LO only helps if the SBC and the carrier pass it on. Notification only helps if the policy is assigned.

Treat emergency location as a system of record shared with LBR and CQD. One subnet list.

Room HTML

Visual

Survivable branch timelineBranch clientsSBA and SBCMicrosoft 365WAN up. Cloud is the path.Meetings and presence are not the survivable set.
What remains when the path to Microsoft 365 drops. Lesson: E911 as a system of record.
One list, three consumersE911 · ConsumerLBR · ConsumerCQD · Consumer
Shared data. Counts in this drawing are teaching order, not customers.

SVGPNGHTML

Worked example

One subnet list feeds emergency location, LBR, and CQD. I can say which consumer is wrong when they disagree.

  1. List One subnet source
  2. LIS Addresses
  3. Route Local
  4. Test Carrier process
  5. Maps CQD uses the same list

If it fails: Three teams edit three maps and a VPN user inherits the HQ address.

Checklist HTML

Quiz

A colleague reports: A site celebrates 95 percent occupancy and abandonment climbs. Where do you start?

Which description of Service level is accurate?

A colleague reports: Two vendors compute abandoned calls differently and both claim the target. Where do you start?

Flashcards

Ecosystem

Glossary

  • Convenience recording A user starts a recording of a call, meeting, or event. Policy can allow it. The user can stop it. Storage follows meeting rules. Config: Set the meeting, calling, and events policies on purpose. Fault: A regulated desk is told to ‘just hit record.’
  • Compliance recording A third-party recorder is invited by policy into new calls, meetings, and events. The user does not start it and participant consent is not the control. Notification is enforced. Config: Create the application instance, enable the policy, grant it, and test a new call. Fault: The policy is granted and nothing records because the bot instance was never created.
  • Compliance recording application The bot instance of a certified recorder. The policy references it. Without it, granting the policy does not record. Config: New-CsTeamsComplianceRecordingApplication attaches it to the policy. Fault: Recording works in the vendor’s cloud and never joins the Teams call.
  • Existing calls are unaffected When you grant a compliance recording policy, calls and meetings already up are not swept in. Test with a new call. Config: Place a fresh call after the grant and confirm the bot joined. Fault: The pilot says recording failed because they watched an old meeting.

Sister technologies

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.

Config and troubleshooting

Three teams edit three maps and a VPN user inherits the HQ address.

Cross-platform bridges

CUCM

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.

Webex

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.

UCCE

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.

Future hooks

Copilot Studio, Azure Communication Services, and Graph are later tracks in this lab. Treat any uncited limit as confirm before relying.

BridgesEcosystem

Sources and go deeper

Opened 2026-10. A row marked confirm did not open. Wikipedia is background. The Teams blog row is the community index.

sources.json