...
This section covers the Ribbon SBC Edge deployment topology and the Interoperability Test Lab Topology.
Deployment Topology : Geographically Located
This deployment topology depicts the ZPLS on a host server which is geographically different from the SBC Edge location.
Caption |
---|
0 | Figure |
---|
1 | Ribbon SBC Edge Deployment Topology |
---|
|
![](/download/attachments/345604910/image-2022-9-12_13-27-7.png?version=1&modificationDate=1663165909000&api=v2)
|
Interoperability Test Lab Topology
Deployment Topology : Co-located & Centralized
This deployment topology depicts ZPLS installed as VM on ASM (Application Solution Module) within the SBC Edge 1K/2K platform.
Caption |
---|
0 | Figure |
---|
1 | Ribbon SBC Edge deployment topology on SBC ASM |
---|
|
Image Added
|
Interoperability Lab Topology : Geographically Located
The following lab topology diagram shows connectivity between the Ribbon SBC Edge on a virtual platform and Zoom The following lab topology diagram shows connectivity between Ribbon SBC Edge on virtual platform and Zoom Phone Local Survivability.
...
Caption |
---|
0 | Figure |
---|
1 | SBC Edge and ZPLS interoperability Test Lab Topology |
---|
|
![](/download/attachments/345604910/image-2022-9-14_13-12-23.png?version=1&modificationDate=1663165909000&api=v2)
|
Document Workflow
Interoperability Lab Topology : Co-located & Centralized
The following lab topology diagram shows connectivity between Ribbon SBC Edge and Zoom Phone Local Survivability on SBC's ASM (Application Solution Module).
Caption |
---|
0 | Figure |
---|
1 | Interoperability Test Lab topology for ZPLS on SBC ASM |
---|
|
Image Added
|
Document Workflow
The The sections in this document follow the sequence below. The reader is advised to complete each section for successful configuration.
![](/download/attachments/345604910/image2022-9-9_13-12-18.png?version=1&modificationDate=1663165911000&api=v2)
Section A: Ribbon SBC Edge Configuration
...
Caption |
---|
0 | Figure |
---|
1 | SBC 2000 Front Panel |
---|
|
Image Removed Image Added
|
Info |
---|
title | Note |
---|
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. |
Warning |
---|
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. |
...
Configure Ethernet 1 and Ethernet 2 of SBC 1000/2000 with the IP as follows:
Navigate to Node Interfaces > Logical Interfaces.
Caption |
---|
0 | Figure |
---|
1 | Logical Interfaces |
---|
|
Image Removed |
Caption |
---|
|
Image Removed
Image Removed
|
Caption |
---|
|
Image Removed
Image Removed
|
Tip |
---|
|
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).
Tip |
---|
|
- For smaller networks with just one or two routes, configuring static routing is preferable. This is often more efficient since a link is not being wasted by exchanging dynamic routing information.
- For networks that have a LAN-side Gateway on Voice VLAN or Multi-Switch Edge Devices (MSEs) with Voice VLAN towards SBC Edge, static routing configurations are not required.
|
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.
Caption |
---|
0 | Figure |
---|
1 | Static Routes |
---|
3 | Static Routes |
---|
|
Image Removed
|
...
|
Image Added
|
Info |
---|
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. |
Network
Configure Ethernet 1 and Ethernet 2 of SBC 1000/2000 with the IP as follows:
Navigate to Node Interfaces > Logical Interfaces.
Caption |
---|
0 | Figure |
---|
1 | Logical Interfaces |
---|
|
Image Added |
Caption |
---|
|
Image Added
Image Added
|
Caption |
---|
|
Image Added
Image Added
|
Tip |
---|
|
To configure Ethernet 1 and Ethernet 2 of SBC SWe Edge, navigate to Networking Interfaces > Logical Interfaces.
|
Anchor |
---|
| Static Routes |
---|
| Static Routes |
---|
|
Static RoutesStatic 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).
Tip |
---|
|
- For smaller networks with just one or two routes, configuring static routing is preferable. This is often more efficient since a link is not being wasted by exchanging dynamic routing information.
- For networks that have a LAN-side Gateway on Voice VLAN or Multi-Switch Edge Devices (MSEs) with Voice VLAN towards SBC Edge, static routing configurations are not required.
|
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.
Caption |
---|
0 | Figure |
---|
1 | Static Routes |
---|
3 | Static Routes |
---|
|
Image Added
|
Anchor |
---|
| TLS Configuration between Ribbon SBC Edge and ZPLS |
---|
| TLS Configuration between Ribbon SBC Edge and ZPLS |
---|
|
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)
...
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.
...
- 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.
...
Info |
---|
Enter a value for SIP sessions as per the requirement. The value can be up to 960. |
Caption |
---|
|
Image Removed
|
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.
Caption |
---|
|
Image Removed
|
Review the configurations in Step1 and Step 2, and click on the Finish button.
Caption |
---|
|
Image Removed
Image Removed
|
...
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
Image Removed icon to create a Message Rule Table.
- Provide a description for the Rule Table.
- Apply Message Rule to "All Requests".
- Click OK.
Caption |
---|
0 | Figure |
---|
1 | Message Rule Table |
---|
|
Image Removed
|
Create Raw Message Rule as follows:
Caption |
---|
|
Image Removed
Image Removed
|
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.
Caption |
---|
0 | Figure |
---|
1 | Message Manipulation |
---|
|
Image Removed
|
...
For configuring both Zoom Phone System and Zoom Phone Local Survivability, refer to the following link:
...
the requirement. The value can be up to 960. |
Caption |
---|
|
Image Added
|
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.
Caption |
---|
|
Image Added
|
Review the configurations in Step1 and Step 2, and click on the Finish button.
Caption |
---|
|
Image Added
Image Added
|
Anchor |
---|
| Message Manipulation |
---|
| Message Manipulation |
---|
|
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
Image Added icon to create a Message Rule Table.
- Provide a description for the Rule Table.
- Apply Message Rule to "All Requests".
- Click OK.
Caption |
---|
0 | Figure |
---|
1 | Message Rule Table |
---|
|
Image Added
|
Create Raw Message Rule as follows:
Caption |
---|
|
Image Added
Image Added
|
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.
Caption |
---|
0 | Figure |
---|
1 | Message Manipulation |
---|
|
Image Added
|
Section B: Zoom Phone Local Survivability ConfigurationFor 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.
Section C: Install VMware ESXi on SBC ASMSBC 2000 Chassis
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:
- Download VMware ESXi 7.0 licensed version along with the USB-LAN converter driver.
- For more information regarding VMware ESXi, refer to:
https://customerconnect.vmware.com/web/vmware/evalcenter?p=free-esxi6
- Remove the front cover of SBC 2000 chassis
- Locate the mini-VGA port and connect the matching plug of proprietary cable.
- Connect the the other end (VGA plug) to to the monitor.
- Insert the bootable USB pen drive (with VMware ESXi 7.0 image) to one of the ports of "USB hub".
- Connect the keyboard to another USB Port.
- Insert the "USB to LAN" converter adaptor (Dongle) to the bottom USB Port (on the right side of the equipment written as "ASM") to convert the USB port to an ethernet port.
- Insert an ethernet cable to the "USB to LAN" converter adaptor and connect the other end to the LAN switch (network).
- Configure the hostname according to the unique serial number of the box.
- Power off and then Power on the equipment to reboot and detect the bootable USB drive.
- Select 'boot' from bootable USB drive to start the VMware installation.
- Follow the instructions prompted by VMware installation process to install VMware ESXi 7.0 on the ASM till VMware installation is complete.
- Once the VMware ESXi installation completes, enable SSH by logging in via a web browser.
- Next, go to Host → manage → services → TSM-SSH → Start.
- Upload the USB to the LAN converter driver file "ESXi670-VMKUSB-NIC-FLING-39203948-offline_bundle-16780994.zip" to the VMware ESXi host under the /tmp/ folder.
Using puTTY, ssh to the VMware server and enter credentials to log in,
Use the command below to install:
Code Block |
---|
[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.
SBC 1000 Chassis
Install VMware ESXi and connect the ASM's only ethernet port to the network
- Download VMware ESXi 7.0 licensed version.
- For more information regarding VMware ESXi, please refer the link https://customerconnect.vmware.com/web/vmware/evalcenter?p=free-esxi6.
- Copy the downloaded licensed VMware ESXi 7.0 iso image to a USB pendrive and make it bootable drive.
- Insert the bootable USB pendrive with VMware ESXi 7.0 image to top USB port on the right side of the equipment marked as "ASM".
- Insert the keyboard to another USB port on the right side of the equipment marked as "ASM".
- Insert the ethernet cable to "ethernet" port on the right side of the equipment marked as "ASM" and connect other end of ethernet cable to the LAN switch.
- Follow the instructions to install VMware ESXi 7.0 on the ASM.
Info |
---|
Once the VMware ESXi is installed on ASM, continue with Section A: Ribbon SBC Edge Configuration for further configurations. |
Anchor |
---|
| Supplementary |
---|
| Supplementary |
---|
|
Supplementary Services and Features Coverage
...