06 · Routing and dial plans
The route is a regular expression plus an ordered list of SBCs. CUCM wildcards will not work here.
Anchor the pattern to the normalized number. List gateways with priorities. In this campus, priority 1 is tried first. Confirm the current article before you depend on a production tie-break. A second gateway that has never carried a call is a drawing.
Unassigned numbers you own should be treated on purpose, usually toward an attendant. A ported block with fifty silent numbers looks like an outage.
A voice route matches the normalized number and tries gateways in priority order. Rehearse the second one.
The voice route is a regex and a gateway list. I rehearse failover.
If it fails: Both SBCs are priority 1 and nobody knows which one took the call.
A colleague reports: The pilot user is still on the global policy, which has no usages. Where do you start?
The pilot user is still on the global policy, which has no usages. Grant it to a test user and read it back with Get-CsOnlineUser. Source: https://learn.microsoft.com/en-us/microsoftteams/manage-voice-routing-policies accessed 2026-10-14.
Which description of Gateway priority is accurate?
Each voice route lists SBCs with a priority. Lower priority number is tried first in this campus’s teaching model. Confirm the current article before you depend on a tie. Failover is a list, not a wish. Source: https://learn.microsoft.com/en-us/microsoftteams/manage-voice-routing-policies accessed 2026-10-14.
A colleague reports: Both gateways are priority 1 and nobody knows which one took the call. Where do you start?
Both gateways are priority 1 and nobody knows which one took the call. Put the local SBC first and a remote SBC second, then pull the cable in a maintenance window. Source: https://learn.microsoft.com/en-us/microsoftteams/manage-voice-routing-policies 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.
Both SBCs are priority 1 and nobody knows which one took the call.
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.
