Source note · Setting up an Oracle SBC for Teams Direct Routing
In the current carrier model, the carrier creates one carrier trunk in its own tenant with New-CSOnlinePSTNGateway; customer tenants add the derived trunk FQDN (for example customer.sbc1.base) to voice routes without registering it, derived trunks inherit all carrier-trunk settings including media bypass and port, OPTIONS go only to the carrier trunk FQDN, and the carrier must publish DNS resolving each derived FQDN to the SBC.
Checked 2026-09-30
- Vendor
- Microsoft
- Product
- Microsoft Teams Phone Direct Routing
- Subsystem
- Multi-tenant hosting
- Deployment
- multi-tenant
- Region
- not restricted
- Release range
- current as of 2026-09-30
- Checked
- 2026-09-30
Sources
- Configure a Session Border Controller for multiple tenants — Microsoft · tier 2 current vendor documentation · Create a trunk and provision users; Provisioning logic and example
Cite this note
APA
WarmTransfer. (2026, September 30). Setting up an Oracle SBC for Teams Direct Routing: source note oracle-sbc-teams-direct-routing-setup-carrier-trunk. WarmTransfer. https://warmtransfer.net/knowledge/claims/oracle-sbc-teams-direct-routing-setup-carrier-trunk
BibTeX
@misc{warmtransfer-claim-oracle-sbc-teams-direct-routing-setup-carrier-trunk,
title = {Setting up an Oracle SBC for Teams Direct Routing: source note oracle-sbc-teams-direct-routing-setup-carrier-trunk},
author = {{WarmTransfer}},
year = {2026},
url = {https://warmtransfer.net/knowledge/claims/oracle-sbc-teams-direct-routing-setup-carrier-trunk},
note = {Source note oracle-sbc-teams-direct-routing-setup-carrier-trunk, checked 2026-09-30}
}