Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Add_workflow_for_techpubs
AUTH1UserResourceIdentifier{userKey=8a00a0c85b2726c2015b58aa779d0003, userName='null'}
JIRAIDAUTHCHOR-4523
REV5UserResourceIdentifier{userKey=8a00a0c85b2726c2015b58aa779d0003, userName='null'}
REV6UserResourceIdentifier{userKey=8a00a0c85b2726c2015b58aa779d0003, userName='null'}
REV3UserResourceIdentifier{userKey=8a00a0c85c46b657015d4f57d577001c, userName='null'}
REV1UserResourceIdentifier{userKey=8a00a02355cd1c2f0155cd26cc5207f0, userName='null'}

Panel

In this section:

Table of Contents
maxLevel2

Overview

The SBC SWe Lite 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 SWe Lite 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 Lite 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.


Caption
0Figure
1SWe Lite in Azure - Network Topology


Step 1: Review Prerequisites

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

Microsoft Azure Subscription

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

Azure Requirements for SBC SWe Lite Virtual Machine


Caption
0Figure
1Azure Requirements for SWe Lite Virtual Machines


ResourceDescription
Resource group

Required by Azure to host the SBC SWe Lite VM and SBC SWe Lite 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 Lite 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 Lite IP addresses (SBC SWe Lite 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

Warning

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 Lite VM and the SBC SWe Lite related resources. To deploy an SBC SWe Lite 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.


    Caption
    0Figure
    1Add Resource Group via Portal


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

    Caption
    0Figure
    1Add Resource Group via Portal



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

    Caption
    0Figure
    1Resource Group List


Step 3: Create a Virtual Network and a Virtual Subnet

The Virtual Network interconnects the SBC SWe Lite with other equipment inside and outside Azure. The Virtual Subnet hosts the SBC SWe Lite IP addresses and are interconnected by the previously created Virtual Network. The SBC SWe Lite 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.

    Caption
    0Figure
    1Create Virtual Networks


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

    Caption
    0Figure
    1Create Virtual Network



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

    Caption
    0Figure
    1Add Virtual Network


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

    Caption
    0Figure
    1Select Subnet


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

  9. Enter the required information.

    Caption
    0Figure
    1Add Subnet Window


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

    Caption
    0Figure
    1Subnet List


Step 4: Deploy SBC SWe Lite From Azure Marketplace

When the SBC SWe Lite 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 Lite instances.

Info
titleConfiguration 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 Lite 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 Lite.


    Caption
    0Figure
    1Search for Ribbon SWe Lite


  4. Review the product description and click Create.

    Caption
    0Figure
    1Product Description


  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)

    Info

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

    Caption
    0Figure
    1Create a virtual machine - Basics


  11. Click Next: Disks.

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

    Caption
    0Figure
    1Select Premium SSD



  13. Click Next: Networking.
  14. Review and verify the default fields.

    Caption
    0Figure
    1Create a virtual machine - Networking


  15.  Click Review + Create.

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

    Caption
    0Figure
    1Validation Passed


  17. Click Create. A VM status is displayed.

    Caption
    0Figure
    1Create VM


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


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

    Caption
    0Figure
    1Select Virtual Machines



Info

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 Lite

Warning

The SBC SWe Lite 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 Lite 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.

    Caption
    0Figure
    1SWe Lite VM - Stop function



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

    Caption
    0Figure
    1Select SWe Lite


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

    Caption
    0Figure
    1Create Network Interface


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

    Caption
    0Figure
    1Create Network Interface


  11. Confirm that your VM has two NICs.

    Caption
    0Figure
    1Confirm NICs


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

Step 6: Connect to SBC SWe Lite via Azure Portal

Connect to the SBC SWe Lite 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 Lite.
  4. From Settings, select Networking.

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

    Info

    To ensure the management interface for the SBC SWe Lite 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).


    Caption
    0Figure
    1HTTP Configuration


    Caption
    0Figure
    1HTTPS Configuration


  6. Click Save.


    Info

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


    Caption
    0Figure
    1Public and Private IP Addresses


Step 7: Run Initial Setup

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

Info

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 SWe Lite 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 SWe Lite to route signaling/media traffic to the Media (non admin) interface(s). 

  • 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 Lite instance in Azure for a trial or demonstration deployment, you can use the 30 day trial license that is included with SBC SWe Lite in Azure by default. If your trial or demonstration deployment lasts for more than 30 days, proceed to Obtaining and Installing a Permanent SWe Lite Trial License.

Production License Installation

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