Versions Compared

Old Version 5

changes.mady.by.user Ribbon Communications

Saved on

compared with

New Version 6

changes.mady.by.user Ribbon Communications

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Add_workflow_for_techpubs
AUTH1UserResourceIdentifier{userKey=8a00a0c880e94aad0181077fa2530009, userName='null'}
JIRAIDAUTHSBX-124029
REV5UserResourceIdentifier{userKey=8a00a02355cd1c2f0155cd26cb8305e9, userName='null'}
REV6UserResourceIdentifier{userKey=8a00a02355cd1c2f0155cd26cb8305e9, userName='null'}
REV3UserResourceIdentifier{userKey=8a00a0c880e94aad0181077fa2530009, userName='null'}
REV1UserResourceIdentifier{userKey=8a00a0c880e94aad0181077fa2530009, userName='null'}



Panel

In this section:

Table of Contents
maxLevel4



Info
iconfalse

Related articles:



Use the TLS Profile to configure a profile for implementing the TLS protocol for SIP over TLS. A TLS profile is assigned to the SIP signaling port and controls behavior of all TLS connections established on that signaling port. An instance of a TLS profile called defaultTlsProfile is present by default, and is used by default by each SIP signaling port; however, additional TLS profile instances may be created and used instead. 

Info
titleNote

The settings within the default TLS profile are editable. Also, you must set the supported transport protocols on the SIP signaling port to allow SIP over TLS.


Include Page
_sip-tls-tcp
_sip-tls-tcp

Command Syntax

Code Block
languagenone
% set profiles security tlsProfile <profile name> 
	acceptableCertValidationErrors <invalidPurpose | none>	
	allowedRoles <clientandserver | server> 
	appAuthTimer <1-60 seconds> 
	authClient <false | true> 
	cipherSuite1 <cipher suite> 
	cipherSuite2 <cipher suite> 
	cipherSuite3 <cipher suite> 
	clientCertName <name> 
    handshakeTimer <1-60 seconds> 
    hashType <md5 | sha1 | sha224 | sha256 | sha384 | sha512>
	ocspProfileName <name>
	peerNameVerify <disabled | enabled>
	serverCertName <name> 
	sessionResumpTimer <0-86400 seconds>
	suppressEmptyFragments <disabled | enabled>
	v1_0 <disabled | enabled>
    v1_1 <disabled | enabled>
    v1_2 <disabled | enabled>
 	v1_3 <disabled | enabled>

Command Parameters

The TLS Profile Parameters are as shown below:

Parameter

Length/Range

Description

tlsProfile

1-23

<name> - Name assigned to this Transport Layer Security (TLS) profile.

For further details, refer to: SBC Provisioning Limits

acceptableCertValidationErrorsN/A

Use this parameter to specify if certificate chain validation errors are acceptable while validating the peer certificate.

  • invalidPurpose 
  • none (default) 

allowedRoles

N/A

Allowed TLS roles for this TLS profile.

  • clientandserver – (default) Choose to select both a TLS client and server role, depending on the request direction. This is primarily for peering applications.
  • server – The 
    Spacevars
    0product
    will only be a TLS server. This is primarily for access applications.

appAuthTimer

1-60

The higher layer authentication timer in seconds. (default = 5).

authClient

N/A

Indicates whether or not a TLS client is forced to authenticate itself within TLS. 

  • false
  • true (default)

cipherSuite1

N/A

Use this parameter to specify the first TLS Cipher Suite choice for this profile.

See Supported Cipher Suites table below for the list of cipher suites.

cipherSuite2

N/A

Use this optional parameter to specify the second TLS Cipher Suite choice for this profile.

See Supported Cipher Suites table below for the list of cipher suites.

cipherSuite3

N/A

Use this optional parameter to specify the third TLS Cipher Suite choice for this profile.

See Supported Cipher Suites table below for the list of cipher suites.

clientCertName

1-23

The name of the default Client Certificate to be used by this TLS profile, created using the SECURITY PKI configuration object.

handshakeTimer

1-60

The time (in seconds) in which the TLS handshake must be completed. The timer starts when the TCP connection is established. (default = 5)

