Page History

Panel
Panel
In this section: Table of Contents maxLevel 3

Introduction

This document describes how to determine vCPU and RAM resources required for an to determine the VM (Virtual Machine), vCPU, and RAM resources (or a VM instance for cloud-related deployments) required for an 

Spacevars
0 product3

 to process planned SIP-based traffic models. Because many deployments are limited due to constraints imposed by existing equipment, it is important to understand and configure your system for media manipulation.

Purpose

This document is intended to help partners and customers:

• Identify the number of media sessions requiring manipulation supported by a given vCPU and RAM configuration of an 

Spacevars
0 product3

• Identify the number

 deployment to support an enterprise's planned maximum SIP session density. The 

Spacevars
0 product3

 session capacity varies in proportion to the vCPU and RAM resources assigned to the VM host; improper assignment of vCPU and RAM resources to

be provisioned to an 

a VM may result in

Spacevars
0 product3

 to address a given number of media sessions requiring manipulation

 being unable to service the required enterprise session workload. Deploying an SBC SWe Lite instance applies to the following:

Both goals support a partner/customer's effort to ensure traffic processing expectations are met in an 

Spacevars
0 product3

 deployment.

The available 

• For an on-premises Microsoft Hyper-V/VMware ESXi/KVM VMM (Virtual Machine Monitor) deployment, identify (for the VM that will host the

• Spacevars
  0 product3

 configurations ("Partner Configurator"), which includes a description of embedded features and options, is available behind the 

• ) the number of vCPU and RAM resources to service a given maximum SIP session density.
• For a Microsoft Azure cloud deployment, identify the required Azure VM for an 

  Spacevars
  0 product3

   to address the required maximum SIP session density

partner portal

• .

Definitions and Terminology

 

Concepts

and Definitions

RTP Direct Media Mode Sessions

Definition

Description

A media session that does RTP direct media mode sessions do not flow through the the

Spacevars
0 product3

. 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 

Spacevars
0 product3

 are:

• • The 

    Spacevars
    0 product3

     does not consume any a VM's RAM or vCPU resources processing the RTP direct media mode sessions; vCPU and RAM resources are consumed for SIP signaling and call processing only.
  • Partners/customers do not need to consider RTP direct media mode sessions when determining an appropriate a VM's vCPU and RAM assignment to resources for a given 

    Spacevars
    0 product3

     deployment.

Licensing

The 

Spacevars
0 product3

 supports a single media session on a 1:1 basis with an associated SIP signaling session. Note the following:

•

• • Multiple direct media mode session streams (audio, video, and so on) may be associated with a given SIP session, and do not require additional licensing unless identified elsewhere.
    
    
  • Only one mode of media is supported against a given SIP session. For example, one stream of media in direct media mode and one stream of media in RTP proxy media mode, cannot both be associated with the same SIP signaling session.

Licensing

The 

Spacevars
0 product3

 requires a license to enable a given quantity of SIP signaling sessions.
•

 supports a single RTP media session on a 1:1 basis with an associated SIP signaling session. Note the following:

• • The 

    Spacevars
    0 product3

 supports a single media session

• •  requires a SIP session license to enable a given SIP signaling session. Refer to: SIP Session Licensing.
  • Any SIP session license also enables RTP direct media mode session support on a 1:1 basis with an associated SIP signaling session

without further licensing. Specifically:

• A direct media mode session will be supported without any additional licensing licensing beyond the corresponding SIP session license.
• Multiple direct media mode session streams (audio, video, and so on) may be associated with a given SIP session, and will not require additional licensing unless identified elsewhere.
• Only one mode of media is supported against a given SIP session. For example, you cannot have one stream of media in direct media mode, one stream of media in RTP proxy media mode, and both associated with the same SIP signaling session.

Refer to Obtaining and Installing a SWe Lite License and Working with Licenses or a description of available 

Spacevars
0 product3

 session and feature licenses.

RTP Proxy Media Mode Sessions

Definition

A media session that flows through the 

