Versions Compared

Key

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

...

  • 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. Provisioning a VM with more resources than it requires can, in some cases, reduce the performance of that VM as well as other virtual machines sharing the same hostAdding 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)


...