Configuration · guide

Setting up Zoom Phone BYOC with an SBC

Verified 2026-09-25 · 57 sources · tier 2

For Zoom Phone account administrators and voice engineers configuring BYOC connectivity through an SBC..

This guide steps through connecting third-party PSTN trunks to Zoom Phone using certified Session Border Controllers or direct cloud peering 7 5.

Before you start

In Zoom Phone BYOC premises peering (BYOC-P), the customer provides and maintains its own supported SBC to peer with Zoom Phone data centers 7. In BYOC cloud peering (BYOC-C), the business's chosen carrier connects to Zoom Phone data centers without requiring on-premises hardware such as an SBC 5. The service areas available for BYOC-P are determined by the customer's chosen telephony service provider, not by Zoom 51. Furthermore, BYOC-P SBCs require bi-directional connectivity with Zoom, because Zoom initiates connections toward the SBC in addition to receiving traffic 6.

What changes by situation

Pick your answers to see only your path. Nothing is sent anywhere until you make a plan.

Which BYOC peering model connects your organisation to Zoom?

How does your SBC reach Zoom Phone data centers?

Which target carrier handles emergency calls for your BYOC numbers?

Three questions. One permanent page you can send to your manager.

Step 1 Confirm the service model and provider coverage

Do

Confirm whether your deployment uses customer-managed hardware under BYOC-P or carrier integration under BYOC-C 7 5. Ensure that your PSTN carrier covers the target countries where your organisation requires BYOC numbers 51. For BYOC-P, plan your network topology to accommodate inbound connections initiated by Zoom data centers to your SBC 6.

Verify

Verify that the carrier contract covers every intended geographic destination for your BYOC numbers 51.

Step 2 Confirm SBC certification and protocol settings

Premises peering (BYOC-P): customer-managed SBC connects to Zoom

Do

Check that your SBC make and model appears on Zoom's list of certified SBC hardware 13. As of 2026-09-25, Zoom's certified list includes SBCs from AudioCodes, Avaya, Cisco (CUBE), Mitel, NextGen, Oracle, Ribbon, and TE-Systems (anynode) 14. Configure the SBC to support:

TLS 1.2 and SRTP when peering over the internet 56
SIP (RFC 3261), DTMF per RFC 2833, and topology hiding (RFC 5853) 53
SIP early offer (SDP present in the INVITE) on all outbound sessions sent to Zoom 19
Supported codecs: Opus, G.722, G.711 u-law, G.711 A-law, or G.729 15
No SRTP Master Key Identifier (MKI) in SDP offers or media streams 32

Verify

Ensure the SBC model is listed as certified by Zoom 13. Verify that outbound INVITE messages to Zoom contain an SDP offer, as Zoom rejects early-offer-free INVITE requests with a 488 response 19 33.

Rollback

Suggested rollback: restore the previous SBC configuration profile from backup.

Cloud peering (BYOC-C): carrier connects directly to Zoom

Do

Review the carrier's support for Zoom Phone cloud peering, as no customer-side SBC hardware is deployed 5.

Verify

Confirm that your carrier provides onboarding via Zoom Provider Exchange 39.

Step 3 Install SBC TLS certificates

Premises peering (BYOC-P): customer-managed SBC connects to Zoom

Do

Obtain a certificate for the SBC issued by an approved certificate authority listed by Zoom 9. Ensure the certificate contains the SBC FQDN in the common name (CN) or a subject alternative name (SAN), or use a wildcard certificate covering the domain 10. The certificate must include the Server Authentication key usage 12. Configure the SBC to present its complete certificate chain, including all intermediate certificates, to Zoom 11. Zoom's mutual TLS implementation does not validate customer SBC peer names, but Zoom publishes per-region hostnames that can be used for peer-name verification on the SBC 31.

Verify

Verify that the SBC presents the full certificate chain including intermediate certificates during TLS handshakes 11. Verify that the SBC FQDN matches the CN or a SAN entry on the certificate 10.

