Source note · Zoom Phone BYOC and Provider Exchange
For inbound BYOC calls the user part of the Request-URI sent to Zoom should contain the E.164 number while BYOP calls may use private extension dialing.
Checked 2026-09-25
The User portion of the Request-URI header for BYOC calls should contain the E164 number
- Vendor
- Zoom
- Product
- Zoom Phone
- Subsystem
- byoc-premises-sip
- Deployment
- multi-tenant
- Region
- not restricted
- Release range
- current as of 2026-09-25
- Checked
- 2026-09-25
Sources
- BYOC-P or BYOP-P call processing — Zoom Communications · tier 2 current vendor documentation · Number format requirements: inbound calls
Cite this note
APA
WarmTransfer. (2026, September 25). Zoom Phone BYOC and Provider Exchange: source note zoom-phone-byoc-inbound-ruri-e164. WarmTransfer. https://warmtransfer.net/knowledge/claims/zoom-phone-byoc-inbound-ruri-e164
BibTeX
@misc{warmtransfer-claim-zoom-phone-byoc-inbound-ruri-e164,
title = {Zoom Phone BYOC and Provider Exchange: source note zoom-phone-byoc-inbound-ruri-e164},
author = {{WarmTransfer}},
year = {2026},
url = {https://warmtransfer.net/knowledge/claims/zoom-phone-byoc-inbound-ruri-e164},
note = {Source note zoom-phone-byoc-inbound-ruri-e164, checked 2026-09-25}
}