Communications Process Manager Release 2.1 Release Notes

Transcription

1 Communications Process Manager Release 2.1 Release Notes About these Release Notes These release notes support release of the Communications Process Manager software. Communications Process Manager Release 2.1 uses Web services to integrate Avaya communications solutions into customer business processes. Different events trigger the Communications Process Manager to invoke varying communication applications to escalate an issue to specifically identified persons for resolution. For example, the Notify and Conference Service sends a notification to end users and places them in a conference for immediate resolution to a business application issue. Integration Compatibility Matrix The following table describes the version requirements for each communication system that integrates with Communications Process Manager. Table 1: Compatibility Matrix Integrating software 1 Software version Communication Manager (CM) S patch for S S SP SIP Enablement Server (SES) SES SES Meeting Exchange Express Edition (Release 1.5) S of 2 Document No , Issue 2 December

2 Communications Process Manager Release 2.1 Release Notes Table 1: Compatibility Matrix (continued) Integrating software 1 Software version Voice Portal av-mpp patch av-mpp , vpms av-mpp , vpms Service Pack 1 Text to Speech (TTS) RealSpeak 4.0 rs-api rs-lic RealSpeak 4.5 rs-api nuance-licmgr Both Realspeak 4.0/4.5 SWMS rs-american-english-en-us-jennifer rs-american-english-en-us-samantha of 2 1. Associated software should follow normal patching guidelines. The Communications Process Manager solution does not require associated software to follow special patching guidelines. Using Australian, Indian, or British English resource packs Communications Process Manager 2.1 supports non-us English (Australian, Indian, and British) resource bundles. To use one of these resource bundles, perform the following procedure: 1. Login on as a root user. 2. Enter the following command to stop cpm-tomcat: lc stop cpm-tomcat. If you do not want to stop Communications Process Manager, you can skip this step. However, after you deploy the resource bundles, you will have to log in to the Web Portal to load the them See Step Go /usr/share/cpm-tomcat/webapps/via/web-inf/resource-bundles. 4. Enter the following command: chmod u+x convert_en_resources.py 5. Run the following executable file:./convert_en_resources.py 6 Communications Process Manager 2.1 Release Notes December 2007

3 Operational issues 6. After the resource bundles are deployed, perform one of the following actions: - If you stopped cpm-tomcat, enter the following command to restart cpm-tomcat: lc restart cpm-tomcat. - If you did not stop cpm-tomcat: a. Log in to the Web Portal as an administrative user. b. In the toolbar, click Administration. c. Under Administration Tasks, select all check boxes. d. Click Execute. To verify that the resource bundles were successfully deployed: 1. Log in to the Web Portal. 2. In the toolbar, click Account. The Account Home page is displayed. 3. Click Account Information in the left column. The Account Information page is displayed. 4. In the Language field, click Edit. All newly deployed languages should be listed in the drop down box. Operational issues Manual restart of Voice Portal 4.0 required if the SIP endpoint goes down If Voice Portal enters a degraded state for over ten minutes, you must manually restart Voice Portal. This issue is fixed in Voice Portal 4.1. Communications Process Manager LDAP The Communications Process Manager LDAP can support up to 12,500 users. However, to support more than 2,000 users, you must perform the following procedures to remove some LDAP restrictions: 1. Launching Fedora Console 2. Removing LDAP restrictions Communications Process Manager 2.1 Release Notes December

4 Communications Process Manager Release 2.1 Release Notes Launching Fedora Console 1. Log in as root. 2. If you log in remotely, export the DISPLAY setting to point at your own machine. 3. Go to /opt/fedora-ds. 4. Execute./start-admin 5. Open the file setup/setup.log and search for the string startconsole 6. Copy the string, for example, startconsole -u admin a localhost.localdomain:1234/, and execute it on the command line. 7. Enter the password when prompted. The default password is admin01. Removing LDAP restrictions 1. In the left pane of the Fedora Console, expand localhost.localdomain > Server Group in the navigation tree, and then click Directory Server. 2. In the left pane, expand Netscape Root > Topology Management in the navigation tree, and then click Administrators. 3. In the right pane, double click admin. The Edit Entry window is displayed for the Configuration Administrator. See Figure 1. 8 Communications Process Manager 2.1 Release Notes December 2007

5 Operational issues Figure 1: Edit Entry window for Configuration Administrator 4. From the list on the right, select Account. 5. Under Resource Limits, set all properties to -1. See Figure 1. Click OK. 6. On the Fedora Console, click the Configuration tab at the top. In the right pane, click the Performance tab. See Figure 2. Communications Process Manager 2.1 Release Notes December

6 Communications Process Manager Release 2.1 Release Notes Figure 2: Performance tab 7. In the Size limit field, replace the current value with the number of users that you need Communications Process Manager to support. See Figure 2. Click Save. 8. In the left pane, click Database Link Settings. In the right pane, click the Default Creation Parameters tab. See Figure Communications Process Manager 2.1 Release Notes December 2007

7 Operational issues Figure 3: Default Creation Parameters tab 9. In the Size Limit field, replace the current value with the number of users that you need Communications Process Manager to support. See Figure 3. Click Save. 10. In the left pane, click Database Settings. In the right pane, click the LDBM Plug-in Settings tab. See Figure 4. Communications Process Manager 2.1 Release Notes December

8 Communications Process Manager Release 2.1 Release Notes Figure 4: LDBM Plug-in Settings tab 11. In the Look-through Limit field, replace the current value with the number of users that you need Communications Process Manager to support. See Figure In the Maximum cache size field, replace the current value with the appropriate size. Avaya recommends that you increase the maximum cache size by one megabyte for every every 350 users in excess of 3,500. Click Save. 12 Communications Process Manager 2.1 Release Notes December 2007

