05 · PSTN connectivity
This is the option with the least SBC work and the least control.
You assign the plan, you receive numbers from Microsoft, and emergency calling in supported countries is part of that service. You still configure emergency locations. You do not pair an SBC for those users.
If a Calling Plan user also matches a Direct Routing voice route, you may send their calls onto your SBC by accident. The policy has to match the license.
Calling Plans use Microsoft as the carrier. Keep those users off a Direct Routing policy you did not intend.
Calling Plan users should not inherit a Direct Routing route by accident.
If it fails: 911 for a Calling Plan user is sent to a foreign SBC by a copied policy.
A colleague reports: A UK SBC was proposed as the egress for an India office. Where do you start?
A UK SBC was proposed as the egress for an India office. Use the current India plan article and the licensed operator there. Source: https://learn.microsoft.com/en-us/microsoftteams/operator-connect-plan accessed 2026-10-14.
Which description of Teams Phone Mobile is accurate?
The user’s mobile SIM number is also their Teams number, through a certified mobile operator. Teams Phone is required. It fits frontline and mobile workers, not a reception queue. Source: https://learn.microsoft.com/en-us/microsoftteams/teams-phone-mobile-plan accessed 2026-10-14.
A colleague reports: One human has two different caller IDs and the CRM matches neither. Where do you start?
One human has two different caller IDs and the CRM matches neither. Assign the operator number to the user. Do not also treat it as a spare Calling Plan. Source: https://learn.microsoft.com/en-us/microsoftteams/teams-phone-mobile-plan 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.
911 for a Calling Plan user is sent to a foreign SBC by a copied policy.
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.
