Versions Compared

Old Version 1

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
AUTH2UserResourceIdentifier{userKey=8a00a0c85b2726c2015b58aa779d0003, userName='null'}
AUTH1UserResourceIdentifier{userKey=8a00a02355cd1c2f0155cd26cb41059c, userName='null'}
JIRAIDAUTHCHOR-4156
REV5UserResourceIdentifier{userKey=8a00a0c85b2726c2015b58aa779d0003, userName='null'}
REV6UserResourceIdentifier{userKey=8a00a0c85b2726c2015b58aa779d0003, userName='null'}
REV3UserResourceIdentifier{userKey=8a00a0c85c46b657015d4f57d577001c, userName='null'}
REV4UserResourceIdentifier{userKey=8a00a02355cd1c2f0155cd26cef30cd0, userName='null'}
REV1UserResourceIdentifier{userKey=8a00a0c86c120d6f016c42a7f6a70026, 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 Microsoft Azure.

Virtual Machine Recommendations for
Spacevars
0series3
running in Azure

Multiexcerpt
MultiExcerptNameSBC SWe Edge Azure


Warning
titleWARNING: USE RECOMMENDED AZURE 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 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 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 Azure VMs


Azure VM Instance

vCPU

Maximum number of vNICs

Spacevars
0series3
 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 (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 combined vCPU performance (200% is the maximum combined vCPU performance) is baseline "always available" performance; additional vCPU performance available through credits. 

3

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

Note: 60 transcode sessions available with B2s baseline performance.

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

500 sessions, with 480 transcode (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 
    Spacevars
    0series3
    VM uses approximately 5 GiB of Virtual Hard Drive space. Drive size is predetermined by the imported image.


Pagebreak