Using a web proxy

You can specify one or more web proxies to use for outbound web requests from the Management Node, and from the Conferencing Nodes in each system location.

When configured, web proxies are used to route all requests from One-Touch Join, Secure Scheduler for Exchange and Epic telehealth; requests from the Management Node to cloud service providers; and for analytics, incident reporting, and license activation requests.

When a web proxy is configured for the Management Node, it is used to route outbound web requests in the following situations:

  • when sending usage statistics and incident reports,
  • for license activation requests,
  • when the Management Node communicates with the service configured for cloud bursting (i.e. Azure, AWS or GCP),
  • for OIDC administrator authentication requests,
  • (for deployments where One-Touch Join is enabled and is using OAuth) when the Management Node sends requests to the OAuth token endpoint,
  • (for deployments where Secure Scheduler for Exchange is enabled) when the Management Node sends requests to the Exchange server / Office 365, and (when OAuth is enabled) the OAuth token endpoint. Note that you can bypass use of the proxy for individual Exchange deployments using the Disable web proxy option.

When a web proxy is configured for a system location:

To use a web proxy, you must first add its details via System > Web Proxies, and then add it to the configuration for the Management Node (Platform > Management Node) or the system location (Platform > Locations) you wish to use it for.

Option Description
Name The name used to refer to this proxy server.
Address The IP address or FQDN of the proxy server.
Port

The IP port of the proxy server.

Default: 8080.

Username

Password

The username and password used when accessing the proxy server.

Next steps

You must now add the web proxy to the Management Node or to one or more System Locations.