Source note · Troubleshooting Teams Direct Routing

Microsoft lists these causes when the SBC gets no 200 OK to its OPTIONS even though TLS and the certificate are valid: the Record-Route or Contact FQDN differs from the FQDN configured in Teams; the Contact header carries an IP address instead of an FQDN; the domain isn't fully validated; or the SBC domain hasn't been activated by adding a licensed user.

Checked 2026-09-25

Vendor: Microsoft
Product: Microsoft Teams Phone Direct Routing
Subsystem: sip-options
Deployment: multi-tenant
Region: not restricted
Release range: current as of 2026-09-25
Checked: 2026-09-25

Sources

SBC connectivity issues — Microsoft · tier 2 current vendor documentation · SIP options issues > SBC doesn't receive a "200 OK" response from SIP proxy

Cite this note

APA

WarmTransfer. (2026, September 25). Troubleshooting Teams Direct Routing: source note teams-direct-routing-troubleshooting-no-200ok-fqdn. WarmTransfer. https://warmtransfer.net/knowledge/claims/teams-direct-routing-troubleshooting-no-200ok-fqdn

BibTeX

@misc{warmtransfer-claim-teams-direct-routing-troubleshooting-no-200ok-fqdn,
  title  = {Troubleshooting Teams Direct Routing: source note teams-direct-routing-troubleshooting-no-200ok-fqdn},
  author = {{WarmTransfer}},
  year   = {2026},
  url    = {https://warmtransfer.net/knowledge/claims/teams-direct-routing-troubleshooting-no-200ok-fqdn},
  note   = {Source note teams-direct-routing-troubleshooting-no-200ok-fqdn, checked 2026-09-25}
}

Read in context