Table A-1: Regional instances resolve to the following IP addresses ...................................................49
Table A-2: Regional Media Traffic and Ports .........................................................................................49
Zoom Phone Carrier Peering 5 AudioCodes SBCs
Zoom Phone Carrier Peering
This page is left intentionally blank.
Configuration Note 6 Document #: LTRT-29341
Configuration Note Notices
Notice
Information contained in this document is believed to be accurate and reliable at the time of
printing. However, due to ongoing product improvements and revisions, AudioCodes cannot
guarantee accuracy of printed material after the Date Published nor can it accept responsibility
for errors or omissions. Updates to this document can be downloaded from
This document is subject to change without notice.
Date Published: March-10-2021
WEEE EU Directive
Pursuant to the WEEE EU Directive, electronic and electrical waste must not be disposed of
with unsorted waste. Please contact your local recycling authority for disposal of this product.
Customer Support
Customer technical support and services are provided by AudioCodes or by an authorized
AudioCodes Service Partner. For more information on how to buy technical support for
AudioCodes products and for contact information, please visit our at
Each abbreviation, unless widely used, is spelled out in full when first used.
.
Zoom Phone Carrier Peering 7 AudioCodes SBCs
Zoom Phone Carrier Peering
Related Documentation
Document Name
Mediant 500 Gateway & E-SBC User's Manual
Mediant 500L Gateway & E-SBC User's Manual
Mediant 800 Gateway & E-SBC User's Manual
Mediant 1000B Gateway & E-SBC User's Manual
Mediant 2600 E-SBC User's Manual
Mediant 4000 SBC User's Manual
Mediant 9000 SBC User's Manual
Mediant Software SBC User's Manual
Gateway and SBC CLI Reference Guide
SIP Message Manipulation Reference Guide
AudioCodes Configuration Notes
Document Revision Record
LTRT Description
29340 Initial document release.
29341 Added call setup rule for outgoing messages towards Zoom; added message manipulation
rule towards Zoom.
Documentation Feedback
AudioCodes continually strives to produce high quality documentation. If you have any
comments (suggestions or errors) regarding this document, please fill out the Documentation
Feedback form on our website at https://online.audiocodes.com/documentation-feedback
.
Configuration Note 8 Document #: LTRT-29341
Configuration Note 1. Introduction
1 Introduction
This document describes how to connect Zoom Phone System to multiple customers using
AudioCodes' SBC in Hosting mode and refers to the AudioCodes SBC configuration only.
This document is intended for IT or telephony professionals.
Note:To zoom in on screenshots of Web interface configuration examples,
press Ctrl and +.
1.1 About the Zoom Phone System
Zoom Phone is a fully featured cloud PBX designed with security, reliability, scalability and
centralized management in mind. Zoom Phone was built from the ground up to seamlessly
integrate with the Zoom Collaboration platform to deliver a feature-rich UCaaS user
experience. Zoom Phone offers various deployment options providing organizations with the
flexibility to migrate and deploy the platform in a manner that best suits their requirements.
Zoom Phone leverages global carrier relationships to deliver PSTN connectivity in many
regions of the world offering phone number portability to Zoom in most regions thereby
simplifying the telephony environment with one partner for your PBX and PSTN connectivity
needs. While native Zoom Phone meets the requirements of most organizations, it’s
understood that some organizations have environments that may need additional
functionality for global support or migration strategies. For organizations with such diverse
requirements of their telephony environments, Zoom’s Premise Peering solution is offered.
Zoom Phone Premise Peering provides organizations with flexibility and seamless options to
migrate their voice workloads to the cloud. This is accomplished by providing two connection
types; Premise Peering PSTN (formally referred to as Bring Your Own Carrier - BYOC) and/or
Premise Peering PBX (formally referred to as Bring Your Own PBX - BYOP). Zoom Phone
Premise Peering PSTN enables organizations to leverage their existing telephony carrier
PSTN environment for Zoom Phone connectivity. Using this functionality organizations can
connect Zoom Phone with virtually any telephony carrier.
1.2 About AudioCodes SBC Product Series
AudioCodes' family of SBC devices enables reliable connectivity and security between the
enterprise's VoIP network and the service provider's VoIP network.
The SBC provides perimeter defense as a way of protecting enterprises from malicious VoIP
attacks; mediation for allowing the connection of any PBX and/or IP-PBX to any service
provider; and Service Assurance for service quality and manageability.
Designed as a cost-effective appliance, the SBC is based on field-proven VoIP and network
services with a native host processor, allowing the creation of purpose-built multiservice
appliances, providing smooth connectivity to cloud services, with integrated quality of service,
SLA monitoring, security and manageability. The native implementation of the SBC provides
a host of additional capabilities that are not possible with standalone SBC appliances such
as VoIP mediation, PSTN access survivability, and third-party value-added services
applications. This enables enterprises to utilize the advantages of converged networks and
eliminate the need for standalone appliances.
AudioCodes' SBC is available as an integrated solution running on top of its field-proven
Mediant Media Gateway and Multi-Service Business Router platforms, or as a software-only
solution for deployment with third-party hardware. The SBC can be offered as a Virtualized
SBC, supporting the following platforms: Hyper-V, AWS, AZURE, AWP, KVM and VMWare.
Zoom Phone Carrier Peering 9 AudioCodes SBCs
Zoom Phone Carrier Peering
This page is intentionally left blank.
Configuration Note 10 Document #: LTRT-29341
Configuration Note 2. Configuring Zoom Phone System
2 Configuring Zoom Phone System
For configuring the Zoom Phone System, refer to Zoom Help Center at
• Contact your Zoom Representative to enable SIP groups and set up SIP trunks
that are directed toward your SBC for your Zoom Phone account.
• Make sure you have Zoom Portal admin credentials. Be aware that each
customer needs to have a Zoom Phone admin account and all Zoom Phone
related configuration will be done by the customer and not by the carrier.
Zoom Phone Carrier Peering 11 AudioCodes SBCs
Zoom Phone Carrier Peering
This page is left intentionally blank.
Configuration Note 12 Document #: LTRT-29341
Configuration Note 3. Configuring AudioCodes' SBC
Internet
Cust omer 1
Manag ement
Stat ion (OAMP)
Cust omer 1 N etwo rk
LAN
Firew all
Cli ent
Cli ent
Manag ement
Stat ion (OAMP)
Cust omer 2 N etwo rk
LAN
Firew all
Cli ent
Cli ent
Cust omer 2
ITSP
PSTN
ITSP
PSTN
Session Border Controller
Cust omer 1
Cli ent
Cust omer 2
Cli ent
suite of
3 Configuring AudioCodes' SBC
This section shows how to configure AudioCodes' SBC for internetworking with Zoom Phone
System. The figure below shows an example of the connection topology for the Zoom Phone
System Premise Peering Mode. Multiple connection entities are shown in the figure:
Note: This document shows how to pair between the AudioCodes' hosting SBC and
the Zoom Phone System with a Customers SIP Trunks. For detailed configuration of
other entities in the deployment such as the SIP Trunk Provider and the local IP-PBX,
see AudioCodes' SIP Trunk Configuration Notes (in the Interoperability
documents).
3.1 Prerequisites
Before you begin configuration, make sure you have obtained the following for each Hosting
SBC you wish to pair:
Public IP address
Public certificate that is issued by one of the Zoom supported CAs
Zoom Phone Carrier Peering 13 AudioCodes SBCs
Zoom Phone Carrier Peering
Pro xy Set
(Customer1
SIP Trunk)
Pro xy Set
(Customer2
SIP Trunk)
Pro xy Set
(Customer3
SIP Trunk)
Phone System
IP Group
(Customer1
SIP Trunk)
IP Group
(Customer2
SIP Trunk)
IP Group
(Customer3
SIP Trunk)
SIP
Interface
SBC
SIP
Interface
IP Group
SI P T r unk
SI P T r unk
SI P T r unk
3.2 Validate AudioCodes SBC License
Zoom has successfully conducted validation tests with AudioCodes' Mediant SBC
Ver. 7.20A.258. For implementing the configuration described in this document, the
AudioCodes SBC must be installed with a License Key that includes the following features:
Number of SBC sessions (based on requirements)
Transcoding sessions (only if media transcoding is needed)
Coders (based on requirements)
For more information about the License Key, contact your AudioCodes sales representative.
3.3 SBC Configuration Concept
The figure below illustrates the underlying concept of the configuration of AudioCodes’ SBC
device.
Figure 3-2: SBC Configuration Concept
The routing from the SIP Trunks to Zoom Phone System and vice versa is dependent on the
Class 4 switch routing method. The routing decision can be based on:
Customer DID Range
Trunk Context (TGRP)
IP Interface
SIP Interface (UDP/TCP Port)
Host name
The configuration shown in this document is based on a Customer DID Range using a Dial
Plan. For more information, see the AudioCodes' Documentation suite.
Configuration Note 14 Document #: LTRT-29341
Configuration Note 3. Configuring AudioCodes' SBC
Management
Station (OAMP )
LAN
WAN
DMZ
LAN Port
LAN Port
Vlan ID 1
Vlan ID 2
Session B order Con troller
Firew all
Phone System
ITSP1
ITSP2
ITSP3
3.4 Configure IP Network Interfaces
This section describes how to configure the SBC's IP network interfaces. There are several
ways to deploy the SBC:
SBC interfaces with the following IP entities:
• Zoom Phone System
• Customers SIP Trunks
Physical connection: The type of physical connection depends on the method used to
connect to the Enterprise's network. In this example topology, SBC connects to the
LAN and DMZ using dedicated Ethernet ports (i.e., two ports and two network cables
are used).
SBC also uses two logical network interfaces:
• LAN (VLAN ID 1)
• DMZ (VLAN ID 2)
Figure 3-3: Network Interfaces in the Topology with all entities on the WAN
3.4.1 Configure LAN and WAN VLANs
This section describes how to define VLANs for each of the following interfaces:
LAN Interface (assigned the name "LAN_IF")
WAN Interface (assigned the name "WAN_IF")
To configure VLANs:
1. Open the Ethernet Device table (Setup menu > IP Network tab > Core Entities
folder > Ethernet Devices).
2. There will be one existing row for VLAN ID 1 and underlying interface GROUP_1.
3. Add another VLAN ID 2 for the WAN side.
Figure 3-4: Configured VLANs in the Ethernet Device Table
Zoom Phone Carrier Peering 15 AudioCodes SBCs
Loading...
+ 35 hidden pages
You need points to download manuals.
1 point = 1 manual.
You can buy points or you can get point for every manual you upload.