Rollback

Suggested rollback: re-bind the prior TLS certificate profile on the SBC.

Cloud peering (BYOC-C): carrier connects directly to Zoom

Do

Confirm that your organisation is not maintaining customer SBC certificates for cloud peering 5.

Verify

Suggested check: ensure no SBC TLS certificate prerequisites remain open in your deployment plan.

Step 4 Establish network and transport connectivity

Over the public internet (TLS 1.2 and SRTP) + Premises peering (BYOC-P): customer-managed SBC connects to Zoom

Do

Assign a public IP address to the SBC interface facing Zoom 40. Verify your account's regional cluster assignment in the Zoom admin portal 57. Configure firewall rules allowing bi-directional traffic between your SBC public IP and the Zoom cluster's published signalling IPs on TCP port 5061, as well as the media port range of UDP 10000-64000 6 52 30 57. Peering over the internet uses TLS 1.2 and SRTP 28.

Verify

Verify that TCP port 5061 connects successfully between the SBC and Zoom's published signalling IP addresses for your regional cluster 52 57.

Rollback

Suggested rollback: delete or disable the configured firewall access rules.

Over a private circuit (BGP peering) + Premises peering (BYOC-P): customer-managed SBC connects to Zoom

Do

Procure a private circuit from your carrier to connect to Zoom 38. Establish BGP peering with Zoom using public ASNs and public IP addresses 38 40. Configure network security policies to permit signalling over TCP port 5061 and media across UDP ports 10000-64000 toward Zoom's regional cluster addresses 52 30 57.

Verify

Verify that the BGP peering session is established using the public ASN and that signalling over TCP 5061 can be reached 38 52.

Rollback

Suggested rollback: withdraw BGP route advertisements and disable the private peering configuration.

Over the public internet (TLS 1.2 and SRTP) + Cloud peering (BYOC-C): carrier connects directly to Zoom

Do

Review provider connectivity settings, as network transport to Zoom data centers is handled directly by the cloud carrier 5.

Verify

Suggested check: verify cloud carrier reachability in the carrier administrative interface.

Over a private circuit (BGP peering) + Cloud peering (BYOC-C): carrier connects directly to Zoom

Do

Review provider connectivity settings, as network transport to Zoom data centers is handled directly by the cloud carrier 5.

Verify

Suggested check: verify cloud carrier reachability in the carrier administrative interface.

Step 5 Register the SBC or link the provider

Premises peering (BYOC-P): customer-managed SBC connects to Zoom

Do

Open the Zoom web portal and navigate to Admin Center > Product configuration > Numbers > BYOC Configuration > Session Border Controllers > Manage > Add 2. Provide a display name, the public IP address, and port 2 40. Select TLS as the transport protocol, as TLS is the only supported transport for BYOC-P 50. Enable OPTIONS ping to allow Zoom to monitor trunk health 2 35. Ensure your firewall permits inbound traffic before saving, as Zoom immediately directs traffic to the configured SBC address 48.

Verify

Verify that the SBC entry is created 2. Inspect the SBC logs to confirm incoming SIP OPTIONS keepalives from Zoom 35.

Rollback

Delete the SBC entry under Session Border Controllers > Manage 2. To change an SBC IP address, the SBC entry must be deleted and re-added because it cannot be modified in place 49.

Cloud peering (BYOC-C): carrier connects directly to Zoom

Do

Navigate to the Zoom admin portal, locate the provider, install the provider's application from the Zoom Marketplace, and connect to Zoom from the provider's management portal 39.

Verify

Verify that the carrier portal confirms the active connection to Zoom Phone 39.

Rollback

Suggested rollback: disconnect the integration from within the provider portal and uninstall the provider application.

Step 6 Create the route group

Premises peering (BYOC-P): customer-managed SBC connects to Zoom

Do

