© 2021 Ribbon Communications Operating Company, Inc. © 2021 ECI Telecom Ltd. All rights reserved. The compilation (meaning the collection, arrangement and assembly) of all content on this site is protected by U.S. and international copyright laws and treaty provisions and may not be used, copied, reproduced, modified, published, uploaded, posted, transmitted or distributed in any way, without prior written consent of Ribbon Communications Inc.
The trademarks, logos, service marks, trade names, and trade dress (“look and feel”) on this website, including without limitation the RIBBON and RIBBON logo marks, are protected by applicable US and foreign trademark rights and other proprietary rights and are the property of Ribbon Communications Operating Company, Inc. or its affiliates. Any third-party trademarks, logos, service marks, trade names and trade dress may be the property of their respective owners. Any uses of the trademarks, logos, service marks, trade names, and trade dress without the prior written consent of Ribbon Communications Operating Company, Inc., its affiliates, or the third parties that own the proprietary rights, are expressly prohibited.
This document outlines the configuration best practices for the Ribbon solution covering the Ribbon SBC Edge when deployed with Zoom Phone Local Survivability (ZPLS).
A Session Border Controller (SBC) is a network element deployed to protect SIP-based Voice over Internet Protocol (VoIP) networks. Early deployments of SBCs were focused on the borders between two service provider networks in a peering environment. This role has now expanded to include significant deployments between a service provider's access network and a backbone network to provide service to residential and/or enterprise customers.
The SBC Edge (SBC 1000/2000) addresses the next-generation needs of SIP communications by delivering embedded media transcoding, robust security, and advanced call routing in a high-performance, small form-factor device enabling service providers and enterprises to quickly and securely enhance their network by implementing services like SIP Trunking, secure Unified Communications and Voice over IP (VoIP).
The SBC Edge provides a reliable, scalable platform for IP interconnect to deliver security, session control, bandwidth management, advanced media services and integrated billing/reporting tools in an SBC appliance. This versatile series of SBCs can be deployed as peering SBCs, access SBCs or enterprise SBCs (eSBCs). The SBC product family is tested for interoperability and performance against a variety of third-party products and call flow configurations in the customer networks.
SBC 1000 and SBC 2000 are represented as SBC Edge in the subsequent sections.
Zoom Phone is a cloud-based service that is dependent on IP connectivity to Zoom’s datacenters. Customers that are using the Zoom Phone solution at corporate locations are encouraged to deploy redundant and reliable internet connectivity with sufficient bandwidth at each corporate office as a base requirement.
For certain business locations maintaining telephony service in the event of an outage is critical. Zoom can offer a survivability solution of basic telephony services in order to provide an additional layer of protection to ensure business continuity. An outage can be the result of an internet service failure at a business location or a failure in multiple Zoom datacenters that prevent client devices from reaching Zoom Phone components.
The Zoom Phone Local Survivability (ZPLS) module leverages the platform and Operating System (OS) provided by the Zoom Node and is distributed as a Linux-based appliance that is spun up on an on-premises VMware ESXi host. The ZPLS module does not affect the phone service during normal operations. Phone clients and devices in survivable Phone Sites register to the corresponding ZPLS module and are able to maintain a subset of Phone features when connectivity to Zoom Phone is lost. When connectivity to the Zoom Phone cloud returns, clients and devices re-register back to the cloud. During the outage, neither the administrator nor the end user is required to take any action to enable survivability. The failover and fallback process is seamless and automatic.
The interoperability compliance testing focuses on verifying inbound and outbound call flows between the Ribbon SBC Edge & ZPLS.
This guide contains the following configuration sections:
Captures the Zoom Phone Local Survivability configuration.
It is not the goal of this guide to provide detailed configurations that will meet the requirements of every customer. Use this guide as a starting point and build the SBC configurations in consultation with network design and deployment engineers.
This is a technical document intended for telecommunications engineers with the purpose of configuring both the Ribbon SBCs and the third-party product.
To perform this interop, you need to:
This configuration guide is offered as a convenience to Ribbon customers. The specifications and information regarding the product in this guide are subject to change without notice. All statements, information, and recommendations in this guide are believed to be accurate but are presented without warranty of any kind, express or implied, and are provided “AS IS”. Users must take full responsibility for the application of the specifications and information in this guide.
The following aspects are required before proceeding with the interop:
The sample configuration in this document uses the following equipment and software:
Requirements
Appliance/Application/Tool | Software Version | |
---|---|---|
Ribbon Communications | SBC 2000 | 11.0.1 build 634 |
Zoom | Zoom Phone Local Survivability (ZPLS) | 1.8.0.73 |
Zoom Client | 5.11.10 (8200) | |
PSTN Phone | Jitsi | 2.10.5550 |
Administration and Debugging Tools | Ribbon LX Tool | 2.1.0.6 |
This section covers the Ribbon SBC Edge deployment topology and the Interoperability Test Lab Topology.
This deployment topology depicts the ZPLS on a host server which is geographically different from the SBC Edge location.
Ribbon SBC Edge Deployment Topology
This deployment topology depicts ZPLS installed as VM on ASM (Application Solution Module) within the SBC Edge 1K/2K platform.
Ribbon SBC Edge deployment topology on SBC ASM
The following lab topology diagram shows connectivity between the Ribbon SBC Edge on a virtual platform and Zoom Phone Local Survivability.
SBC Edge and ZPLS interoperability Test Lab Topology
The following lab topology diagram shows connectivity between Ribbon SBC Edge and Zoom Phone Local Survivability on SBC's ASM (Application Solution Module).
Interoperability Test Lab topology for ZPLS on SBC ASM
The sections in this document follow the sequence below. The reader is advised to complete each section for successful configuration.
The following SBC Edge configurations are included in this section:
TLS Configuration between SBC Edge and ZPLS
SBC 2000 Front Panel
SBC 2000 is connected to the network as follows:
Ethernet 1: RJ45 "1" is connected towards the PSTN leg.
Ethernet 2: RJ45 "2" is connected towards the ZPLS leg.
USB 1: USB - LAN adapter used to connect ASM to network.
USB 2: Connect the keyboard.
Deployment Topology : Co-located & Centralized would make use of the USB ports to connect to the network. USB-LAN adapter would be required to connect ASM to network on SBC 2000.
SBC 1000 has a dedicated ASM port to connect to enterprise network.
SBC 1000 Front Panel
SBC 1000 is connected to the network as follows:
Ethernet 1: RJ45 "1" is connected towards the PSTN leg.
Ethernet 2: RJ45 "2" is connected towards the ZPLS leg.
ASM port: RJ45 "1" is connected to enterprise network.
USB 2: Connect the keyboard.
Configure Ethernet 1 and Ethernet 2 of SBC 1000/2000 with the IP as follows:
Navigate to Node Interfaces > Logical Interfaces.
Logical Interfaces
Ethernet 1
Ethernet 2
To configure Ethernet 1 and Ethernet 2 of SBC SWe Edge, navigate to Networking Interfaces > Logical Interfaces.
Static routes are used to create communication to remote networks. In a production environment, static routes are mainly configured for routing from a specific network to a network that can only be accessed through one point or one interface (single path access or default route).
Static routes need to be added towards the Eth1 interface 172.16.X.X (PSTN) and the Eth2 interface 172.16.X.X (ZPLS).
Default static route is towards the Eth1, which is in a private network.
Static Routes
Prerequisites:
Request a certificate for the SBC and configure it based on the example using GoDaddy as follows:
Step 1: Generate a Certificate Signing Request and obtain the certificate from a Certificate Authority (CA).
Use the generated CSR text from the clipboard to obtain the certificate.
Generate Certificate Signing Request
Step 2: Deploy the Root/Intermediate and SBC certificates on the SBC.
After receiving the certificates from the certificate authority, install the SBC Certificate and the Root/Intermediate certificates as follows:
Validate the certificate is installed correctly.
Trusted CA certificate table
Validate certificate
Configure the SBC Edge with ZPLS using the Easy Config Wizard.
Easy Config Wizard
Fill in the details for Step 1 as follows:
Enter a value for SIP sessions as per the requirement. The value can be up to 960.
Step 1
Fill in the details for Step 2 as follows:
Step 2
Review the configurations in Step1 and Step 2, and click on the Finish button.
Step 3
The Message Manipulation SAVP is used for the following purposes:
Go to Settings > SIP > Message Manipulation >Message Rule Tables. Click the to create a Message Rule Table.
Message Rule Table
Raw Message Rule
Go to the Signaling Groups > (SIP) ZPLS:Zoom as created earlier with Easy Config Wizard.
Apply the Outbound Message Manipulation rule to the Zoom Signaling Group as shown below.
Message Manipulation
For configuring both Zoom Phone System and Zoom Phone Local Survivability, refer to the following link:
https://support.zoom.us/hc/en-us/articles/360001297663-Getting-started-with-Zoom-Phone-admin.
Install VMware ESXi & USB-LAN driver (to convert USB port to ethernet port) in order to connect the ASM to the network using the following steps:
Using puTTY, ssh to the VMware server and enter credentials to log in,
Use the command below to install:
[root@localhost:/tmp] esxcli software vib install -d /tmp/ESXi670-VMKUSB-NIC-FLING-39203948-offline_bundle-16780994.zip Installation Result Message: The update completed successfully, but the system needs to be rebooted for the changes to be effective. Reboot Required: true VIBs Installed: VMW_bootbank_vmkusb-nic-fling_2.1-6vmw.670.2.48.39203948 VIBs Removed: VIBs Skipped: [root@localhost:/tmp]
At the prompt, enter "reboot" and press Enter.
Install VMware ESXi and connect the ASM's only ethernet port to the network
Once the VMware ESXi is installed on ASM, continue with Section A: Ribbon SBC Edge Configuration for further configurations.
The following checklist depicts the set of services/features covered through the configuration defined in this Interop Guide.
Sr. No. | Supplementary Features/Services | Coverage |
---|---|---|
1 | Internal Extension Dialing | |
2 | Dial By Name | |
3 | Dial From Call History | |
4 | OPTIONS ping (SBC to ZPLS) | |
5 | OPTIONS ping (ZPLS to SBC) | |
6 | Basic Call from PSTN to Zoom | |
7 | Basic Call from Zoom to PSTN | |
8 | Call Hold & Call Resume | |
9 | Mute/Unmute | |
10 | DTMF (RFC 2833) | |
11 | Blind/Unattended Transfer | |
12 | Consultative/Attended Transfer | |
13 | Call Park & Retrieve | |
14 | Adhoc 3-Party Conference |
Legend
Supported | |
Not Supported | |
N/A | Not Applicable |
The following items should be noted in relation to this Interop - these are either limitations, untested elements, or useful information pertaining to the Interoperability.
For any support related queries about this guide, contact your local Ribbon representative, or use the details below:
For detailed information about Ribbon products & solutions, go to :
https://ribboncommunications.com/products
For information about Zoom products & solutions, go to:
This Interoperability Guide describes a successful configuration of the Zoom Phone Local Survivability interoperability with Ribbon SBC Edge.
All features and capabilities tested are detailed within this document - any limitations, notes or observations are also recorded in order to provide the reader with an accurate understanding of what has been covered, and what has not.
Configuration guidance is provided to enable the reader to replicate the same base setup - there maybe additional configuration changes required to suit the exact deployment environment.
© 2021 Ribbon Communications Operating Company, Inc. © 2021 ECI Telecom Ltd. All rights reserved.