Avaya Oceana® and Avaya Analytics™ users use FQDNs to access the functionality in the solution. In the enterprise, FQDNs are resolved to the IP addresses through the internal Domain Name Server (DNS). For example, Avaya Workspaces users access Avaya Oceana® Cluster 1 or Avaya Oceana® Cluster 2 FQDNs to login and receive basic user functionality depending on the agent footprint size.

Similar to on-premise workers, remote workers must also be able to utilize the same URLs and client requests, even though they are outside of the enterprise. Therefore, customers must publish a DNS entry for each required Avaya Oceana® and Avaya Analytics™ FQDN that remote workers use. The number of FQDNs for publishing depends on customer configuration. For example, if a customer does not require Co-Browsing functionality, then the customer does not need to publish the Avaya Oceana® Cluster 4 FQDN.

When the remote worker accesses or requests a URL containing the Avaya Oceana® FQDNs, the FQDNs are resolved to a single IP, which is the external firewall Listen IP address.