Spacevars
0 product3

 but does not require media manipulation. These flows may be common with endpoints that may 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, as many public carriers do not support the forwarding of encrypted media or private IP addresses. However, complex media manipulation such as transcoding will not be required due to enterprise-wide policies surrounding codec usage being in force. The implications of such sessions on the 

Spacevars
0 product3

 are:

1. The 

Spacevars
0 product3

 consumes RAM and vCPU resources processing the RTP proxy media mode sessions
2. Consumption of RAM and vCPU resources is less than the consumption of RAM and vCPU resources associated with media manipulation mode sessions
3. Partners/customers need to consider RTP proxy media mode sessions when determining an appropriate vCPU and RAM assignment to a given 

Spacevars
0 product3

RTP Proxy Media Mode Sessions –

• • (i.e., no additional licensing beyond the SIP session license is required for RTP direct media mode session support). 

Refer to Working with Licenses for a description of available 

Spacevars
0 product3

 SIP session licenses that include support for RTP direct media mode session, as follows:

• • For KVM, VMware, Microsoft Hyper-V on-premises SBC SWe Lite deployments, all SIP session licenses that end with the following characters: -SG, -SGX, -SP
  • For Microsoft Azure cloud-based SBC SWe Lite deployments, all SIP session licenses that end with the following characters: -SG-CLOUD, -SGX-CLOUD, -SP-CLOUD

RTP Proxy Media Mode Sessions

Description

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 

  Spacevars
  0 product3

   consumes a VM's RAM and vCPU resources processing the RTP proxy media mode sessions.
• Consumption of RAM and vCPU resources is less than the consumption of RAM and vCPU resources associated with RTP media manipulation mode sessions.
• RTP proxy media mode sessions must be accessed when determining a VM's vCPU and RAM resources for a given 

  Spacevars
  0 product3

  deployment.

• Multiple RTP proxy media mode session streams (audio, video, and so on) may be associated with a given SIP session, and do not require additional licensing unless identified elsewhere.
  
  
• Only ONE mode of media is supported against a given SIP session. For example, with one stream of media in direct media mode and one stream of media in RTP proxy media mode, both cannot be associated with the same SIP signaling session.

Licensing

The 

Spacevars
0 product3

 supports a single RTP proxy media mode session on a 1:1 basis with an associated SIP interworking signaling session. Note the following regarding RTP proxy media mode session:

• An RTP proxy media mode session will be supported without any additional licensing beyond the corresponding SIP session license if encryption/decryption services are not required. Services the SBC is capable of applying to such media streams include:

• The modification of

sessions:

• • The 

    Spacevars
    0 product3

     requires a SIP session license to enable a given SIP signaling session. For more information, refer to: SIP Session Licensing.
    
    
  • Any SIP session license also enables RTP proxy media mode session support without encryption/decryption services on a 1:1 basis with an associated SIP signaling session (i.e. no additional licensing beyond the SIP session license is required for RTP proxy media mode session support without encryption/decryption services). The SBC applies the following:
    
    • The modification of the IP address and other data within the S/RTP, UDP, IP and other header data as provisioned by the user.

•

• • • The pass-through of encrypted media traffic (SRTP ↔ SRTP) where no change is required to the previously applied encryption

• • • .
      
      
  • Select (not all) SIP session licenses also enable RTP proxy media mode session support with encryption/decryption services on a 1:1 basis with an associated SIP signaling session

• An RTP proxy media mode session requiring encryption/decryption services will require additional licensing beyond the corresponding SIP session license

