In this section:

Overview

The SBC SWe Edge is a Microsoft-certified virtualized Session Border Controller (SBC) designed to provide small and mid-sized businesses interworking, security, and survivability for unified communications. The SBC SWe Edge is available for deployment in Azure Marketplace as a BYOL (Bring Your Own License); it will be created as a virtual machine (VM) hosted in Azure. 

These instructions include how to configure and deploy the SBC SWe Edge in Microsoft Azure cloud. All configuration commands are via Azure Portal; the equivalent Powershell configuration comments are referenced here: Using Powershell Commands to Add Resource Groups and Virtual Networks in Azure.


SBC SWe Edge in Azure - Network Topology


Step 1: Review Prerequisites

This section details the Microsoft Azure cloud computing requirements for hosting the SBC SWe Edge VM and SBC SWe Edge related resources.

Microsoft Azure Subscription

A Microsoft Azure subscription (with credit) is required. Refer to Microsoft Azure.

Azure Requirements for SBC SWe Edge Virtual Machine


Azure Requirements for SBC SWe Edge Virtual Machines

ResourceDescription
Resource group

Required by Azure to host the SBC SWe Edge VM and SBC SWe Edge related resource. Resource types are assigned into a resource group.

Configuring a resource group is included in the instructions below.

Virtual network

Interconnects SBC SWe Edge with other equipment, inside and outside Azure.

Minimum of 1 Virtual Network(s) required. Instructions for adding a virtual network are included below.

Virtual subnet

Hosts the SBC SWe Edge IP addresses (SBC SWe Edge support 2 to 5 Network Adapters that require separate subnets).

Minimum of 2 Virtual Subnets required. Instructions for adding a virtual subnet are included below.

Azure Virtual Machine RequirementsRefer to Virtual Machine Requirements - Microsoft Azure.

Step 2: Create Resource Group

When creating the Azure resource, Ribbon recommends always using the same resource location.

The Resource Group contains the necessary configuration for Azure to host the SBC SWe Edge VM and the SBC SWe Edge related resources. To deploy an SBC SWe Edge in the Microsoft Azure cloud, the resource group is required for a Virtual Machine (VM).

Create a Resource Group via Azure portal as follows:

  1. Connect to the Azure portal. Refer to portal.azure.com.
  2. From the menu, click Resource groups. For configuration of a Resource Group via Powershell refer to: Using Powershell Commands to Add Resource Groups and Virtual Networks in Azure.

  3. Click Add.


  4. Enter the Resource Group Name and click Review and Create. The Resource Group is validated.

  5. Click Create. The Resource Group is added and listed in the list of Resource Groups.

Step 3: Create a Virtual Network and a Virtual Subnet

The Virtual Network interconnects the SBC SWe Edge with other equipment inside and outside Azure. The Virtual Subnet hosts the SBC SWe Edge IP addresses and are interconnected by the previously created Virtual Network. The SBC SWe Edge requires at least two Virtual Subnets, one for management and one for signaling/media. Even though management operations can be performed through the signaling/media subnet, for security reasons, Ribbon recommends disabling HTTP/HTTPS on the signaling/media subnet via ACL.

Create a Virtual Network and a Virtual Subnet via Azure Portal

  1. Connect to the Azure portal. Refer to portal.azure.com.
  2. From the main menu, select Virtual Networks. For configuration of a Virtual Network and Virtual Subnet via Powershell refer to: Using Powershell Commands to Add Resource Groups and Virtual Networks in Azure.

  3. Click the Add button.

  4. Enter the Virtual network information.  See below for example entries.

  5. Click Create. The Virtual network is added and listed in the list of Virtual networks.

  6. From the list of virtual networks, click on the newly created Virtual network (i.e., SWeLite-Network).

  7. From Settings, select Subnets.

  8. Click +Subnet. The Add subnet window is displayed.

  9. Enter the required information.

  10. Click OK. The subnet is added to the list of subnets.

Step 4: Deploy SBC SWe Edge From Azure Marketplace

When the SBC SWe Edge image is deployed via Azure Marketplace, the image automatically appears in the general list of available images in Azure Portal. The single image can be used to deploy multiple SBC SWe Edge instances.

Configuration Notes
  • For configuration, Ribbon recommends using a Premium SSD Disk Drive and Non-accelerated networking.
  • Configuration examples for fields are displayed (i.e., IP address, subnet, etc); configure these fields to match your specific deployment.

