Source note · Troubleshooting Teams Direct Routing
Microsoft's SBC connectivity troubleshooting article still says that if the SBC doesn't trust the SIP proxy certificate, you should download and install the Baltimore CyberTrust root on the SBC.
disputed · Checked 2026-09-25
- Vendor
- Microsoft
- Product
- Microsoft Teams Phone Direct Routing
- Subsystem
- tls-certificates
- Deployment
- multi-tenant
- Region
- not restricted
- Release range
- as printed in the article as of 2026-09-25
- Status
- disputed
- Checked
- 2026-09-25
Sources
- SBC connectivity issues — Microsoft · tier 2 current vendor documentation · TLS connection issues > SBC doesn't trust SIP proxy certificate
Cite this note
APA
WarmTransfer. (2026, September 25). Troubleshooting Teams Direct Routing: source note teams-direct-routing-troubleshooting-baltimore-advice. WarmTransfer. https://warmtransfer.net/knowledge/claims/teams-direct-routing-troubleshooting-baltimore-advice
BibTeX
@misc{warmtransfer-claim-teams-direct-routing-troubleshooting-baltimore-advice,
title = {Troubleshooting Teams Direct Routing: source note teams-direct-routing-troubleshooting-baltimore-advice},
author = {{WarmTransfer}},
year = {2026},
url = {https://warmtransfer.net/knowledge/claims/teams-direct-routing-troubleshooting-baltimore-advice},
note = {Source note teams-direct-routing-troubleshooting-baltimore-advice, checked 2026-09-25}
}