09 · Devices and media
A bargain SIP phone is not a Teams client. The certified list is the product boundary.
Teams-certified phones sign in as Teams users and use the Teams media stack. SIP Gateway covers a smaller set of compatible SIP and analog devices, with a smaller feature list. Check the current list before you buy.
QoS for phones follows the same DSCP story, with device-specific notes in the rooms and devices articles. A phone that never registers is often identity or Conditional Access, not a codec.
Use Teams-certified phones or the SIP Gateway device list. Do not invent a third category.
I buy from the current certified list, or I use SIP Gateway for the devices it actually supports.
If it fails: A generic SIP phone is forced into the design and never registers.
Which description of Teams Rooms license is accurate?
Rooms use their own SKU family, not a borrowed user Calling Plan. Names such as Basic and Pro change. Check the current name. A room that cannot join is often a license or a resource account, not a codec. Source: https://learn.microsoft.com/en-us/microsoftteams/teams-phone-licensing accessed 2026-10-14.
A colleague reports: The room account has a user E5 stack and still fails sign-in policy. Where do you start?
The room account has a user E5 stack and still fails sign-in policy. Assign the current room license to the room account and keep Conditional Access from blocking the device. Source: https://learn.microsoft.com/en-us/microsoftteams/teams-phone-licensing accessed 2026-10-14.
Which description of Media bypass is accurate?
Media can flow between the Teams client and the SBC, skipping Microsoft’s media processors. Signaling still goes through Teams. People hear ‘bypass’ and think the SBC talks to Teams with no SIP proxy. Source: https://learn.microsoft.com/en-us/microsoftteams/direct-routing-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.
A generic SIP phone is forced into the design and never registers.
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.
