User's Manual 966 Document #: LTRT-27045
Mediant 1000B Gateway & E-SBC
Parameter Description
configure network/security-
settings/tls-re-hndshk-int
[TLSReHandshakeInterval]
The interval range is 0 to 1,500 minutes. The default is 0 (i.e., no
TLS Re-Handshake).
TLS Mutual Authentication
[SIPSRequireClientCertificate]
Defines the device's mode of operation regarding mutual
authentication and certificate verification for TLS connections.
ï‚§ [0] Disable = (Default)
Device acts as a client: Verification of the server’s
certificate depends on the VerifyServerCertificate
parameter.
Device acts as a server: The device does not request the
client certificate.
ï‚§ [1] Enable =
Device acts as a client: Verification of the server certificate
is required to establish the TLS connection.
Device acts as a server: The device requires the receipt
and verification of the client certificate to establish the TLS
connection.
Note:
ï‚§ For the parameter to take effect, a device reset is required.
ï‚§ This feature can be configured per SIP Interface (see
''Configuring SIP Interfaces'' on page 326).
ï‚§ The SIPS certificate files can be changed using the
parameters HTTPSCertFileName and HTTPSRootFileName.
Peer Host Name Verification
Mode
[PeerHostNameVerificationMode]
Enables the device to verify the Subject Name of a TLS certificate
received from SIP entities for authentication and establishing TLS
connections.
ï‚§ [0] Disable (default).
ï‚§ [1] Server Only = Verify Subject Name only when acting as a
client for the TLS connection.
ï‚§ [2] Server & Client = Verify Subject Name when acting as a
server or client for the TLS connection.
If the device receives a certificate from a SIP entity (IP Group)
and the parameter is configured to Server Only or Server &
Client, it attempts to authenticate the certificate based on the
certificate's address.
The device searches for a Proxy Set that contains the same
address (IP address or FQDN) as that specified in the certificate's
SubjectAltName (Subject Alternative Names). For Proxy Sets with
an FQDN, the device checks the FQDN itself and not the DNS-
resolved IP addresses. If a Proxy Set is found with a matching
address, the device establishes a TLS connection.
If a matching Proxy Set is not found, one of the following occurs:
ï‚§ If the certificate's SubjectAltName is marked as "critical", the
device rejects the call.
ï‚§ If the SubjectAltName is not marked as "critical", the device
checks if the FQDN in the certificate's Common Name (CN) of
the SubjectName is the same as that configured for the
TLSRemoteSubjectName parameter or for the Proxy Set. If
they are the same, the device establishes a TLS connection;
otherwise, the device rejects the call.
Note: