Zoom Gateway

[[File:VoIPms_Zoom_BYOC.png|300px|right|link=https://www.zoom.com/|Zoom BYOC with VoIP.ms]]

This guide explains how to configure '''Zoom Phone BYOC''' ''(Bring Your Own Carrier)'' with '''VoIP.ms''', allowing you to use Zoom Phone as your business phone interface while keeping VoIP.ms as the underlying PSTN carrier for inbound and outbound calling.

In simple terms: Zoom becomes the phone-system interface, while VoIP.ms remains the carrier behind the scenes.

= Why Zoom BYOC can be useful for VoIP.ms customers? =

: Zoom BYOC lets customers use Zoom Phone as the collaboration/UC platform while keeping VoIP.ms as the PSTN carrier for inbound/outbound calling. Zoom becomes the phone-system interface; VoIP.ms remains the carrier behind the scenes.

: Zoom supports BYOC through models such as '''Premises Peering''', where a customer connects Zoom Phone to their own carrier through an SBC, and '''Cloud Peering / Provider Exchange''', which is designed to simplify carrier connectivity without on-premise hardware in some cases. Zoom describes Provider Exchange as a way to connect preferred providers directly from the Zoom portal, with "no hardware" and "no infrastructure" for that model.

: <h3> 1. Keep VoIP.ms pricing and flexibility </h3>

:: Customers who like VoIP.ms because of its pay-as-you-go model, DID availability, porting flexibility, international coverage, and granular routing can continue benefiting from that while using Zoom Phone for the user experience.

:: This is especially attractive for customers who already use Zoom heavily but do not want to move all phone numbers and call traffic to Zoom's native calling plans.

: <h3> 2. Better fit for customers with complex PSTN needs </h3>

:: Zoom itself positions Provider Exchange/BYOC as useful for businesses with more complex PSTN needs and access to diverse providers. For VoIP.ms customers, that could mean:

:::* multiple countries or regions;
:::* specific DID inventory needs;
:::* custom routing;
:::* cost-sensitive outbound calling;
:::* reseller or multi-location deployments;
:::* keeping existing numbers with minimal disruption.

: <h3> 3. Easier migration to Zoom Phone </h3>

:: Some companies want Zoom Phone, but they are hesitant to port numbers away from their existing provider right away. BYOC can reduce that friction.

:: They can move users to Zoom Phone while keeping VoIP.ms as the underlying carrier. That can make the migration more gradual and less risky.

: <h3> 4. Preserve existing carrier relationship </h3>

:: For customers already satisfied with VoIP.ms support, billing, rates, number inventory, or API capabilities, BYOC lets them avoid a full carrier replacement.

:: This matters for MSPs and IT providers who already built processes around VoIP.ms, including provisioning, porting, billing, and support.

: <h3> 5. Combine Zoom's UC features with VoIP.ms telecom control </h3>

:: Zoom Phone brings the UCaaS experience: users, call queues, auto receptionists, admin portal, Zoom ecosystem, meetings/chat integration, and mobile/desktop apps. Zoom notes that BYOC-C allows businesses to keep Zoom Phone cloud PBX features such as call queues, auto receptionists, and number assignment while the telephony connection is handled by the chosen provider.

:: VoIP.ms brings carrier-level flexibility: SIP trunking, DID management, termination, origination, porting, routing, and API-driven control.

:: Together, the value proposition is: use Zoom for the employee phone experience, and VoIP.ms for the carrier layer.

: <h3> 6. Useful for MSPs and resellers </h3>

:: This is especially powerful for VoIP.ms partners who already support SMB customers. Instead of positioning only "VoIP.ms Cloud PBX vs. Zoom Phone," the MSP can offer a hybrid model:

:: ''"You can use Zoom Phone as your business phone interface, while we keep your numbers, routing, and PSTN service managed through VoIP.ms."''

:: That creates a more consultative offer and helps partners serve customers who are already standardized on Zoom.

: <h3> Best customer profiles </h3>

:: Zoom BYOC with VoIP.ms would be most useful for:

:::* companies already using Zoom Workplace heavily;
:::* customers considering Zoom Phone but wanting to keep VoIP.ms;
:::* multi-location businesses;
:::* MSP-managed customers;
:::* organizations with international DIDs or custom routing needs;
:::* customers sensitive to bundled calling-plan pricing;
:::* businesses that want UCaaS simplicity without losing carrier flexibility.

<div style="margin-left:50px;
            padding:5px;
            border-left: 6px solid rgb(255, 165, 0, 0.9);
            box-shadow: 8px 6px 9px -2px #f2f2f2;
            background-color: rgba(255, 165, 0, 0.08);
            width:70vw;">

'''Important note'''
: There are different BYOC models. '''Premises Peering''' typically requires an SBC and more technical configuration, while '''Provider Exchange / Cloud Peering''' is intended to simplify the experience and may avoid on-premise hardware depending on provider participation. Zoom's documentation distinguishes these models, so the exact deployment path depends on whether VoIP.ms integrates directly as a Zoom Provider Exchange partner or supports customers through a customer-managed SBC model.
</div>

= How to Get Started =

: <h3> 1. Contact Sales </h3>

:: To enable Zoom BYOC with your VoIP.ms account, reach out to our sales team at [mailto:sales@voip.ms sales@voip.ms]. They will help you determine the best deployment model for your needs and get the integration activated.

: <h3> 2. Zoom Account Configuration ''(Coming Soon)'' </h3>

<div style="margin-left:50px;
            padding:5px;
            border-left: 6px solid rgb(208, 56, 45, 0.8);
            box-shadow: 8px 6px 9px -2px #f2f2f2;
            background-color: rgba(208, 56, 45, 0.08);
            width:70vw;">

🚨 '''In Progress'''
: This step is currently '''in progress'''. Detailed instructions will be added here soon.
</div>

= Configuration =

Setting up Zoom BYOC with VoIP.ms involves two directions of call flow: routing inbound calls from VoIP.ms toward Zoom, and authenticating outbound calls from Zoom toward VoIP.ms.

== VoIP.ms → Zoom ==

: In this direction, you route calls from a desired DID in your VoIP.ms account to Zoom by pointing the DID to a Zoom SIP-URI.

: <h3> 1. Create the SIP-URI </h3>

:: In your VoIP.ms Customer Portal, go to '''DID Numbers''' >> '''SIP URI's''' and create a SIP-URI using the following format:

::: <code>sip:+1{DID}@zgw0.vcn.ms</code>

:: Replace <code>{DID}</code> with the DID number you want to use.

:: [[File:Zoom_VoIPms_SIP_URI_Menu_1.png|border|600px|none]]

: <h3> 2. Route the DID to the SIP-URI </h3>

:: Direct calls from your desired DID to the SIP-URI created in the previous step, so inbound calls are delivered to Zoom.

== Zoom → VoIP.ms ==

: In this direction, you create a sub-account with IP-based authentication so Zoom can send outbound calls through VoIP.ms.

: <h3> 1. Create a Sub Account with IP-based authentication </h3>

:: In your VoIP.ms Customer Portal, go to '''Sub Accounts''' >> '''Create Sub Account''' and configure it as follows:

:::# Set '''Authentication type''' = '''Static IP Authentication (SIP only)'''
:::# Set the value of '''IP Address or Fully Qualified Domain Name''' = <code>zgw0.vcn.ms</code>
:::# Define a '''Username''' (any name you want)
:::# Set '''CallerID Number''' = '''I use a system capable of passing its own CallerID'''

:: [[File:Zoom_VoIPms_Create_Sub_Account.png|border|600px|none]]

= Resources =

* [https://www.zoom.com/en/products/voip-phone/ Zoom Phone]
* [https://support.zoom.com/hc/en/article?id=zm_kb&sysparm_article=KB0061434 Zoom – Bring Your Own Carrier (BYOC)]
* [https://wiki.voip.ms/article/Sub_Accounts VoIP.ms – Sub Accounts]
* [https://wiki.voip.ms/article/Choosing_Server VoIP.ms – Choosing a Server]