|
1
|
Have the completed installation worksheets ready to help answer the questions raised during the configuration.
|
|
|
|
2
|
If the customer plans to have their system maintained by Avaya Services, set up the Avaya Services access requirements.
|
|
|
|
3
|
Log in to the Experience Portal Manager (EPM) web interface.
Tip:
Once you log in, click the Help button on the appropriate EPM web page for information on how to configure the EPM web page.
|
|
|
|
4
|
Install the Experience Portal license file.
|
|
|
|
5
|
Add at least one Voice over IP (VoIP) H.323 or SIP connection.
|
|
|
|
6
|
(Optional) Add multichannel applications, such as SMS, Email, and HTML applications. You can add one SMS, one Email, and one HTML applications for each channel.
|
See Administering Avaya Experience Portal.
|
|
|
7
|
Add the MPP server to the system and start the MPP server.
|
|
|
|
8
|
(Optional) Add one or more Automatic Speech Recognition (ASR) servers.
|
|
|
|
9
|
(Optional) Add one or more Text-to-Speech (TTS) servers.
|
|
|
|
10
|
Add the Experience Portal test application.
|
|
|
|
11
|
Test the basic system by running the sample application.
|
|
|
|
12
|
(Optional) Connect the EPM server to an external time source so that all servers in the Experience Portal system are synchronized.
|
|
|
|
13
|
EPM can accept input in non-English languages. If you are using Red Hat Enterprise Linux, the languages need to be installed with the operating system. If you are using Avaya Enterprise Linux, you can configure it to accept input in Chinese, Japanese, or Korean.
|
|
|
|
14
|
If you want to enable organization level access in Experience Portal, run the EnableOrganizationscommand.
|
See Administering Avaya Experience Portal.
|
|