AudioCodes Mediant 500 MSBR, User Manual

Page: 254 / 1248

User's Manual 254 Document #: LTRT-10375
Mediant 500 MSBR
Persistent Connection
http-persistent-
connection
[HTTPRemoteServices_Pe
rsistentConnection]
Defines whether the HTTP connection with the host remains open or is
only opened per request.

[0] Disable = Connection is not persistent and closes when the
device detects inactivity. The device uses HTTP keep-alive
messages to detect inactivity.

[1] Enable = (Default) Connection remains open (persistent) even
during inactivity. The device uses HTTP keep-alive / HTTP
persistent connection messages to keep the connection open.
Number of Sockets
http-num-sockets
[HTTPRemoteServices_Nu
mOfSockets]
Defines how many sockets (connection) are established per remote
host.
The valid value is 1 to 10. The default is 1.
Login
Login Needed
http-login-needed
[HTTPRemoteServices_Lo
ginNeeded]
Enables the use of proprietary REST API Login and Logout commands
for connecting to the remote host. The commands verify specific
information (e.g., software version) before allowing connectivity with
the device.

[0] Disable = Commands are not used.

[1] Enable (default)
Username
rest-user-name
[HTTPRemoteServices_Au
thUserName]
Defines the username for HTTP authentication.
The valid value is a string of up to 80 characters. The default is "user".
Password
rest-password
[HTTPRemoteServices_Au
thPassword]
Defines the password for HTTP authentication.
The valid value is a string of up to 80 characters. The default is
"password".
Security
TLS Context
rest-tls-context
[HTTPRemoteServices_TL
SContext]
Assigns a TLS Context for connection with the remote host.
By default, no value is defined.
To configure TLS Contexts, see Configuring TLS Certificate Contexts
on page 117.
Note: The parameter is applicable only if the connection is HTTPS.
Verify Certificate
rest-verify-
certificates
[HTTPRemoteServices_Ve
rifyCertificate]
Enables certificate verification when connection with the host is based
on HTTPS.

[0] Disable = (Default) No certificate verification is done.

[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.
Timeouts