Source note · Troubleshooting Teams Direct Routing
Sometimes the SBC certificate or required intermediates are missing from the SBC's TLS Hello even though the configuration looks correct. Microsoft notes that a packet capture can show the certificate isn't actually being presented to Teams.
Checked 2026-09-25
- Vendor
- Microsoft
- Product
- Microsoft Teams Phone Direct Routing
- Subsystem
- tls-certificates
- 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 · TLS connection issues > SBC certificate or intermediary certificates are missing in the SBC TLS "Hello" message
Cite this note
APA
WarmTransfer. (2026, September 25). Troubleshooting Teams Direct Routing: source note teams-direct-routing-troubleshooting-hello-missing-cert. WarmTransfer. https://warmtransfer.net/knowledge/claims/teams-direct-routing-troubleshooting-hello-missing-cert
BibTeX
@misc{warmtransfer-claim-teams-direct-routing-troubleshooting-hello-missing-cert,
title = {Troubleshooting Teams Direct Routing: source note teams-direct-routing-troubleshooting-hello-missing-cert},
author = {{WarmTransfer}},
year = {2026},
url = {https://warmtransfer.net/knowledge/claims/teams-direct-routing-troubleshooting-hello-missing-cert},
note = {Source note teams-direct-routing-troubleshooting-hello-missing-cert, checked 2026-09-25}
}