• • . Encryption/decryption services means:
  •
  • • • An RTP proxy media mode session that requires the SBC to support RTP ↔ SRTP conversions
  •
  • • • An RTP proxy media mode session that requires SRTP ↔ SRTP changes, such as a cipher change
  ,
  • • • and authentication algorithm, change as the media flow transits the SBC
  • • • .

  Refer to Working with Licenses for more information about SIP session licenses that support RTP proxy media mode sessions:

  • • For SIP sessions requiring no support for encryption/decryption services within the context of RTP proxy media mode sessions:
      • KVM, VMware, Microsoft Hyper-V on-premises SBC SWe Lite deployments, all licenses that end with the following characters: -SG, -SGX, -SP
      • Microsoft Azure cloud-based SBC SWe Lite deployments, all licenses that end with the following characters: -SG-CLOUD, -SGX-CLOUD, -SP-CLOUD
        
        
    • For SIP sessions requiring support for encryption/decryption services within the context of RTP proxy media mode sessions:
      • KVM, VMware, Microsoft Hyper-V on-premises SBC SWe Lite deployments, all licenses that end with the following characters: -SGX, -SP
      • Microsoft Azure cloud-based SBC SWe Lite deployments, all licenses that end with the following characters: -SGX-CLOUD, -SP-CLOUD

  RTP Media Manipulation Mode Sessions

  Description

  A media session requiring media manipulation is labeled an RTP

  Other considerations:

  • Multiple RTP proxy media mode session streams (audio, video, and so on) may be associated with a given SIP session, and will not require additional licensing unless identified elsewhere
  • Only ONE mode of media is supported against a given SIP session; for example, you cannot have one stream of media in direct media mode, one stream of media in RTP proxy media mode, both associated with the same SIP signaling session

  Refer to Obtaining and Installing a SWe Lite License and Working with Licenses for a description of available 

  Spacevars
  0 product3

   session and feature licenses, including instructions on how to enable RTP proxy encryption/decryption services. 

  RTP Media Manipulation Mode Sessions

  Definition

  A media session requires media manipulation is considered a media manipulation mode session. Such flows may be are common with endpoints that may communicate across enterprise and public boundaries. The common call types that require

  Spacevars
  0 product3

   delivers RTP media manipulation services include the following (not an exhaustive list):through the application of virtual DSP (Digital Signal Processing) feature to the media session. The media manipulation services delivered by the 

  Spacevars
  0 product3

  include:
  1. 1. Transcoding. This includes Sessions that require transcoding, such as G.711 (common codec in enterprises) ↔ G.729ab (common codec in public networks) translation, and G.711 A-law ↔ G.711 µ-law, and so on. Please refer . Refer to Protocols and Protocols and Functions Supported for the list of codecs supported by the 

        Spacevars
        0 product3

        ..
     2. Transrating. Transrating includes Transrating, that is, call legs that carry a different time sample size of media, where the 

        Spacevars
        0 product3

         performs the translation. Used Transrating is used often when enterprises or the service provider is looking to save bandwidth by reducing packet count at the expense of voice quality (should a packet be dropped).
     3. Silence suppression, where the . The

        Spacevars
        0 product3

         looks to remove/insert RTP packets carrying no meaningful media , again to to save packet traffic;.
     4. Fax calls.
        
        1. Fax tone detection and interworking to T.38 (T.38 support will be available in a future release of the 

           Spacevars
           0 product3

           )
        2. G.711 fax media pass-through, as DSP intervention reduces the likelihood of in-band fax signaling/media issues
     5. Any call flow where inIn-band ↔ out-of-band interworking is required. Examples. Required for the following:
        
        1. In-band DTMF tone detection interworking with out-of-band RFC 4733 (supersedes RFC 2833)
        2. In-band DTMF tone detection interworking with SIP INFO messages
        3. Interworking RTP dynamic payload types, required when the subtended SBC peers use differing payload type identifiers from the dynamic RTP payload range (for example 96 - 127) to identify a common payload format (in other words,  codec)
     6. Any form of media Media that originates from the SBC in support of call developments. For example:
        1. Announcement playback
        2. Local
  ring back
  2. 1. 1. ringback tone
        2. Music on Hold
        3. Comfort noise
     2. Jitter compensation
  ,
  3. 1. . Used to maximize user experience with voice quality.
     2. Certified Skype for Business/Teams Phones and Devices interworking with non-certified endpoints. With virtual DSP intervention, 

        Spacevars
        0 product3

        s can address media incompatibility issues
  that at first glance may not be apparent
  4. 1. between certified Skype for Business Server endpoints (
  as documented at 
  5. 1. Refer to https://technet.microsoft.com/en-us/office/dn947482) and other SIP-based client endpoints, such as RTCP reporting interval mismatch, and unrecognized in-band supplementary service requests.

  The implications of RTP media manipulation mode sessions

  on the 

  are the following:

  • • The 

      Spacevars
      0 product3

   are:
  The

  Spacevars
  0 product3

   consumes
  • •  consumes VM RAM and vCPU resources
  processing
  • • to deliver RTP media manipulation
  mode sessions
  • • services via the virtual DSP feature.
    • Consumption of a VM's RAM and vCPU resources is higher
  than
  • • when delivering RTP media manipulation services than the consumption of RAM and vCPU resources associated with RTP proxy media mode
  sessionsPartners/customers need to consider
  • • services.

    • Consider RTP media manipulation mode session density

  when determining an appropriate

  • • to determine a VM's vCPU and RAM

  assignment to

  • • resources for a

  given 

  • • specific

      Spacevars
      0 product3

  Media Manipulation Mode Sessions – Licensing

  The 

  Spacevars
  0 product3

   supports a single media manipulation mode session on a 1:1 basis with an associated SIP signaling session. Note the following regarding licensing implications:

  • A media manipulation mode session requires additional licensing beyond the corresponding SIP session license. Refer to the section above for an example of services available with a media manipulation mode-related license.

  • A media manipulation mode session supports encryption/decryption services. Encryption/decryption services means:

  • An RTP proxy media manipulation mode session that requires that the SBC support RTP ↔ SRTP conversions.
  • An RTP proxy media manipulation mode session that requires SRTP ↔ SRTP changes, such as a cipher change, authentication algorithm change, and so on as the media flow transits the SBC.

  Other considerations:

  • Multiple media manipulation mode session streams (such as audio) may be associated with a given SIP session, and will not require additional licensing unless identified elsewhere.
  • Only one mode of media is supported against a given SIP session. For example, you cannot have one stream of media in media manipulation mode session mode, one stream of media in RTP proxy media mode, both associated with the same SIP signaling session.
  Refer to Obtaining and Installing a SWe Lite License and Working with Licenses for a description of available

  Spacevars
  0 product3

   session and feature licenses, including instructions on how to enable RTP proxy encryption/decryption services. 

  Considerations for Video Interworking in Non-DSP Mode

  To come. Image Removed Image Removed

  Session

  • • . 

      
      

      Note
      title RTP Media Manipulation Mode - Notes
      The virtual DSP (within the context of an RTP media manipulation mode session) supports complete encryption/decryption services, such as RTP ↔ SRTP conversions, cipher change, & authentication algorithm change. Multiple RTP media manipulation mode session streams (audio, video, and so on) may be associated with a given SIP session, and do not require additional licensing unless identified elsewhere. Only one mode of media is supported against a given SIP session; for example, you cannot have one stream of media in RTP media manipulation mode, one stream of media in RTP proxy media mode, both associated with the same SIP signaling session.

      
      

  Licensing

  The 

  Spacevars
  0 product3

   supports a single RTP media manipulation mode session on a 1:1 basis with an associated SIP signaling session. See below.
  • • The 

      Spacevars
      0 product3

       requires a SIP session license to enable a given SIP signaling session. Refer to SIP Session Licensing.
    • Select (not all) SIP session licenses also enable RTP media manipulation mode session support on a 1:1 basis with an associated SIP signaling session.

  Refer to Working with Licenses for a description of available 

  Spacevars
  0 product3

   SIP session licenses that include support for RTP media manipulation mode sessions. See below.
  • • For SIP sessions requiring no support for transcoding and/or transrating but support for all other RTP media manipulation services: 
      • KVM, VMware, Microsoft Hyper-V on-premises SBC SWe Lite deployments, all licenses that end with the following characters: -SGX, -SP, -ME
      • Microsoft Azure cloud-based SBC SWe Lite deployments, all licenses that end with the following characters: -SGX-CLOUD, -SP-CLOUD, -ME-CLOUD
        
        
    • For SIP sessions requiring support for transcoding and/or transrating over and above other RTP media manipulation services: 
      
      • KVM, VMware, Microsoft Hyper-V on-premises SBC SWe Lite deployments, all licenses that end with the following characters: -SP, -ME
      • Microsoft Azure cloud-based SBC SWe Lite deployments, all licenses that end with the following characters: -SP-CLOUD, -ME-CLOUD

  Session Density Map

  The table below is a guide to the maximum capacity of an  an 

  Spacevars
  0 product3

   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:
  • RTP Media media manipulation mode sessions;
  • RTP proxy session mode sessions requiring encryption/decryption services;
  • RTP proxy session mode sessions not requiring encryption/decryption services;
  • Direct media mode sessions (not presented in the table, but equivalent to RTP proxy session mode sessions not requiring encryption/decryption services;)
  • SIP registrations.

  The table will be used extensively to Use the tables below to identify and plan the required resource configuration for a given deployment of an 

  Spacevars
  0 product3

   to address a partner/customer's expected SIP traffic flow.

  Anchor
  SessionDensityMap SessionDensityMap

  caption

  Multiexcerpt include

  0

  MultiExcerptName

  Table

  Performance

  1Session Density MapSWe Lite Virtual Machine Resources, applicable to all supported hypervisors (KVM, VMware®, Hyper-V®)Maximum SIP with corresponding RTP SessionsSIP Signaling SessionsRTP Media SessionsRTP Media Manipulation Mode (transcode, in-band services, encryption, and other services)RTP Proxy Media ModevCPU #GB RAMMaximum TCP/TLS-based SIP Signaling SessionsMaximum SIP Registrations (60 minute refresh rate)No transcode, with in-band services scenarioDefault transcode

  PageWithExcerpt SBC SWe Lite Performance and Capacity

  Multiexcerpt include
  MultiExcerptName Transcoding - For KVM, VMWare and Microsoft Hyper-V PageWithExcerpt SBC SWe Lite Performance and Capacity

  Multiexcerpt include
  MultiExcerptName Transcoding - For Azure PageWithExcerpt SBC SWe Lite Performance and Capacity

  Process to Determine VM Resources 

  1. Identify and record the minimum quantity of VM resources to support your maximum default RTP media manipulation mode sessions: 

     1. For an on-premises

        Spacevars
        0 product3

         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.

  711 SRTP

  1. 1. 711SRTP, with in-band services

  1. 1. column.

     2. For an Microsoft Azure-based 

        Spacevars
        0 product3

         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

  Complex transcode

  1. 1. scenario: G.

  7xx

  1. 1. 711/G.729ab RTP ↔ G.

  7xx SRTP

  1. 1. 729ab/G.711SRTP, with in-band

  services¹Encryption services:

  1. 1. services column.

        Warning
        title Use of Table 3 for non-default RTP media manipulation mode sessions
        If on-premises Spacevars 0 product3  deployment is required to support a transcoding scenario other than G.711

  RTP

  1. 1. ↔ G.

  711 SRTP, with or without RTP/UDP/IP header changesNo encryption services: RTP proxy media mode, including RTP↔RTP,  SRTP↔SRTP, with or without RTP/UDP/IP header changes

  1. 1. 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).

        
        

  2. 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 

     Spacevars
     0 product3

      deployment.

     Warning
     title Calculating the maximum available RTP proxy mode sessions for your VM resource
     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  Spacevars 0 product3  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  Spacevars 0 product3  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: If... Then Calculated capacity from 2 (a) is larger than required RTP proxy session mode sessions Proceed to step 3, using the quantity of vCPUs and RAM determined from point 2(a) above. Calculated capacity from 2 (a) is smaller than required RTP proxy session mode sessions Review Table 1 (or Table 2 for an Azure-based deployment) and increase the quantity of vCPUs and RAM (or upgrade to a more powerful) Azure VM, then re-execute step 2(a).

     
     

  3. Prepare to configure your 

     Spacevars
     0 product3

      with the resources arrived at the end of step 2.

     1. For an on-premises 

        Spacevars
        0 product3

        deployment, refer Installing SBC SWe Lite.

     2. For an Microsoft Azure-based 

        Spacevars
        0 product3

        deployment, refer to Running a SWe Lite via Microsoft Azure Marketplace.

  Examples

  Info
  For details on the numbers used for calculations, see the Transcoding and Call Performance tables above.

  Calculating a VM's vCPU and RAM Resource Requirements for an On-premises Low-Density KVM-based 

  Spacevars
  0 product3

   Deployment

  1. Fifty (50) RTP media manipulation mode sessions are required (a session is equivalent to the Default RTP Media Manipulation Scenario defined above).
     1. A single vCPU and 1 GiB of RAM is the minimal vCPU and RAM count that supports this number of  RTP media manipulation sessions. 
     2. Record these values as the potential number of vCPU and RAM resources to assign to the VM hosting the

        Spacevars
        0 product3

        .
        
        
  2. One hundred (100) additional RTP proxy session mode sessions services are required.
     
     1. A single vCPU and 1 GiB of RAM supports a maximum of 300 total SIP with corresponding RTP sessions.  Subtract the 50 RTP media manipulation mode sessions from the 300 and there are 250 remaining sessions.
     2. 250 sessions is greater than the 100 additional RTP proxy session mode sessions; run concurrent to the 50 RTP media manipulation mode sessions, and use the 1 vCPU and 1 GiB RAM resources identified from point 1.
  3. Refer to the Installing SBC SWe Lite on KVM Hypervisor to configure a VM with 1 vCPU and 1 GiB RAM to host the 

     Spacevars
     0 product3

     .

  Identifying the Microsoft Azure VM Instance for a Cloud-based 

  Spacevars
  0 product3

   Deployment

  111001001000505050100100221000100010001001001001000100042100010001000300300300100010004410001000500030030030010001000 

  ¹ G.722 (AMR) reduces values by 30%.

  How to Determine vCPU and RAM Requirements

  Follow these steps to determine the number of vCPUs and RAM required for your 

  Spacevars
  0 product3

   deployment.

