05 · PSTN connectivity

Teams Phone Mobile

The SIM number and the Teams number are the same number. That is a gift for frontline staff and a trap for a reception queue.

Room HTMLAll downloads

Learn it in 5 minutes

Teams Phone Mobile uses a certified mobile operator. The user’s SIM number is assigned as their Teams number. They need Teams Phone. They do not need a separate Calling Plan for that path.

Do not put the main queue on someone’s SIM. When that person leaves, the number leaves. CRM matching also fails if the same human presents two caller IDs.

Teams Phone Mobile is for people with a SIM, not for the company’s main queue.

Room HTML

Visual

Media bypass beside the signaling pathTeams clientMedia processorCertified SBCMedia bypass candidate, same site. Signaling still visits Teams.Signaling does not bypass
Two paths for Teams Phone Mobile. RTP may skip the processor. SIP does not.
Good fitFrontline user · Good fitReception queue · Wrong tool
Qualitative fit, not a survey. Counts in this drawing are teaching order, not customers.

SVGPNGHTML

Worked example

Teams Phone Mobile makes the SIM number the Teams number. I would not put a queue on it.

  1. Operator Certified mobile
  2. SIM Becomes the Teams number
  3. User Frontline
  4. Not The main queue

If it fails: One person has two caller IDs and the CRM matches neither.

Checklist HTML

Quiz

A colleague reports: A mobile user matches a Direct Routing route and hairpins. Where do you start?

Which description of SIP proxies is accurate?

A colleague reports: A lockdown allows only today’s DNS answer and the trunk fails next week. Where do you start?

Flashcards

Ecosystem

Glossary

  • Operator Connect A certified carrier manages PSTN for you inside the tenant. You need Teams Phone. You do not need a Microsoft Calling Plan or your own SBC. Config: Enable the operator in the admin center and assign the numbers they provide. Fault: Someone also builds a Direct Routing SBC for the same numbers and the routes fight.
  • Operator Connect for India The India-specific operator model. It exists because India PSTN rules are not the same as a generic Operator Connect deployment. Config: Use the current India plan article and the licensed operator there. Fault: A UK SBC was proposed as the egress for an India office.
  • Teams Phone Mobile The user’s mobile SIM number is also their Teams number, through a certified mobile operator. Teams Phone is required. Config: Assign the operator number to the user. Do not also treat it as a spare Calling Plan. Fault: One human has two different caller IDs and the CRM matches neither.
  • Direct Routing You connect a certified SBC to Teams and bring your own carrier. Users need Teams and Teams Phone. They must be homed online. Islands mode is not supported. Config: Pair the FQDN, open 5061, allow media ranges, assign a voice route. Fault: The SBC is up and the user has no voice routing policy.

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

One person has two caller IDs and the CRM matches neither.

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.

  • Plan Teams Phone Mobile — confirm — last checked 2026-10. Did not open when checked. HTTP 404.
  • Plan for Teams Phone Mobile - Microsoft Teams | Microsoft Learn — Microsoft Learn — last checked 2026-10. Opened in place of a page that did not open when checked. This is the page that opened, not proof it equals the old slug
  • RFC 3261 — RFC — last checked 2026-10.
  • Public switched telephone network — Wikipedia — last checked 2026-10. Wikipedia fallback for background. Confirm the vendor page before you change a tenant
  • Session Initiation Protocol — Wikipedia — last checked 2026-10. Wikipedia fallback for background. Confirm the vendor page before you change a tenant
  • Microsoft Teams blog index — Community — last checked 2026-10. Community index for the Microsoft Teams blog. This is the index, not a claim that a post discusses this room

sources.json