You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 2 Next »

 

In this section:

Introduction

This document describes how to identify the required vCPU and RAM resources 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

Terminology

TermDefinition
Default Media Manipulation ScenarioA basic IP ↔ IP media manipulation session scenario for the SBC SWe Lite is G.711 (RTP) ↔ G.729ab (SRTP). This is considered as the default media manipulation scenario for SBC SWe Lite when calculating vCPU and RAM resource requirements.
Media ManipulationThe action taken by 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 translation of media from one codec to another, encrypting/decrypting media, and in-band tone detection.
Media SessionA bi-directional flow of audio, video, or other real-time information (such as FAX) between two endpoints that may or may not directly subtend the SBC.
RAMRandom Access Memory. Refer to Random Access Memory. For SBC SWe Lite planning, RAM requirements are always presented in integer GB multiples (Gigabyte).
vCPURefer 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.
 

 

Concepts

ConceptDefinition
Direct Media Mode Sessions

 

 

A media session that does 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:

1. The SBC SWe Lite does not consume any RAM or vCPU resources processing the direct media mode sessions.
2. Partners/customers do not need to consider direct media mode sessions when determining an appropriate vCPU and RAM assignment to a given SBC SWe Lite.
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

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 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 SBC SWe Lite are:

1. The SBC SWe Lite 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 SBC SWe Lite

RTP Proxy Media Mode Sessions – Licensing

As mentioned previously, the SBC SWe Lite supports a single RTP proxy media mode session 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 Sessions

A 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):

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

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

  3. Silence suppression, where the SBC looks to remove/insert RTP packets carrying no meaningful media, again to save packet traffic;
  4. Fax calls.
    1. Fax tone detection and interworking to T.38* (T.38 support available in future release of the SBC SWe Lite);
    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 in-band ↔ out-of-band interworking is required. Examples:
    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 (e.g. 96 - 127) to identify a common payload format (i.e. codec).

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

  7. Jitter compensation, to maximize user experience with voice quality.

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

Session 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

 


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):

    StepAction
    aFrom 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.
    b

    Determine 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 from (a) is largerProceed to step 3, using the quantity of vCPUs and RAM determined from point 1 above.
    Capacity from (a) is smallerReview 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.

  3. 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.
  4. 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.

(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 another SIP based peer) can be configured to use either media manipulation session mode or a RTP proxy session mode. Note the following:

• 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 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 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 mid-call dynamic switch to change mode, including the case of call transfer and conference. 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 have an available media manipulation session mode resource; 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 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 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 not process the DTMF.

  • No labels