Versions Compared

Old Version 2

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=8a00a02355cd1c2f0155cd26ce5f0b8d, userName='null'}
AUTH1UserResourceIdentifier{userKey=8a00a0c85b2726c2015b58aa779d0003, userName='null'}
JIRAIDAUTHCHOR-1899, CHOR-

1607

2397
REV5UserResourceIdentifier{userKey=8a00a0c85b2726c2015b58aa779d0003, userName='null'}
REV6

UserResourceIdentifier{userKey=8a00a0c85b2726c2015b58aa779d0003, userName='null'}
REV3UserResourceIdentifier{userKey=8a00a02355cd1c2f0155cd26c99e02c0, userName='null'}
REV4UserResourceIdentifier{userKey=8a00a02355cd1c2f0155cd26c91d01f9, userName='null'}
REV1UserResourceIdentifier{userKey=8a00a02355cd1c2f0155cd26c9d6032b, userName='null'}
REV2UserResourceIdentifier{userKey=8a00a02355cd1c2f0155cd26cabc04c3, userName='null'}

REV3REV4REV1REV2

 


Panel

In this section:

Table of Contents
maxLevel43

Introduction

This document describes how to identify the required vCPU This document describes how to determine the VM (Virtual Machine), vCPU, and RAM resources (or a VM instance for an SBC SWe Lite to process planned SIP-based traffic models.

Purpose

This document is intended to help partners and customers accomplish one of the following goals:

• Identify the number of media sessions requiring manipulation supported by a given vCPU and RAM configuration of an SBC SWe Lite;
• Identify the number of vCPU and RAM resources to be provisioned to an SBC SWe Lite to address a given number of media sessions requiring manipulation.

Both goals support a partner/customer's effort to ensure traffic processing expectations are met in a given SBC deployment.

How To Use This Document

This document is intended to be used offline by Sonus customers to help select an SBC SWE Lite configuration instance that includes an appropriate quantity of vCPU and RAM resources to support a given density of call sessions subject to media intervention. The available SBC SWe Lite configurations (i.e. "Partner Configurator"), which includes a description of embedded features and options, is available behind the partner portal.

Definitions and Terminology

Caption

cloud-related deployments) required for an 

Spacevars
0product3
 deployment to support an enterprise's planned maximum SIP session density. The 
Spacevars
0product3
 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
Spacevars
0product3
 being unable to service the required enterprise session workload. Deploying an SBC SWe Lite instance applies to the following:

  • For an on-premises Microsoft Hyper-V/VMware ESXi/KVM VMM (Virtual Machine Monitor) deployment, identify (for the VM that will host the
    Spacevars
    0product3
    ) 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
    0product3
     to address the required maximum SIP session density.

Definitions and

0Table1

Terminology

TermDefinition
Default RTP Media Manipulation Mode ScenarioA
basic IP ↔ IP
bi-directional IP-based RTP ↔ RTP media manipulation mode session scenario
for the SBC SWe Lite is
providing G.711 (RTP) ↔ G.729ab (SRTP) transcoding services. This is
considered as
the
default
suggested RTP media manipulation scenario
for SBC SWe Lite when calculating
when determining a VM's vCPU and RAM resource requirements.
RTP Media Manipulation
The action taken by
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 on a bi-directional media session to accomplish some form of intended media manipulation such as
Spacevars
0product3
. Virual DSP services include translation of media from one codec to another ("transcoding"), encrypting/decrypting media,
and Media Session
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
subtend
transit the SBC.
RAM
Random Access Memory. Refer to Random Access Memory. For
SBC SWe Lite
Spacevars
0product3
planning, RAM requirements are always presented in integer
GB
GiB multiples (
Gigabyte
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
Spacevars
0product3
planning, vCPU requirements are always presented in integer vCPU multiples.
   Caption
0Table
1Concepts


Concepts

RTP Direct Media

ConceptDefinitionDirect Media

Mode Sessions

 

 

A media session that does

Description

RTP direct media mode sessions do not flow through the

SBC SWe Lite

Spacevars
0product3
. 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:
1. The SBC SWe Lite does not consume any

the 

Spacevars
0product3
 are:

    • The 
      Spacevars
      0product3
       does not consume 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.
2.
    • Partners/customers do not need to consider RTP direct media mode sessions when determining
an appropriate
    • a VM's vCPU and RAM
assignment to a given SBC SWe Lite.
    • resources for a given 
      Spacevars
      0product3
       deployment.
    • 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
0product3
 supports a single RTP media session on a

Licensing

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

• The SBC SWe Lite requires a license to enable a given quantity of SIP signaling sessions.
• The SBC SWe Lite supports a single media session 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, etc.) 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 for a description of available SBC SWe Lite session and feature licenses. 

