CHAPTER16 Services
Mediant 1000 Gateway & E-SBC | User's Manual
Parameter Description
â– [1] Enable = The device verifies the authentication of the
certificate received from the HTTPS peer. The device
authenticates the certificate against the trusted root
certificate store associated with the associated TLS
Context (see 'TLS Context' parameter above) and if ok,
allows communication with the HTTPS peer. If
authentication fails, the device denies communication
(i.e., handshake fails). The device can also authenticate
the certificate by querying with an Online Certificate
Status Protocol (OCSP) server whether the certificate
has been revoked. This is also configured for the
associated TLS Context.
Note: The parameter is applicable only if the connection is
HTTPS.
'Verify Certificate Subject
Name'
verify-cert-subject-
name
[HTTPRemoteServices_
VerifyCertificateSubjectName]
Enables the verification of the TLS certificate subject name
(Common Name / CN or Subject Alternative Name / SAN)
when connection with the host is based on HTTPS.
â– [0] Off = (Default) No verification is done.
â– [1] On = The device verifies the subject name of the
certificate received from the HTTPS peer. If the server's
URL contains a hostname, it verifies the certificate
against the hostname; otherwise, it verifies the
certificate against the server's IP address. If
authentication fails, the device denies communication
(i.e., handshake fails).
Note: The parameter is applicable only if the connection is
HTTPS.
Timeouts
'Response Timeout'
rest-timeout
[HTTPRemoteServices_
TimeOut]
Defines the TCP response timeout (in seconds) from the
remote host. If one of the remote hosts does not respond to a
request within the specified timeout, the device closes the
corresponding socket and attempts to connect to the next
remote host.
The valid value is 1 to 65535. The default is 5.
'Keep-Alive Timeout'
rest-ka-timeout
[HTTPRemoteServices_
KeepAliveTimeOut]
Defines the duration/timeout (in seconds) in which HTTP-
REST keep-alive messages are sent by the device if no
other messages are sent. Keep-alive messages may be
required for HTTP services that expire upon inactive
sessions. For Remote Web Service whose 'Type' is
Routing, Call Status, Topology Status, or QoS,
proprietary keep-alive messages are sent. For 'Type' that is
General, HTTP OPTIONS keep-alive messages are sent.
The valid value is 0 to 65535. The default is 0 (i.e., no keep-
alive messages are sent).
Status
- 248 -