Source note · Setting up an Oracle SBC for Teams Direct Routing
The SIP proxy matches the Contact FQDN against the SBC certificate CN/SAN (exact or wildcard), then finds the tenant by looking up the full Contact FQDN as a registered domain and, failing that, the FQDN with its host portion removed; if neither is found the call fails.
Checked 2026-09-30
- Vendor
- Microsoft
- Product
- Microsoft Teams Phone Direct Routing
- Subsystem
- SIP headers
- Deployment
- multi-tenant
- Region
- not restricted
- Release range
- current as of 2026-09-30
- Checked
- 2026-09-30
Sources
- Teams Phone System Direct Routing: SIP protocol — Microsoft · tier 2 current vendor documentation · Processing the incoming request: finding the tenant and user, steps 1-3
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-contact-cert-match. WarmTransfer. https://warmtransfer.net/knowledge/claims/oracle-sbc-teams-direct-routing-setup-contact-cert-match
BibTeX
@misc{warmtransfer-claim-oracle-sbc-teams-direct-routing-setup-contact-cert-match,
title = {Setting up an Oracle SBC for Teams Direct Routing: source note oracle-sbc-teams-direct-routing-setup-contact-cert-match},
author = {{WarmTransfer}},
year = {2026},
url = {https://warmtransfer.net/knowledge/claims/oracle-sbc-teams-direct-routing-setup-contact-cert-match},
note = {Source note oracle-sbc-teams-direct-routing-setup-contact-cert-match, checked 2026-09-30}
}