RTP Proxy Media Mode Sessions

. Note the following:

    • The 
      Spacevars
      0product3
       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 (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
0product3
 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

A media session that flows through the SBC SWe Lite 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

 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

. Many public carriers do not support the forwarding of encrypted media or private IP addresses.

However

 However, complex media manipulation such

as

as transcoding

will not be

is not required due to enterprise-wide policies surrounding codec usage being in force. The implications

of such sessions on the SBC SWe Lite are:1. The SBC SWe Lite consumes

for these sessions include:

  • The 
    Spacevars
    0product3
     consumes a VM's 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 RTP media manipulation mode sessions

3. Partners/customers need to consider
  • .
  • RTP proxy media mode sessions must be accessed when determining
an appropriate
  • a VM's vCPU and RAM
assignment to a given SBC SWe LiteRTP Proxy Media Mode Sessions – Licensing
  • resources for a given 
    Spacevars
    0product3
    deployment.
  • Multiple
As mentioned previously, the SBC SWe Lite supports a single
  • RTP proxy media mode session streams (audio, video, and so on
a 1:1 basis with an associated SIP interworking 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 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

• 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 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

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 for a description of available SBC SWe Lite session and feature licenses, including instructions on how to enable RTP proxy encryption/decryption services. Media Manipulation Mode SessionsA media session requires media manipulation is considered a media manipulation mode session. Such flows may be common with endpoints that may communicate across enterprise and public boundaries. The common call types that require media manipulation services include the following (not an exhaustive list):
  • ) 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
0product3
 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:

    • The 
      Spacevars
      0product3
       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. 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 media manipulation mode session. Such flows are common with endpoints that communicate across enterprise and public boundaries. The

Spacevars
0product3
 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 
Spacevars
0product3
include:

    1. Transcoding. This includes G.711 (common codec in enterprises) ↔ G.729ab (common codec in public networks) translation, and G.711 A-law ↔ G.711 µ-law. Refer to Protocols and Protocols and Functions Supported for the list of codecs.
    2. Transrating. Transrating includes call legs that carry a different time sample size of media, where the 
      Spacevars
      0product3
       performs the translation. 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. The
      Spacevars
      0product3
       looks to remove/insert RTP packets carrying no meaningful media to save packet traffic.
    4. Fax calls.
      1. Fax tone detection and interworking to T.38
      2. G.711 fax media pass-through, as DSP intervention reduces the likelihood of in-band fax signaling/media issues
    5. In-band ↔ out-of-band interworking. 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. Media that originates from the SBC in support of call developments. For example:
      1. Announcement playback
      2. Local ringback tone
      3. Music on Hold
      4. Comfort noise
    7. Jitter compensation. Used to maximize user experience with voice quality.
    8. Certified Skype for Business/Teams Phones and Devices interworking with non-certified endpoints. With virtual DSP intervention, 
      Spacevars
      0product3
      s can address media incompatibility issues between certified Skype for Business Server endpoints (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 are the following:

    • The 
      Spacevars
      0product3
       consumes VM RAM and vCPU resources to deliver RTP media manipulation services via the virtual DSP feature.
    • Consumption of a VM's RAM and vCPU resources is higher when delivering RTP media manipulation services than the consumption of RAM and vCPU resources associated with RTP proxy media mode services.

    • Consider RTP media manipulation mode session density to determine a VM's vCPU and RAM resources for a specific

      Spacevars
      0product3
      . 


      Note
      titleRTP 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
Sessions that require transcoding, such as G.711 (common codec in enterprises) ↔ G.729ab (common codec in public networks) translation, G.711 A-law ↔ G.711 µ-law, etc. Please refer to /*embed link here* for the list of supported codecs by the SBC SWe Lite.
Transrating i.e. call legs that carry a different time sample size of media, where the SBC performs the translation. 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).
  • Silence suppression, where the SBC looks to remove/insert RTP packets carrying no meaningful media, again to save packet traffic;
    • Fax calls.
  • Fax tone detection and interworking to T.38* (T.38 support available in future release of the SBC SWe Lite);
    • G.711 fax media pass-through, as DSP intervention reduces the likelihood of in-band fax signaling/media issues.
    Any call flow where in-band ↔ out-of-band interworking is required. Examples:
  • In-band DTMF tone detection interworking with out-of-band RFC 4733 (supersedes RFC 2833);
  • In-band DTMF tone detection interworking with SIP INFO messages;
    • Interworking RTP dynamic payload types, required when the subtended SBC peers use differing payload type identifiers from the dynamic RTP payload range (e.g. 96 - 127) to identify a common payload format (i.e. codec).
    Any form of media that originates from the SBC in support of call developments. For example:
  • Announcement playback
  • Local ring back tone
  • Music on Hold
    • Comfort noise
    Jitter compensation, to maximize user experience with voice quality.
    Certified Skype for Business Phones and Devices interworking with non-certified endpoints. With DSP intervention, SBCs can address media incompatibility issues that at first glance may not be apparent between certified Skype for Business Server endpoints (as documented at https://technet.microsoft.com/en-us/office/dn947482) and other SIP-based client endpoints, such as RTCP reporting interval mismatch, unrecognised in-band supplementary service requests, etc.

    The implications of media manipulation mode sessions on the SBC SWe Lite are:

    1. The SBC SWe Lite consumes RAM and vCPU resources processing media manipulation mode sessions;
    2. Consumption of RAM and vCPU resources is higher than the consumption of RAM and vCPU resources associated with RTP proxy media mode sessions;
    3. Partners/customers need to consider media manipulation mode session density when determining an appropriate vCPU and RAM assignment to a given SBC SWe Lite.
    Media Manipulation Mode Sessions – Licensing

    The SBC SWe Lite 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
        • do not require additional licensing unless identified elsewhere.
    • Only one
        • Only one mode of media is supported against a given SIP session
    . For
        • ; for example, you cannot have one stream of media in RTP 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 for a description of available SBC SWe Lite session and feature licenses, including instructions on how to enable RTP proxy encryption/decryption services. Session Density Map

    The following table presents a guide to partners and customers regarding the maximum capacity of:

    • 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 supported with a given vCPU and RAM resource assignment

    ...on an example SBC SWe Lite.

    The table will be used extensively to identify and plan the required resource configuration for a given deployment of an SBC SWe Lite to address a partner/customer's expected SIP traffic flow.

    AnchorSessionDensityMapSessionDensityMap
    Caption
    0Table
    1Session Density Map

    Number of

    vCPUs

    Amount of

    RAM

    Number of

    Registrations

    Total

    Number of

    Allowed

    Calls

    Number of

    proxy calls

    only

     

    Maximum # of
    default media
    manipulation
    mode sessions

    		Maximum  #
    of RTP
    proxy mode
    sessions
    11 GB

    1000

    		100100

    50:50

    		 
    22 GB

    5,000

    		1,0001,000

    100:900

    		 
    44 GB

    5,000

    		1,0001,000

    300:700

    		 


    Licensing

    The 

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

      • The 
        Spacevars
        0product3
         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
    0product3
     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 

    Spacevars
    0product3
     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 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.

    Use the tables below to identify and plan the required resource configuration for a given deployment of an 

    Spacevars
    0product3
     to address SIP traffic flow.

    Anchor
    SessionDensityMap
    SessionDensityMap

    Multiexcerpt include
    MultiExcerptNamePerformance
    PageWithExcerptSBC SWe Lite Performance and Capacity

    Multiexcerpt include
    MultiExcerptNameTranscoding - For KVM, VMWare and Microsoft Hyper-V
    PageWithExcerptSBC SWe Lite Performance and Capacity

    Multiexcerpt include
    MultiExcerptNameTranscoding - For Azure
    PageWithExcerptSBC 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
        0product3
         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.

      2. For an Microsoft Azure-based 

        Spacevars
        0product3
         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.

        Warning
        titleUse of Table 3 for non-default RTP media manipulation mode sessions

        If on-premises

        Spacevars
        0product3
         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).


    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
      0product3
       deployment.

      Warning
      titleCalculating 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.


      StepAction
      a

      For an on-premises 

      Spacevars
      0product3
       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
      0product3
       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

    Determining vCPU and RAM Requirements

    Follow these steps to determine the number of vCPUs and RAM required for your SBC SWe Lite deployment.

    1. Determine the number of 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.

    2. Determine the additional RTP proxy session mode sessions requiring encryption/decryption services for your SBC SWe Lite deployment (taking into account future growth):

      StepActionaFrom Table 3, identify the available RTP proxy session mode session capacity (with encryption/decryption services) available with the quantity of of vCPUs and RAM recorded from Step 1.bDetermine if the

      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
      Calculated capacity from 2 (a) is larger than required RTP proxy session mode sessionsProceed to step 3, using the quantity of vCPUs and RAM determined from point
      1
      2(a) above.
      Capacity
      Calculated capacity from 2 (a) is smaller than required RTP proxy session mode sessionsReview Table
      3
      1 (or Table 2 for an Azure-based deployment) 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 SBC SWe Lite deployment (taking into account future growth):
      StepAction
      aFrom Table 3, identify the total number of media sessions available with the quantity of vCPUs and RAM recorded from point 2(a) or 2(b) above.
      bAdd the number of required 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).

      dDetermine 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 SBC SWe Lite deployment. 

       

      If...Then
      The value in (c) above is greater than/equal toProceed to step 4, using the quantity of vCPUs and RAM determined from point 3(a) above.
      The value in (c) above is less thanReview 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.
    3. Prepare to configure your SBC SWe Lite with the required number of vCPUs and RAM by referring to Provisioning the SWe Lite with a Given CPU and RAM.

    Examples

    Calculating the DSP Resource Requirements for a Low-Density SBC SWe Lite Deployment

    1. I need 15 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 SBC SWe Lite.
    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 50 RTP proxy session mode sessions requiring encryption/decryption services alongside a maximum of 50 media manipulation mode sessions. I continue to use the number of vCPU and RAM resources from point 1 to assign to my SBC SWe Lite.
    3. I need 50 additional RTP proxy session mode sessions not requiring encryption/decryption services.
    1. (or upgrade to a more powerful) Azure VM, then re-execute step 2(a).



    2. Prepare to configure your 
      Spacevars
      0product3
       with the resources arrived at the end of step 2.

      1. For an on-premises 

        Spacevars
        0product3
        deployment, refer Installing SBC SWe Lite.

      2. For an Microsoft Azure-based 
        Spacevars
        0product3
        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
    0product3
     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
        0product3
        .

    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
      0product3
      .

    Identifying the Microsoft Azure VM Instance for a Cloud-based 
    Spacevars
    0product3
     Deployment

    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 
        Spacevars
        0product3
        .

      2. 800 additional RTP proxy session mode sessions 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 

      Spacevars
      0product3
      .

    Calculating the vCPU and RAM Resource Requirements for an On-premises High-Density Hyper-V based 
    Spacevars
    0product3
     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
        0product3
        . Note the required RAM will be determined in the next step.

      2. 800 additional RTP proxy session mode sessions with encryption/decryption services.

      • From Table 1, I see 4 vCPU and 2.5 GiB of RAM 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
      0product3
      .

    Calculating the vCPU and RAM Resource Requirements for a High-Density SIP Registration 
    Spacevars
    0product3
     Deployment

    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.

    Considerations for RTP

    (a) From Table 3, I see a single vCPU and 1 GB of RAM will support up to 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 SBC SWe Lite.

    Calculating the DSP Resource Requirements for a High-Density SBC SWe Lite Deployment

    1. I need 100 media manipulation mode sessions (sessions will be equivalent to the Default Media Manipulation Scenario defined above). From Table 3, I see two vCPU and 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 SBC SWe Lite.

    2. I need 400 additional RTP proxy session mode sessions requiring encryption/decryption services. From Table 3, I see a two vCPU and 2 GB of RAM will support up to 700 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 SBC SWe Lite.

    3. I need 500 additional RTP proxy session mode sessions not requiring encryption/decryption services.

    (a) From Table 3, I see a two vCPU and 2 GB 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 determined from point 2 above to assign to my SBC SWe Lite.

    Considerations for

    Media Manipulation Session Mode versus RTP Proxy Session Mode

    SIP Signaling Group Considerations

    SIP Signaling groups (provisioning constructs that represent a connection between the SBC SWe Lite and the 

    Spacevars
    0product3
     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 SBC SWe Lite in
    • the 
      Spacevars
      0product3
       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 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 SBC must
    • the 
      Spacevars
      0product3
       must have an available media manipulation session mode resource
    ; otherwise
    • . Otherwise, the call will fail.

    Considerations for DTMF

    There are several alternatives for DTMF calls:

    •
    • When a DTMF call is received,
    the SBC SWe Lite terminates
    • the 
      Spacevars
      0product3
       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 SBC SWe Lite terminates the
    • the 
      Spacevars
      0product3
       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 SBC SWe Lite does
    • the 
      Spacevars
      0product3
       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