ADAM PULSE Knowledge Base
Zoom administration · BYOC · BYOP · Provider Exchange · SBC

BYOC vs BYOP with Zoom Phone: when does bringing your own carrier make sense?

By Michael Obraitis, Managing Partner, and Michael Dale, CEO · Published August 18, 2026 · Last reviewed August 2026 · ADAM Pulse Knowledge Base · Zoom Phone Administrator Series

Short answer

Zoom Phone does not require every organization to move all telephone numbers and PSTN services to Zoom native calling.

Organizations can also integrate existing carriers and legacy PBX environments with Zoom.

The two concepts administrators need to separate are:

BYOC = Bring Your Own Carrier

BYOP = Bring Your Own PBX

They solve different problems.

BYOC

BYOC allows an organization to keep a third party PSTN carrier while using Zoom Phone as the cloud phone platform.

In simple terms:

Users and call control = Zoom Phone

PSTN carrier = your chosen carrier

Zoom currently supports more than one BYOC model, including premises based peering and cloud provider connectivity.

BYOP

BYOP Premises allows Zoom Phone to interoperate with an existing PBX through customer Session Border Controller infrastructure.

In simple terms:

Some users or services = Zoom Phone

Some users or services = existing PBX

SBC = controlled bridge between them

BYOP is especially useful during migrations and hybrid environments.

The most important architecture rule is:

Do not choose BYOC simply because keeping the existing carrier sounds easier.

And do not choose BYOP simply because an old PBX still exists.

Choose the architecture because there is a defined business, regulatory, geographic, migration, technical, or resiliency requirement that justifies the additional operational complexity.

Important:

Zoom licensing, carrier availability, supported countries, SBC certification, emergency calling requirements, SMS support, regulatory requirements, and peering options change over time. Verify the current Zoom first party documentation and carrier requirements before implementing a production design.

The four architectures Zoom actually offers

What Does BYOC Mean in Zoom Phone?

BYOC means Bring Your Own Carrier.

Instead of using Zoom as the PSTN carrier for a particular number or calling path, the organization retains a third party carrier and connects that carrier to Zoom Phone.

The employee can still use Zoom Phone.

The phone number can still be assigned within Zoom.

The calling experience can still be managed through Zoom.

But the PSTN service behind that number is supplied through the BYOC architecture.

What Is PSTN?

PSTN means Public Switched Telephone Network.

It is the traditional telephone network that connects business telephone numbers, mobile phones, landlines, toll free services, and other public telephone endpoints.

Zoom Phone provides cloud call control and can also provide PSTN calling through Zoom native services.

BYOC separates those two roles.

What Does BYOP Mean?

BYOP means Bring Your Own PBX.

Zoom currently documents BYOP Premises, or BYOP P, for Zoom Phone.

It allows an existing PBX to connect logically to Zoom Phone through an SBC.

This can support extension based dialing and private numbering between Zoom Phone and the legacy PBX.

BYOP is not primarily about choosing a different PSTN carrier.

It is about PBX interoperability.

What Is the Difference Between BYOC and BYOP?

The easiest way to remember it is:

BYOC connects Zoom to your carrier.

BYOP connects Zoom to your PBX.

BYOC answers:

"Who provides my PSTN service?"

BYOP answers:

"How does Zoom Phone communicate with the PBX I still operate?"

A hybrid migration may use both.

What Is BYOC Premises?

Zoom calls the premises based model Bring Your Own Carrier Premises, or BYOC P.

In this architecture, the organization supplies and administers Session Border Controller infrastructure.

A simplified call path is:

Zoom Phone user

→ Zoom cloud

→ secure SIP trunk

→ customer SBC

→ existing carrier

→ PSTN

Zoom currently supports peering over the Internet and private circuit options for applicable BYOC P deployments.

What Is BYOC Cloud?

BYOC Cloud allows organizations to use participating carrier partners without operating the same customer premises SBC architecture required by BYOC P.

Zoom Number Management identifies these numbers as BYOC Cloud.

Zoom's Provider Exchange can simplify connection with supported providers through the Zoom web portal.

This can be attractive when an organization wants carrier choice without owning SBC infrastructure.

What Is Zoom Provider Exchange?

