The reverse proxy determines which URL requests must be allowed and how the requests must flow into enterprise applications. They also determine the reverse communications to remote workers.
The reverse proxy is configured with a whitelist. Customers configure the whitelist for their deployment and it has all internal Avaya Oceana® and Avaya Analytics™ URLs that all workers require to access the contact center functionality.
The following tables shows a sample whitelist configuration:
Cluster/Server
Whitelist URL in Request
Reverse Proxy Listen IP
Listen Port
Internal Firewall Destination IP
Internal Firewall Port
Avaya Oceana® Cluster 1
/services/CustomerManagement/
Avaya Oceana® Cluster 1
/services/OCPDataServices/
Avaya Oceana® Cluster 1
/services/CustomerJourneyService/
Avaya Oceana® Cluster 2
/services/UnifiedAgentController/
Avaya Oceana® Cluster 2
/services/Broadcast-UnifiedAgentController/
Avaya Oceana® Cluster 3
/services/AgentControllerService/
Avaya Oceana® Cluster 3
/services/CustomerControllerService/
Avaya Oceana® Cluster 4
/services/CoBrowse/
Avaya Analytics™
/orca-streams-rest/
/orca-streams-data-publisher/
/AvayaAnalytics/
Avaya Aura® Device Services
/acs/
Avaya Aura® Device Services
/notification/
Avaya Oceana® Cluster 2
/services/AuthorizationService
A remote worker who requests a destination containing an internal URL in the HTTPS request, such as /services/CustomerManagement/, gets forwarded to a preconfigured IP address and port on the internal firewall for that URL. The internal firewall uses its own rule (NAT) to allow/deny this request into the final internal destination component in Avaya Oceana® and Avaya Analytics™.
Note:
For the following clusters, reverse proxy relays require you to enable WebSockets on the proxy connection:
