Source note · Setting up Zoom Phone BYOC with an SBC
Zoom's mutual TLS implementation for BYOC-P does not perform peer name validation of customer SBC connections, while Zoom publishes per-region hostnames customers can use for peer-name verification on their own SBCs.
Checked 2026-09-25
Zoom's mTLS implementation does not include peer name validation for customer SBC connections.
- Vendor
- Zoom
- Product
- Zoom Phone
- Subsystem
- sbc-certificates
- Deployment
- multi-tenant
- Region
- not restricted
- Release range
- current as of 2026-09-25
- Checked
- 2026-09-25
Sources
- BYOC-P or BYOP-P infrastructure requirements — Zoom Communications · tier 2 current vendor documentation · Peer name validation section
Cite this note
APA
WarmTransfer. (2026, September 25). Setting up Zoom Phone BYOC with an SBC: source note zoom-phone-byoc-setup-mtls-no-peer-name. WarmTransfer. https://warmtransfer.net/knowledge/claims/zoom-phone-byoc-setup-mtls-no-peer-name
BibTeX
@misc{warmtransfer-claim-zoom-phone-byoc-setup-mtls-no-peer-name,
title = {Setting up Zoom Phone BYOC with an SBC: source note zoom-phone-byoc-setup-mtls-no-peer-name},
author = {{WarmTransfer}},
year = {2026},
url = {https://warmtransfer.net/knowledge/claims/zoom-phone-byoc-setup-mtls-no-peer-name},
note = {Source note zoom-phone-byoc-setup-mtls-no-peer-name, checked 2026-09-25}
}