Contents
Introduction
This document contains Experience Portal 7.0 Service Pack 2 product information that is not included in the product documentation. This document highlights known issues about the Experience Portal product along with workarounds that are available.
Note: Before continuing, check the Avaya support Web site at http://support.avaya.com for an updated version of this document.
Problems Fixed
| Number | Problem Description |
|---|---|
| wi01220233 | VoiceXML interpreter core dump |
| wi01220061 | Need to update Java |
| wi01219577 | After an upgrade some MPP processes are incorrectly limited to a single CPU core |
| wi01218915 | MediaManager core dump |
| wi01214514 | Need to update PostgreSQL |
| wi01214195 | Unrecognized fmtp parameters in an SDP offer cause SIP 500 error response |
| wi01213028 | ASR language selection does not work correctly when Web browser set to Spanish |
| wi01212823 | Need to update samba package in Avaya Linux |
| wi01212625 | Allow scheduled reports to trigger an event for a specified peak busy contact value |
| wi01212622 | Non-organization LDAP user incorrectly allowed to log in when system is configured to allow only organization LDAP users |
| wi01212566 | Session Detail Record fields TerminationInfo1 and TerminationInfo2 sometimes not set correctly for short lived sessions |
| wi01210129 | Auxiliary EPM sometimes stuck in Not the owner mode |
| wi01209918 | VoiceXML interpreter core dump |
| wi01209909 | Need to update tzdata package in Avaya Linux |
| wi01208781 | Need to update the kernel in Avaya Linux |
| wi01208780 | Need to update glibc package in Avaya Linux |
| wi01208777 | Need to update jasper package in Avaya Linux |
| wi01208775 | Need to update openjdk package in Avaya Linux |
| wi01208146 | Protect EPM login page from cross frame scripting attack |
| wi01207961 | Hang-up during record can cause a hung session |
| wi01207938 | Need to update openssl package in Avaya Linux |
| wi01207739 | Disable interrupt remapping on servers with chipsets that do not support it |
| wi01206954 | Nuance does not log for some applications |
| wi01206619 | DTMF input ignored when prompt timeout is too short |
| wi01206335 | Speech recognition does not correctly abort when external event received |
| wi01206158 | SessionManager core dump when receive H.323 call |
| wi01205937 | Changing launch order of parent application incorrectly changes launch order of child applications |
| wi01205935 | Should not be able to enable/disable an email processor if no email license is installed |
| wi01205934 | Should be able to enter SMS short codes that include "-", "+", and "*" |
| wi01205930 | Need to update Apache Tomcat |
| wi01205410 | Prompts sometimes not played during event handler |
| wi01205401 | Add timestamps to dmesg and kernel logging |
| wi01204464 | Scheduled backup fails if backup server is already mounted |
| wi01204321 | Need to update ntp package in Avaya Linux |
| wi01203944 | Need to update mailx package in Avaya Linux |
| wi01203941 | Need to update bind package in Avaya Linux |
| wi01203940 | Need to update rpm package in Avaya Linux |
| wi01202584 | Pass UCID on consultative transfers |
| wi01201704 | Harden security on network configuration in Avaya Linux |
| wi01201482 | Disable SSLv3 |
| wi01201193 | Set limit to 5 simultaneous SSH sessions in Avaya Linux |
| wi01201191 | Disable X11 forwarding in Avaya Linux |
| wi01199940 | Disable TCP forwarding in Avaya Linux |
| wi01196883 | Preserve existing keystore and truststore during upgrades |
| wi01195290 | Remove unused applications host-manager and manager from mmsserver instance of Tomcat |
| wi01193145 | Display error message when Avaya Linux upgrade fails because vpupgrade.sh has not been run |
| wi01166708 | SSH session timeout sometimes does not work in Avaya Linux |
| wi01100375 | Show EPM patch version in EPM web interface |
Product Information
The Experience Portal Documentation Library contains some information in hypertext markup language (HTML) and some information in portable document format (PDF). The HTML information is available on the Experience Portal software DVD. The PDF information is available from the Avaya support Web site at http://support.avaya.com.
See the document Avaya Aura® Experience Portal Documentation Roadmap (http://downloads.avaya.com/css/P8/documents/100183027) for a description of the various documents related to Experience Portal that are available.
To access the Experience Portal Documentation Library, place the Experience Portal DVD into a Windows system and use Internet Explorer to view the file \Documentation\VoicePortalDocLibrary\_StartHere.html.
Note: License agreements for each of the third-party components that ship with Experience Portal can be found in the Experience Portal DVD directory \Licenses.
Installation Notes
Important: Before installing or upgrading Experience Portal, please review the Known Issues section in this document for issues that are not addressed in the product documentation.
This service pack can be used to do a fresh install of a new Experience Portal system. You do not need to install Experience Portal 7.0 or Experience Portal 7.0 Feature Pack 1 before installing this service pack.
Important: Fresh installs of Experience Portal 7.0 SP2 require Red Hat Enterprise Linux Server release 6.6 (x86_64) or later 6.x release, or Avaya Enterprise Linux version RH6.6.64-AV02EP7SP2 or later.
For detailed installation procedures for non-OVA based systems, see either Implementing Avaya Aura Experience Portal on multiple servers or Implementing Avaya Aura Experience Portal on a single server, whichever is appropriate for your installation. These guides also contain important installation worksheets that should be filled out before starting the Experience Portal installation.
Important: Before starting an upgrade, you should back up your existing Voice Portal or Experience Portal database. In many cases the upgrade procedure requires you to take a backup in order to preserve your existing data. Additionally, if the upgrade fails for any reason you will need this backup to restore your system to its prior state.
Important: Upgrades from Voice Portal 5.1.3 and Experience Portal 6.x require upgrading to Red Hat Enterprise Linux Server release 6.6 (x86_64) or later 6.x release, or Avaya Enterprise Linux version RH6.6.64-AV02EP7SP2 or later. When upgrading from Experience Portal 7.0.x, upgrading Linux is recommended but not required.
For detailed upgrade procedures, see Upgrading to Avaya Aura Experience Portal 7.0.1. The procedure to upgrade to Experience Portal 7.0 SP2 is identical to the procedure to upgrade to Experience Portal FP1.
For instructions on how to deploy Experience Portal from OVA files in a VMware environment, see Deploying Avaya Aura Experience Portal in an Avaya Customer Experience Virtualized Environment.
Note: Deploying Avaya Aura Experience Portal in an Avaya Customer Experience Virtualized Environment contains procedures for both new deployments and upgrades of existing deployments.
The document Deploying Avaya Aura Experience Portal in an Avaya Customer Experience Virtualized Environment does not cover upgrading a single-server system. (That is systems that consist of a single server that has the Primary EPM and MPP co-resident, and may include a co-resident application server.)
The upgrade procedure for OVA based single-server systems is similar to the upgrade procedure for OVA based multi-server systems. The important differences are:
Note: This includes backing up all applications and any custom Apache Tomcat configuration (for example Tomcat users).
Note: This involves running the script configureMPP.sh as described in Deploying Avaya Aura Experience Portal in an Avaya Customer Experience Virtualized Environment.
Known Issues
N/A
While you are upgrading the Experience Portal software on an Auxiliary EPM server, a message similar to the following might be repeatedly displayed. The message might appear in any shell connected to that Auxiliary EPM server. This includes the system console and any SSH sessions that are open at the time.
PHP Warning: pg_connect(): Unable to connect to PostgreSQL server: could not connect to server: No such file or directory
Is the server running locally and accepting
connections on Unix domain socket "/tmp/.s.PGSQL.5432"? in /opt/Avaya/ExperiencePortal/VPMS/CompMgrService/bin/db_usage_query.php on line 30
You may safely ignore these messages. The message should no longer be displayed once the upgrade is completed.
Applications can make outcalls using the Application Interface web service. This web service runs on the Primary EPM server and on all Auxiliary EPM servers. Normally, throughout the upgrade process at least once instance of the Application Interface web service is available to make outcalls. However, if the name of the Primary EPM or any Auxiliary EPM contains a space (" ") character, then there may be a period of several minutes during the upgrade when all instances of the Application Interface web service are out of service at the same time. Note that once the upgrade is completed, all instances of the Application Interface web service will again operate correctly.
To work around this issue, remove all space characters from your EPM names before starting the upgrade.
Note: This issue does not apply if you are upgrading from Experience Portal 7.0.x.
In some cases, when an Experience Portal server is upgraded a new security certificate is generated for that server. (Experience Portal also provides the utility GenerateServerCertificate.sh that allows you to generate a new security certificate for a server after it has been upgraded.) If your Experience Portal system includes Intelligent Customer Routing (ICR), ICR may stop working whenever a new security certificate is generated on your Primary EPM or any Auxiliary EPM sever.
To make ICR operate correctly again, you must run the ICR utility update_cert.sh. See the section Fetching certificates in the document Upgrading Intelligent Customer Routing (http://downloads.avaya.com/css/P8/documents/100176439) for the procedure details.
In some cases, when an Experience Portal server is upgraded a new security certificate is generated for that server. (Experience Portal also provides the utility GenerateServerCertificate.sh that allows you to generate a new security certificate for a server after it has been upgraded.) If your Experience Portal system includes Proactive Outreach Manager (POM), POM may stop working whenever a new security certificate is generated on your Primary EPM or any Auxiliary EPM sever.
Additionally, when you upgrade your Primary EPM server the password for the database user named postgres is reset to a randomly generated value and access to the Experience Portal database using that account is prohibited from servers other than the Primary EPM. Both of these actions can also cause POM to stop working.
To make POM operate correctly again, refer to the document Upgrading Proactive Outreach Manager (http://downloads.avaya.com/css/P8/documents/100178576). Among other things, you may need to:
Important: Use the updated version of vpUpgrade.sh from POM301_EPFP1_Upgrade_patch.zip (https://support.avaya.com/downloads/download-details.action?contentId=C20141293557140_5&productId=P0638&releaseId=3.0.x).
Each OVA for Experience Portal 7.0 and Experience Portal 7.0 FP1 reserved 2400 MHz of processor within VMware vSphere. In Experience Portal 7.0 SP2 the CPU reservation in each OVA was increased to 9500 MHz. As a result, when you upgrade an OVA based system you may find that not all of your virtual machines fit on the VMware vSphere ESXi servers to which they are assigned.
To work around this issue, move some virtual machines to other ESXi servers that have available capacity. Note that you can choose to move either Experience Portal virtual machines or other virtual machines that happen to co-reside on the same ESXi servers.
As a last resort, you can use the VMware vSphere Client to lower the amount of processor reserved for each Experience Portal virtual machine. Be aware, though, that when you lower the CPU reservation there is some risk of introducing performance problems.
The Session Detail Report can optionally display a transcription that shows the details of what happened during a session. For example, the session transcription will show all VoiceXML pages loaded, all prompts played, and all utterances spoken by the caller. The Session Detail Report, however, will fail to show the session transcription if the name of the MPP that processed the call contains a hash ("#") character.
To work around this issue, remove all hash characters from your MPP names. Note that the Change MPP Server web page does not allow you to edit the name of an MPP. You must delete and re-add any MPP whose name you wish to change.
Typically, Experience Portal displays times in either the local time of the Primary EPM server or in the local time of the user's web browser. Sometimes the time displayed by Experience Portal is not correct for a particular time zone because the rules for that time zone have changed recently. In a typical year, for example, there are several countries around the world that either adopt or abandon daylight saving time (also known as summer time), or adjust when daylight saving time begins or ends.
To fix time zone related display issues, update each Experience Portal server to the latest version of the Linux time zone information RPM, tzdata. Also update the time zone information used by the Java Runtime Environment (JRE) on each Primary EPM and each Auxiliary EPM server. See PSN003432u (http://downloads.avaya.com/css/P8/documents/100149873) for the procedure details.
When Linux boots on HP ProLiant servers you may see the error below displayed on the system console. This error may safely be ignored.
[Firmware Bug]: the BIOS has corrupted hw-PMU resources
N/A
More Information
Online: