DO NOT SHARE THESE DOCS WITH CUSTOMERS!
This is an LA release that will only be provided to a select number of PLM-sanctioned customers (PDFs only). Contact PLM for details.
In this Section:
Use the TLS Profile window to create and configure profiles for implementing the Transport Layer Security (TLS) protocol for use with SIP over TLS. TLS is an IETF protocol for securing communications across an untrusted network. Normally, SIP packets travel in plain text over TCP or UDP connections; Secure SIP is a security measure that uses TLS, the successor to the Secure Sockets Layer (SSL) protocol.
To add TLS policy to the SBC you configure a TLS profile. The 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. The settings within the defaultTlsProfile may be modified. Also, the supported transport protocols for the SIP signaling port must be set to allow SIP over TLS over TCP.
If a zone's sipSigPort
is configured for transportProtocolsAllowed
= sip-tls-tcp
, the SBC increments the configured portNumber
by 1 and uses it as the new port number for SIP over TLS signaling. The SBC then opens a TCP socket for SIP over TLS for the new TCP port number.
Example: When sipSigPort
is configured with a portNumber
of 5060 and transportProtocolsAllowed
= sip-tls-tcp
, the SBC listens on TCP port 5061 for SIP over TLS.
On the SBC main screen, go to Configuration > System Provisioning > Security Configuration > TLS Profile.
To create a new TLS Profile:
Click New TLS Profile.
Use the following table to configure the options and then click Save.
Parameter | Description |
---|---|
Name | The name assigned to this Transport Layer Security (TLS) profile. Must be 1 - 23 characters. You can create a maximum of 16 TLS profiles. |
App Auth Timer | Specifies the higher layer authentication timer in seconds. Must be 1-60 seconds. The default value is 5. |
Handshake | Specifies the time in which the TLS handshake must be completed. The timer starts when the TCP connection is established. Must be 1 - 60 seconds; default is 5. |
Session Resume | Specifies the TLS session resumption period for which cached sessions are retained (in seconds). 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. Must be 0 - 86,400 seconds; default is 3600. |
Cipher Suite1 | Use this parameter to specify the first TLS Cipher Suite choice for this profile.
* To use this cipher, TLS version 1.2 must be enabled in the TLS Profile. ** To use this cipher, TLS version 1.2 must be enabled in the TLS Profile and SSL certificates must be created using ECC keys. NOTE: When Fips-140-2 mode is enabled, Rsa-with-null-sha should not be used. The SBC releases 7.2.x and 10.1.3 are compliant with FIPS-140-2 and FIPS-140-3 respectively. To verify the current status of FIPS certification, contact the Global Support Assistance Center: Ribbon Support Portal: https://ribboncommunications.com/services/ribbon-support-portal Voice: +1-833-RIBBON1 (1-833-742-2661) |
Cipher Suite2 | Use this parameter to specify the second TLS Cipher Suite choice for this profile.
* To use this cipher, TLS version 1.2 must be enabled in the TLS Profile. ** To use this cipher, TLS version 1.2 must be enabled in the TLS Profile and SSL certificates must be created using ECC keys. NOTE: When Fips-140-2 mode is enabled, Rsa-with-null-sha should not be used. |
Cipher Suite3 | Use this parameter to specify the third TLS Cipher Suite choice for this profile.
* To use this cipher, TLS version 1.2 must be enabled in the TLS Profile. ** To use this cipher, TLS version 1.2 must be enabled in the TLS Profile and SSL certificates must be created using ECC keys. NOTE: When Fips-140-2 mode is enabled, Rsa-with-null-sha should not be used. |
Allowed Roles | Specifies which role the SBC 5000 series will act in for this TLS profile:
|
Auth Client | Indicates whether or not a TLS client is forced to authenticate itself within TLS. If set to false, the client is not required to authenticate itself at the TLS layer but must complete authentication within a higher-lever protocol after the TLS connection is established (i.e. SIP registration):
|
Client Cert | Specifies the name of the default Client Certificate to be used by this TLS profile, created using the SECURITY PKI configuration object. Must be 1-23 characters or none. |
Server Cert | Specifies the name of the Server Certificate to be used by this TLS profile, created using the SECURITY PKI configuration object. Must be 1-23 characters or none. |
Acceptable Cert Validation Errors | Use this parameter to specify if certificate chain validation errors are acceptable while validating the peer certificate.
|
Ocsp Profile Name | Specifies the name of OCSP profile object referenced by TLS profile. |
V1_0 | TLS protocol version 1.0.
|
V1_1 | TLS protocol version 1.1.
|
V1_2 | TLS protocol version 1.2.
|
Suppress Empty Fragments | If enabled, SBC will not insert empty fragments while sending packets on TLS over TCP connection. The options are:
|
Peer Name Verify | If enabled, the SBC verifies the value of the parameter
|
Hash Type | Specifies the type of TLS hash function allowed for TLS sessions governed by the specified TLS profile. The options are:
|
To edit a TLS Profile:
To copy a TLS Profile and make any minor changes:
To delete a TLS Profile: