Crypto Suite Profile - CLI

The Crypto Suite Profile is used to negotiate cryptographic algorithms when establishing unicast media streams involving Secure RTP/RTCP. The SBC includes the crypto suites and optional session parameters in one or more crypto attributes (a=crypto) of SDP offers and answers. Each crypto attribute describes a cryptographic suite, key parameters, and any optional session parameters. The most preferred crypto suite is listed first. A SIP call signals and negotiates cryptographic parameters for the media stream via the SDP m= line Crypto attribute. These parameters are mostly grouped into a "crypto-suite" field that describes the encryption and authentication algorithms for transport. The appropriate crypto suite profile may include valid combinations of the following session parameters:

• unauthenticatedSRTP—Signals that the SRTP packet payloads are not authenticated.
• unencryptedSRTP—Signals that the SRTP packet payloads are not encrypted.
• unencryptedSRTCP—Signals that the SRTCP packet payloads are not encrypted.

By default, SRTP and SRTCP packet payloads are both authenticated and encrypted. The SRTP specification requires the use of message authentication for SRTCP, but not for SRTP. Use of unauthenticatedSRTP is not recommended. 

Command Syntax

% set profiles security cryptoSuiteProfile <profile name> 
	entry <priority> 
	cryptoSuite <cryptoSuite> 
	sessionParameterFlags <sessionParameterFlags> 

% show profiles security cryptoSuiteProfile <cryptoSuiteProfile> displaylevel <displaylevel> 

% delete profiles security cryptoSuiteProfile <cryptoSuiteProfile>

Command Parameters

The Crypto Suite Profile Parameters are as shown below:

Command Example

% show profiles security cryptoSuiteProfile 
cryptoSuiteProfileTest DEFAULT  {
     entry 1 { 
	cryptoSuite AES-CM-128-HMAC-SHA1-80; 
	sessionParameterFlags { 
	    unencryptedSRTCP enable; 
	    unencryptedSRTP enable; 
	    unauthenticatedSRTP enable; 
        } 
    } 
}