Calculating DSP Requirements for SBC SWe Lite

Concepts

Direct Media Mode Sessions

A media session that does not flow through the 

. 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  are:

• The 
  Unable to show "metadata-from": No such page "_space_variables"
   does not consume any RAM or vCPU resources processing the direct media mode sessions.
• Partners/customers do not need to consider direct media mode sessions when determining an appropriate vCPU and RAM assignment to a given 
  Unable to show "metadata-from": No such page "_space_variables"
  .

Licensing

The 

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

• The 

 requires a license to enable a given quantity of SIP signaling sessions.
• The  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, 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 for a description of available 

 session and feature licenses.

RTP Proxy Media Mode Sessions

A media session that flows through the 

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

1. The 

 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 

RTP Proxy Media Mode Sessions – Licensing

The 

 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 

 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, and so on. Please refer to /*embed link here* for the list of supported codecs by the 
   Unable to show "metadata-from": No such page "_space_variables"
   .
   
   
2. Transrating, that is, call legs that carry a different time sample size of media, where the 
   Unable to show "metadata-from": No such page "_space_variables"
    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 
   Unable to show "metadata-from": No such page "_space_variables"
    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 will be available in a future release of the 
      Unable to show "metadata-from": No such page "_space_variables"
      )
   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 (for example 96 - 127) to identify a common payload format (in other words,  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, 
   Unable to show "metadata-from": No such page "_space_variables"
   s 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, and unrecognized in-band supplementary service requests.
   
   

The implications of media manipulation mode sessions on the 

 are:

• The
  Unable to show "metadata-from": No such page "_space_variables"
   consumes RAM and vCPU resources processing media manipulation mode sessions
• Consumption of RAM and vCPU resources is higher than the consumption of RAM and vCPU resources associated with RTP proxy media mode sessions
• Partners/customers need to consider media manipulation mode session density when determining an appropriate vCPU and RAM assignment to a given 
  Unable to show "metadata-from": No such page "_space_variables"

Media Manipulation Mode Sessions – Licensing

The 

 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

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

Examples

Calculating the DSP Resource Requirements for a Low-Density 

Unable to show "metadata-from": No such page "_space_variables"

 Deployment

1. I need 15 media manipulation mode sessions (sessions will be equivalent to the Default Media Manipulation Scenario defined above). From the Session Density Map table 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 

.

2. I need 35 additional RTP proxy session mode sessions requiring encryption/decryption services. From  the Session Density Map table 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 .

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

(a) From  the Session Density Map table 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 

.

Calculating the DSP Resource Requirements for a High-Density 

Unable to show "metadata-from": No such page "_space_variables"

 Deployment

1. I need 100 media manipulation mode sessions (sessions will be equivalent to the Default Media Manipulation Scenario defined above). From the Session Density Map table  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 

2. I need 400 additional RTP proxy session mode sessions requiring encryption/decryption services. From  the Session Density Map table  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 

.

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

(a) From  the Session Density Map table I see 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 

.

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 

 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 

 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 

 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 

 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 

 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 

 does not process the DTMF.