Navigate to Admin Center > Product configuration > Numbers > BYOC Configuration > Route Groups > Manage, and select the Common tab 45. Select Add and enter a display name, set Type to BYOC-P, choose the region, set the distribution method to Sequential or Load Balancing, and assign the SBCs 44. Optionally select a backup route group 44. Zoom routes to an alternate SBC within the route group when the primary SBC does not answer OPTIONS keepalive pings or returns specific SIP failure codes 3. Because route group creation can take up to 48 hours, WarmTransfer's reading of the sources is that the route group should be created at least two days before any planned number cutover 37 43.

Verify

Verify that the new route group is visible on the Common tab with Type set to BYOC-P and includes the assigned SBCs 45 44.

Rollback

Delete the route group from the Route Groups page 45 54.

Cloud peering (BYOC-C): carrier connects directly to Zoom

Do

Manage call routing directly within the carrier's interface, as on-premises route groups are not used 5 39.

Verify

Suggested check: check the provider portal to ensure routing profiles are configured.

Step 7 Create the SIP group

Premises peering (BYOC-P): customer-managed SBC connects to Zoom

Do

Navigate to Numbers > BYOC Configuration > SIP Groups > Manage > Add 54. Set the route group source to Common and select your configured BYOC-P route group 54. Note that BYOC-P route groups require phone numbers in E.164 format and do not support private numbering plans 18.

Verify

Confirm that the new SIP group is listed and references the Common BYOC-P route group 54.

Rollback

Delete the SIP group, or adjust its assigned route group 54. Note that modifying a SIP group can alter routing for multiple numbers at once, so Zoom recommends performing edits during a maintenance window 55. Zoom notes, for its Hong Kong data centre maintenance, that while a SIP group is temporarily pointed at an alternate route group, calls from associated numbers may fail to complete 41.

Cloud peering (BYOC-C): carrier connects directly to Zoom

Do

Confirm SIP routing settings inside your cloud provider's administrative portal 39.

Verify

Suggested check: verify in the carrier portal that the SIP interconnect status is green.

Step 8 Add and assign BYOC numbers

Premises peering (BYOC-P): customer-managed SBC connects to Zoom

Do

Navigate to Admin Center > Product configuration > Numbers > Phone Numbers > Add Number > BYOC Number 1. Specify the product, target site, country or region, the phone numbers in E.164 format, and assign them to your Common SIP group 1 16. BYOC phone numbers must be assigned to a Common SIP group to enable both inbound and outbound calling 16. Numbers should be added to the specific site where they will be assigned 34. Go to the Unassigned numbers list and assign each number to its user using the Assign to action 34. To update SIP groups across large batches of numbers, use Phone Numbers > Import > BYOC Number > Update BYOC Numbers via CSV upload 4. Ensure your SBC sends inbound calls with the destination in E.164 format in the user part of the Request-URI 27.

Verify

Under Phone Numbers, filter by BYOC and verify that each number displays the expected site, Common SIP group, and assigned user 1 34.

Rollback

Unassign numbers from users in the Phone Numbers view 34.

Cloud peering (BYOC-C): carrier connects directly to Zoom

Do

Provision phone numbers through the provider portal 39. In Zoom Phone, locate the provisioned numbers on the Unassigned list under the relevant site, and use Assign to to map them to users 34.

Verify

Verify that the numbers appear in the Zoom Phone Numbers list assigned to the target users and sites 34.

Rollback

Unassign the numbers from users in the Zoom Phone Numbers view 34.

Step 9 Configure custom dial plan routing rules

Premises peering (BYOC-P): customer-managed SBC connects to Zoom

Do

If your dial plan requires custom call routing, create a routing rule at the account, site, or group level 46 47. Specify the rule name, regular-expression pattern, optional translation, and set the routing path to SIP Group, Other Sites, or PSTN 46. When a rule must route in E.164 format, select a SIP group backed by a BYOC-P route group 47.

Verify

Place a test outbound call matching the pattern and verify on the SBC that Zoom sends the destination in E.164 format in the Request-URI and the caller identity in E.164 format in the From header 36.

Rollback

Delete the custom routing rule from the Routing Rules configuration table 46.

