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. Web proxies, when configured, are used to route all requests for analytics and incident reporting, Epic telehealth requests, some requests for license activation, requests from the Management Node to cloud service providers, and One-Touch Join requests. Support for other types of outbound web requests will be added in later releases.
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 sent to activation.pexip.com,
- when the Management Node is communicating with the service configured for cloud bursting (i.e. Azure, AWS or GCP), and
- (for deployments where One-Touch Join has been enabled and is using OAuth) when the Management Node is sending requests to the OAuth token endpoint.
When a web proxy is configured for a system location:
- all Conferencing Nodes in that location will use that web proxy for incident reporting, Epic telehealth REST API requests, and
if the system location is being used for One-Touch Join, all One-Touch Join-related outbound requests from Conferencing Nodes in that location will use the web proxy. These requests include:
- connections to Cisco endpoints
- connections to the Exchange server
- connections to Google Workspace
- (for deployments where One-Touch Join is using OAuth) for sending requests to the OAuth token endpoint.
To use a web proxy, you must first add its details via , and then add it to the configuration for the Management Node ( ) or the system location ( ) you wish to use it for.
|Name||The name used to refer to this proxy server.|
|Address||The IP address or FQDN of the proxy server.|
The IP port of the proxy server.
|The username and password used when accessing the proxy server.|