Source note · One SBC serving several calling platforms
During mutual TLS, Zoom does not validate the CN or SAN of the SBC certificate against an expected hostname or FQDN.
Checked 2026-10-14
Zoom does not validate the CN or SAN of the SBC certificate against an expected hostname or FQDN.
- Vendor
- Zoom
- Product
- Zoom Phone
- Subsystem
- BYOC-P
- Deployment
- multi-tenant
- Region
- not restricted
- Release range
- current as of 2026-10-14
- Checked
- 2026-10-14
Sources
- BYOC-P or BYOP-P infrastructure requirements — Zoom Communications · tier 2 current vendor documentation · Certificate requirements (mutual TLS hostname validation)
Cite this note
APA
WarmTransfer. (2026, October 14). One SBC serving several calling platforms: source note multi-platform-sbc-design-zoom-no-mtls-hostname-check. WarmTransfer. https://warmtransfer.net/knowledge/claims/multi-platform-sbc-design-zoom-no-mtls-hostname-check
BibTeX
@misc{warmtransfer-claim-multi-platform-sbc-design-zoom-no-mtls-hostname-check,
title = {One SBC serving several calling platforms: source note multi-platform-sbc-design-zoom-no-mtls-hostname-check},
author = {{WarmTransfer}},
year = {2026},
url = {https://warmtransfer.net/knowledge/claims/multi-platform-sbc-design-zoom-no-mtls-hostname-check},
note = {Source note multi-platform-sbc-design-zoom-no-mtls-hostname-check, checked 2026-10-14}
}