Reverse proxy policies, TLS profiles, and relay services

Last Updated : Oct 13, 2020 |

Session Border Controller and reverse proxy perform many essential functions that must be appropriately configured on each deployment:

  • Many whitelist relays require a WebSocket connection. Therefore, on Session Border Controller, you must create a reverse proxy policy with WebSockets enabled.

  • Session Border Controller reverse proxy relay requires the following:

    • A TLS client profile for the interface facing the internal Intranet Avaya Oceana® and Avaya Analytics™ servers/clusters

    • A TLS server profile for the interface facing the Internet

  • For each server/cluster:port combination, you must configure a reverse proxy relay service. For multiple servers using the same port, such as 443, Session Border Controller directs the requests to the appropriate back-end server/cluster based on the URL in the request.

    For example, you must configure a relay service for each of the following:

    • Avaya Oceana® clusters containing the Authorization service

    • Avaya Analytics™ Real-time and Historical Reporting