Cloud peering (BYOC-C): carrier connects directly to Zoom

Do

Confirm whether any site-specific dial plan adjustments are required inside the carrier management portal 39.

Verify

Suggested check: confirm dial plan entries inside the carrier management portal.

Step 10 Configure emergency call routing

BYOC carrier (required outside US and Canada)

Do

Navigate to Phone system > Company Info > Emergency Services 24. Set the Target Carrier setting to the third-party BYOC carrier 24. For BYOC numbers located outside the United States and Canada, emergency calls must use the BYOC carrier, and this setting cannot be changed 23. Assign Emergency Location Identification Numbers (ELINs) at the site level or to a location within a site 21. Because carrier-handled emergency signalling cannot carry the address, Zoom transmits the ELIN as caller ID, and the PSAP resolves the physical address from the carrier's database 20. WarmTransfer's reading of the sources is that the administrator must ensure the carrier provisions the correct physical address for each ELIN or emergency caller ID number prior to going live 42.

Verify

Verify that the Target Carrier field displays the BYOC carrier under Emergency Services 24. WarmTransfer's reading of the sources is that each ELIN must be registered to the correct address in the carrier database 42.

Rollback

For United States and Canada numbers, change the Target Carrier back to Zoom if needed 25. For numbers outside the United States and Canada, the Target Carrier setting cannot be altered 23.

Zoom (US and Canada only)

Do

Navigate to Phone system > Company Info > Emergency Services 24. For BYOC numbers in the United States and Canada, select Zoom as the Target Carrier 24 25. Note that any BYOC numbers outside the United States and Canada must remain set to the BYOC carrier 23.

Verify

Verify that Target Carrier displays Zoom for the relevant US or Canadian sites 24 25.

Rollback

Change the Target Carrier setting back to the third-party carrier under Emergency Services 24 25.

Step 11 Enable international destinations and test failover

Premises peering (BYOC-P): customer-managed SBC connects to Zoom

Do

If users must dial international or special destinations, enable those destinations on the BYOC tab of the account's Zoom Phone Countries/Regions billing configuration, then permit them in the International Calling policy for assigned users 29. Perform end-to-end acceptance testing:

Send an inbound call to a BYOC number, ensuring the SBC includes an SDP offer and formats the destination number as E.164 in the Request-URI 19 27.
Place an outbound call from Zoom Phone, ensuring Zoom sends E.164 numbers in the Request-URI and the From header 36.
Simulate an SBC failure by withholding responses to Zoom's SIP OPTIONS pings 35. Zoom marks the trunk down after 4 consecutive failed keepalives (which takes 90 to 120 seconds) and fails over to backup SBCs in the group or regional alternatives 35 26. Zoom also attempts backup SBCs when receiving SIP 403, 408, 480, 488, 500, 502, 503, 504, or 606 26.

Verify

Verify successful two-way audio on both inbound and outbound test calls 15. Verify in the SBC logs that calls fail over to secondary trunks when the primary returns an eligible SIP error code or fails OPTIONS keepalives 35 26.

Rollback

Re-enable normal OPTIONS keepalive responses on the primary SBC 35. If international permissions were temporary, disable them under Countries/Regions and the International Calling policy 29.

Cloud peering (BYOC-C): carrier connects directly to Zoom

Do

Enable required international or special destination calling permissions under the BYOC tab of Countries/Regions and in the user International Calling policy 29. Coordinate with the cloud provider to place test calls to and from provisioned BYOC numbers 39.

Verify

Suggested check: verify two-way audio on inbound and outbound test calls through the cloud provider.

Rollback

Suggested rollback: disable any temporary international destinations added to the policy.

Applicability

Applies to: Zoom Phone. Deployments: multi-tenant. Sources checked 2026-09-25. BYOC numbers outside the United States and Canada must use the third-party carrier for emergency services 23. United States and Canada BYOC numbers allow selecting either the BYOC carrier or Zoom as the emergency target carrier 25. Porting existing BYOC numbers directly to native Zoom Phone service is handled separately via a letter of agency submitted to Zoom Support 8.

