Avaya Aura Messaging v6.0.1 Service Pack 2 Release Notes July 14, 2011 Overview Avaya Aura Messaging v6.0.1 Service Pack 2 (SP2) contains several key fixes, including several for performance improvements. Additionally, this update also includes support for System Platform v6.0.3. Messaging v6.0.1 must be installed prior to applying this Service Pack. This SP2 supersedes Messaging v6.0.1 SP1, Message Core Patch A, Cornerstone Patch B and Messaging Application 6.0.1 RFU ak, as it includes all fixes provided in those updates. The Service Pack must be loaded via the System Platform Console Domain (C-dom) under Server Management > Patch Management. The Messaging SMI must not be used to load Service Packs. New Language Packs and a new System Platform Service Pack and Patch are included in the rollout, but are loaded separately. Please refer to the System Platform Service Pack 6.0.3 and System Platform Patch 6.0.3.1.3 Release Notes for additional details. IMPORTANT: Please note that after upgrading Avaya Aura Messaging 6.0.1 to Service Pack 2, an automatic reformat of the Avaya Message Store will be performed. This message store reformat can take some time to complete depending on the size of the customer data. This process can take as much as an hour on a large system. To monitor the progress of the message store reformat: 1. Log onto the Avaya Aura Messaging System Management Interface (SMI) 2. Select Administration > Messaging > Utilities > Start Messaging 3. A pop-up message box is displayed that states Voice Messaging is already started. Press OK to dismiss the pop-up box. 4. Scroll down to the bottom of the web page. You will see the following once the reformat is complete and messaging is online: End: start_vm:. followed by a date and timestamp line. 5. Alternatively, you will see Reformat of LDAP data Started while the message store reformat is still in progress. NOTE: This page will not refresh automatically. Please continue selecting Start Messaging periodically till you see the End: start_vm: message followed by a date and timestamp. Do not attempt to stop messaging or reboot the server while this message store reformat is taking place. If you do stop messaging or reboot during the message store reformat process, you will have to restore the data again and start over. Please also refer to the Avaya Product Support Notice PSN003372u. Please note that installing updates as outlined in this document will be Service Affecting. Available downloads Messaging v6.0.1 SP2 comprises of the following software: Description File PLDS ID Messaging 6.0.1 Service Pack 2 MSG-00.1.510.1-004_0201.tar.gz AAM00000400 System Platform Service Pack 6.0.3 vsp-6.0.3.0.3.iso AAM00000401 System Platform Patch 6.0.3.1.3 vsp-patch-6.0.3.1.3.noarch.rpm AAM00000402
The following new additional language packs are available with this revision of the Avaya Aura Messaging software. Please note that you must install this SP in order to deploy these two new language packs: Description File PLDS ID Simplified Chinese Language Pack for 6.0.1 Japanese Language Pack for 6.0.1 MSG-zh-CN-00000000-6.0.1-3.lpk MSG-ja-JP-00000000-6.0.1-3.lpk AAM00000316 AAM00000317 The following language packs were released with 6.0.1 Service Pack 1 and can continue to be used with Service Pack 2 (unchanged since Service Pack 1): Description File PLDS ID US English Rapid Prompts Language Pack MSG-en-US-00000001-6.0.1-2.lpk AAM00000310 German Language Pack MSG-de-DE-00000000-6.0.1-2.lpk AAM00000311 British English Language Pack MSG-en-UK-00000000-6.0.1-2.lpk AAM00000312 Latin American Spanish Language Pack MSG-es-XL-00000000-6.0.1-2.lpk AAM00000313 Canadian French Language Pack MSG-fr-CA-00000000-6.0.1-2.lpk AAM00000314 Brazilian Portuguese Language Pack MSG-pt-BR-00000000-6.0.1-2.lpk AAM00000315 Issues addressed in Messaging 6.0.1 Service Pack 2 MSGESC-182 MSGESC-256 MSGESC-258 MSGESC-277 MSGESC-279 MSGESC-284 Unable to delete a broadcast message from a user's mailboxes in a multi server model where there are clustered application servers. Recipients are experiencing inconsistent MWI updates for messages sent via Enhanced List In some cases, delays in completion of nightly maintenance occur due to consistency checks looping every ~15 minutes, resulting in intermittent delays for end user. Delays and bad gateway error may be seen sometimes while accessing User Reports pages with large numbers of subscribers and/or remote users. To prevent delay in turning on or off a user s MWI light, MWI requests are now throttled at the SIP layer. Only one outstanding request will be allowed at one time. If a response has not been received within 15 seconds of sending the NOTIFY, the MWI update will be flagged as failed. After changing the default LDAP password, you cannot create a new ELA. It fails with Error: Password is invalid(1023). You can create a new user. In order to create a new ELA you have
to revert to the default LDAP password. MSGESC-297 MSGESC-298 MSGESC-301 MSG-1861 MSG-2096 MSG-2106 MSG-2114 MSG-2129 MSG-2254 After installing v6.0.1 SP1, the AxC configuration information was lost on application servers. The result was that users were unable to access their voice messages. To workaround this issue, manual configuration of AxC IP Address and AxC Port was needed. Callers experience 1.2 second delay during transfers. The workaround was to reduce this deliberate delay by setting the SendReferInit delay value to zero. Password expiring message to the user in User Preferences is showing {0} instead of a valid value. Help button on ELA Delivery Failures page is not directed to its help page. Improved serviceability allowing SIP call id to be tracked in the cstrace logs. When creating or editing an ELA list on AAM, the following javascript error is seen: document.add_local_sub.ummessageorderingflagsadmin is null or not an object In Outlook 2010, if the client uses the default of "none" for encryption on the Advanced tab, and SPA (Secure Password Authentication) is checked, login to SMTP doesn't work "Saved" messages forwarded with Outlook are incorrectly classified in TUI review. Saved" messages after changing status using Outlook (e.g. reply) get classified incorrectly when listening to them with the TUI. Issues addressed in previous Messaging 6.0.1 updates MSGESC-201 MSGESC-202 MSGESC-211 MSGESC-222 MSGESC-226 MSGESC-229 MSGESC-232 Error received when attempting to save an edited Caller Application if no Additional Extensions are defined. To workaround this issue, insert a unique value in the first Additional Extension field for the Caller Application. Certain Messaging SMI pages could not be accessed when using a limited Web Access Mask, such as User Management, User Reports, Class of Service, Sites, Topology, and System Status (Application). You will get an LDAP 1505 error if you attempt to set a secondary extension to match any mailbox or extension number already in use. If the IP Codecs are not set to the same size, then DTMFs are not recognized when dialing into the Avaya Aura Messaging system from one-x Communicator. Incoming audio will also not be processed, so no messages can be left for subscribers. Internal Server error on User Management pages may sometimes be seen due to a Read timeout error while accessing the license status. Reach me settings are not retained after being disabled and then re-enabled using the TUI Percolation (delays) when Reach Me setting is modified via TUI
MSGESC-234 MSGESC-235 MSGESC-238 MSGESC-243 MSGESC-249 MSGESC-255 Message retrieval from backend is time consuming, causing timeouts and percolation during message retrieval Messages are not fetched from cluster cache in a cluster when they are not in local cache causing percolation during message retrieval OutOfMemoryError: Java heap space caused GAL Reload to fail for installations that contained large sets of Remote Users Messaging Announcements options have been removed from the Backup Data Sets list in the SMI as they are no longer applicable. Mailbox Initialization TUI plays incorrect prompts License file is installed but not showing in the active or normal mode. Showing exceeded mode. This is due to an expired certificate. MSGESC-257 User cannot successfully setup account in Outlook 2010 MSGESC-261 MSGESC-267 MSGESC-271 MSGESC-272 MSGESC-287 MSGESC-288 Intermittent failures seen with fax and outcalls after the system is running for a while. Intermittent dead air symptoms are seen on some calls. Outcalls are failing intermittently with "Unknown call outcome(9)=irem_error" No audio while attempting to leave a call answer message Intermittently users experience percolation symptoms (delays) during message retrieval Intermittently users experience percolation symptoms (delays) and dead air, upon logging into mailbox Installation IMPORTANT: Please perform a complete system backup prior to applying this update. For more information, refer to the Backup and restore section of the Administering Avaya Aura Messaging guide. For new installations, please refer to the Implementing Avaya Aura Messaging and the Administering Avaya Aura Messaging guides for information on installing and configuring Avaya Aura Messaging. Applying the Service Pack Apply both the System Platform and Messaging updates using the method outlined below. For detailed instructions on how to apply a Messaging Service pack, see the Applying software updates and the Service pack installation sections in the Implementing Avaya Aura Messaging guide. To apply Language Packs, select the Administration > Messaging > Server Settings (Application) > Languages page in the SMI. NOTE: In a Messaging System that consists of more than one server role, upgrade the Storage role server first, then proceed to upgrade all Application role servers. Prior to installing this Service Pack, stop Aura Messaging:
1. Log on to the Messaging System Management Interface (SMI). 2. Select Administration > Messaging > Utilities > Stop Messaging. To download: 1. Log on to the System Platform Web Console. Use the advanced administrator login and password. 2. Click Server Management > Patch Management > Download/Upload. 3. From the Choose Media list, select the medium to search for a patch. 4. From the Select Patches list, select the patch that you want to download. 5. Click Select. To install: 1. Click Server Management > Patch Management > Manage. 2. On the Patch List page, click on the patch ID link to see the details. 3. On the Patch Detail page, click Install. Install any required Language Packs to each Application server role in the Messaging system. Removing the Service Pack Removing Service Pack 2 will remove all post 6.0.1 updates from the system and revert it to a base 6.0.1 installation. Therefore, if you wish to remove this Service Pack, you will need to reinstall Messaging 6.0.1 Service Pack 1 and any applicable post SP1 Remote Field Updates (RFUs) and/or Patches in order for Messaging to function properly. See the Installing 6.0.1 Remote Field Updates section below for details. NOTE: In a Messaging System that consists of more than one server role, downgrade all application role servers first, and then downgrade the Storage role server. To remove the Service Pack: 1. Log on to the System Platform Web Console. Use the advanced administrator login and password. 2. Click Server Management > Patch Management > Manage. 3. Under the msg section on the Patch List page, click on the patch ID link to see the details. 4. On the Patch Detail page, click Remove. Known Issues SAPP-1653 SAPP-1812 SYSI-1437 wi00727257 Users cannot address a message to newly added Remote Subscribers or new subscribers that have been added using the Provision tool until the Nightly Maintenance has completed or a manual reload of the Userlist/GAL on each application server has been performed. When changing the default System Language, you need to reload the User List and the Global Address List for names recognition to work in the new language. When callers are waiting while their call is routed to Reach Me destinations, there is no audible feedback from the system while it is trying to complete the call. This is normal and users should not hang up. The maintenance log may contain multiple occurrences of the following VOIP006 error, which can be ignored:
IP CA 23 ERR VOIP 1 AudioProcessor.cc:1 App: VP EventID:VOIP006 Date/Time Rec:09/09/10 09:26:54 Cnt: 1 Media problem. Reason: RTP: under=0 over=1 wi00832767 MSGESC-245 MSGESC-252 If a server has the role of Storage Server only, the System Status command will incorrectly state the Voice System is down. When deleting a mailbox that has a message in it, it does not turn off MWI on station. In rare situations, MWI can stop working with Connection refused errors. In this situation a restart of the Messaging system is required Known Issues for New Language Packs MSG-1465 MSG-1663 MSG-1664 MSG-1666 MSG-1727 MSG-1788 User names must be entered using only the English alphabet. In the User Management Properties for any user, the First Name, Last Name, and Display Name must not contain any characters not found in the English alphabet. Invalid characters may cause problems in the User List, the GAL and may result in the user not being found in the TUI. Prompts that request a spoken response will not be recognized in Chinese or Japanese. When the system language is set to Chinese or Japanese and speech recognition is enabled in the Auto Attendant, the system will not recognize responses in Chinese or Japanese. It is recommended to either disable speech recognition in the SMI, on the Sites page under Auto Attendant when the system language is set to Chinese or Japanese or set the system language to the default American English, therefore prompting for responses that will be recognized. Spell mode will not recognize user names using non-english alphabet characters. When attempting to lookup a user by spelling their name using the keypad in the TUI, only English alphabet letters will be recognized. Name recognition in Chinese and Japanese will only work if the Pronounceable name field contains only English alphabet characters. It is recommended to enter a Chinese or Japanese user s name using the English alphabet and spelling in such a way that the pronunciation would be recognized by an English speaker. In addition, if the expected behavior by a user or caller during name recognition is to use the name order: Last name then First name; enter the Pronounceable name in the same order. Chinese and Japanese users that would like their name order to be Last name then First name, must have it entered in this order in the Display Name field in the User Management Properties of the SMI. If the Display name field if left blank, by default it will be populated with First name Last name. The subject line of a voice message in Outlook does not display Chinese or Japanese characters defined in the SMI. In the SMI, when Chinese or Japanese characters are used to define the subject line of an original message, message reply or forwarded message, the string will display as?????????? in Outlook rather than show the defined characters.
MSG-2012 MSG-2044 Chinese and Japanese prompts in the TUI will use 12-hour time format. Incorrect and/or incomplete character set for messaging menu items in the Outlook rightclick menu for Chinese and Japanese. When a Chinese or Japanese Outlook end-user right-clicks on a voice message, the messaging menu items Play On Phone, Voice Reply, Voice Forward and Call Sender do not accurately display these choices in Chinese and Japanese. These phrases are either shortened or contain characters that indicate that not all localized characters are displayed.