Source note · Troubleshooting Teams Direct Routing
A TLS connection that drops or never forms, even though certificates and SBC settings are fine, may be closed by a device in the path such as a firewall or router. Microsoft points to the customer-managed network as the place to fix it.
Checked 2026-09-25
- Vendor
- Microsoft
- Product
- Microsoft Teams Phone Direct Routing
- Subsystem
- tls
- 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 connection is interrupted
Cite this note
APA
WarmTransfer. (2026, September 25). Troubleshooting Teams Direct Routing: source note teams-direct-routing-troubleshooting-midbox-tls-close. WarmTransfer. https://warmtransfer.net/knowledge/claims/teams-direct-routing-troubleshooting-midbox-tls-close
BibTeX
@misc{warmtransfer-claim-teams-direct-routing-troubleshooting-midbox-tls-close,
title = {Troubleshooting Teams Direct Routing: source note teams-direct-routing-troubleshooting-midbox-tls-close},
author = {{WarmTransfer}},
year = {2026},
url = {https://warmtransfer.net/knowledge/claims/teams-direct-routing-troubleshooting-midbox-tls-close},
note = {Source note teams-direct-routing-troubleshooting-midbox-tls-close, checked 2026-09-25}
}