In this Section:
This object creates and configures a profile 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 a TLS protection-level policy, you create a TLS PROFILE and configure each of the parameters. The TLS profile is specified on 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. The settings within the defaultTlsProfile may be modified. Also, the supported transport protocols 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 SBC main screen, go to Configuration > System Provisioning > Security Configuration > TLS Profile. The TLS Profile window is displayed.
Click to view more parameters.
To edit any of the TLS Profile in the list, click the radio button next to the specific TLS Profile name.
The Edit Selected TLS Profile window is displayed.
Make the required changes and click Save at the right hand bottom of the panel to save the changes made.
To create a new TLS Profile, click New TLS Profile tab on the TLS Profile List panel.
The Create New TLS Profile window is displayed.
The following fields are displayed:
Parameter | Description |
---|---|
| The name assigned to this Transport Layer Security (TLS) profile. Must be 1 - 23 characters. |
| Specifies the higher layer authentication timer in seconds. Must be 1-60 seconds. The default value is 5. |
| 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. |
| 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 |
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 |
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: WhenFips-140-2 mode is enabled, Rsa-with-null-sha should not be used. |
| Specifies which role the SBC 5000 series will act in for this TLS profile:
|
| 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):
|
| 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. |
| 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
|
To copy any of the created TLS Profile and to make any minor changes, click the radio button next to the specific TLS Profile to highlight the row.
Click Copy TLS Profile tab on the TLS Profile List panel.
The Copy Selected TLS Profile window is displayed along with the field details which can be edited.
Make the required changes to the required fields and click Save to save the changes. The copied TLS Profile is displayed at the bottom of the original TLS Profile in the TLS Profile List panel.
To delete any of the created TLS Profile, click the radio button next to the specific TLS Profile which you want to delete.
Click Delete at the end of the highlighted row. A delete confirmation message appears seeking your decision.
Click Yes to remove the specific TLS Profile from the list.