© 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 Edge series ATA (Analog Telephone Adaptor)/IAD (Integrated Access Device) when deployed with Zoom.
The Ribbon Edge is a low-density analog gateway or ATA/IAD device that gives small businesses, SOHOs and branch offices with analog voice infrastructures an easy, cost-effective way to capitalize on Voice over Internet Protocol (VoIP) services. The Ribbon Edge ATA/IAD offers a survivable branch office solution, providing support for integrating analog endpoints and the Public Switched Telephone Network (PSTN) and support for all Session Initiation Protocol (SIP) calls. The Ribbon Edge supports any-to-any connectivity between analog and SIP devices, enabling branch offices to rapidly migrate analog phones onto SIP-based networks and communicate seamlessly.
The interoperability compliance testing focuses on verifying inbound and outbound call flows between Ribbon Edge ATA & Zoom Cloud.
This guide contains the following configuration sections:
It is not the goal of this guide to provide detailed configurations that meets the requirements of every customer. Use this guide as a starting point and build the SBC configurations as ATA in consultation with network design and deployment engineers.
This is a technical document intended for telecommunications engineers with the purpose of configuring the Ribbon SBC.
To perform this interop, you need:
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 following equipment and software were used for the sample configuration provided:
This section covers the Ribbon Edge deployment topology and the Interoperability Test Lab Topology.
The following lab topology diagram shows connectivity between Zoom and Ribbon Edge ATA/IAD.
The following SBC Edge configurations are included in this section:
The SBC 1000/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 Zoom leg.
Configure Ethernet 1 and Ethernet 2 of SBC 1000/2000 with the IP as follows:
Navigate to Node 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).
Add Static routes need to be added towards Eth1 interface 172.16.X.X(PSTN) and Eth2 interface 162.12.X.0(Zoom), as Zoom uses multiple IPs in this subnet.
Default static route is towards the Eth1 that is in a private network.
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 Certification Authority (CA).
Click Generate SBC Edge CSR.
Enter data in the required fields.
Click OK. After the Certificate Signing request finishes generating, copy the result to the clipboard.
5. 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 certification authority, install the SBC Certificate and Root/Intermediate Certificates as follows:
Validate the certificate is installed correctly.
6. Click Import and select X.509 Signed Certificate.
7. Validate the certificate is installed correctly.
As mentioned in Zoom Portal "Please download DigiCert Global Root CA, DigiCert Global Root G2, DigiCert Global Root G3 and import to your IP phone if they are not in the trust list of the device."
TLS Profile
TLS Profile is required for the TLS handshake between the SBC Edge and Zoom. This profile defines cipher suites supported by the SBC Edge.
Default TLS Profile need to be attached to SIP Server Table on Zoom leg.
Navigate to Security > TLS Profiles. Use the Default TLS Profile with the following modifications:
To create a Media Profile:
To create a SRTP Profile:
A SIP profile is used to modify the different SIP parameters like Session timers, SIP Header Customization, and SDP Customization. Create a new SIP Profile "ZOOM_SIP".
Create profiles with a specific set of characteristics corresponding to Analog (PSTN). This includes configuration of the following entities on the Analog leg:
Signaling groups allow telephony channels to be grouped together for the purposes of routing and shared configuration. The signaling groups are the entity where calls are routed, as well as the location where Call Routes are selected. They are also the location where the Tone Tables and Action Sets are selected.
Set Tone Table as "Default Tone Table".
Set Call Routing table as "Analog_Zoom" that is created in the Call Routing Table section.
Transformation table is used to map the 3 digit analog line to 20 digit Zoom Username. In the current setup, "analog_sip" transformation rule applied for outgoing call towards Zoom.
Navigate to Settings > Call Routing > Transformation.
Call Routing allows calls to be carried between signaling groups, thus allowing calls to be carried between ports, and between protocols (like ISDN to SIP). Routes are defined by Call Routing Tables, which allow for flexible configuration where calls are carried and how they are translated. These tables are one of the central connection points of the system, linking Transformation Tables, Message Translations, Cause Code Reroute Tables, Media Lists and the three types of Signaling Groups (ISDN, SIP and CAS).
Attach the Media List and Destination Signaling Groups that are created in Zoom Leg Configuration.
Create profiles with a specific set of characteristics corresponding to Zoom. This includes configuring the following entities on the Zoom leg:
Media List allows you to specify a set of codecs used for the call. They contain a list of codecs, defined in Media Profile.
The Contact registrant table contains the address of record URI required for REGISTER with Zoom.
A Remote authorization table contains a realm, authentication ID and password, used when the REGISTER and INVITE is challenged by Zoom.
The SIP Server Tables contain information about the SIP devices connected to the SBC Edge. The entries in the tables provide information about the IP Addresses, ports and transport protocols used to communicate with each server.
Signaling groups allow telephony channels to be grouped together for the purposes of routing and shared configuration. The signaling groups are the entity where calls are routed, as well as the location where Call Routes are selected. They are also the location where Tone Tables and Action Sets are selected. In the case of SIP, they specify protocol settings and link to server, media and mapping tables.
Set the Call Routing table as "Zoom_RT" as created in the Call Routing Table section.
The "Remove_plusOne" transformation rule is required for the call towards PSTN.
Navigate to Settings > Call Routing > Transformation.
Call Routing allows calls to be carried between signaling groups, thus allowing calls to be carried between ports, and between protocols (such as ISDN to SIP). Routes are defined by Call Routing Tables, which allow for flexible configuration where calls are carried, and how they are translated. These tables are one of the central connection points of the system, linking Transformation Tables, Message Translations, Cause Code Reroute Tables, Media Lists and the three types of Signaling Groups (ISDN, SIP and CAS).
Attach the Media List and Destination Signaling Groups that are created in the Analog Leg Configuration section.
The SBC 1000 can be provisioned as an ATA/IAD with Zoom, contact Zoom for Provisioning details.
The details provided by Zoom to configure Analog(FXS) Port 1 and Port 2 for the SBC 1000 are as follows:
Ribbon SBC 1K Generic Device Account details MAC: 00:10:23:e1:04:2f SIP Account SBC-1K-FXS1 Extension: 809 1. SIP Domain: 10000587.zoom.us 2. Outbound Proxy: gosip0h.sc.zoom.us:5091 3. User Name: 77746483298489165551 4. Authorization ID: 475370019876 5. Password: xxxxx ============================================= SIP Account 1SBC-1K-FXS2 Extension: 810 1. SIP Domain: 10000587.zoom.us 2. Outbound Proxy: gosip0h.sc.zoom.us:5091 3. User Name: 20407385877802799170 4. Authorization ID: 247646854027 5. Password: xxxxx
Zoom supports multiple supplementary services. To configure different supplementary services in Zoom, refer to the following links:
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 | Basic Registration over TLS | |
2 | Basic Call Setup | |
3 | Basic Call Termination | |
4 | Auto Receptionist (Auto Attendant) | |
5 | Call Hold/Resume | |
6 | Call Transfer - Blind (Cold transfer) | |
7 | Call Transfer - Consult (Warm transfer) | |
8 | Conference | |
9 | Call Waiting | |
10 | Call Queue | |
11 | Shared Line Group (SLG) | |
12 | Shared Line Appearance (SLA) or Call Delegation | |
13 | Call Recording | |
14 | Call Flip | |
15 | Call Park |
Legend
Supported | |
Not Supported | |
N/A | Not Applicable |
The following issues are observed during the testing:
The issues above must fixed in the upcoming SBC 1000 and 2000 software release.
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, refer to:
https://ribboncommunications.com/products
For information about Zoom products & solutions, refer to:
This Interoperability Guide describes a successful configuration covering Zoom interop with Ribbon Edge ATA/IAD.
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.