Provider Exchange is Zoom's mechanism for connecting supported third party providers to Zoom Phone.

Zoom describes Provider Exchange as a way to bring a carrier into Zoom Phone without requiring on premises hardware.

Administrators can discover supported providers, establish the provider relationship, and make provider supplied numbers available in Zoom.

This can dramatically reduce the technical burden compared with building and maintaining premises peering.

Is Provider Exchange the Same as BYOC Premises?

No.

They solve a similar carrier choice problem through different architectures.

Provider Exchange or BYOC Cloud

The provider handles the cloud peering relationship.

BYOC Premises

The customer operates the SBC and associated infrastructure connecting Zoom to the carrier.

That difference has major consequences for:

Session border controllers: who supplies one, and when

What Is an SBC?

SBC means Session Border Controller.

An SBC sits at the boundary between voice environments.

In a Zoom BYOC P or BYOP P architecture, it can perform functions involving:

The SBC is a critical production component.

It should not be treated as a generic firewall with a SIP feature enabled.

Does Zoom Require an SBC for BYOC Premises?

Yes.

Zoom's current BYOC P requirements include the ability to administer customer SBC infrastructure.

Zoom also requires a public IP address for SIP trunk connectivity in the documented premises architecture.

Use a Zoom supported SBC and current Zoom infrastructure requirements.

Does BYOC Cloud Require My Own SBC?

Provider Exchange is specifically designed to allow carrier connectivity without requiring on premises hardware.

That is one of the strongest reasons to evaluate cloud peering before building a customer managed SBC environment.

When BYOC makes sense, and when it does not

Why Would a Company Keep Its Existing Carrier?

There are many legitimate reasons.

Examples include:

But every reason should be documented.

"That is how we have always done it" is not an architecture requirement.

When Does BYOC Make the Most Sense?

BYOC is worth serious evaluation when one or more of these are true:

  1. The organization has a strategic carrier contract it wants to

retain.

  1. Required telephone numbers or countries are better supported through

another carrier.

  1. A global enterprise needs carrier flexibility by region.
  2. Regulatory requirements influence carrier choice.
  3. The organization has sophisticated telecom engineering capabilities.
  4. A staged migration requires existing carrier services to remain

active.

  1. Carrier diversity is part of a documented resiliency strategy.
  2. Specialized PSTN services are required.
  3. Commercial economics materially favor the existing carrier.
  4. The organization needs greater control over PSTN routing.

When Does BYOC Not Make Sense?

BYOC may be unnecessary when:

value

In those situations, native Zoom Phone may be the cleaner architecture.

Is Native Zoom Phone Simpler Than BYOC?

Usually, yes from an operational ownership perspective.

With native Zoom Phone, fewer organizations and infrastructure layers are involved in the PSTN path.

With BYOC P, troubleshooting can involve:

That does not make BYOC bad.

It means the flexibility comes with responsibility.

What Is the Support Ownership Problem?

Consider a failed inbound call.

In a BYOC environment, the failure could occur at:

PSTN

→ carrier

→ SIP trunk

→ customer SBC

→ network

→ Zoom cloud

→ Zoom Phone routing

→ user endpoint

Without good monitoring and documentation, each vendor can report that its own portion looks healthy.

The customer needs enough visibility to identify the failure domain.

Does BYOC Save Money?

It can.

But do not compare only the per minute rate.

A proper cost model includes:

A lower carrier rate can still produce a higher total operating cost.

What Is the Right BYOC Cost Question?

Do not ask:

"Is the carrier cheaper?"

Ask:

"What is the total three year cost of providing and supporting PSTN service through this architecture?"

That is the decision metric that matters.

Can We Use Different Carriers in Different Countries?

Potentially, yes.

BYOC is particularly relevant for global organizations that need different carrier strategies by geography.

Zoom's premises architecture allows organizations to establish regional SIP trunk connections and recommends placing premises equipment appropriately for the corresponding regions.

Design regional failure domains intentionally.

Can We Use Multiple BYOC Carriers?

An enterprise can design multiple carrier relationships where supported and appropriate.

The reason should be clear.

Possible goals include:

More carriers also mean more operational relationships.

Numbers, formats and call routing

