AudioCodes Mediant 4000 SBC, User Manual

Page: 294 / 1037

CHAPTER 16 Services
Mediant 4000 SBC | User's Manual
This feature integrates the NGINX platform, which is an open source proxy server. When you
enable the HTTP Proxy application, the NGINX daemon is launched. When you then configure the
various HTTP Proxy tables, the configuration is reflected in the NGINX configuration file
(nginx.conf). Each parameter has its own NGINX Directive notation syntax, which is shown in the
nginx.conf file. For example, if you have configured an Upstream Host (discussed later in this
section), it is displayed in the NGINX file as "server host:port". You can also configure and apply
additional NGINX Directives that do not have any corresponding parameters in the device's Web
interface. For more information, see
Configuring HTTP Directive Sets on page 275.
The device supports the following proxy services:
■ HTTP Reverse Proxy for managing equipment behind NAT: You can configure the
device to function as a Reverse HTTP Proxy server. You can use this for many HTTP-based
applications. For example, you can use it to intermediate between REST API clients and a
REST server.
Another example is to use the HTTP Proxy to intermediate between IP Phones and remote
servers for file download. The figure below illustrates this example where IP Phones (clients)
retrieve their configuration and firmware files from remote file servers (Upstream Hosts) and
where the device (HTTP Proxy) intermediates between the two. The HTTP hosts are located in
the cloud and the clients are located behind NAT. The HTTP Proxy listens for incoming HTTP
requests (Listening Interface and HTTP/S Listening Port) from the clients and then forwards the
requests to the relevant HTTP host, based on the URL (HTTP Location) in the incoming HTTP
GET request. If the URL matches the pattern "/firmware/", the HTTP Proxy sends the request
to the firmware file server; if the URL matches the pattern "/ipp/*.cfg", the requests are sent to
the configuration file server. In addition, customized NGINX directives have been configured for
each HTTP Location to define the maximum time to wait for an HTTP connection.
A summary of the required configuration for this example is listed below:
a. Enable the HTTP Proxy application (see Enabling the HTTP Proxy Application on the next
page).
b. Configure two Upstream Groups, where each is configured with an Upstream Host that
defines the IP address of the HTTP host (i.e., firmware and configuration file servers). See
Configuring Upstream Groups on page 272.
c. Configure two NGINX directives for proxy timeout connection (see Configuring HTTP
Directive Sets on page 275).
d. Configure a local, listening IP network interface for the leg interfacing with the HTTP
clients (see
Configuring IP Network Interfaces on page 96) or use the default.
- 261 -