This document outlines the configuration best practices for the Ribbon EdgeMarc SBC when deployed with Zoom BYOC (Bring Your Own Carrier).
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 interoperability compliance testing focuses on verifying inbound and outbound calls flows between Ribbbon EdgeMarc and Zoom cloud. The Ribbon EdgeMarc SBC is deployed on the customer site to resolve any potential numbering format issues between Zoom and the customer's existing carrier dial plan numbering.
This guide contains the following sections:
Captures the Zoom BYOC configuration.
All basic calls, along with the supplementary features like call hold, call transfer, and conference can be tested with configurations from Section A and Section B.
Advanced supplementary features can be configured on Zoom as mentioned in Supplementary Services Configuration on Zoom. These cover:
Shared Line Appearance (SLA) or Call Delegation
Shared Line Group (SLG)
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. Steps will require navigating the third-party product as well as the Ribbon SBC Command Line Interface (CLI). Understanding the basic concepts of TCP/UDP, IP/Routing, and SIP/RTP is needed to complete the configuration and any necessary troubleshooting.
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 sample configuration in this document uses the following equipment and software:
Equipment Software Version Ribbon EdgeMarc 2900A V15.8.0 Third-party Equipment Kapanga Softphone
Ribbon Communications Zoom Zoom app Desktop 4.6.10(20033.0407) Zoom app Mobile 4.6.11(20553.0413) 1.00 Phonerlite 2.77 Zoiper 5.3.8
Ribbon EdgeMarc 2900A
Configuration guide is designed keeping EdgeMarc 2900A as a representative model with the software version V15.8.0 but it applies to all models in the EdgeMarc portfolio (300, 2900, 480x, 6000, 7301, 7400) with same software version.
The following topology diagram shows connectivity between Zoom and Ribbon EdgeMarc 2900A.
The following EdgeMarc configurations are included in this section:
EdgeMarc 2900a interface/port details are listed in the table:
In the current test bed setup, the RJ45 port is used for both LAN and WAN interfaces
IP-PBX (PSTN side) is connected towards the LAN interface of EdgeMarc 2900a.
Zoom cloud is connected towards the WAN interface of EdgeMarc 2900a.
Login to the EdgeMarc as root user and click Network to configure the LAN and WAN 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 LAN interface 172.16.X.X(IP-PBX) and WAN interface 162.12.X.0(Zoom), as Zoom uses multiple IP's in this subnet.
172.16.X.X is the IP of the phone behind the IP-PBX. Add the static route for the media to also work.
Navigate to VoIP and check whether the LAN and WAN interfaces configured earlier are reflected accordingly.
Check the following option "Route all SIP signalling through B2BUA"
PSTN side is not expected to send Comfort Noise packets on Mute. However, it might send out empty RTP packets towards EdgeMarc. It is recommended to uncheck the following option "Enable Comfort Noise Generation(CNG)" so that EdgeMarc does not generate Comfort Noise packets towards Zoom.
E.164 Country code Mapping
Example: A customer has an existing carrier that only accepts U.S.A. domestic 10 digit dial plan numbering format. For example: (XXX) YYY-ZZZZ, where XXX=area code, YYY-ZZZZ=7-digit phone number. At the same time, Zoom is using the E.164 numbering format: +(country code)(phone number). This has created a phone number format incompatibility issue between Zoom and the customer carrier. Zoom expects to receive calls in E.164 numbering format, while the customer carrier expects the USA 10-digit domestic numbering format. EdgeMarc SBC is introduced to solve the numbering interop issue between the two entities. The EdgeMarc SBC inserts a “+1” for all U.S. phone numbers destined for Zoom, and removes “+1” for all U.S. phone numbers destined for customer carrier(s).
Ribbon EdgeMarc SBC can be programmed for different country E.164 code mapping in addition to the U.S. dial plan.
The following rule is required to "Add +1" to outgoing call towards Zoom.
The following rule is required to "Remove +1" to call towards IP-PBX.
Ensure a Zoom BYOC SIP trunk is built between Zoom SBC and EdgeMarc SBC deployed on a customer site.
Once the Zoom Go account is available, login to Zoom Web BYOC portal at https://go.zoom.us/.
The following Zoom BYOC configurations are included in this section:
Navigate to Phone Systems Management > Phone Numbers > External
Select Add to add external phone numbers provided by your carrier into Zoom portal. These numbers are the DID numbers provided by your carrier.
Select BYOC as the carrier and enter the customer existing phone numbers (from carrier) separated by commas. Click Submit.
Verify the external numbers have been created successfully as shown below.
Zoom Users are created in order to login to Zoom clients on a desktop or mobile. Create a user as follows:
4. Assign the External Numbers created previously in the Add External Number section.
5. Click Confirm to finish. Once the User is assigned with a Calling Plan and Number, it should look like the following example.
Zoom supports multiple supplementary services. To configure different supplementary services in Zoom, refer to the following links:
3. Shared Line Appearance (SLA) or Call Delegation: https://support.zoom.us/hc/en-us/articles/360032881731
4. Shared Line Group/SLG: https://support.zoom.us/hc/en-us/articles/360038850792/
Generate a CSR from EdgeMarc SBC
Navigate to Security > Certificates.
Common name: should be the valid fqdn, here "trials.com" is given as a sample configuration.
Email: Provide the valid Email ID.
Download the CSR certificate from SBC and get it signed from a Trusted CA.
Obtain the Root certificate and EdgeMarc SBC signed certificate from the Trusted CA and upload as follows:
Key file and Password is not required.
Upload the Signed certificate from CA as follows:
Certificate Name: SBCpem (in our case).
Certificate Type: SSL.
Select certificate file: Signed SBC certificate from Trusted CA.
Select Key file: Private key of SBC.
Apply the following settings as mentioned below.
Choose the SBCpem certificate that was uploaded in a previous step.
Navigate to VoIP > Media Security.