• Determine the number of RTP media manipulation mode sessions needed (taking into account future growth): From Table 3, identify the required minimum quantity of vCPUs and RAM to address your required capacity, and then record the values.

• Determine the additional RTP proxy session mode sessions requiring encryption/decryption services for your 

  Spacevars
  0 product3

   deployment (taking into account future growth):

  Step	Action
  a	From Table 3, identify the maximum available RTP proxy session mode session capacity (with encryption/decryption services) available with the quantity of of vCPUs and RAM recorded from Step 1.
  b	Determine if the maximum available RTP proxy session capacity from (a) above is larger than your required capacity of additional RTP proxy session mode sessions requiring encryption/decryption services: If... Then Capacity from (a) is larger Proceed to step 3, using the quantity of vCPUs and RAM determined from point 1 above. Capacity from (a) is smaller Review Table 3 and increase the quantity of vCPUs and RAM until you arrive at a quantity of both that supports an RTP proxy session capacity (with encryption/decryption services) equal to/greater than your required number of sessions. Record these values.

Determine the additional RTP proxy session mode sessions not requiring encryption/decryption services for your 

Spacevars
0 product3

 deployment (taking into account future growth):


Step	Action
a	From Table 3, identify the total number of RTP media sessions available with the quantity of vCPUs and RAM recorded from point 2(a) or 2(b) above. This value can be found in the Maximum SIP with corresponding RTP Sessions column.
b	Add the number of required RTP media manipulation mode sessions and RTP proxy session mode sessions requiring encryption/decryption services and record the value.
c	Subtract the value recorded in 3(b) from the value recorded in 3(a).
d	Determine if the value in (c) above is greater than/equal to the required additional RTP proxy session mode sessions not requiring encryption/decryption services for your Spacevars 0 product3 deployment.    If... Then The value in (c) above is greater than/equal to Proceed to step 4, using the quantity of vCPUs and RAM determined from point 3(a) above. The value in (c) above is less than Review Table 3 and increase the quantity of vCPUs and RAM and repeat steps 3(a) through 3(c) until you arrive at a quantity of both that supports an overall session capacity greater than your total required number of sessions across all modes. Record these vCPU and RAM values.

