Configuring Remote Http Hosts - AudioCodes Mediant 4000 SBC User Manual

User's Manual
Parameter
Timeouts
Response Timeout
rest-timeout
[HTTPRemoteServices_TimeOut]
Keep-Alive Timeout
rest-ka-timeout
[HTTPRemoteServices_KeepAliv
eTimeOut]

15.6.1.1 Configuring Remote HTTP Hosts

The HTTP Remote Hosts table lets you configure up to 10 remote HTTP hosts per Remote
Web Service. The HTTP Remote Hosts table is a "child" of the Remote Web Services table
(configured in ''Configuring Remote Web Services'' on page 271).
The following procedure describes how to configure HTTP Remote hosts through the Web
interface. You can also configure it through ini file (HTTPRemoteServices) or CLI
(configure system > http-services > http-remote-hosts).

To configure a remote HTTP host:
1. Open the Remote Web Services table (Setup menu > IP Network tab > Web
Services folder > Remote Web Services).
2. In the table, select the required remote Web service index row, and then click the
HTTP Remote Hosts link located below the table; the HTTP Remote Hosts table
appears.
Version 7.2
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.
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.
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.
The valid value is 0 to 65535. The default is 0 (i.e., no keep-alive
messages are sent).
Note: The parameter is applicable only if the 'Persistent
Connection' parameter (in the table) is configured to Enable.
275
Description
Mediant 4000 SBC
15. Services