Current Publication | x
Close

Access Proxy Settings

When configured as an edge server, the Polycom ® RealPresence ® DMA ®  system provides proxy services for external devices. You can configure access proxy settings to enable firewall and NAT traversal for sign-in and provisioning requests from remote endpoints. When the RealPresence DMA system receives a request from a remote endpoint, the system sends a new request on behalf of the remote endpoint to the appropriate application server. The RealPresence DMA system then proxies the request response from the application server to the remote endpoint. The request response directs the remote endpoint where to send registration and provisioning requests.

If the request is accepted, the RealPresence DMA system sends a new request on behalf of the remote client to the appropriate application server. Access proxy is the sign-in data connection from remote user to rpad to rprm, css, mea, or wsp. DMA/Edge receives HTTPS requests destined for someone else (RPRM, etc.). Edge will proxy the provisioning request response from RPRM, CSS, etc, to the ep. The response tells ep where to register for sip, h323 (these registrations ARE subject to ACLs)

 

Caution: Before configuring any access proxy settings, you must configure the network interface settings for public and private access proxy IP addresses.

The RealPresence DMA system supports five types of proxies that route communication requests based on the type of target application server:

HTTPS Proxy–HTTPS servers that provide management services (Polycom ® RealPresence ® Resource Manager system, Polycom ContentConnect™ system), and web-based video conferencing services (Polycom ® RealPresence ® Web Suite)

HTTP Tunnel Proxy–Polycom   RealPresence Web Suite systems that provide web-based video conferencing services.

LDAP Proxy–LDAP servers that provide directory services

XMPP Proxy–XMPP servers that provide message, presence, or other XMPP services

Passthrough Proxy–A passthrough proxy provides transparent relay of communication requests through the RealPresence DMA system to internal application servers.

PassThrough_proxy is used primarily for backward compatibility with the TCP reverse proxy feature. Note that if you upgrade your system to a new version, PassThrough_proxy will not display on the main Access Proxy Settings page if you did not configure a TCP reverse proxy in a previous version of the RealPresence DMA system.

 

Note: If you created an HTTP tunnel proxy in a previous version of the RealPresence Access Director system, the HTTP tunnel proxy configuration will display on the Access Proxy Settings page after you upgrade your system to a new version.

You can add proxies for different internal application servers. When you configure the proxies, you must specify an external IP address and an external listening port for access proxy. You can reuse an external IP address but the port, in most cases, must be unique for each proxy configuration that uses the same external IP address. For example, if you create two proxy configurations for LDAP directory services, the combined external IP address for access proxy and the external listening port cannot be the same for both LDAP proxy configurations.

The following example shows some possible external IP address and port combinations.

Name of Proxy

External IP Address for Access Proxy

External Listening Port

LDAP proxy 1
10.20.102.58
389
LDAP proxy 2
10.20.102.58
9980
HTTPS proxy
10.20.102.58
443
HTTP tunnel proxy
10.20.102.58
443

When adding or editing a proxy, the system validates the settings to ensure that no conflicts exist with any other proxy configurations and displays a warning message if conflicts are found.

Related Topics

Machine Translation

You are cautioned that the translation of this document is generated by a machine; therefore, the translated document may have errors and be inconsistent with the original English language version of the document.

The English language version of this document shall be considered the governing document related to the Polycom product.

If there is any contradiction between the English language version of the document and the translated version of the document, the English language version of the document shall take precedence.

The translation is provided for your convenience only. Neither Google nor Polycom shall be responsible for translated content or for the performance of the translation tool. If you require further assistance on non-translation issues, please contact Polycom support.

Translated documents are not available in PDF format.