Beyond the Enterprise Applications Security

Last Updated : Sep 29, 2020 |

All Avaya Oceana® and Avaya Analytics™ deployments must be accessible to the Internet world. This access cannot be direct, but is allowed and made available in a secure manner through various security specific applications.

The following are examples of external access that are required for Avaya Oceana® and Avaya Analytics™ deployments:

  • Avaya Oceana® Chat and Messaging customers require their communications to be securely routed in and out of the Avaya Oceana® core and surround applications including users' desktops and browser. Avaya Workspaces users require Internet access for messaging.

  • Avaya Oceana® Email contacts require routing in and out of the Avaya Oceana® Email processing engine and its agent desktop client.

  • Avaya WebRTC Connect customers using either voice and/or Video require their communications to be securely routed in and out of the Avaya Oceana® core and surround applications including users' desktop and browser.

  • Other supported channels like SMS, Social and Generic, all require access from the Internet world in and out of the enterprise deployment.

  • Remote users require secure access to all the functionality available inside the enterprise when they are working remotely.