Can We Use Zoom Native Numbers and BYOC Numbers Together?

Yes.

Zoom's current dial plan documentation supports environments containing both Zoom native numbers and BYOC P numbers.

Routing can depend on the calling number and assigned package.

This makes phased migrations and mixed carrier environments possible.

How Does Zoom Know Which Carrier to Use?

Zoom's dial plan logic identifies whether a number is associated with native Zoom Phone or BYOC.

For BYOC P numbers, calls can be routed through the configured BYOC SIP trunk.

For native Zoom numbers, calls use Zoom's PSTN service according to the applicable configuration.

What Number Format Does BYOC Premises Use?

Zoom's current BYOC P documentation requires calls through BYOC P trunks to use E.164 formatting.

Example:

`+13125551212`

rather than a localized format such as:

`3125551212`

or:

`9 1 312 555 1212`

The actual example above is fictitious.

Number normalization should be designed before production cutover.

What Is E.164?

E.164 is the international telephone numbering format commonly represented with:

plus sign

Using a standardized format makes global dial plan behavior more predictable.

Does BYOP Require E.164?

Not in the same way.

Zoom's current dial plan documentation says BYOP P can use a private numbering plan and does not require E.164 signaling in the same way BYOC P does.

That is logical because BYOP may be carrying private extension traffic between Zoom and an existing PBX.

Can BYOP Preserve Our Existing Extension Dialing?

Yes.

That is one of its important migration use cases.

A company might have:

Zoom users on extensions 2000 through 2999

and

legacy PBX users on extensions 3000 through 3999

BYOP can help create routing between those environments while migration continues.

The actual ranges should be planned to avoid conflicts.

Migration and coexistence

Can We Migrate One Department at a Time?

Yes.

BYOP can be particularly useful for phased migration.

For example:

Phase 1

Legacy PBX remains primary.

Phase 2

IT and pilot users move to Zoom Phone.

Phase 3

Office departments move to Zoom.

Phase 4

Remote offices move.

Phase 5

Special analog or legacy services are addressed.

Phase 6

PBX is retired.

During the transition, BYOP can support controlled interoperability.

Do We Need BYOP Forever?

Not necessarily.

BYOP can be a migration architecture rather than a permanent architecture.

This distinction matters.

If the end state is full Zoom Phone, define a retirement milestone for the legacy PBX and SBC dependency.

Otherwise, temporary hybrid infrastructure has a habit of becoming permanent.

When Should BYOP Be Permanent?

Potentially when a real business requirement remains.

Examples might include:

Document why the PBX remains.

Can BYOC Help With a Migration to Zoom Phone?

Yes.

Zoom explicitly describes BYOC P as supporting organizations that want to use existing PSTN carriers while moving to Zoom Phone.

This can separate two migration events:

PBX migration

from

carrier migration

That can reduce the number of simultaneous changes during a cutover.

Why Is Separating PBX Migration From Carrier Migration Useful?

A traditional migration might change all of these at once:

That creates a large failure domain.

BYOC can let the organization move call control to Zoom while keeping the carrier stable.

The carrier can be changed later if desired.

Number ownership and portability

Can We Move From BYOC to Zoom Native Later?

Yes.

Zoom supports porting BYOC numbers to native Zoom Phone where eligible.

This means BYOC does not necessarily lock the organization into the third party carrier forever.

Plan the eventual number ownership strategy from the beginning.

Can We Move Zoom Native Numbers to BYOC Later?

Zoom's current Number Management capabilities also support migration workflows from native Zoom Phone numbers to BYOC Premises or BYOC Cloud.

Zoom documents an automated migration process that can preserve number assignments, call logs, SMS history, and user associations when the required migration process is followed.

This makes carrier strategy more flexible than many administrators assume.

Who Owns the Phone Number in BYOC?

For BYOC Premises, Zoom's Number Management describes the number as customer owned through a third party carrier and uploaded to the Zoom account by the customer.

For BYOC Cloud, the number is provided through the connected certified provider.

Administrators should still document the contractual and porting ownership of every number.

Why Does Number Ownership Matter?

Because numbers are business assets.

A company should know:

Do not wait for a migration emergency to discover nobody knows who controls the main number.

SMS, international, toll free, fax and analog