Configure the SBC SWe Edge VM via Azure Portal as follows:

  1. Connect to the Azure portal. Refer to portal.azure.com.

  2. From the menu, click Create a Resource.

  3. In the search bar, enter Ribbon and click <Enter>. From the selections, click on SBC SWe Edge.

  4. Review the product description and click Create.

  5. In the Basics tab, configure the fields as described below.

  6. From the Resource group drop down list in the left side menu, select the Resource Group created previously (i.e., SWeLite-RG)

    To view recommended VM sizes, refer to Virtual Machine Requirements - Microsoft Azure.

  7. In Virtual machine name field, enter SWeLite.

  8. In Size, click Change size to select the applicable VM size. To determine the required VM size, refer to Calculating Virtual Machine Requirements for an SBC SWe Edge Supported VM sizes include:

    1. B1ms

    2. B2s

    3. DS1_v2

    4. DS3_v2

  9. In Authentication Type, click on Password.

  10. Enter Username, Password, and Confirm Password.

  11. Click Next: Disks.

  12. From OS disk type drop down list, select Premium SSD.


  13. Click Next: Networking.

  14. Review and verify the default fields.

  15.  Click Review + Create.

  16. A screen indicates validation of the VM has passed.

  17. Click Create. A VM status is displayed.


    When finished, this message is displayed: Your deployment is complete.


  18. From the main menu, select Virtual Machines. The newly created SBC SWe Edge instance is displayed.

For detailed information on reserving a VM resource, refer to Reserving a VM Resource in Azure.

Step 5: Create/Assign Signaling Network Interface on SBC SWe Edge

The SBC SWe Edge requires at least two Network Interfaces to function at the minimum, one for management and one for signaling/media.

Assign Additional Network Interface via Azure Portal as follows:

  1. Connect to the Azure portal. Refer to portal.azure.com.
  2. From the menu, select Virtual Machines
  3. From the list of VMs, click the check box next to the desired SBC SWe Edge VM.

  4. From the main menu select Stop and then Yes to acknowledge stopping the VM. Wait for the VM status to be Stopped (Deallocated), which can sometimes take a few minutes. Alternatively, right-click on the desired VM and select Stop.

  5. Click on the desired VM to view the settings.
  6. From Settings > Networking, click Attach network interface.

  7. Click Create network interface.

  8. In the Create network interface window, enter the required information. Ensure you enter the signaling subnet address configured previously.

  9. Click Create.

  10. Click Attach network interface and select the newly created Network Interface. Click OK.

  11. Confirm that your VM has two NICs.

  12. From  the list of VMs, select the SBC SWe Edge VM.
  13. From the main menu select Start (alternatively, right-click on the desired VM and select Start).

Step 6: Connect to SBC SWe Edge via Azure Portal

Connect to the SBC SWe Edge via Azure Portal as follows:

  1. Connect to the Azure portal. Refer to portal.azure.com.
  2. From the menu, click Virtual Machines.
  3. Click on the newly created SBC SWe Edge.

  4. From Settings, select Networking.

  5. Under Inbound port rules, restrict the HTTP and HTTPS access to pubic and private address. See below.

    To ensure the management interface for the SBC SWe Edge can only be reached from the IP address(es) you specify, restrict the HTTP and HTTPS access to your personal IP address (per previous step).

  6. Click Save.


    The Public IP and Private IP addresses in the example screen below; these values are required for subsequent SBC SWe Edge logins during Running Initial Setup on SBC SWe Edge. 

Step 7: Run Initial Setup

Proceed to Running Initial Setup on SBC SWe Edge for initial configuration and next steps, which include how to access the WebUI and options to extend the SBC SWe Edge trial indefinitely. One initial setup is complete, return here to Step 8,

By default, Azure designates the VM’s first network's Interface as the primary network interface. Only the primary network interface receives a network default gateway and routes via DHCP. The first network interface on the SBC SWe Edge is recommended to be used only for management. Media traffic routed to this interface will not be processed. To avoid this problem, you must either:

  • Create a Static Route(s) on the SBC SWe Edge to route signaling/media traffic to the Media (non admin) interface(s).
  • Create a Static Route(s) on the SBC SWe Edge to route all traffic to the Media (non admin) interface(s). When you do this, you must configure all Logical Interfaces with the DHCP Options to Use field set to IP Address (refer to Configuring and Modifying Logical Interfaces).

  • Change the primary network interface assignment from the Management interface to the Media interface. Refer to Change Azure Default Route.

Step 8: License Installation

Trial License Installation

If you are installing an SBC SWe Edge instance in Azure for a trial or demonstration deployment, you can use the 30 day trial license that is included with SBC SWe Edge in Azure by default. If your trial or demonstration deployment lasts for more than 30 days, proceed to Obtaining and Installing a Permanent SWe Edge Trial License.

Production License Installation

If you are installing an SBC SWe Edge instance to carry live/production enterprise traffic, proceed to Obtaining and Installing an SBC SWe Edge Production Node-Locked License.