• Prepare to configure your 

  Spacevars
  0 product3

   with the required number of vCPUs and RAM by referring to Configuring the SBC Edge and SBC SWe Lite.

Examples

Calculating the vCPU & RAM Resource Requirements for a Low-Density 

Spacevars
0 product3

 Deployment

1. I need 15 RTP media manipulation mode sessions (sessions will be equivalent to the Default Media Manipulation Scenario defined above). From Table 3 I see a single vCPU and 1 GB of RAM will support this capacity. I record these values as the potential number of vCPU and RAM resources to assign to my 

Spacevars
0 product3

.
2. I need 35 additional RTP proxy session mode sessions requiring encryption/decryption services. From Table 3 I see a single vCPU and 1 GB of RAM will support up to 100 RTP proxy session mode sessions requiring encryption/decryption services  I continue to use the number of vCPU and RAM resources from point 1 to assign to my 
1.  200 RTP media manipulation mode sessions that support G.711 ↔ G.729ab transcoding are required.
   • The F2s VM supports this capacity of the default RTP media manipulation sessions. 
   • Record the F2s value as the potential Azure VM that will host the 

1. • Spacevars
     0 product3

     .
3

1. 2.

I need 50 2 GB of RAM will support this capacity. I record these values as the potential number of vCPU and RAM resources to assign to my 