Can BYOC Support SMS?

Zoom currently documents SMS support for eligible US and Canada BYOC numbers under applicable requirements.

SMS availability is not automatic for every BYOC number.

Review:

Treat messaging as its own migration workstream.

Can BYOC Support International Calling?

Yes, subject to Zoom policy, carrier capability, account configuration, country rules, and licensing.

Zoom provides administrative controls for international and special destination calling in BYOC environments.

International calling should be deliberately authorized rather than broadly enabled without policy.

What About Toll Free Numbers?

Toll free numbers require special attention during carrier and porting changes.

Inventory:

Do not treat toll free numbers as ordinary local DIDs.

What About Fax?

Fax should be evaluated separately.

Do not assume a SIP voice architecture automatically guarantees reliable fax behavior.

Inventory:

Decide whether fax should migrate to a cloud fax service rather than follow the voice architecture.

What About Analog Devices?

Analog devices are frequently the hidden reason a PBX cannot simply be turned off.

Examples include:

Each should be inventoried and given an explicit migration plan.

Do not assume BYOP is automatically the long term solution for all analog equipment.

Resilience and failover

Does BYOC Improve Redundancy?

It can, but only if the architecture actually removes a failure mode.

Adding another carrier does not create useful redundancy if both paths share:

Draw the complete path.

What Should a Resilient BYOC Premises Design Consider?

Consider:

Zoom supports multiple SBCs in route groups and can use OPTIONS based health checks and alternate routing behavior in supported configurations.

What Are Route Groups?

Route Groups define groups of SBCs and routing behavior in Zoom's BYOC and BYOP architecture.

They help determine which SBC receives outbound calls.

With multiple SBCs, routing can support sequential behavior or load distribution depending on configuration.

What Are SIP Groups?

SIP Groups associate telephone numbers and routing paths with the appropriate Route Groups.

A simplified model is:

Phone number

→ SIP Group

→ Route Group

→ SBC

→ carrier or PBX

Understanding these objects is fundamental to administering BYOC P.

What Happens if an SBC Fails?

SIP OPTIONS-based health monitoring between the SBC and Zoom is the usual mechanism, but the exact behaviour is a function of your SBC platform and your Route Group configuration. Confirm it against Zoom's current configuration guide and your SBC vendor's documentation rather than assuming a default.

If an SBC becomes unavailable, routing can move to another SBC in the Route Group according to the configured behavior.

Do not assume failover works merely because two SBCs exist.

Test it.

What Should We Test for SBC Failover?

Test controlled scenarios such as:

Validate both inbound and outbound calling.

Network and security

Does BYOC Use Encryption?

Zoom's current BYOC P Internet peering documentation states that TLS 1.2 and SRTP are used to secure communications between customer SBCs and the Zoom environment.

Certificate management and security policy therefore become part of the operating model.

Can BYOC Use a Private Circuit?

Yes.

Zoom supports private circuit connectivity for applicable premises peering deployments.

The documented model requires appropriate private connectivity and BGP peering using public ASNs and public IP addresses.

This is an enterprise network architecture project, not simply a Zoom portal setting.

Is a Private Circuit Better Than Internet Peering?

Not automatically.

Internet peering can provide:

Private connectivity can be attractive where organizations require:

The business requirement should drive the choice.

Can We Use SD WAN With BYOC?

Potentially.

But voice routing, SBC placement, public IP behavior, NAT, failover, and media paths must be understood.

Do not let an SD WAN policy move a production SIP session unpredictably between egress paths without testing.

What Firewall Requirements Apply?

BYOC P requires deliberate network and firewall design.

Review current Zoom documentation for:

Also review the SBC vendor's requirements.

Do not build a BYOC firewall policy from a generic "open SIP" checklist.

Should the SBC Sit Behind NAT?

Follow Zoom and the SBC vendor's supported architecture.

The public IP relationship and SIP signaling behavior must be predictable.

Complex or unstable NAT behavior can make voice troubleshooting extremely difficult.

What About Certificates?

TLS based SIP connectivity requires certificate planning.

Document:

A certificate expiration should never become an unexpected voice outage.

Who Should Monitor the SBC?

Someone must.

Define responsibility for:

