10 · Session border controllers
Ribbon Core and software editions differ. The brand is not the release.
Ribbon SBCs are a normal Direct Routing choice when the edition and release are certified. Answer OPTIONS on the interface Teams will actually reach. A 200 on the management port does not count.
Same support rule: Ribbon first. Bring their show-tech equivalent and a SIP ladder with the Call-ID.
For Ribbon, match the certified edition and answer OPTIONS on the signaling interface.
I confirm the Ribbon release and the interface that answers OPTIONS.
If it fails: OPTIONS are answered on the wrong interface, so Teams marks the trunk down.
Which description of Oracle SBC is accurate?
Oracle Communications Session Border Controller can be certified for Direct Routing on specific releases. Check the Microsoft list for the release, not the logo. An unlisted release is an unsupported trunk. Source: https://www.oracle.com/communications/session-border-controller/ accessed 2026-10-14.
A colleague reports: The beautiful config is one release below the certified list. Where do you start?
The beautiful config is one release below the certified list. Match the certified software version and the certificate name. Source: https://www.oracle.com/communications/session-border-controller/ accessed 2026-10-14.
Which description of Cisco CUBE is accurate?
Cisco Unified Border Element on IOS-XE, when the release is certified, is a normal Direct Routing SBC and the usual bridge to CUCM. CUBE is still an SBC. It does not make Teams ‘speak SCCP.’ Source: https://www.cisco.com/c/en/us/products/unified-communications/unified-border-element/index.html 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.
OPTIONS are answered on the wrong interface, so Teams marks the trunk down.
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.