hashType
  • Md5
  • Sha1 
  • Sha224
  • Sha256
  • Sha384
  • Sha512
The type of TLS hash function allowed for TLS sessions governed by the specified TLS profile. (default= Sha1)
ocspProfileName1-23

Name of OCSP profile object referenced by TLS profile.

peerNameVerifyN/A

This flag is used to verify the authenticity of a client certificate. When enabled, the

Spacevars
0product
validates the TLS peer name of the SIP peer against either a Common Name (CN) present in the subject or the DNS names or IP addresses in the Subject Alternate Name Extension (SAN) field in the certificate presented by the peer.

For example, if the

Spacevars
0product
establishes a TLS session with "sonus.customer.net", this feature verifies the CN in the subject (or a DNS entry in the SAN field) of the certificate contains "sbc.customer.net" as the value.

  • disabled  (default)
  • enabled

NOTE: This flag is used in conjunction with the trunk group parameter, tlsPeerName, which associates the TLS peer name with a trunk group. Refer to SIP TG - Signaling - TLS Peer Name - CLI for details.

serverCertName

1-23

Specifies the name of the Server Certificate to be used by this TLS profile, created using the SECURITY PKI configuration object.

sessionResumpTimer

0-86400

The TLS session resumption period (in seconds) for which cached sessions are retained. TLS allows successive connections to be created within one TLS session (and the resumption of a session after a TLS connection is closed or after a server card failover) without repeating the entire authentication and other setup steps for each connection, except when the space must be reclaimed for a new session. (default = 3600)

suppressEmptyFragmentsN/A

Enable flag to prevent the

Spacevars
0product
from inserting empty fragments when sending packets on TLS over TCP connection in support of older versions of TLS implementation.

  • disabled  (default)
  • enabled
v1_0N/A

TLS protocol version 1.0 (see note below)

  • disabled
  • enabled (default)
v1_1N/A

TLS protocol version 1.1 (see note below)

  • disabled  (default)
  • enabled
v1_2N/A

TLS protocol version 1.2 (see note below)

  • disabled (default)
  • enabled
v1_3N/A

TLS protocol version 1.3 (see note below)

  • disabled (default)
  • enabled


Include Page
_TLS_version
_TLS_version


The

Spacevars
0product
includes crypto suites that define a set of ciphers (algorithms used for encrypting data) which allow the selection of an appropriate level of security. The crypto suites are supported for both TLS and DTLS (Datagram Transport Layer Security) connections. When a TLS or DTLS connection is established, the client and server exchange information about which cipher suites they have in common. Refer to SBC for WRTC for more  information on DTLS. The following crypto suites are supported. 

Anchor
CipherSuites
CipherSuites
Multiexcerpt include
MultiExcerptNameDTLS Crypto Suites Table
PageWithExcerptTLS for Signaling

Command Examples

Code Block
languagenone
> show profiles security tlsProfile defaultTlsProfile
appAuthTimer       5;
handshakeTimer     5;
hashType        Sha1;
sessionResumpTimer 3600;
cipherSuite1       rsa-with-aes-128-cbc-sha;
allowedRoles       clientandserver;
v1_0               enabled;
v1_1               enabled;
v1_2               enabled;
v1_3               enabled;  

% set profiles security tlsProfile defaultTlsProfile ocspProfileName myOcspProfile
% commit
 
> show profiles security tlsProfile defaultTlsProfile
appAuthTimer       5;
handshakeTimer     5;
hashType        Sha1;
sessionResumpTimer 3600;
cipherSuite1       rsa-with-aes-128-cbc-sha;
allowedRoles       clientandserver;
ocspProfileName    myOcspProfile;
v1_0               enabled;
v1_1               enabled;
v1_2               enabled;
v1_3               enabled;


Code Block
languagenone
% set profiles security tlsProfile TLS-1 v1_3 enabled
% set profiles security tlsProfile TLS-1 cipherSuite1 tls_ecdh_ecdsa_with_aes_256_gcm_sha384
% commit
 
> show profiles security tlsProfile TLS-1
cipherSuite1 tls_ecdh_ecdsa_with_aes_256_gcm_sha384;
v1_3         enabled;