Avaya Experience Portal 7.2 and later versions support HTML as an additional communication channel and provide a mechanism to move a self-service interaction from a voice interface to a web interface. HTML applications are always launched by name through the Application Interface web service. As a result, there is no concept of launch criteria, launch order, and default HTML application.
Note:
Experience Portal supports HTML applications that are developed using Avaya Orchestration Designer only.
In this deployment, Experience Portal is completely isolated from the public network while the Orchestration Designer application is partially isolated from the public network by using the customer’s HTTP reverse proxy server. An additional security layer is provided by isolating the internal configuration and parameters from the public network. In addition, the system provides a mechanism to make visible only established Orchestration Designer sessions to the public network by session initiation that comes through the HTML Redirector application and Experience Portal.
Note:
You must specify the host address of the reverse proxy if you are using a reverse proxy in front of the redirector or multiple redirectors for added redundancy.
You must configure and use a separate redirector for each zone on zoned systems.
The HTML feature in Experience Portal is used to create applications called Visual IVR - that is they create a visual metaphor for an IVR flow.