What remains uncertain

Specific procedures for placing live test emergency calls to local Public Safety Answering Points (PSAPs) are not covered by the sources below. Configuration steps for routing rules and dial plan manipulation in cloud-peering provider portals are not covered by the sources below. Specific CLI syntax for configuring Zoom SIP trunks on Cisco CUBE or AudioCodes Mediant hardware is not covered by the sources below. Account-level licensing prerequisites to activate the BYOC-P feature in Zoom Phone are not covered by the sources below.

Sources

1
BYOC numbers are added under Admin Center > Product configuration > Numbers > Phone Numbers > Add Number > BYOC Number, specifying product, site, country or region, the numbers (E.164 preferred) and a SIP group.
BYOC-P or BYOP-P configuration guide · Assign SIP Groups to Phone Numbers > Add new phone numbers to SIP Group · Checked 2026-09-25
2
An SBC is added in the Zoom web portal under Admin Center > Product configuration > Numbers > BYOC Configuration > Session Border Controllers > Manage > Add, with a display name, IP address, port and optional settings such as OPTIONS ping.
BYOC-P or BYOP-P configuration guide · How to manage new Session Border Controllers > Add a Session Border Controller · Checked 2026-09-25
3
Within a route group, Zoom selects an alternate SBC when the primary does not respond to Zoom's OPTIONS ping or returns certain SIP response codes.
BYOC-P or BYOP-P configuration guide · Add a Route Group, distribution note · Checked 2026-09-25
4
SIP groups for many BYOC numbers can be changed in bulk through Phone Numbers > Import > BYOC Number > Update BYOC Numbers with a CSV upload.
BYOC-P or BYOP-P configuration guide · Assign SIP Groups to Phone Numbers > Bulk-update SIP Groups · Checked 2026-09-25
5
In Zoom Phone BYOC cloud peering (BYOC-C), the business's chosen carrier connects to Zoom Phone data centers without the business needing on-premises hardware such as an SBC.
Bring Your Own Carrier - Cloud Peering (BYOC-C) | Zoom Technical Library · Bring Your Own Carrier - Cloud Peering (BYOC-C), opening paragraph · Checked 2026-09-25
6
BYOC-P SBCs require bi-directional connectivity with Zoom, unlike standard Zoom Phone endpoints that only initiate connections toward Zoom data centers.
Bring Your Own Carrier - Premises Peering (BYOC-P) | Zoom Technical Library · Bring Your Own Carrier - Premises Peering (BYOC-P), network paragraph · Checked 2026-09-25
7
In Zoom Phone BYOC premises peering (BYOC-P), the customer provides and maintains its own supported SBC to peer with Zoom Phone data centers, instead of the underlying carrier doing so.
Bring Your Own Carrier - Premises Peering (BYOC-P) | Zoom Technical Library · Bring Your Own Carrier - Premises Peering (BYOC-P), opening paragraphs · Checked 2026-09-25
8
Zoom supports porting existing BYOC numbers to native Zoom Phone service via a letter of agency and BYOC porting sheet submitted to Zoom Support.
Requesting a BYOC number port · Article overview and key steps · Checked 2026-09-25
9
The SBC certificate for BYOC-P must be issued by one of the certificate authorities Zoom lists as approved.
BYOC-P or BYOP-P infrastructure requirements · Certificate requirements section, approved CA list · Checked 2026-09-25
10
The SBC certificate must carry the SBC FQDN in the common name or a subject alternative name, and a wildcard certificate covering the SBC's domain is acceptable.
BYOC-P or BYOP-P infrastructure requirements · Certificate requirements section · Checked 2026-09-25
11
The SBC must present its complete certificate chain, including any intermediate certificates, to Zoom.
BYOC-P or BYOP-P infrastructure requirements · Certificate requirements section · Checked 2026-09-25
12
The SBC certificate must include the Server Authentication key usage.
BYOC-P or BYOP-P infrastructure requirements · Certificate requirements section · Checked 2026-09-25
13
Zoom maintains a list of certified SBC vendors and models that have undergone interoperability testing for BYOC-P.
BYOC-P or BYOP-P infrastructure requirements · SBC requirements section, first bullet linking KB0060242 · Checked 2026-09-25
14
As of 2026-09-25 the Zoom Phone certified hardware list names SBCs from AudioCodes, Avaya, Cisco (CUBE), Mitel, NextGen, Oracle, Ribbon and TE-Systems (anynode).
Zoom Phone certified hardware · Zoom Phone Certified Hardware, session border controllers section · Checked 2026-09-25
15
The codecs listed for BYOC-P are Opus, G.722, G.711 u-law, G.711 A-law and G.729.
BYOC-P or BYOP-P infrastructure requirements · SBC requirements section, codecs bullet · Checked 2026-09-25
16
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 · Assign SIP Groups to Phone Numbers, note · Checked 2026-09-25
17
Zoom's infrastructure requirements call for two DigiCert root certificates on the SBC for communication from the SBC toward Zoom.
BYOC-P or BYOP-P infrastructure requirements · Certificate requirements section, root certificates for outbound communication · Checked 2026-09-25
18
BYOC-P route groups are for third-party PSTN interoperability, do not support a private numbering plan, and require numbers in E.164 format; BYOP-P accepts localized or E.164 numbers up to 24 digits.
BYOC-P or BYOP-P call processing · Route groups and number formats sections · Checked 2026-09-25
19
Zoom mandates SIP early offer (SDP in the INVITE) for INVITEs the SBC sends to Zoom.
BYOC-P or BYOP-P infrastructure requirements · SBC requirements section · Checked 2026-09-25
20
When a BYOC carrier handles emergency calls, the address cannot be carried in the call signalling, so Zoom uses an ELIN as the caller ID and the PSAP looks the address up from the carrier's database.
Emergency Location Identification Number (ELIN) · ELIN page, BYOC carrier paragraph · Checked 2026-09-25
21
ELINs are assigned at the site level, or to a location within a site, in the Zoom admin portal, and each ELIN's address is registered with the carrier.
Emergency Location Identification Number (ELIN) · ELIN page, configuration and example paragraphs · Checked 2026-09-25
22
Zoom states that for BYOC emergency calls the caller's address reported to the PSAP is based on the BYOC carrier's records, and that Zoom cannot report nomadic (detected) addresses directly to the PSAP, only in call logs and to an internal safety response team.
Routing emergency calls · Target Carrier setting description · Checked 2026-09-25
23
BYOC numbers outside the United States and Canada must use the BYOC carrier for emergency calling and the Target Carrier setting cannot be changed for them.
Routing emergency calls · Target Carrier setting, note for non-United States/Canada BYOC numbers · Checked 2026-09-25
24
The Emergency Services tab under Phone system > Company Info has a Target Carrier setting that chooses Zoom or the third-party carrier for emergency calls placed by BYOC numbers.
Routing emergency calls · How to route emergency calls to a public-safety answering point (PSAP), Target Carrier setting · Checked 2026-09-25
25
For United States and Canada BYOC numbers, the admin can select either the BYOC carrier or Zoom as the emergency Target Carrier.
Routing emergency calls · Target Carrier setting, note for United States and Canada BYOC numbers · Checked 2026-09-25
26
Zoom tries backup SBCs when the primary fails or returns 403, 408, 480, 488, 500, 502, 503, 504 or 606, first within the same route group and then in the regional alternative.
BYOC-P or BYOP-P call processing · Failover routing section · Checked 2026-09-25
27
For inbound BYOC calls, the user part of the Request-URI the SBC sends should be the E.164 number of the destination within Zoom.
BYOC-P or BYOP-P call processing · Inbound calls section · Checked 2026-09-25
28
BYOC-P can run over the internet (over the top), secured with TLS 1.2 and SRTP, with calls routed to active data centers in the region and failing over to alternates.
BYOC-P or BYOP-P deployment and connectivity options · Connectivity options, Internet (OTT) · Checked 2026-09-25
29
International and special-destination calling for BYOC is enabled on the BYOC tab of the account's Zoom Phone Countries/Regions billing setting and then allowed for users in the International Calling policy.
Enabling international and special destination calls for BYOC · Enable at account level; Enable for users · Checked 2026-09-25
30
The BYOC-P media port range is UDP 10000-64000.
BYOC-P or BYOP-P infrastructure requirements · Network requirements section, media · Checked 2026-09-25
31
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.
BYOC-P or BYOP-P infrastructure requirements · Peer name validation section · Checked 2026-09-25
32
Zoom does not accept SDP offers or media streams that specify an SRTP Master Key Identifier (MKI).
BYOC-P or BYOP-P infrastructure requirements · Cipher specifications section, note under media ciphers · Checked 2026-09-25
33
Zoom answers an inbound BYOC-P INVITE that carries no SDP offer with a 488 response.
BYOC-P or BYOP-P call processing · Inbound calls section · Checked 2026-09-25
34
BYOC numbers should be added to the specific site where they will be assigned, and are then assigned to users from the Unassigned numbers list with Assign to.
(Optional) BYOC Number Management · Adding BYOC numbers; Assigning numbers to users · Checked 2026-09-25
35
Zoom uses SIP OPTIONS as a heartbeat to the SBC and marks the trunk down after four consecutive failed keepalives, which takes 90 to 120 seconds.
BYOC-P or BYOP-P call processing · Health monitoring section · Checked 2026-09-25
36
On outbound BYOC-P calls Zoom sends the destination in E.164 in the Request-URI and the calling party in E.164 in the user part of the From header.
BYOC-P or BYOP-P call processing · Outbound calls section · Checked 2026-09-25
37
Because route group creation can take up to 48 hours, the route group should be created at least two days before any planned number cutover.inferred
BYOC-P or BYOP-P configuration guide · Add a Route Group, note (inference from the 48-hour statement) · Checked 2026-09-25
38
BYOC-P over private circuits requires BGP peering between Zoom and the customer using public ASNs and public IP addresses, with the circuit procured by the customer from its carrier.
BYOC-P or BYOP-P deployment and connectivity options · Connectivity options, Private circuits · Checked 2026-09-25
39
Zoom describes cloud-peering onboarding through Provider Exchange as four steps: find the provider from the Zoom admin portal, get the provider app from Zoom Marketplace, connect with Zoom from the provider portal, and provision numbers from the provider portal.
Zoom Phone: Provider Exchange · Provider Exchange page, how-it-works four-step sequence · Checked 2026-09-25
40
A public IP address is required on the SBC side for BYOC-P SIP trunk connectivity.
BYOC-P or BYOP-P deployment and connectivity options · Infrastructure paragraph · Checked 2026-09-25
41
While a SIP group is temporarily pointed at a different route group, calls from the numbers assigned to that SIP group may not complete successfully.
Adding SBCs to existing Route Groups · Step 1, remove route group from SIP group, note · Checked 2026-09-25
42
Before BYOC numbers go live with the BYOC carrier as emergency target, the admin must have the carrier provision the correct address against each number or ELIN used as emergency caller ID, because the PSAP address comes from the carrier's records.inferred
Emergency Location Identification Number (ELIN) · ELIN page, BYOC carrier paragraph (inference combined with KB0061026 Target Carrier description) · Checked 2026-09-25
43
Creating a BYOC route group may take up to 48 hours to complete.
BYOC-P or BYOP-P configuration guide · Add a Route Group, note · Checked 2026-09-25
44
A BYOC route group takes a display name, a type of BYOC-P or BYOP-P, a region, a distribution of Sequential or Load Balancing, one or more SBCs and an optional backup route group.
BYOC-P or BYOP-P configuration guide · Add a Route Group, field list · Checked 2026-09-25
45
A route group is added under Admin Center > Product configuration > Numbers > BYOC Configuration > Route Groups > Manage, and Zoom Phone and Zoom Contact Center customers are asked to use the Common tab.
BYOC-P or BYOP-P configuration guide · How to manage Route Groups > Add a Route Group · Checked 2026-09-25
46
A routing rule is set at account, site or group level with a name, a regular-expression number pattern, an optional translation and a routing path of Other Sites, PSTN or SIP Group.
BYOC-P or BYOP-P configuration guide · Add a Routing Rule, field list · Checked 2026-09-25
47
Zoom Phone routing rules are needed only when a dial plan requires custom routing, and a rule that must route in E.164 must select a SIP group backed by a BYOC-P route group.
BYOC-P or BYOP-P configuration guide · Add a Routing Rule, notes · Checked 2026-09-25
48
Zoom's configuration guide warns that Zoom will direct traffic to the SBC address entered, so the necessary firewall ports must be open.
BYOC-P or BYOP-P configuration guide · Add a Session Border Controller, IP address field note · Checked 2026-09-25
49
To change an SBC's IP address in Zoom, the SBC entry must be deleted and re-added; the address cannot be edited in place.
BYOC-P or BYOP-P configuration guide · Edit a Session Border Controller, note · Checked 2026-09-25
50
When adding an SBC for BYOC-P, only TLS is supported as the transport protocol and it cannot be changed.
BYOC-P or BYOP-P configuration guide · Add a Session Border Controller, Protocol field note · Checked 2026-09-25
51
For BYOC-P, the service areas available are determined by the customer's chosen telephony service provider, not by Zoom.
Bring Your Own Carrier - Premises Peering (BYOC-P) | Zoom Technical Library · Bring Your Own Carrier - Premises Peering (BYOC-P), service area paragraph · Checked 2026-09-25
52
All BYOC-P signalling between Zoom and the SBC uses TCP port 5061.
BYOC-P or BYOP-P infrastructure requirements · Network requirements section, signalling · Checked 2026-09-25
53
The BYOC-P SBC must support SIP (RFC 3261), DTMF per RFC 2833 and topology hiding (RFC 5853).
BYOC-P or BYOP-P infrastructure requirements · SBC requirements section · Checked 2026-09-25
54
A SIP group is added under Numbers > BYOC Configuration > SIP Groups > Manage > Add and links a route group, chosen from a Common, Phone or Contact Center source, to numbers and call destinations.
BYOC-P or BYOP-P configuration guide · How to manage SIP Groups > Add a SIP Group · Checked 2026-09-25
55
Saving an edit to a SIP group can change routing for multiple entities at once, and Zoom recommends doing it in a maintenance window.
BYOC-P or BYOP-P configuration guide · Edit a SIP Group, note · Checked 2026-09-25
56
BYOC-P requires the SBC to support TLS 1.2 and SRTP when peering over the internet.
BYOC-P or BYOP-P infrastructure requirements · SBC requirements section · Checked 2026-09-25
57
Zoom publishes BYOC-P signalling IPs and media subnets per regional cluster and advises verifying the account's cluster assignment in the Zoom admin portal before configuring firewall rules.
BYOC-P or BYOP-P infrastructure requirements · Network requirements section, regional data centers and firewall rules tables · Checked 2026-09-25

Documents

tier 2 current vendor documentation

Cite this page

APA

WarmTransfer. (2026, September 25). Setting up Zoom Phone BYOC with an SBC. WarmTransfer. https://warmtransfer.net/guides/zoom-phone-byoc-setup

BibTeX

@misc{warmtransfer-zoom-phone-byoc-setup,
  title  = {Setting up Zoom Phone BYOC with an SBC},
  author = {{WarmTransfer}},
  year   = {2026},
  url    = {https://warmtransfer.net/guides/zoom-phone-byoc-setup},
  note   = {Verified 2026-09-25}
}