9 Operational issues Fedora Console does not launch after performing a backup and restore After restoring the Communications Process Manager server from a backup archive, attempts to launch the Fedora Console fail. The following message is displayed if you attempt to launch the Fedora Console: Can not connect to The port number specified in the error message is taken from the restored database and does not match the port number in the property files. This issue prevents you from using the procedure in Removing LDAP restrictions to support more than 2,000 users. Workaround Change all the values for the new administration port under /opt/fedora/ to match the database. See the setup.log file, startconsole line for the port number that you need to change. The change must be made in the following configuration files. File: /opt/fedora-ds/admin-serv/config/console.conf Line: Listen <PortNumber> File: /opt/fedora-ds/admin-serv/config/local.conf Line: configuration.nsserverport: <PortNumber> File: /opt/fedora-ds/admin-serv/config/adm.conf Line: port: <PortNumber> File: /opt/fedora-ds/setup/setup.log Line:./startconsole -u admin -a After making the changes, restart the administration server to load the changes. Run the Fedora console now by using the old port number, and it will be able to access the directory server. User authentication To access the Communications Process Manager Web Portal, users must enter either their account number or handle and their personal identification number (PIN). Communications Process Manager 2.1 does not directly authenticate users against the enterprise LDAP. Because of this issue, administrators should, if possible, map the userpassword CPM LDAP attribute to the same enterprise LDAP attribute that the employeenumber CPM attribute is mapped to. Use the LDAP Synchronization Configuration page of the OAM interface to map CPM LDAP attributes to enterprise LDAP attributes. This workaround ensures that users have a numeric CPM PIN. If no numeric identifier exists on the enterprise LDAP, you can map the userpassword attribute to the same enterprise attribute that the uid CPM attribute is mapped to. After the enterprise and CPM LDAPs are synchronized, users should log in to the Web Portal and change their password to a numeric PIN. Use the Change PIN page of the Web Portal to change your PIN. Communications Process Manager 2.1 Release Notes December

10 Communications Process Manager Release 2.1 Release Notes Communications Process Manager Watchdog Watchdog (watchd) version is part of Communications Process Manager Release 2.1. Watchdog monitors various services and thresholds in Communications Process Manager and also restarts any services that may enter an unintended shut down state. Watchdog version supports a maximum of 4092 threads in the system for real-time Linux priorities. If the number of active threads in the system exceeds this number, watchdog may abort. This issue will be resolved in a subsequent release/patch of Communications Process Manager. Workaround To prevent this issue from occurring in Communications Process Manager 2.1, perform the following procedure: 1. Open the file /opt/coreservices/watchd/conf/watchd.conf for editing. 2. Search for the entry CPUOccupancyInterval in this file. 3. Ensure that this variable is set equal to 0 (default is 30). 4. Save the file and exit. 5. Restart watchd by typing: /sbin/service watchd restart Token for external recipients and unauthenticated internal recipients Communications Process Manager leaves different tokens (single-use PINs) in and voice mail messages for external recipients and unauthenticated internal recipients of Advisory and Notify and Response notifications. However, recipients can enter either token when they call in to Communications Process Manager to retrieve the notification. SES host maps do not match URIs that contain an IP address In SES version , host maps do not match URIs that contain an IP address. For example, given the following host map: pattern: sip:dialog@.* contact: sip:dialog@ :5061;transport=tls A SIP message with the URI of sip:dialog@ will not match the pattern (even though it matches the regular expression), so the port and transport are not added. 14 Communications Process Manager 2.1 Release Notes December 2007

11 Operational issues Workaround In the Communications Process Manager OAM interface, configure Voice Portal and Meeting Exchange Express Edition with the SES SIP domain in place of the IP address. For example, configure Voice Portal as follows: SIP User field: dialog IP Address/Hostname field: SES domain (for example, avaya.com) Then configure the host mapping as follows: pattern: contact: (assuming that VP is using TLS) Ampersand, greater than, and less than symbols in notifications Do not use the ampersand (&), greater than (>) or less than (<) characters in the message or subject of notifications. These characters can cause the corresponding request to fail. This issue applies only to requests that are initiated by client applications. Requests that are initiated from the Web Portal display these characters correctly. Expired Notify and Conference requests and Find and Call requests display a status of canceled Expired Notify and Conference requests and expired Find and Call requests are displayed as canceled requests. Setting attributes of addrecipients operations Setting the following attributes in addrecipients operations has no effect: unauthenticated cancel previous person reminder delay sequence delay The initial settings from the start request are used for these attributes instead. This issue applies only to requests that client applications initiate. The Web Portal does not allow addrecipients operations for open requests. Communications Process Manager 2.1 Release Notes December

12 Communications Process Manager Release 2.1 Release Notes Backing up customized style sheets Avaya strongly recommends that you manually copy any customized stylesheets to a safe place for backup. Perform this manual backup immediately after installing the customized style sheets. Customized style sheets are not currently backed up by the Communications Process Manager backup utility. If you upgrade the Communications Process Manager software, or if a loss of data occurs on the server, the customized style sheets are lost. updatemediacontent operation for the Notify and Conference service The updatemediacontent operation is not supported for the Notify and Conference service once the conference is already running. When a blank subject, non-blank subject, or no subject is specified in the updatemediacontent operation for Notify and Conference, an error is returned. However, Communications Process Manager does support media content lists in StartNotification operations for the Notify and Conference service. 16 Communications Process Manager 2.1 Release Notes December 2007