10 · Session border controllers
Oracle’s session border controller is a Direct Routing option only on the releases Microsoft lists.
Check the certified list for the Oracle software version, not the product family name. An unlisted release is an unsupported trunk no matter how complete the configuration looks.
Certificate name, TLS version, and early offer still apply. Oracle’s configuration model is its own language. Translate the shared gate into that language using their current guide.
Oracle SBCs count only when that release is on Microsoft’s certified list.
I match the Oracle release to the certified list before I praise the config.
If it fails: The config is one release below the list and Microsoft declines the case.
A colleague reports: A voice engineer applies a SIP trunk to CUCM and never peers with the pstnhub names. Where do you start?
A voice engineer applies a SIP trunk to CUCM and never peers with the pstnhub names. Use Cisco’s current CUBE for Teams guide. Trust the signaling ranges. Present the paired name. Source: https://www.cisco.com/c/en/us/products/unified-communications/unified-border-element/index.html accessed 2026-10-14.
Which description of Vendor-first support is accurate?
Microsoft’s Direct Routing support boundary: you call the SBC vendor, they escalate to Microsoft if they must. Non-certified SBCs can be refused. Opening a Microsoft case with a homemade SBC wastes the outage. Source: https://learn.microsoft.com/en-us/microsoftteams/direct-routing-border-controllers accessed 2026-10-14.
A colleague reports: A ticket is opened with no SBC logs and no firmware. Where do you start?
A ticket is opened with no SBC logs and no firmware. Keep the certified-list screenshot with the firmware version. Source: https://learn.microsoft.com/en-us/microsoftteams/direct-routing-border-controllers 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.
The config is one release below the list and Microsoft declines the case.
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.
