Zoom's mTLS for BYOC-P does not validate peer names: certificates are exchanged in the handshake, but Zoom does not check the SBC certificate CN or SAN against an expected hostname or FQDN.
Checked 2026-10-02
Zoom's mTLS implementation does not include peer name validation for customer SBC connections.
- Vendor
- Zoom
- Product
- Zoom Phone
- Subsystem
- BYOC-P trunk
- Deployment
- multi-tenant
- Region
- not restricted
- Release range
- current as of 2026-10-02
- Checked
- 2026-10-02
Sources
- BYOC-P or BYOP-P infrastructure requirements — Zoom Communications · tier 2 current vendor documentation · Section 'Public Trusted Certificates' (mTLS note)
Cite this note
APA
WarmTransfer. (2026, October 2). SIP trunk authentication: registration and static IP and mutual TLS: source note sip-trunk-authentication-models-zoom-byoc-mtls-no-peer-name. WarmTransfer. https://warmtransfer.net/knowledge/claims/sip-trunk-authentication-models-zoom-byoc-mtls-no-peer-name
BibTeX
@misc{warmtransfer-claim-sip-trunk-authentication-models-zoom-byoc-mtls-no-peer-name,
title = {SIP trunk authentication: registration and static IP and mutual TLS: source note sip-trunk-authentication-models-zoom-byoc-mtls-no-peer-name},
author = {{WarmTransfer}},
year = {2026},
url = {https://warmtransfer.net/knowledge/claims/sip-trunk-authentication-models-zoom-byoc-mtls-no-peer-name},
note = {Source note sip-trunk-authentication-models-zoom-byoc-mtls-no-peer-name, checked 2026-10-02}
}