Versions Compared

Old Version 1

changes.mady.by.user Ribbon Communications

Saved on

compared with

New Version 2

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-23713623
REV5UserResourceIdentifier{userKey=8a00a0c85b2726c2015b58aa779d0003, userName='null'}
REV6UserResourceIdentifier{userKey=8a00a0c85b2726c2015b58aa779d0003, userName='null'}
REV3UserResourceIdentifier{userKey=8a00a02355cd1c2f0155cd26c99e02c08a00a0c85c46b657015d4f57d577001c, userName='null'}
REV4REV1UserResourceIdentifier{userKey=8a00a02355cd1c2f0155cd26c91d01f98a00a02355cd1c2f0155cd26cc5207f0, userName='null'}
REV1REV2UserResourceIdentifier{userKey=8a00a02355cd1c2f0155cd26cc5207f08a00a02355cd1c2f0155cd26c91d01f9, userName='null'}


Panel

In this section:

Table of Contents
maxLevel4


This section describes 

Spacevars
0series3
virtual machine recommendations for the SBC SWe Lite when running on Microsoft Azure.

Virtual Machine Recommendations for
Spacevars
0series3
running in Azure


Multiexcerpt
MultiExcerptNameSBC SWe Lite Azure


Warning
iconfalse

The recommended hardware and software settings are intended to ensure optimum stability and performance. If the recommended settings are not used, the

Spacevars
0series3

SBC SWe Lite may not behave as expected. Ribbon does not provide support for SBC SWe Lite instances deployed in non-recommended Azure VMs. For more information regarding the recommended Azure VM instances, please refer to https://docs.microsoft.com/en-us/azure/virtual-machines/linux/.

  • Plan enough resources (RAM, CPU, NIC ports, hard disk, etc.) for all virtual machines (VMs) to run in Azure. 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 host.

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

 


Caption
0Table
1SWe Lite Instance - Recommended Azure VMs


Azure VM Instance

vCPU

Maximum number of vNICs

SBC SWe Lite Supported Session Density

B1ms

1

Note: 20% of the vCPU is baseline "always available" performance; additional vCPU performance available through credits. 

2

10 sessions, with 10 transcode (

711 SRTP ↔ 729 RTP, full in band service suite)F1s12300 sessions, with 100 transcode (711 SRTP ↔ 729 RTP, full in band service suite)F2s221000 sessions, with 200 transcode (711 SRTP ↔ 729 RTP, full in band service suite)

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

Note: 10 transcode sessions available with B1ms baseline performance.

B2s

2

Note: 40% of the combine vCPU is baseline "always available" performance; additional vCPU performance available through credits. 

3

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

Note: 30 transcode sessions available with B2s baseline performance.

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

1000 sessions, with 400 transcode (

711 SRTP ↔ 729 RTP, full in band service suite

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




Additional Information

  • Minimal networking configuration requires the Management Network Interface and at least one Media Interface to be assigned.
  • Each SBC SWe Lite VM uses approximately 5 GiB of Virtual Hard Drive space. Drive size is predetermined by the imported image.
 


Pagebreak