Source note · Setting up CUBE as a Microsoft Teams Direct Routing SBC

Direct Routing matches the FQDN in the Contact header against the certificate's CN or SAN (wildcards allowed) and then uses that FQDN, or its parent domain, to find the tenant; a mismatch fails the call.

Checked 2026-09-30

Vendor: Microsoft
Product: Microsoft Teams Phone
Subsystem: Direct Routing SIP
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; Use of FQDN name in Contact or Record-Route

Cite this note

APA

WarmTransfer. (2026, September 30). Setting up CUBE as a Microsoft Teams Direct Routing SBC: source note cube-teams-direct-routing-setup-contact-cert-match. WarmTransfer. https://warmtransfer.net/knowledge/claims/cube-teams-direct-routing-setup-contact-cert-match

BibTeX

@misc{warmtransfer-claim-cube-teams-direct-routing-setup-contact-cert-match,
  title  = {Setting up CUBE as a Microsoft Teams Direct Routing SBC: source note cube-teams-direct-routing-setup-contact-cert-match},
  author = {{WarmTransfer}},
  year   = {2026},
  url    = {https://warmtransfer.net/knowledge/claims/cube-teams-direct-routing-setup-contact-cert-match},
  note   = {Source note cube-teams-direct-routing-setup-contact-cert-match, checked 2026-09-30}
}

Read in context