CHAPTER 16 Services
Mediant 4000 SBC | User's Manual
Parameter
Description
■
The NGINX directive for this parameter is "proxy_pass
scheme://upstream".
'OVOC Interface TLS
Context'
ovoc-interface-tls-
context
[OVOCService_
EMSInterfaceTLSContext]
Assigns a TLS Context (TLS certificate) for the OVOC listening
interface. This is required if you have configured the 'OVOC
Scheme' parameter to
HTTPS
(see above). To configure TLS
Contexts, see
Configuring TLS Certificate Contexts
Note:
The NGINX directive for this parameter is "proxy_ssl_
certificate", "proxy_ssl_certificate_key", "proxy_ssl_ciphers",
and "proxy_ssl_protocols".
'OVOC Interface Verify
Certificate'
ovoc-verify-cer
[OVOCService_
EMSInterfaceVerifyCert]
Enables the verification of the TLS certificate that is used in the
incoming connection request from OVOC.
■
[0]
No
= (Default) No certificate verification is done.
■
[1]
Yes
= The device verifies the authentication of the
certificate received from OVOC. The device authenticates
the certificate against the trusted root certificate store
associated with the assigned TLS Context (see 'OVOC
Interface TLS Context' parameter above) and if ok, allows
communication with OVOC. 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 NGINX directive for this parameter is "proxy_ssl_
verify".
'OVOC Primary Server'
primary-server
[OVOCService_
PrimaryServer]
Defines the address of the primary OVOC server.
Note:
■
This parameter is mandatory.
■
When you configure this parameter, an Upstream Group is
automatically added (see
page 272).
■
The NGINX directive for this parameter is "upstream ems {
addr1, addr2 backup }" and "proxy_pass scheme://ems".
'OVOC Backup Server'
secondary-server
[OVOCService_
SecondaryServer]
Defines the address of the secondary OVOC server.
Note:
■
When you configure this parameter, an Upstream Group is
automatically added.
■
The NGINX directive for this parameter is "upstream ems {
addr1, addr2 backup }" and "proxy_pass scheme://ems".
- 281 -
Содержание Mediant 4000 SBC
Страница 1: ...User s Manual AudioCodes Series of Session Border Controllers SBC Mediant 4000 SBC Version 7 2...
Страница 40: ...Part I Getting Started with Initial Connectivity...
Страница 48: ...Part II Management Tools...
Страница 113: ...Part III General System Settings...
Страница 118: ...Part IV General VoIP Configuration...
Страница 525: ...Part V Session Border Controller Application...
Страница 654: ...Part VI Cloud Resilience Package...
Страница 663: ...Part VII High Availability System...
Страница 685: ...Part VIII Maintenance...
Страница 759: ...Part IX Status Performance Monitoring and Reporting...
Страница 844: ...Part X Diagnostics...
Страница 888: ...Part XI Appendix...
Страница 1036: ...This page is intentionally left blank CHAPTER 62 Technical Specifications Mediant 4000 SBC User s Manual 1003...