Avaya Aura Communication Manager Messaging R6.2 SP3 Release Notes

Transcription

1 Avaya Aura Communication Manager Messaging R6.2 SP3 Release Notes August 24, 2015 Overview Communication Manager Messaging R6.2 Service Pack 3 (SP3) contains several important fixes listed later in this release letter. Notes: Communication Manager Messaging 6.2 must be installed prior to applying this service pack. Service Pack 3 is cumulative so you do not need to install any previous service packs. Installing this service pack as outlined in this document will be service affecting. Available downloads File Description PLDS File ID CMM tar Avaya Aura Communication Manager Messaging R6.2 Service Pack 3 CMM Installation It is highly recommended that a system backup of the Messaging data set Messaging Translations, Names and Messages be performed prior to applying any update. Service Pack 3 is service affecting for the Communication Manager Messaging Application. To stop the messaging application: 1. Log on to the Communication Manager/Messaging SMI. 2. Click Administration > Messaging. 3. Click Utilities > Stop Messaging. 4. Follow all prompts to stop the messaging application. Apply updates using the method outlined below. To download: 1. Log on to the System Platform Web Console. Use an 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. Choose the medium specific selections to complete the download.

2 To install: 1. Click Server Management > Patch Management > Manage. 2. On the Patch List page, click on the Service Pack ID link to see the details. 3. On the Patch Detail page, click Install. Removing the Service Pack Removing a Service Pack will remove all updates from the system and bring it to a base installation. Note that removing the service pack will leave the messaging system in a stopped state. Manual starting of messaging via the SMI is required to start the voice system. Note a subsequent Service Pack install will automatically start messaging. To remove: 1. Log on to the System Platform Web Console. Use an advanced administrator login and password. 2. Click Server Management > Patch Management > Manage. 3. Under the cm section on the Patch List page, click on the service pack ID link to see the details. 4. On the Patch Detail page, click Remove. 5. Optionally if it is desired to remove the original tar file from the system click Remove Patch File. This will remove the service pack tar file from the system.

3 Issues Fixed in SP 3 MSG Support upgrades from CMM6.2 and to CMM 7.0 Issues Previously Fixed in SP 2 MSG-6456 MSG-7135 Large Postfix logs can cause problems for browsers MCAPI: get_subscriber_id_by_number() fails unexpectedly in some circumstances. MSG-5044 Test Outgoing Call Sequence doesn't take port numbers from 3 to 9. MSG-5927 MSG-6243 MSG-7413 MSG-7351 MSG-6414 MSG-7672 MSG-7687 MSG-6453 MSG-8891 MSG-9052/MSG-9059 MSG-8737 Block characters ^ and \ for the local and remote subscribers' names. Wrong error message popup when entering long first name. CMM plays the message header of a voice message sent from AAM incorrectly. Delta update does not work on CMM - Deleted Subscribers are not sent. Restore failed due to large mailbox. CMM user can't send private Message to AAM user using LDAP/SMTP networking. Ldap transaction logging not being logged Display activity log is unable to display activity log records for timezones ahead of the machine where the clinet browser is run. The original message was not played when reply or forward with comment to the remote SMTP subscriber. MSS stopped delivering outbound messages when it found an originator w/an apostrophe in it Many H323Card core dumps being created

4 Issues Previously Fixed in SP 1 MSG-5041 MSG-5042 MSG-5236 MSG-5233 MSG-5333 MSG-5484 MSG-5238 MSG-5043 Excluded Mailbox number shows wrong error message Unable to remove added numbers when erase invalid entry Leading zeroes not always preserved when displaying list of subs System Administration page does not allow "Ldap Athenticated only" setting to be saved Add/Edit Networked Server help page missing information about certain fields. Unable to change mailbox password after first change. Received error when adding subscriber with non-existent extension. Change Extensions web page is unable to handle extensions more than 15 digits long MSG-4535 Weekly audit failed if subscribers names start with "**" MSG-5882 MSG-6365 MSG-6389 MSG-6412 MSG-6401 MSG-6268 MSG-6497 MSG-6825 MSG-6450 MSG-6539 MSG-6966 MSG-6390 Can't edit subscriber Mailbox number if "Messaging Server Admin" has a prefix configured Filter local/remote web pages don't enforce matching mailbox number lengths Some LDAP data configuration files have the wrong permissions Update Sort and Filter help page; allow 'From' or 'To' value. Long Server Side folder names w/lots of path name components causes imapd to use all virtual memory and swap space. Some RFC822-generated dates: timezones east of GMT incorrect format Several errors w/change announcement form Missing caller extension on forwarded message Message Server Admin -"Log Update In" can not be changed. Outgoing messages won't use SMTPS Add Help for "Update Received" field of "Request Remote Update" form. System Administration->Covering Extension accepts less than 3 digits.

5 MSG-5366 When running ILG load, No Answer rate is high MSG-6510 SipAgent core dumps in CMM 6.2 MSG-6448 MSG-5203 MSG-4822 MSG-5465 MSG-4598 MSG-5300 MSG-5507 MSG-5080 MSG-5635 Increase the delay between when a call ends on a channel and it's put back in service CM -Media Encryption set to [1-srtp-aescm128-hmac80, none] Call to CMM drops SMI>Call Transfer Administration>Addition/Deletion don t accept variable length extension FAX print from Messaging is failing when G350/G250/G700 used call rejected for non-numeric calling number Large SIP messages (~4kb) could potentially break processing of incoming TLS packets resulting in all incoming calls to fail Cannot change a 50-digit extension to a shorter extension MWI failure when active SM controller fails over to secondary SM Retry NOTIFY requests for MWI if the primary SM is set to Deny New Service state