Versions Compared

Old Version 2

changes.mady.by.user Ribbon Communications

Saved on

compared with

New Version Current

changes.mady.by.user Ribbon Communications

Saved on

Key

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

Add_workflow_for_techpubs
AUTH1UserResourceIdentifier{userKey=8a00a0c85b2726c2015b58aa779d0003, userName='null'}
JIRAIDAUTHCHOR-1578
REV5UserResourceIdentifier{userKey=8a00a0c85b2726c2015b58aa779d0003, userName='null'}
REV6UserResourceIdentifier{userKey=8a00a0c85b2726c2015b58aa779d0003, userName='null'}
REV3UserResourceIdentifier{userKey=8a00a0c85c46b657015d4f57d577001c, userName='null'}
REV1UserResourceIdentifier{userKey=8a00a02355cd1c2f0155cd26ccf70906, userName='null'}
REV2UserResourceIdentifier{userKey=8a00a02355cd1c2f0155cd26cef30cd0, userName='null'}

Panel

In this section:

Table of Contents
maxLevel4

This section describes 

Spacevars
0series3
 virtual machine recommendations for the 
Spacevars
0series3
when running on Amazon Web Services (AWS).

Virtual Machine Recommendations for 
Spacevars
0series3
running in AWS.

Warning

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 

Spacevars
0series3
may not behave as expected. Ribbon does not provide support for 
Spacevars
0series3
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.


Caption
0Table
1SBC SWe Edge Instance - Recommended AWS VMs


AWS VM Instance

vCPU

Maximum number of vNICs

Spacevars
0series3
 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)