Zoom Phone BYOC and Provider Exchange

See also

Sources

1. 1
   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.

   Bring Your Own Carrier - Cloud Peering (BYOC-C) | Zoom Technical Library · Definition · Checked 2026-09-25
2. 2
   With Provider Exchange cloud peering the customer contracts and is billed separately by the chosen provider and by Zoom.

   Bring Your Own Carrier - Cloud Peering (BYOC-C) | Zoom Technical Library · Provider Exchange section · Checked 2026-09-25
3. 3
   Unlike Zoom endpoints which always connect outward to Zoom a BYOC-P SBC requires bi-directional connectivity with Zoom data centers.

   Bring Your Own Carrier - Premises Peering (BYOC-P) | Zoom Technical Library · Key requirements: bi-directional connectivity · Checked 2026-09-25
4. 4
   BYOC-Premises presumes existing PSTN connections with a carrier while BYOP-Premises presumes a PBX with logical connections to an SBC and applies to Zoom Phone only.

   BYOC-P or BYOP-P deployment and connectivity options · BYOC-P vs BYOP-P prerequisites · Checked 2026-09-25
5. 5
   Zoom supports caller names up to 47 bytes on BYOC-P calls which is 47 ASCII characters but fewer accented or CJK characters.

   BYOC-P or BYOP-P call processing · Caller name limits · Checked 2026-09-25
6. 6
   The Zoom Phone certified hardware list shows AudioCodes Mediant SBCs from Mediant 500 through Mediant 9080C and Mediant Software SBC certified at firmware 7.40A.605.092.

   Zoom Phone certified hardware · Session Border Controllers section: AudioCodes · Checked 2026-09-25
7. 7
   A BYOC SBC must present its complete certificate chain including intermediates and the certificate must have Server Authentication key usage.

   BYOC-P or BYOP-P infrastructure requirements · Certificate requirements section · Checked 2026-09-25
8. 8
   The Zoom Phone certified hardware list shows Cisco Unified Border Element (CUBE) certified at version 17.3.3.

   Zoom Phone certified hardware · Session Border Controllers section: Cisco · Checked 2026-09-25
9. 9
   The public certificate on a BYOC SBC must carry the SBC FQDN in the certificate common name or subject alternative name.

   BYOC-P or BYOP-P infrastructure requirements · Certificate requirements section · Checked 2026-09-25
10. 10
    SBC vendors on the Zoom Phone certified hardware list are AudioCodes Avaya Cisco Mitel NextGen Oracle Ribbon and TE-Systems (anynode).

    Zoom Phone certified hardware · Session Border Controllers section vendor headings · Checked 2026-09-25
11. 11
    Zoom directs BYOC-P customers to use an SBC vendor and model from its certified SBC list which have undergone interoperability testing with Zoom.

    BYOC-P or BYOP-P infrastructure requirements · Certified SBC requirement paragraph linking KB0060242 · Checked 2026-09-25
12. 12
    Zoom's preferred codec order for BYOC-P and BYOP-P calls is Opus first then G.722 then G.711 A-law or u-law then G.729.

    BYOC-P or BYOP-P call processing · Audio codec preferences section · Checked 2026-09-25
13. 13
    Zoom BYOC-P and BYOP-P support the Opus G.722 G.711 u-law G.711 A-law and G.729 audio codecs.

    BYOC-P or BYOP-P infrastructure requirements · Requirements list: codec support · Checked 2026-09-25
14. 14
    BYOC phone numbers must be assigned to a Common SIP Group to enable both inbound and outbound calling.

    BYOC-P or BYOP-P configuration guide · SIP group management section · Checked 2026-09-25
15. 15
    Zoom requires DigiCert Global Root G2 and DigiCert X9 Financial PKI RSA 4096 Root to be installed in the BYOC SBC trust store.

    BYOC-P or BYOP-P infrastructure requirements · DigiCert root certificates section · Checked 2026-09-25
16. 16
    SIP Early Offer is mandatory for INVITEs that a BYOC-P or BYOP-P SBC sends to Zoom.

    BYOC-P or BYOP-P infrastructure requirements · Requirements list: SIP Early Offer · Checked 2026-09-25
17. 17
    Zoom number management offers a BYOC Address Confirmation bulk action to confirm emergency addresses for applicable BYOC-Premises numbers.

    Managing Your Numbers · Managing multiple numbers at once · Checked 2026-09-25
18. 18
    When BYOC emergency calls are routed through the carrier Zoom can show detected nomadic addresses in call logs and to internal safety teams but cannot pass them to the PSAP.

    Routing emergency calls · Step 9 description of carrier routing · Checked 2026-09-25
19. 19
    BYOC numbers outside the US and Canada must use the BYOC carrier for emergency calling and the target-carrier setting cannot be changed for them.

    Routing emergency calls · How to route emergency calls to a PSAP: step 9 note · Checked 2026-09-25
20. 20
    Who holds the emergency address of record for a US or Canada BYOC number likely depends on the Target Carrier setting: Zoom-managed addresses when routed via Zoom and the carrier's address records when routed via the carrier.inferred

    Routing emergency calls · Step 9 Target Carrier description · Checked 2026-09-25
