Ribbon SBC Edge R11.0 Interop with Zoom Phone Local Survivability : Interoperability Guide

Interoperable Vendors

Copyright

© 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.

Document Overview

This document outlines the configuration best practices for the Ribbon solution covering the Ribbon SBC Edge when deployed with Zoom Phone Local Survivability (ZPLS).

About Ribbon SBC Edge

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.

About Zoom Phone Local Survivability (ZPLS)

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: 

• Section A: Ribbon SBC Edge Configuration
  
  • Captures general SBC Edge configurations for deploying SBC with ZPLS.
• Section B: Zoom Phone Local Survivability Configuration

  • Captures the Zoom Phone Local Survivability configuration.

Non-Goals

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. 

Audience

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:

• use the graphical user interface (GUI) or command line interface (CLI) of the Ribbon product.
• understand the basic concepts of TCP/UDP/TLS and IP/Routing.
• have SIP/RTP/SRTP to complete the configuration and for troubleshooting.

Prerequisites

The following aspects are required before proceeding with the interop:

• Ribbon SBC Edge
• Public IP Addresses
• Zoom Go account - a special type of account where the Zoom user can be configured for ZPLS.
• TLS Certificates for Ribbon SBC Edge signed by one of the Zoom approved CA vendors.

Product and Device Details

The sample configuration in this document uses the following equipment and software:

Network Topology Diagram

This section covers the Ribbon SBC Edge deployment topology and the Interoperability Test Lab Topology.

Deployment Topology

Ribbon SBC Edge Deployment Topology

Interoperability Test Lab Topology

The following lab topology diagram shows connectivity between Ribbon SBC Edge on virtual platform and Zoom Phone Local Survivability.

Document Workflow

The sections in this document follow the sequence below. The reader is advised to complete each section for successful configuration.

Section A: Ribbon SBC Edge Configuration

The following SBC Edge configurations are included in this section:

Connectivity

Network

Static Routes

TLS Configuration between SBC Edge and ZPLS

Easy Config Wizard

Message Manipulation

• SBC Edge can connect to the network as mentioned in Connectivity and Network.
• Zoom prefers transport as TLS. Establishing a TLS connection between SBC Edge and ZPLS is covered under TLS Configuration between Ribbon SBC Edge and ZPLS.
• Configure the SBC Edge with PSTN and ZPLS using Easy Config Wizard.

Connectivity

SBC 2000 Front Panel

Network

Configure Ethernet 1 and Ethernet 2 of SBC 1000/2000 with the IP as follows:

Navigate to Node Interfaces > Logical Interfaces.

Logical Interfaces

 

Static Routes

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.

• Navigate to Settings > Protocol > IP > Static Routes to configure the routes.

Static Routes

TLS Configuration between SBC Edge and ZPLS

Prerequisites:

• For TLS to work on the public side of the network, a trusted Certificate Authority (CA) is needed. In this scenario, GoDaddy is used as a trusted CA.
• Digicert Global Root CA and Digicert Global G2 are also required for TLS handshake.
• ZPLS is enabled with TLS/SRTP by default.

Request a certificate for the SBC and configure it based on the example using GoDaddy as follows:

• Generate a Certificate Signing Request (CSR) and obtain the certificate from a Certificate Authority.
• Import the Public CA Root/Intermediate Certificate and the SBC Certificate on the SBC.
  

Step 1: Generate a Certificate Signing Request and obtain the certificate from a Certificate Authority (CA).

• Navigate to Settings > Security > SBC Certificates.
• Click Generate SBC Edge CSR.
• Enter data in the required fields. Click OK. After the Certificate Signing Request is generated, copy the result to the clipboard.

• Use the generated CSR text from the clipboard to obtain the certificate. 

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:

• Obtain Trusted Root and Intermediary signing certificates from your Certificate Authority.
• To install the Trusted Root/Intermediate certificates, go to Settings > Security > SBC Certificates > Trusted Root Certificates.
• Click Import and select the trusted root certificates.
• To install the SBC certificate, open Settings > Security > SBC Certificates > SBC Edge Certificate.

• Validate the certificate is installed correctly.

Trusted CA certificate table

• Click Import and select X.509 Signed Certificate.
• Validate the certificate is installed correctly.

Validate certificate

Easy Config Wizard

Configure the SBC Edge with ZPLS using the Easy Config Wizard.

• Access the WebUI of SBC 2000.
• Click on the Tasks tab.
• From the left side menu, click SBC Easy Setup > Easy Config Wizard.

Easy Config Wizard

Fill in the details for Step 1 as follows:

• Scenario Description as ZPLS.
• SIP Sessions as 50.

Step 1

Fill in the details for Step 2 as follows:

• Border Element Server would be the PSTN IP.
• Use Secondary Border Element Server should be Disabled.
• Signaling/Media Source IP towards ZPLS.
• Host IP of the ZPLS.
• Port of the ZPLS, i.e. 5061.

Step 2

Review the configurations in Step1 and Step 2, and click on the Finish button.

Message Manipulation 

The Message Manipulation SAVP is used for the following purposes:

• To modify the RTP/AVP to RTP/SAVP for all the request messages.

Go to Settings > SIP > Message Manipulation >Message Rule Tables. Click the  icon to create a Message Rule Table.

• Provide a description for the Rule Table.
• Apply Message Rule to "All Requests".
• Click OK.

Message Rule Table

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

Section B: Zoom Phone Local Survivability Configuration

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.

Supplementary Services and Features Coverage

The following checklist depicts the set of services/features covered through the configuration defined in this Interop Guide. 

Legend

Caveats

The following items should be noted in relation to this Interop - these are either limitations, untested elements, or useful information pertaining to the Interoperability.

• SBC Edge Media List created using Easy Config Wizard would have the G711-Alaw as highest priority then G711-Mulaw. Alter the codec priority as per requirement.

Support

For any support related queries about this guide, contact your local Ribbon representative, or use the details below:

• Sales and Support: 1-833-742-2661
• Other Queries: 1-877-412-8867
• Website: https://ribboncommunications.com/services/ribbon-support-portal

References

For detailed information about Ribbon products & solutions, go to :

https://ribboncommunications.com/products

For information about Zoom products & solutions, go to:

 https://zoom.us 

Conclusion

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.