1. 800 additional RTP proxy session mode sessions

not requiring encryption/decryption services.

(a) From Table 3, I see a single vCPU and 1 GB of RAM will support a maximum of 100 total sessions.
(b) The sum from adding the required media manipulation mode sessions plus RTP proxy session mode sessions requiring encryption/decryption services is 50.
(c) The difference from subtracting 3(b) from 3( a) results in 50 sessions.
(d) As 3(c) is equal to the 50 RTP proxy session mode sessions not requiring encryption/decryption services, I continue to use the number of vCPU and RAM resources determined from point 2 above to assign to my 

Spacevars
0 product3

.

Calculating the vCPU & RAM Resource Requirements for a High-Density 

Spacevars
0 product3

 Deployment

1. I need 100 RTP media manipulation mode sessions (sessions will be equivalent to the RTP Default Media Manipulation Scenario defined above). From Table 3, I see 2 vCPU and

1. are required.

   • The F2s VM supports 1000 SIP with corresponding RTP media sessions.
   • Subtract the 200 RTP media manipulation mode sessions from the 1000, and 800 sessions remain.
   • Record the F2s VM instance as the 800 sessions determined previously is equal to the 800 additional RTP proxy session mode sessions required to run concurrent to the 200 RTP media manipulation mode sessions.

   3. Refer to Running a SWe Lite via Microsoft Azure Marketplace to start an F2s VM hosting the 

