In this section:
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.
This section details the Microsoft Azure cloud computing requirements for hosting the SWe Lite VM and SWe Lite related resources.
A Microsoft Azure subscription (with credit) is required. Refer to Microsoft Azure.
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 SWe Lite VM and the SWe Lite related resources. To deploy a 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:
Enter the Resource Group Name and click Review and Create. The Resource Group is validated.
Click Create. The Resource Group is added and listed in the list of Resource Groups.
The Virtual Network interconnects SWe Lite with other equipment inside and outside Azure. The Virtual Subnet hosts the 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
Click the Add button.
Enter the Virtual network information. See below for example entries.
Click Create. The Virtual network is added and listed in the list of Virtual networks.
From Settings, select Subnets.
Click +Subnet. The Add subnet window is displayed.
Enter the required information.
Click OK. The subnet is added to the list of subnets.
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.
Configure the SBC SWe Lite VM via Azure Portal as follows:
From the menu, click Create a Resource.
Review the product description and click Create.
In the Basics tab, configure the fields as described below.
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.
In Virtual machine name field, enter SWeLite.
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:
Enter Username, Password, and Confirm Password.
Click Next: Disks.
From OS disk type drop down list, select Premium SSD.
Review and verify the default fields.
Click Review + Create.
A screen indicates validation of the VM has passed.
Click Create. A VM status is displayed.
From the main menu, select Virtual Machines. The newly created SBC SWe Lite instance is displayed.
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:
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.
Click Create network interface.
In the Create network interface window, enter the required information. Ensure you enter the signaling subnet address configured previously.
Click Attach network interface and select the newly created Network Interface. Click OK.
Confirm that your VM has two NICs.
Connect to the SBC SWe Lite via Azure Portal as follows:
From Settings, select Networking.
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 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).
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.
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,
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:
The SBC Edge is configured via Easy Configuration Wizard.
Calls can be tested via the SWe Lite's WEB UI.
In the left navigation pane, under Tools, click Test a Call.