If the answer is "the carrier probably monitors it," verify that contractually.

Can BYOC Create More Security Risk?

It adds infrastructure and therefore adds operational responsibilities.

Potential areas include:

Use supported SBCs and security best practices.

What Is Toll Fraud?

Toll fraud occurs when unauthorized users or systems generate chargeable telephone calls.

BYOC environments should include controls for:

Telephony is a financial security domain as well as a communications domain.

Emergency calling and outages

What About E911?

Emergency calling must be designed before production migration.

Do not assume retaining the old carrier means the old emergency calling behavior automatically survives.

Document:

E911 ownership should be explicit, and for BYOC numbers Zoom states plainly where it sits. Zoom's emergency services guidance says the address of record for each phone number is maintained by the carrier, that customers must work with their BYOC carrier to update or modify those addresses, and that Zoom's emergency address fields can collect and manage user and device information but do not change the carrier's number-to-address mapping. Read that twice before assuming a Zoom-side address change reaches the PSAP.

Can We Keep Our Existing E911 Provider?

Potentially, depending on the carrier and architecture.

But "keep" does not mean "do nothing."

Validate how emergency calls route through the BYOC architecture and how location information is supplied.

What Happens During a Carrier Outage?

That depends on the design.

Questions to answer before the outage:

users?

Write the failure procedure before you need it.

What Happens During a Zoom Outage?

BYOC does not automatically make Zoom Phone independent of Zoom.

If Zoom remains the call control platform, a Zoom service disruption can still affect calling.

Carrier diversity and platform diversity are different things.

Do not confuse them.

Call quality, codecs and media handling

Does BYOC Mean Calls Bypass the Zoom Cloud?

No.

Zoom Phone remains part of the call architecture.

Zoom's current peer to peer media documentation notes that PSTN calls, including calls using native or BYOC carriers, are routed through the Zoom cloud.

BYOC changes the PSTN carrier relationship, not the fact that Zoom Phone is the cloud communications platform.

Can BYOC Improve Call Quality?

Not inherently.

Call quality depends on:

A premium carrier does not repair bad office WiFi.

What Codecs Does Zoom Use for Premises Peering?

Zoom's current BYOC P and BYOP P call processing documentation lists preferred codecs including:

Codec negotiation and transcoding behavior should be considered when connecting legacy PBXs and carriers.

Can Transcoding Become a Problem?

Yes.

If systems do not share a compatible codec, an intermediary may need to transcode.

That can affect:

Include codec compatibility in the design review.

What About DTMF?

DTMF behavior should be tested.

This matters for:

A call can sound perfect while keypad input fails.

What About Caller ID?

Test both directions.

Verify:

Zoom provides configuration options involving SIP headers such as P Asserted Identity and diversion headers in applicable BYOC scenarios.

Carrier requirements can differ.

What About Call Forwarding?

Forwarded calls can expose interoperability issues.

Test:

Check caller ID presentation and carrier acceptance.

What About Call Recording?

Call recording requirements should be reviewed separately from carrier architecture.

Consider:

Do not assume carrier ownership determines recording behavior.

Zoom Contact Center

What About Contact Center?

BYOC can also be relevant to Zoom Contact Center.

Zoom's current BYOC P documentation applies to both Zoom Phone and Zoom Contact Center in applicable scenarios.

However, feature support can differ by product and integration.

Validate Contact Center requirements independently.

Can the Same Phone Number Be Assigned to Phone and Contact Center?

Treat a phone number as belonging to one product at a time. Plan number ownership and routing on that basis, and confirm the current behaviour in your own account before you design around sharing a number between Zoom Phone and Zoom Contact Center.

Choosing an architecture

Can BYOC Help During an Acquisition?

Yes.

Suppose Company A uses Zoom Phone and Company B still uses a legacy PBX and carrier.

A transition architecture can provide:

This can be much safer than forcing an immediate telecom consolidation.

What Should We Inventory Before Choosing BYOC?

Inventory:

The carrier decision should follow the inventory, not precede it.

What Should We Inventory Before Choosing BYOP?

Inventory:

Then determine what actually needs interoperability.

Should We Replace the PBX Instead of Integrating It?

Often, yes.