21. 21
    For US and Canada BYOC numbers the admin chooses in the emergency routing settings whether emergency calls go through Zoom or the third-party BYOC carrier.

    Routing emergency calls · How to route emergency calls to a PSAP: step 9 Target Carrier · Checked 2026-09-25
22. 22
    Zoom reroutes a BYOC-P call when the SBC is down or answers with SIP 403 408 480 488 500 502 503 504 or 606.

    BYOC-P or BYOP-P call processing · Failover routing section · Checked 2026-09-25
23. 23
    BYOC-P failover tries alternate SBCs in the same route group first then backup route groups then alternate Zoom data centers.

    BYOC-P or BYOP-P call processing · Failover routing section · Checked 2026-09-25
24. 24
    For BYOC-P trunks terminated in Hong Kong Zoom support deletes and recreates the route group with dual data center termination after the admin temporarily unassigns it from the SIP group.

    Adding SBCs to existing Route Groups · Steps: remove route group then notify Zoom then assign new route group · Checked 2026-09-25
25. 25
    For a hybrid environment Zoom requires both BYOC-P and BYOP-P to be enabled at the SBC level whereas a cloud-only deployment needs only BYOC-P.

    BYOC-P or BYOP-P call processing · Architecture and components section · Checked 2026-09-25
26. 26
    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.

    BYOC-P or BYOP-P call processing · Number format requirements: inbound calls · Checked 2026-09-25
27. 27
    International and special destinations such as satellite phones for BYOC are enabled on the BYOC tab of the account Countries/Regions billing settings and then allowed to users through the International Calling policy BYOC tab.

    Enabling international and special destination calls for BYOC · Steps to enable: billing portal paths and allow user access · Checked 2026-09-25
28. 28
    The Zoom BYOC configuration guide gives a 10-second INVITE response timeout before failover is triggered.

    BYOC-P or BYOP-P configuration guide · Route group setup section · Checked 2026-09-25