1. Spacevars
   0 product3

2. I need 400 additional RTP proxy session mode sessions requiring encryption/decryption services. From Table 3, I see a 2 vCPU and 2 GB of RAM will support up to 1000 RTP proxy session mode sessions requiring encryption/decryption services alongside a maximum of 100 media manipulation mode sessions. I continue to use the number of vCPU and RAM resources from point 1 to assign to my 

1. .

Calculating the vCPU and RAM Resource Requirements for an On-premises High-Density Hyper-V based 

Spacevars
0 product3

 Deployment

1. 200 RTP media manipulation mode sessions are required to support G.711 ↔ AMR WB transcoding.
   
   
   • 4 vCPU supports this capacity. 
   • Record the 4 vCPU value as the potential number of vCPU resources to assign to the VM that will host (under Hyper-V) the 

     Spacevars
     0 product3

     .
1. • Note the required RAM will be determined in the next step.

   2. 800

3. I need 500

1. additional RTP proxy session mode sessions

not requiring

1. with encryption/decryption services.
   

(a)

1. 
   

   • From Table
3
1. • 1, I see
a 2
1. • 4 vCPU and 2
GB
1. • .5 GiB of RAM
will support up to 1000 total sessions.

(b) The sum of adding the required media manipulation mode sessions and RTP proxy session mode sessions requiring encryption/decryption services is 500.

(c) The difference from subtracting 3( b) from 3(a) is 500 sessions.