If the PBX exists only because nobody has planned its retirement, BYOP may simply preserve technical debt.

Ask:

What requirement prevents this workload from moving to Zoom Phone?

If there is no good answer, migration may be better than permanent integration.

What Is the Biggest BYOC Design Mistake?

Treating carrier retention as a purely procurement decision.

BYOC affects:

Procurement should be part of the decision, not the entire decision.

What Is the Biggest BYOP Design Mistake?

Failing to define the end state.

If BYOP is a migration bridge, put the PBX retirement target into the project plan.

Otherwise, the organization can end up supporting two phone systems indefinitely.

What Is the Best Migration Strategy?

For many organizations:

Discover

→ Inventory

→ Define end state

→ Choose carrier strategy

→ Build pilot

→ Configure SBC or Provider Exchange if needed

→ Validate dial plan

→ Validate E911

→ Test inbound and outbound calls

→ Test failure scenarios

→ Migrate users

→ Migrate numbers where required

→ Retire unnecessary infrastructure

The end state should be simpler than the starting state.

BYOC vs BYOP Decision Table

Requirement mapped to the architecture worth evaluating
Requirement Architecture to evaluate
Use Zoom native PSTN service Native Zoom Phone
Keep existing PSTN carrier BYOC
Keep carrier without a customer SBC where supported BYOC Cloud / Provider Exchange
Customer manages SBC and carrier trunk BYOC Premises
Connect Zoom users to existing PBX extensions BYOP Premises
Temporary PBX coexistence during migration BYOP Premises
Keep both existing carrier and PBX interoperability BYOC Premises plus BYOP Premises
Simplest cloud operating model Native Zoom Phone
Global carrier flexibility Evaluate BYOC
Existing strategic carrier agreement Evaluate BYOC
No permanent reason to retain the PBX Migrate rather than preserve BYOP

Worked examples

Example 1: Keep the Carrier, Replace the PBX

Company has:

Possible architecture:

Zoom Phone

→ BYOC Premises

→ customer SBC

→ existing carrier

The PBX can be retired while the carrier remains.

Example 2: Keep the PBX Temporarily

Company has:

Possible architecture:

Zoom Phone

↔ BYOP Premises

↔ legacy PBX

Users can be migrated in waves while extension interoperability remains available.

Example 3: Keep Carrier Without Managing SBCs

Company wants:

Possible architecture:

Zoom Phone

→ BYOC Cloud / Provider Exchange

→ participating provider

This can reduce operational complexity.

Example 4: Global Hybrid

Company has:

Possible architecture:

US

→ Zoom native

Region B

→ BYOC

Acquired office

→ temporary BYOP

There is no requirement that every site use an identical PSTN architecture if the operational model can support the differences.

Checklists

BYOC Readiness Checklist

Business

Numbers

Architecture

SBC

Network and Security

Calling

Resiliency

BYOP Migration Checklist

Frequently asked questions

What does BYOC mean in Zoom Phone?

BYOC means Bring Your Own Carrier. It lets an organization use Zoom Phone while retaining a third party PSTN carrier.

What does BYOP mean in Zoom Phone?

BYOP means Bring Your Own PBX. Zoom's premises architecture allows Zoom Phone to interoperate with an existing PBX through SBC infrastructure.

Is BYOC the same as BYOP?

No. BYOC connects Zoom Phone to a carrier. BYOP connects Zoom Phone to an existing PBX.

Do I need an SBC for Zoom BYOC?

For BYOC Premises, yes. The customer provides and administers supported SBC infrastructure. Provider Exchange and applicable BYOC Cloud models can avoid customer premises SBC hardware.

Can I keep my existing carrier with Zoom Phone?

Yes, through supported BYOC architectures.

Can I keep my existing PBX while moving users to Zoom Phone?

Yes. BYOP Premises can support hybrid PBX coexistence and extension dialing during an appropriate migration.

Can I use Zoom native numbers and BYOC numbers at the same time?

Yes. Zoom supports mixed environments.

Can I move BYOC numbers to native Zoom Phone later?

Eligible BYOC numbers can be ported to native Zoom Phone.

Can I move Zoom numbers to BYOC?

Zoom currently supports Number Management workflows for migrating eligible native Zoom numbers to BYOC Premises or BYOC Cloud.

