06 · Routing and dial plans
One concrete walk is worth a page of definitions.
A London user dials a UK national number. Their dial plan emits +44. Their policy lists emergency, then UK national, then international. The UK route matches +44 and prefers sbc-lon, with sbc-man as priority 2. A Manchester-only policy has no international usage, so a US number fails closed.
An emergency 999 hits a rule that rewrites it to the emergency route, not to an extension and not to the international gateway. If you cannot tell that story with your own site names, you are not ready to change production.
Walk a number: dial plan, then usages in order, then the route, then the gateway priority.
I can walk one number through normalize, usage, route, and gateway.
If it fails: 999 matches an international route via another country.
Which description of Emergency short code is accurate?
999, 112, and 911 must be normalized on purpose. A general rule that runs first can swallow them. An emergency call that matches an international route is a design defect. Source: https://learn.microsoft.com/en-us/microsoftteams/what-are-emergency-locations-addresses-and-call-routing accessed 2026-10-14.
A colleague reports: A user dials 999 and the dial plan turns it into an extension. Where do you start?
A user dials 999 and the dial plan turns it into an extension. Put emergency rules above catch-alls, and give them a route that is always present. Source: https://learn.microsoft.com/en-us/microsoftteams/what-are-emergency-locations-addresses-and-call-routing accessed 2026-10-14.
Which description of E.164 is accurate?
The international form of a number, starting with + and a country code. Routes and CRM lookups should use it after normalization. Raw digits mean different things in different countries. Source: https://learn.microsoft.com/en-us/microsoftteams/create-and-manage-dial-plans 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.
999 matches an international route via another country.
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.
