Source note · SIP TLS handshake failures on trunks
After an SBC certificate is renewed, TLS connections set up with the old certificate must be torn down and re-established, for example by restarting the SBC in a maintenance window; otherwise the Teams admin center keeps raising certificate expiry warnings.
Checked 2026-09-25
- Vendor
- Microsoft
- Product
- Teams Phone Direct Routing
- Subsystem
- certificate lifecycle
- 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 is invalid, second paragraph
Cite this note
APA
WarmTransfer. (2026, September 25). SIP TLS handshake failures on trunks: source note sip-tls-handshake-failures-dr-renewal-old-sessions. WarmTransfer. https://warmtransfer.net/knowledge/claims/sip-tls-handshake-failures-dr-renewal-old-sessions
BibTeX
@misc{warmtransfer-claim-sip-tls-handshake-failures-dr-renewal-old-sessions,
title = {SIP TLS handshake failures on trunks: source note sip-tls-handshake-failures-dr-renewal-old-sessions},
author = {{WarmTransfer}},
year = {2026},
url = {https://warmtransfer.net/knowledge/claims/sip-tls-handshake-failures-dr-renewal-old-sessions},
note = {Source note sip-tls-handshake-failures-dr-renewal-old-sessions, checked 2026-09-25}
}