Does BYOC save money?

It can, but total cost should include carrier service, SBCs, licensing, circuits, support, monitoring, engineering, security, and operations.

Is Zoom native calling easier to manage?

It is generally a simpler ownership model because it removes some carrier and customer SBC dependencies.

Does BYOC bypass the Zoom cloud?

No. Zoom Phone remains the cloud communications platform. Zoom's current documentation says PSTN calls using native or BYOC carriers remain cloud routed.

Can BYOC use private connectivity?

Zoom supports applicable private circuit peering for BYOC Premises, subject to its current technical requirements.

Can BYOC support SMS?

Zoom currently supports SMS for eligible US and Canada BYOC numbers under applicable requirements.

Can BYOC support international calling?

Yes, subject to the carrier, country, account policy, Zoom configuration, and regulatory requirements.

Can BYOP use private extension numbers?

Yes. Zoom's BYOP Premises dial plan can support private numbering between Zoom and the PBX.

Should BYOP be permanent?

Only if a continuing business or technical requirement justifies retaining the PBX. It can also be used as a temporary migration bridge.

References

Zoom's own documentation, first party only. Zoom, carriers and SBC vendors all change requirements; verify the current version before you build against any of it.

  1. Zoom — BYOC-P or BYOP-P Infrastructure Requirements— the source for the customer-administered SBC, the public IP for SIP trunk connectivity, TLS 1.2 with SRTP, and BGP peering with public ASNs on a private circuit.
  2. Zoom — BYOC-P or BYOP-P Deployment and Connectivity Options— codec support for premises peering: Opus, G.722, G.711 µ-law, G.711 A-law, G.729.
  3. Zoom — Zoom Phone Certified Hardware— the certified SBC list lives in the Session Border Controllers section: AudioCodes, Avaya, Cisco, Mitel, NextGen, Oracle, Ribbon, TE-Systems.
  4. Zoom — BYOC-P or BYOP-P Call Processing— BYOC-P requires E.164 in the Request-URI; BYOP-P accepts localised or E.164 up to 24 digits.
  5. Zoom — Managing dial plan functionality— outbound routing is determined by the package assigned to each user; where a user has both native and BYOC-P packages, calls route according to the calling number.
  6. Zoom — Using Number Management for managing phone numbers— defines BYOC - Premises and BYOC - Cloud as distinct number types.
  7. Zoom — Migrating phone numbers across Zoom Phone and BYOC services in Number Management— native to BYOC migration preserves number assignments, call logs, SMS history and user associations.
  8. Zoom — Requesting a BYOC Number Port— the reverse direction, BYOC to native, is a port request rather than the automated migration.
  9. Zoom — Activating SMS for BYOC phone numbers— SMS cannot be activated for non-US/CA BYOC numbers, US/CA toll-free or wireless numbers, or numbers with 10DLC registration pending.
  10. Zoom — Enabling International and Special Destination Calls— BYOC destinations are enabled deliberately at account, site, group or extension level.
  11. Zoom — Setting Up Phone Provider Exchange— Provider Exchange brings a carrier in with no on-premises hardware required.
  12. Zoom Technical Library — Bring Your Own Carrier: Cloud Peering (BYOC-C)— cloud peering works without on-premises hardware such as an SBC.
  13. Zoom Technical Library — Regulatory Considerations in the United States— for BYOC numbers the address of record is maintained by the carrier; Zoom's emergency address fields do not override that mapping.
  14. Zoom — Adding SBCs to Existing Route Groups— Route Groups and SIP Groups are the objects that carry this design.
Ask ADAM Pulse whether BYOC, BYOP or native Zoom Phone fits

USA Telecom is a Zoom partner. ADAM Pulse scopes carrier, SBC and emergency-calling ownership before anyone buys a trunk they then have to support.

Prepared by ADAM Pulse (USA Telecom Consulting LLC)

Managed Zoom Phone and network services, SDVOSB. We run BYOC readiness assessments, design and coordinate SBC and SIP trunk builds, plan BYOP coexistence and PBX retirement, and hold the carrier relationship so support ownership is decided before an outage rather than during one. Support: (888) 989-4872 · support@adampulse.us