In this section:
This document describes how to determine the VM (Virtual Machine), vCPU, and RAM resources (or a VM instance for cloud-related deployments) required for an SBC SWe Lite deployment to support an enterprise's planned maximum SIP session density. The SBC SWe Lite session capacity varies in proportion to the vCPU and RAM resources assigned to the VM host; improper assignment of vCPU and RAM resources to a VM may result in SBC SWe Lite being unable to service the required enterprise session workload. Deploying an SBC SWe Lite instance applies to the following:
Term | Definition |
---|---|
Default RTP Media Manipulation Mode Scenario | A bi-directional IP-based RTP ↔ RTP media manipulation mode session scenario providing G.711 (RTP) ↔ G.729ab (SRTP) transcoding services. This is the suggested RTP media manipulation scenario when determining a VM's vCPU and RAM resource requirements. |
RTP Media Manipulation Mode Session | A bi-directional IP-based RTP ↔ RTP media session that receives services from the virtual DSP (Digital Signal Processor) logic within the SBC SWe Lite. Virual DSP services include translation of media from one codec to another ("transcoding"), encrypting/decrypting media, in-band tone detection, enhanced interoperability, improved user experience, and other media-related services that require direct access to the media flow and information. |
RTP Media Session | A bi-directional flow of audio, video, or other real-time information (such as FAX) between two endpoints that may or may not directly transit the SBC. |
RAM | Random Access Memory. Refer to Random Access Memory. For SBC SWe Lite planning, RAM requirements are always presented in integer GiB multiples (https://en.wikipedia.org/wiki/Gibibyte ). |
vCPU | Refer to https://www.quora.com/What-is-the-difference-between-a-core-a-virtual-CPU-and-a-thread. For SBC SWe Lite planning, vCPU requirements are always presented in integer vCPU multiples. |
RTP direct media mode sessions do not flow through the SBC SWe Lite. These flows are common with endpoints that reside within the same physical premises (such as a single branch office) where there is no need for any manipulation of any aspect of the media flow (such as codecs, headers, and encrypting/decrypting). The implications of such sessions on the SBC SWe Lite are:
The SBC SWe Lite supports a single RTP media session on a 1:1 basis with an associated SIP signaling session. Note the following:
Refer to Working with Licenses for a description of available SBC SWe Lite SIP session licenses that include support for RTP direct media mode session, as follows:
These flows are common with endpoints that do not reside within the same physical premises, but do reside within the same enterprise. If these sessions require access to a public SIP trunk (call flows out of the corporate WAN), there may be a need for encryption/decryption and IP address manipulation services. Many public carriers do not support the forwarding of encrypted media or private IP addresses. However, complex media manipulation such as transcoding is not required due to enterprise-wide policies surrounding codec usage being in force. The implications for these sessions include:
The SBC SWe Lite supports a single RTP proxy media mode session on a 1:1 basis with an associated SIP signaling session. Note the following regarding RTP proxy media mode sessions:
Refer to Working with Licenses for more information about SIP session licenses that support RTP proxy media mode sessions:
A media session requiring media manipulation is labeled an RTP media manipulation mode session. Such flows are common with endpoints that communicate across enterprise and public boundaries. The SBC SWe Lite delivers RTP media manipulation services through the application of virtual DSP (Digital Signal Processing) feature to the media session. The media manipulation services delivered by the SBC SWe Lite include:
The implications of RTP media manipulation mode sessions are the following:
Consider RTP media manipulation mode session density to determine a VM's vCPU and RAM resources for a specific SBC SWe Lite.
The SBC SWe Lite supports a single RTP media manipulation mode session on a 1:1 basis with an associated SIP signaling session. See below.
Refer to Working with Licenses for a description of available SBC SWe Lite SIP session licenses that include support for RTP media manipulation mode sessions. See below.
The table below is a guide to the maximum capacity of an SBC SWe Lite configured into a VM (Virtual Machine) with a given set of vCPU and RAM resources. The maximum number of the following items vary depending upon a given VM resource profile:
Use the tables below to identify and plan the required resource configuration for a given deployment of an SBC SWe Lite to address SIP traffic flow.
Call Performance - KVM, VMware, Microsoft Hyper-V On-Premises Deployments 1 Maximum number of concurrent sessions. The number assumes that calls are made using RTP/SRTP Proxy mode, or a mix of RTP/SRTP Proxy, media manipulation and video calls. 2 Maximum number of concurrent sessions with virtual DSP intervention. See Transcoding Capacity below for details. 3 Maximum number of concurrent audio/video sessions. The total system capacity is affected if A/V calls are introduced into the call mix. Maximum number of calls is reduced by the number of video streams used. For example, 1 vCPU instance processing 25 A/V calls has a total capacity of: 300 (max number of calls) - 25 (calls processed with 1 vCPU instance) = 275 calls. 4 Maximum number of concurrent sessions (when virtual DSP intervention is applied to 450 sessions) is 1000. 5 Maximum number of concurrent sessions (when virtual DSP intervention is applied to 600 sessions) is 600. 6 Maximum number of proxy media mode concurrent sessions is reduced by a count equivalent to the active number of concurrent RTP media manipulation sessions. Refer to note 1. 7 Supported by *-SG/*-SGX/*-SP licenses. 8 Supported by *-SGX/*-SP licenses. 9 Supported only by *-SP licenses. 10 Supported by -SGX/-SG/-SP. See "SIP Signaling & RTP Direct Media/RTP Proxy Sessions without Encryption Services" in Working with Licenses. Modified: for 8.1.5 Call Performance - Microsoft Azure Cloud 1 Maximum number of concurrent sessions. The number assumes that calls are made using RTP/SRTP Proxy mode, or a mix of RTP/SRTP Proxy, media manipulation and video calls. 2 Maximum number of concurrent sessions with virtual DSP intervention. See Transcoding Capacity below for details. 3 Maximum number of proxy media mode concurrent sessions is reduced by a count equivalent to the active number of concurrent RTP media manipulation sessions. Refer to note 1. 4Supported by -SG-CLOUD/-SGX-CLOUD/-SP-CLOUD licenses. 5 Supported by -SGX-CLOUD/-SP-CLOUD licenses. 6 Supported by -SP-CLOUD license. The number of RTP Port Pairs must be configured slightly larger than the actual number of ports required to support the projected number of calls. We recommend you over-allocate the number of port pairs by approximately 25 - 30% above the number of calls you want to support. For details, see Configuring the Media System.SWe Lite Virtual Machine Resources, applicable to all supported hypervisors (KVM, VMware® Microsoft Hyper-V) Maximum SIP
with corresponding
RTP Media Sessions1 SIP Signaling Session Limits RTP Media Session Limits Maximum Call Rate Setup (CPS) Media Manipulation Mode2 (Requires Virtual DSP Intervention) Proxy Media Mode (No Virtual DSP Intervention) Audio/Video Streams 3 vCPU # GB RAM Maximum TCP/TLS-based SIP↔SIP Signaling Sessions7 Maximum SIP Registrations (60 minute refresh rate) No transcode, with in-band services scenario8 Default scenario: G.711/G.729ab RTP ↔ G.729ab/G.711SRTP, with in-band services9 Encryption services: G.711 RTP ↔ G.711 SRTP8 No encryption services: RTP ↔ RTP/SRTP ↔ SRTP10 1 1 GiB 100 300 1000 100 100 300 6 300 6 25 10 2 1.5 GiB 1000 1000 1000 200 200 1000 6 1000 6 50 10 4 2.5 GiB 1000 1000 4 /600 5 5000 450 4 /600 5 450 4 /600 5 1000 6 1000 6 100 10 10 2.5 GiB 1000 1200 5000 1200 1200 1200 1200 100 10 Azure Virtual Machine (VM) Resources Maximum SIP
with corresponding
RTP Media Sessions1 SIP Signaling Session Limits RTP Media Session Limits Maximum Call Rate Setup (CPS) Media Manipulation Mode2 (Requires Virtual DSP Intervention) Proxy Media Mode (No Virtual DSP Intervention) VM Instance vCPU Maximum TCP/TLS-based SIP↔SIP Signaling Sessions4 Maximum SIP Registrations (60 minute refresh rate) No transcode, with in-band services scenario5 Default scenario: G.711/G.729ab RTP ↔ G.729ab/G.711SRTP, with in-band services6 Encryption services: G.711 RTP ↔ G.711 SRTP5 No encryption services: RTP ↔ RTP/SRTP ↔ SRTP4 B1ms 1 10 10 100 10 10 10 3 10 3 10 B2s 2 100 100 500 30 30 100 3 1003 10 DS1_v2 1 300 300 1000 100 100 300 3 300 3 10 DS3_v2 4 1000 1000 5000 400 400 500 3 1000 3 10
Transcoding Capacity - KVM, VMware, Microsoft Hyper-V On-premises Deployments (1, 2, 4 vCPU)
Transcoding Scenario | Virtual Machine vCPU Count | |||
CODEC 1 | CODEC 2 | 1 vCPU | 2 vCPU | 4 vCPU |
---|---|---|---|---|
G.711A-law or G.711u-law | G.711A-law or G.711u-law | 100 | 200 | 600 |
G.711A-law or G.711u-law | G.723 | 80 | 160 | 480 |
G.711A-law or G.711u-law | G.726 or G.729 | 100 | 200 | 600 |
G.711A-law or G.711u-law | AMR WB | 38 | 76 | 225 |
G.711A-law or G.711u-law | Opus | 24 | 54 | 165 |
G.711A-law or G.711u-law | T.38 | 50 | 100 | 300 |
Transcoding Capacity - KVM, VMware, Microsoft Hyper-V On-premises Deployments (10 vCPU)
CODEC 1 | CODEC 2 | 10 vCPU |
---|---|---|
G.711A-law or G.711u-law | G.711A-law or G.711u-law | 1200 |
G.711A-law or G.711u-law | G.729 | 1200 |
Opus | G.711A-law/mu-law | 360 |
Transcoding Capacity - Microsoft Azure Cloud Deployments
Transcoding Scenario | Microsoft Azure VM Instance | ||||
CODEC 1 | CODEC 2 | B1MS VM | B2S VM | DS1_v2 | DS3_v2 |
---|---|---|---|---|---|
G.711A-law or G.711u-law | G.711A-law or G.711u-law | 10 | 30 | 100 | 400 |
G.711A-law or G.711u-law | G.726 or G.729 | 10 | 30 | 100 | 400 |
The following table outlines the SILK performance numbers for Microsoft Azure Cloud deployments. SILK Performance for Microsoft Azure Cloud Deployments The following table outlines the SILK performance numbers for On-premises deployments. SILK Performance for On-premises Deployments 95SILK Performance for Microsoft Azure Cloud Deployments
Transcoding Scenario Microsoft Azure VM Size B1ms B2s DS1_v2 DS3_v2 SILKNB SRTP -> G711U RTP 10 30 95 400 SILKNB SRTP -> G729A RTP 10 30 50 300 SILKNB SRTP -> SILKWB RTP 10 30 35 200 SILK Performance for On-premises Deployments
Codec Virtual Machine vCPU Count 1 vCPU 2 vCPU 4 vCPU SILK-WB-G711U 55 135 340 SILK-WB-G729 35 95 230 SILK-WB-SILK-NB 35 88 215 SILK-NB-G711U 95 200 595 SILK-NB-G729 50 130 325 G711U-SILK-NB 200 595 G729-SILK-NB 50 130 325 SILK-NB-WB 35 88 215
Identify and record the minimum quantity of VM resources to support your maximum default RTP media manipulation mode sessions:
For an on-premises SBC SWe Lite deployment, refer to Table 1 and record the required minimum quantity of vCPUs and RAM found in the vCPU # and GB RAM column that supports a number of default RTP media manipulation mode sessions greater or equal to your deployment need; note the number of supported default RTP media manipulation mode sessions is found in the Default scenario: G.711/G.729ab RTP ↔ G.729ab/G.711SRTP, with in-band services column.
For an Microsoft Azure-based SBC SWe Lite deployment, refer to Table 2 and record the required minimum Azure VM instance type found in the VM instance column that supports a number of default RTP media manipulation mode sessions greater or equal to your deployment need; note the number of supported default RTP media manipulation mode sessions is found in the Default scenario: G.711/G.729ab RTP ↔ G.729ab/G.711SRTP, with in-band services column.
If on-premises SBC SWe Lite deployment is required to support a transcoding scenario other than G.711 ↔ G.729ab (the default RTP media manipulation mode session scenario), use Table 3 to identify the required minimum quantity of vCPUs to assign to the VM. For example, support for 50 G.711 ↔ OPUS sessions requires 2 vCPUs. The 2 vCPU figure should be used when undertaking step 2(a).
Identify and record the minimum quantity of VM resources to support the additional RTP proxy session mode sessions (beyond the maximum default RTP media manipulation mode sessions) for your SBC SWe Lite deployment.
The maximum available RTP proxy session mode session capacity is not equal to a value found in the Maximum SIP with corresponding RTP Media Sessions column in Tables 1 or 2; rather, it is determined by subtracting the maximum default RTP media manipulation mode sessions identified in Step 1 from the Maximum SIP with corresponding RTP Media Sessions column value associated with the quantity of vCPUs and RAM recorded from Step 1.
Step | Action | ||||||
---|---|---|---|---|---|---|---|
a | For an on-premises SBC SWe Lite deployment, refer to Table 1 and calculate the maximum available RTP proxy session mode session capacity with the quantity of vCPUs and RAM recorded from Step 1 (or Step 2 (b)). For an Microsoft Azure-based SBC SWe Lite deployment, refer to Table 2 and calculate the maximum available RTP proxy session mode session capacity with the Azure VM instance type recorded from Step 1 (or Step 2(b)). | ||||||
b | Identify if the calculated maximum available RTP proxy session capacity from (a) above is larger than your required additional RTP proxy session mode sessions:
|
For an on-premises SBC SWe Litedeployment, refer Installing SBC SWe Lite.
For details on the numbers used for calculations, see the Transcoding and Call Performance tables above.
800 additional RTP proxy session mode sessions are required.
Refer to Running a SWe Lite via Microsoft Azure Marketplace to start a DS3 v2 VM hosting the SBC SWe Lite.
800 additional RTP proxy session mode sessions with encryption/decryption services.
Refer to Hyper-V installation guide to begin the process of instantiating a VM with 1 vCPU and 1 GiB RAM to host the SBC SWe Lite.
The required vCPU and RAM for a high capacity SIP Registration deployment are relatively simple: if the number of SIP registrations exceeds 1,000 endpoints, configure the VM with a minimum of 4 vCPUs and 2.5 GiB RAM. If less/equal to 1,000, the RAM is defined by the required session capacity.
SIP Signaling groups (provisioning constructs that represent a connection between the SBC SWe Lite and another SIP based peer) can be configured to use either RTP media manipulation session mode or a RTP proxy session mode. See below:
There are several alternatives for DTMF calls:
The SBC SWe Lite supports 25 video streams per vCPU to a maximum of 100 streams. Exceeding 4 vCPUs does not allow more than 100 video streams.