(d) As 3(c) is equal to the 500 RTP proxy session mode sessions not requiring encryption/decryption services, I continue to use the number of vCPU and RAM resources (2 vCPUs, 2 GB RAM) determined from point 2 above to assign to my 
1. • supports 1000 SIP with corresponding RTP media sessions are required.
   • Subtract the 200 RTP media manipulation mode sessions from the 1000, and 800 sessions remain.
   • Record the 4 vCPU and 2.5 GiB RAM figures; the 800 session figure determined previously is equal to the 800 additional RTP proxy session mode sessions required to run concurrent to the 200 RTP media manipulation mode sessions.

   3. Refer to Hyper-V installation guide to begin the process of instantiating a VM with 1 vCPU and 1 GiB RAM to host the 

   Spacevars
   0 product3

   .

Calculating the vCPU

&

and RAM Resource Requirements for a High-Density SIP Registration 

Spacevars
0 product3

 Deployment

The required vCPU and RAM for a high capacity SIP Registration deployment are relatively simple: if the # number of SIP registrations exceeds 1000 1,000 endpoints, please configure the VM with a minimum of 4 vCPUs and 4 GB 2.5 GiB RAM. If less/equal to 10001,000, the RAM is defined by the required session capacity.

Considerations for RTP Media Manipulation Session Mode versus RTP Proxy Session Mode

SIP Signaling Group Considerations

SIP Signaling groups (provisioning constructs that represent a connection between the 

Spacevars
0 product3

 and another SIP based peer) can be configured to use either RTP media manipulation session mode or a RTP proxy session mode. Note the followingSee below:
•
• Preference can be set so that either media manipulation session mode or RTP proxy session mode is preferred, but not required.
•
• If RTP proxy session mode is configured as preferred by both signaling groups, the call proceeds using RTP proxy session mode.
•
• If media manipulation session mode is configured as preferred by both signaling groups, the call proceeds in media manipulation session mode.
•
• If one signaling group is configured as media manipulation session mode preferred, and the other signaling group is configured as RTP proxy session mode preferred, the selection of mode is based on the preference of the signaling group associated with the party initiating the call. If media manipulation session mode is preferred but there is no available resource for the initiating party, the initiating party
will fall
• falls back to attempt the call using RTP proxy session mode.
•
• After a media path is established between the SIP client and the 

  Spacevars
  0 product3

   in either media manipulation session mode or RTP proxy session mode, there is no support for a mid-call dynamic switch to change mode – this includes the case of call transfer and conference. This is not necessarily a limitation – it
simply
• emphasizes the
importance of understanding the network deployment/architecture. It simply means that
• importance of understanding the network deployment/architecture
needs to be understood
• .
•
• If media manipulation session mode is preferred but not required, and if the other signaling group is configured for RTP proxy session mode only, the call goes through using RTP proxy session mode. This improves preservation of the media manipulation session mode resource for calls which require the resources most.
However, keep in mind that there is no support for a
• A mid-call dynamic switch to change mode, including the case of call transfer and conference is not supported. This is not necessarily a limitation. This also emphasizes the importance of understanding the network deployment/architecture.
•
• If media manipulation session mode is either required or preferred and a RTP proxy session mode route is not possible, the 

  Spacevars
  0 product3

   must have an available media manipulation session mode
resource – otherwise
• resource. Otherwise, the call will fail.

Considerations for DTMF

There are several alternatives for DTMF calls:

•
• When a DTMF call is received, the 

  Spacevars
  0 product3

   terminates the call and transmits G.711. Other codec types may also be used. However, types such as G.723.1 may be less reliable.
•
• When a DTMF call is received, the 

  Spacevars
  0 product3

   terminates the call and transmits the signals as out-of-band RFC 2833/4733 compliant messages or out-of-band SIP INFO messages.
•
• A signaling group can be provisioned to transmit in-band signals as voice, RFC 2833/4733, or SIP INFO messages. There is no fall-back function.
•
• In the case of RTP proxy session mode, the 

  Spacevars
  0 product3

   does not process the DTMF.

Considerations for Video Interworking

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.pagebreak