29. 29
    Internet Security Research Group (Let's Encrypt) is on Zoom's list of supported certificate authorities for BYOC SBC certificates alongside DigiCert Sectigo GlobalSign and others.

    BYOC-P or BYOP-P infrastructure requirements · Supported certificate authorities list · Checked 2026-09-25
30. 30
    Zoom's highest-priority SRTP crypto suite for BYOC-P media is AEAD_AES_256_GCM followed by AES_256_CM_HMAC_SHA1_80 then AES_CM_128_HMAC_SHA1_80 then AES_CM_128_HMAC_SHA1_32.

    BYOC-P or BYOP-P infrastructure requirements · Media cipher priorities table · Checked 2026-09-25
31. 31
    The media port range for Zoom BYOC-P and BYOP-P is UDP 10000-64000 which Zoom notes differs from its standard client range.

    BYOC-P or BYOP-P infrastructure requirements · Media port range section · Checked 2026-09-25
32. 32
    Zoom's Provider Exchange product page describes Zoom Native PSTN as available in over 48 countries or territories distinct from Cloud Peering and Premises Peering BYOC.

    Zoom Phone: Provider Exchange · PSTN connectivity options panel · Checked 2026-09-25
33. 33
    Zoom does not accept SDP offers or media streams from a BYOC SBC that specify an SRTP Master Key Identifier (MKI).

    BYOC-P or BYOP-P infrastructure requirements · SRTP media key identifier note · Checked 2026-09-25
34. 34
    Zoom BYOC-P accepts only SIP URIs; Tel URIs and secure SIP (SIPS) URIs are not supported.

    BYOC-P or BYOP-P call processing · Number format requirements: inbound calls · Checked 2026-09-25
35. 35
    Zoom sends SIP OPTIONS to a BYOC-P SBC every 30 seconds and marks it down after 4 consecutive failures which takes 90 to 120 seconds.

    BYOC-P or BYOP-P call processing · OPTIONS keepalive and SBC status monitoring · Checked 2026-09-25
36. 36
    A BYOC-P SBC marked down returns to service after three consecutive successful OPTIONS exchanges which typically takes 60 to 90 seconds.

    BYOC-P or BYOP-P call processing · OPTIONS keepalive and SBC status monitoring · Checked 2026-09-25
37. 37
    On calls from Zoom to the SBC the Request-URI is E.164 for BYOC-P while BYOP-P allows localized or E.164 format up to 24 digits.

    BYOC-P or BYOP-P call processing · Number format requirements: outbound calls · Checked 2026-09-25
38. 38
    BYOC SBCs route groups and SIP groups are configured in the Zoom web portal under Product Configuration then Numbers then BYOC Configuration.

    BYOC-P or BYOP-P configuration guide · Session Border Controller creation section · Checked 2026-09-25
39. 39
    Private-circuit peering for BYOC-P requires BGP peering between Zoom and the customer using public ASNs and public IP addresses over circuits the customer procures from its carrier.

    BYOC-P or BYOP-P deployment and connectivity options · Connectivity options: Private circuits · Checked 2026-09-25
40. 40
    The Zoom Technical Library states the Provider Exchange network collectively covers over 90 countries with PSTN connectivity.

    Bring Your Own Carrier - Cloud Peering (BYOC-C) | Zoom Technical Library · Geographic coverage paragraph · Checked 2026-09-25
41. 41
    Numbers provisioned by Provider Exchange carriers appear in the Zoom web portal under Number Management then Phone Numbers on the Cloud Peering tab.

    Setting up Phone provider exchange · View assigned numbers · Checked 2026-09-25
42. 42
    An admin connects a Provider Exchange carrier from Number Management then Provider Exchange by clicking Connect and entering the account name exactly as shown in the account profile.

    Setting up Phone provider exchange · Setup via Zoom web portal steps · Checked 2026-09-25
43. 43
    A Provider Exchange connection can be disconnected by the admin only while no phone numbers from that provider have been provisioned.

    Setting up Phone provider exchange · After connection section · Checked 2026-09-25
44. 44
    Zoom lets organizations build BYOC-P SIP trunks to SBCs in chosen regions and expects premises equipment in each corresponding region.

    BYOC-P or BYOP-P deployment and connectivity options · Deployment options section · Checked 2026-09-25
45. 45
    Zoom states that route group creation may take up to 48 hours to complete.

    BYOC-P or BYOP-P configuration guide · Route group setup section · Checked 2026-09-25
46. 46
    A Zoom BYOC route group is created with a route type (BYOC-P or BYOP-P) a region and a distribution method of sequential or load balancing and can name a backup route group.

    BYOC-P or BYOP-P configuration guide · Route group setup section · Checked 2026-09-25
47. 47
    The support-recreated route group procedure in KB0057948 probably reflects a Hong Kong special case or an earlier workflow since the current configuration guide describes admins creating route groups and backup route groups themselves.inferred

    BYOC-P or BYOP-P configuration guide · Route group setup section compared with KB0057948 steps · Checked 2026-09-25
48. 48
    Zoom Phone routing rules for BYOC use regular expressions and can be set at account site or group level with the lower-level rule taking precedence.

    BYOC-P or BYOP-P configuration guide · Routing rules (Zoom Phone only) section · Checked 2026-09-25
49. 49
    The Zoom Phone SBCs dashboard shows each SBC as Online Offline Warning or Disabled and keeps historical call-attempt and SIP cause-code data for up to 13 months.

    Viewing the Zoom Phone SBCs dashboard · What the dashboard shows section · Checked 2026-09-25
50. 50
    Zoom uses a 30-minute session expiration timer on BYOC-P calls and accepts a minimum session expiration of 90 seconds.

    BYOC-P or BYOP-P call processing · SIP headers and session management section · Checked 2026-09-25
51. 51
    Zoom's highest-priority TLS cipher for BYOC-P signaling is TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384.

    BYOC-P or BYOP-P infrastructure requirements · Signaling cipher priorities table: priority 1 · Checked 2026-09-25
52. 52
    Zoom BYOC-P and BYOP-P SIP signaling between Zoom and the customer SBC uses TCP port 5061.

    BYOC-P or BYOP-P infrastructure requirements · Signaling ports section · Checked 2026-09-25
53. 53
    Zoom lists SIP per RFC 3261 and DTMF per RFC 2833 and topology hiding per RFC 5853 among BYOC-P SBC requirements.

    BYOC-P or BYOP-P infrastructure requirements · Requirements list: SIP DTMF topology hiding · Checked 2026-09-25
54. 54
    When an admin adds a BYOC SBC in the Zoom web portal only the TLS transport protocol is supported and it cannot be changed.

    BYOC-P or BYOP-P configuration guide · Session Border Controller creation section · Checked 2026-09-25
55. 55
    TLS 1.2 and SRTP are required for BYOC-P and BYOP-P when peering with Zoom over the Internet.

    BYOC-P or BYOP-P infrastructure requirements · Requirements list: protocols · Checked 2026-09-25
56. 56
    During a Zoom Phone Local Survivability event each site supports one ELIN which uses a BYOC number as the outgoing calling number to emergency services.

    (Optional) BYOC Number Management · ELIN paragraph · Checked 2026-09-25
57. 57
    ZPLS forwarding of user numbers to BYOC numbers is disabled by default and must be enabled manually in the web portal during a survivability event.

    (Optional) BYOC Number Management · Call forwarding logic · Checked 2026-09-25

Documents

Cite this page

WarmTransfer. (2026, September 25). Zoom Phone BYOC and Provider Exchange. WarmTransfer. https://warmtransfer.net/knowledge/zoom-phone-byoc

@misc{warmtransfer-zoom-phone-byoc,
  title  = {Zoom Phone BYOC and Provider Exchange},
  author = {{WarmTransfer}},
  year   = {2026},
  url    = {https://warmtransfer.net/knowledge/zoom-phone-byoc},
  note   = {Verified 2026-09-25}
}