Source note · One SBC serving several calling platforms
On an inbound INVITE, the Teams Direct Routing proxy finds the destination tenant from the FQDN in the Contact header (full FQDN first, then the FQDN without its host part), and that FQDN must match the certificate CN or SAN.
Checked 2026-10-14
- Vendor
- Microsoft
- Product
- Teams Phone
- Subsystem
- Direct Routing
- Deployment
- multi-tenant
- Region
- not restricted
- Release range
- current as of 2026-10-14
- Checked
- 2026-10-14
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, October 14). One SBC serving several calling platforms: source note multi-platform-sbc-design-teams-contact-fqdn-tenant. WarmTransfer. https://warmtransfer.net/knowledge/claims/multi-platform-sbc-design-teams-contact-fqdn-tenant
BibTeX
@misc{warmtransfer-claim-multi-platform-sbc-design-teams-contact-fqdn-tenant,
title = {One SBC serving several calling platforms: source note multi-platform-sbc-design-teams-contact-fqdn-tenant},
author = {{WarmTransfer}},
year = {2026},
url = {https://warmtransfer.net/knowledge/claims/multi-platform-sbc-design-teams-contact-fqdn-tenant},
note = {Source note multi-platform-sbc-design-teams-contact-fqdn-tenant, checked 2026-10-14}
}