Source record · tier 2 current vendor documentation
Bring Your Own Carrier - Cloud Peering (BYOC-C) | Zoom Technical Library
- Publisher
- Zoom Communications
- URL
- https://library.zoom.com/zoom-workplace/zoom-phone/zoom-phone-bluepaper/overview/bring-your-own-carrier-cloud-peering-byoc-c
- Published
- unknown
- Updated
- unknown
- Accessed
- 2026-09-24
- HTTP status
- 200
- License
- Zoom proprietary; all rights reserved; no-redistribution; short excerpts and locators only
Source notes citing this source
- Zoom BYOC Cloud Peering (BYOC-C) connects one or more carriers to Zoom Phone data centers without customer on-premises hardware such as an SBC. in context
- With Provider Exchange cloud peering the customer contracts and is billed separately by the chosen provider and by Zoom. in context
- The Zoom Technical Library states the Provider Exchange network collectively covers over 90 countries with PSTN connectivity. in context
- BYOC-C lets a business connect one or more carriers to Zoom Phone data centers through cloud peering without any on-premises hardware. in context
- BYOC-C customers pick an approved provider from Zoom's Provider Exchange and contract and pay that provider separately, in addition to their Zoom Phone bill. in context
- A cloud peering provider can be combined with the Zoom Phone Native model to reach PSTN services that Native alone does not offer. in context
- The Zoom Technical Library states the Provider Exchange network collectively covers over 90 countries with PSTN connectivity. in context
Cite this source record
APA
WarmTransfer. (2026, September 24). Bring Your Own Carrier - Cloud Peering (BYOC-C) | Zoom Technical Library. WarmTransfer. https://warmtransfer.net/knowledge/sources/zoom-library-bluepaper-byoc-c
BibTeX
@misc{warmtransfer-zoom-library-bluepaper-byoc-c,
title = {Bring Your Own Carrier - Cloud Peering (BYOC-C) | Zoom Technical Library},
author = {{WarmTransfer}},
year = {2026},
url = {https://warmtransfer.net/knowledge/sources/zoom-library-bluepaper-byoc-c},
note = {Zoom Communications, accessed 2026-09-24}
}