In this section:

This section describes SBC SWe Edge virtual machine recommendations for the SBC SWe Edge when running on Amazon Web Services (AWS).

Virtual Machine Recommendations for SBC SWe Edge running in AWS.

WARNING: USE RECOMMENDED AWS VM INSTANCES FOR RELIABLE PERFORMANCE

The recommended hardware and software settings are intended to ensure optimum stability and performance. If the recommended settings are not used, the SBC SWe Edge may not behave as expected. Ribbon does not provide support for SBC SWe Edge instances deployed in non-recommended AWS VMs. For more information regarding the recommended AWS VM instances, please refer to https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ec2-instance-recommendations.html.


  • Plan enough resources (RAM, CPU, NIC ports, hard disk, etc.) for all virtual machines (VMs) to run in AWS. Minimal networking configuration requires the Management Network Interface and at least one media interface to be assigned. To use a separate Media Interface for each peer (phone system, SIP trunking provider, etc.) select a VM size with a higher number of Network Interfaces.
  • Allocate each VM with only as much virtual hardware as that VM requires. Adding excess resources may not result in improved performance nor will improved performance or feature difference be supported. Refer to the SBC SWe Edge Performance and Capacity for sanctioned VM sizes and supported performance against sanctioned VMs.

  • The vNIC recommendation is from 2 vNIC to 4 vNIC. See below for guidelines.


SBC SWe Edge Instance - Recommended AWS VMs

AWS VM Instance

vCPU

Maximum number of vNICs

SBC SWe Edge Supported Session Density

t3.small

2


3

100 sessions, with 30 transcode (G.711 μ-law/A-law ↔ G.729ab, with full media services including RTP ↔ SRTP encryption)

c5.large

2

3

300 sessions with 120 transcode (G.711 μ-law/A-law ↔ G.729ab, with full media services including RTP ↔ SRTP encryption).

c5.xlarge44500 sessions, with 480 transcode (G.711 μ-law/A-law ↔ G.729ab, with full media services including RTP ↔ SRTP encryption)