AudioCodes Mediant 500 MSBR, Руководство пользователя

Страница: 264 / 1248

User's Manual 264 Document #: LTRT-10375
Mediant 500 MSBR
Table 18-16: HTTP Interfaces Table Parameter Descriptions
Parameter Description
General
Index
[HTTPInterface_Index]
Defines an index number for the new table row.
Note:

Each row must be configured with a unique index.

The parameter is mandatory.
Name
interface-name
[HTTPInterface_InterfaceN
ame]
Defines a descriptive name, which is used when associating the row in
other tables.
The valid value is a string of up to 40 characters. By default, no value
is defined.
Note:

Each row must be configured with a unique name.

The parameter is mandatory.
Network Interface
network-interface
[HTTPInterface_NetworkInt
erface]
Assigns a local, network interface to the HTTP interface.
By default, no value is defined.
Note: The parameter is mandatory.
Protocol
protocol
[HTTPInterface_Protocol]
Defines the protocol type.

[0] HTTP (default)

[1] HTTPS
HTTP Port
http-port
[HTTPInterface_Port]
Defines the local, listening HTTP port.
The valid value is 0 to 65534. The default is 0.
Note: The parameter is mandatory.
Security
TLS Context
tls-context
[HTTPInterface_TLSConte
xt]
Assigns a TLS Context for the connection with the HTTP Proxy
service.
By default, the default TLS Context (Index 0) is assigned.
To configure TLS Contexts, see Configuring TLS Certificate Contexts
on page 117.
Note: The parameter is applicable only if the connection protocol is
HTTPS (defined using the 'Protocol' parameter, above).
Verify Certificate
verify-cert
[HTTPInterface_VerifyCert]
Enables TLS certificate verification when the connection with the proxy
service is based on HTTPS.

[0] No = (Default) No certificate verification is done.

[1] Yes = 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 protocol is
HTTPS (defined using the 'Protocol' parameter, above).