AudioCodes E-SBC User Manual page 296

CHAPTER 16 Services
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
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
c. Configure two NGINX directives for proxy timeout connection (see
Directive Sets
d. Configure a local, listening IP network interface for the leg interfacing with the HTTP
clients (see
e. Configure a local, IP network interface for the outbound leg interfacing with the HTTP
hosts (or use the default).
f. Configure the HTTP Proxy server, by assigning it the listening IP network interface and
configuring a listening HTTP/S port (see
g. Configure two HTTP Locations for the HTTP Proxy server, where each is configured with
a URL pattern to match the incoming HTTP requests for determining the destination host
(Upstream Group-Upstream Host). In addition, assign it the relevant HTTP Directive Set.
See
■ Non-HTTP Proxy (referred to as TCP/UDP Proxy Server): The device can serve as a proxy
for other applications that are not based on HTTP. For example, it can be used to intermediate
between clients and a DNS server for DNS lookup, or between clients and an NTP server for
clock synchronization. For more information, see
page 266.
on page 272).
Configuring IP Network Interfaces
Configuring HTTP Locations
Mediant 1000 Gateway & E-SBC | User's Manual
Enabling the HTTP Proxy Application
on page 268.
on page 97) or use the default.
Configuring HTTP Proxy Servers
on page 262.
Configuring TCP-UDP Proxy Servers
- 258 -
on the next
Configuring HTTP
on page 260).
on