Add the Next Hop Based on the Host Header Filter

You must add the RealPresence Web Suite Experience Portal as a next hop before you can configure an HTTP tunnel proxy.

Use the Host header filter when adding a next hop to various HTTPS application servers, including the RealPresence Web Suite Experience Portal. You can also add a next hop to the RealPresence Web Suite Services Portal but should do so only if you want SIP guest clients to access the service from outside the firewall.

CAUTION: If you add host header next hops, you must specify the host FQDNs as Subject Alternative Names (SANs) in the Certificate Signing Request for the RealPresence DMA system.


  1. Go to Service Config > Access Proxy Settings.
  2. Do one of the following:
    • Click Add HTTPS Proxy to add a new HTTPS proxy.
    • Select an existing HTTPS proxy and click Edit.
  3. Under Next Hops, click Add.
  4. Configure the settings as described in the following table:
    Field Description
    Type Request-URI or Host header
    Name The unique name of this next hop.

    For Request-URI next hop only.

    Polycom Management System or Polycom Content Sharing Suite (also called Polycom ContentConnect)

    Note: Add a separate Request-URI next hop if you need to configure HTTPS settings for both systems.
    Host value

    For Host header next hop only.

    The FQDN in the request message header that identifies the resource being requested.

    Address The private IP address of the target HTTPS server. After accepting the HTTPS request from the external endpoint, the RealPresence DMA system sends a new HTTPS request to this IP address.
    Port The listening port of the internal application server.
    For Host header type, use the following configuration:
    next hop configuration
  5. Click OK to save the settings.