Avaya Aura Conferencing 7.0 Service Pack 0, Patch 2 Release Notes v1.5

Transcription

1 Avaya Aura Conferencing 7.0 Service Pack 0, Patch 2 Release Notes v1.5

2 Contents 1 Introduction Avaya Aura Conferencing 7.0 feature overview Software Versions Avaya Aura Conferencing 7.0 Software Line-up Avaya Clients Load line up Avaya Aura load line up Load line up for other servers Technical documentation Software updates Technical Advisements AMS Upgrade Procedure Hot Fix required for System Manager R6.2 SP1 to add or modify users in System Manager related to Conferencing profile System Manager R6.1 to R6.2 upgrade Single Sign On parameter needs to be manually turned on Alarm for WCMS resynch failure After a fresh install DCS file uploads can hang if proper procedure to download the DCS load is not followed Adhoc conference calls initiated by Avaya Flare Experience or 96x1 sets require 8 call appearances configured for Avaya Flare Experience and 96x1 sets Cannot add user in SMGR with 4 specific Time Zones Checkpoint versioning on redundant systems is not supported so these swerrs can be ignored Call server failover will cause active Avaya Aura Conferencing calls to be terminated Supported JAVA versions Excel documents cannot be uploaded using My Library Supported Flash versions with Firefox Avaya Flare Experience moderator on an Avaya Aura Conferencing 7 bridge dial out to a CS1000 Mobile-X client not supported Participants can access operator when in an active call Invited participant will not hear audible feedback prompt when they enter adhoc conference which is starting lecture mode Roster list is not updated when moderator dials out to user who is call forwarded to PSTN Avaya Flare Experience - Carousel of participant does NOT update status when participant puts the call on hold Add Location field to AAC Conferencing Profile Technical Support... 14

3 1 Introduction This bulletin includes important details that apply to the Beta Tech Trial for Avaya Aura Conferencing 7.0. It provides the software load line-up of Avaya Aura Conferencing 7.0, Avaya Aura, supported Avaya Clients and other call servers with which Avaya Aura Conferencing 7.0 interoperates. It also provides a list of advisements, limitations along with workarounds. The main focus of this trial is the audio and web conferencing features which are being introduced in Avaya Aura Conferencing7.0 2 Avaya Aura Conferencing 7.0 feature overview Avaya Aura Conferencing 7.0 delivers audio & collaboration conferencing features and advanced User Experience to Avaya Flare Experience clients and 96x1 R6.2. Clients that utilize all or some of the Avaya Aura Conferencing 7.0 Advanced UX/UI are: Avaya Flare Experience, Avaya Collaboration Agent/Web Collaboration and the 96x1 phones. Avaya Aura Conferencing features are accessible on clients using the advanced UI or TUI commands. The following are the highlights of the Avaya Aura Conferencing 7.0 feature: - System Features o MeetMe and Adhoc audio conference, Web Conferencing and Collaboration Agent. o Event Conferencing o Application Servers, Media Servers, Web server redundancy. o Supports Avaya Aura CM, CS1000, branch call servers and clients. - User features o Conference Roster. o Mute self, Mute/Mute all participants. o Lecture Mode. o Conference Lock/un-Lock. o Assume Moderator Role. o Promote to Moderator or Presenter. o Entry/Exit tones on/off. o Conference Continuation on/off. o Destroy Conference. o Add User. o Drop User. o Count Users. o Document sharing and Whiteboarding Collaboration. Page 3 of 15

4 3 Software Versions 3.1 Avaya Aura Conferencing 7.0 Software Line-up: Note: The data migration tool is required only if migrating from Avaya Aura Conferencing 6.0 to Avaya Aura Conferencing 7.0. PLDS ID PLDS Name File Name AAC AAC Data Migration Tool AAC_Data_Migration_Tool msi AAC AAC Platform Installer mcp_core_linux_ple iso dvd_aac_mcp_ _ AAC AAC Application Bundle _coreApps.iso AAC AAC Platform Patches mcp_core_linux_ple patches.r-1.ext.iso AAC AAC Application Patches MCP_ _ zip AAC AAC Application Patches MCP_ _ zip AAC AAC Media Server Upgrade MCP_MediaServer_ _ _183.zip Note: This patch includes an AMS upgrade. Please refer to section 6.1 for instructions. 3.2 Avaya Clients Load line up ** Please use the load versions published in PLDS** Please note that all clients (Avaya and 3 rd party) are supported for basic audio meet-me conferencing. SIP 96x1 R6.2 and Avaya Flare Experience 1.0 (Windows and ipad) provide support for advanced conference control. 3.3 Avaya Aura load line up ** The load line ups below are minimum load line ups please use the load versions published in PLDS** System Manager 6.2 SP1 AND HOT PATCH (refer to PSN003677u) Section 6.1 * Session Manager 6.2 SP1 Communication Manager patch Note: You MUST apply System Manager R6.2 SP1 and the hot patch Note: If System Manager R6.2 SP2 or higher version of patch is available, use that patch version. You do not require the hot patch for System Manager R6.2 SP2 or higher versions. 3.4 Load line up for other servers ** The load line ups below are minimum load line ups please use the load versions published in PLDS** Below is the minimum load line up required for these other servers: BCM450 CS1000 R7.5 B BCM050.R600.CORE-TELEPHONY-51-1 BCM050.R600.IPTEL-52-2 patch: cs1000-vtrk i MPLR31809 Page 4 of 15

5 4 Technical documentation See the latest versions of documents published on Avaya Support website. Title Accounting Records for Avaya Aura Conferencing 7.0 Administering Avaya Aura Conferencing Avaya Aura Conferencing Security Hardening Avaya Aura Conferencing 7.0 Security Design Avaya Aura Conferencing Alarms and Logs Avaya Aura Conferencing Collaboration Quick Reference Avaya Aura Conferencing Solution Description Avaya Aura Conferencing Overview and Specification Maintaining and Troubleshooting Avaya Aura Conferencing 7.0 Operational Measurements for Avaya Aura Conferencing 7.0 Planning and Design for Avaya Aura Conferencing 7.0 Using Avaya Aura Conferencing Collaboration Agent (PDF) Deploying Avaya Aura Conferencing 5 Software updates Regular patch advisements are provided on the Avaya Support website. The following is a list of issues addressed in SP0 patch2. Component Issue ID Reference Collab After stopping Primary WCS instance, Meeting Agent Report does not update wi Base Port redirection support on DMZ (enhance firewall rules for web server in the DMZ) wi Element FQDN needs to be prompted for during installation Mgr and populated in EM / Host wi CallP Missing user element in Notification packet causes Adhoc conference from 96x1 to fail wi IPDR Add dialled phone number into the IPDR records wi Technical Advisements The following section details technical advisements and other items of interest that may not have been published in the Customer documentation. Readers are encouraged to read this section in its entirety before attempting a software installation or upgrade. 6.1 AMS Upgrade Procedure A new Media Server software upgrade is available as part of the SP0 Patch2 release. Please refer to the Deploying Avaya Aura Conferencing document for instructions on how to upgrade Avaya Aura Conferencing 7.0 Release Notes v1.4 Page 5 of 15

6 the Avaya Media Server. However, since this upgrade is not delivered as part of an Application Bundle, you will need to copy the Media Server install.zip file directly to the Media Server folder instead of extracting it from the Application Bundle. To do this just replace steps 3-7 in the procedure with step 8. Copy MCP_MediaServer_ _ _183.zip to /var/mcp/loads on each Media Server. Procedure: 1. Stop the Avaya Media Server network element instance. 2. Log on to Avaya Media Server as ntappadm through ssh or directly at the server console. 3. Insert the Application Bundle DVD-ROM into the server. 4. Enter mcpextractcontent -at mcp_ams_platform to extract the Avaya Media Server software. 5. If prompted, type the password for the ntappadm account, and press Enter. 6. At the prompt The following files have been found, [1] Optical drive, [2] Quit, type 1 to extract the files from the DVD. 7. Verify the AMS load zip file entitled MCP_MediaServer_7.5.0.###_YYYY.MM.DD_##.zip is available. Enter 11 /var/mcp/loads. For example, MCP_MediaServer_ _ _77.zip. 8. Copy MCP_MediaServer_ _ _183.zip to /var/mcp/loads on each Media Server. 9. Log on to ntsysadm through ssh. 10. Enter su - to log on as root. 11. At the prompt, type mcpmsinstall.pl, and press Enter. 6.2 Hot Fix required for System Manager R6.2 SP1 to add or modify users in System Manager related to Conferencing profile Note: This is NOT required if using System Manager R6.2 SP2 or higher version patch. Please refer to PSN id PSN003677u. The System Manager patch must be applied on top of SMGR R6.2 SP1 load else you cannot modify or add users in SMGR related to Avaya Aura Conferencing conferencing profile To apply the hot patch: Note: This patch must be applied to Avaya Aura System Manager 6.2 Service Pack #1 Release. 1. Determine that the System Manager 6.2 Service Pack 1 release that is running by: a. Logging into System Manager b. Click the About link on the home/landing page. c. Verify that the System Manager Build No. is: System Manager SP1 Build No and Software Update Revision No: Backup System Manager before applying the patch Recommended 3. Download Follow the instructions below to download the patch: 1. Go to 2. Click on Products link on the left hand navigation menu. This will give a pop where you Page 6 of 15

7 type system manager and then select Avaya Aura System Manager 3. Now click on the Downloads link on the left hand navigation menu. 4. Select 6.2.X from the dropdown 5. Click on Avaya Aura System Manager Release 6.2 Service Pack 1 Downloads if you have System Manager Release 6.2 Service Pack 1 installed. 6. Go to the Downloads tab where you will find the patch System_Manager_06_02_ServicePack1_Patch1.bin for System Manager 6.2 Service Pack 1 Release. Patch install instructions Serviceinterrupting? Follow the instructions below to install the patch: Yes. During the 1. Get access to the System Manager Command Line Interface using patch installation the appropriate local OS user with root level permission. the System 2. Copy (System_Manager_06_02_ServicePack1_Patch1.bin ) from Manager your system to the system on which you have installed System services (web Manager Release. access to 3. Verify md5sum of System System_Manager_06_02_ServicePack1_Patch1.bin with the value Manager) will be from PLDS. disrupted for 4. Navigate to the directory where you copied the patch installer and approximately grant execute permissions to the file using the following command: 20+ minutes. # chmod +x System_Manager_06_02_ServicePack1_Patch1.bin 5. Run the patch installer using the following command: # sh System_Manager_06_02_ServicePack1_Patch1.bin 6. Wait for the system to execute the patch installer and display the installer prompt. 7. Log on to System Manager Console, and verify whether the System Manager UI is displayed correctly Follow the instructions below to install the patch: Yes. During the 8. Get access to the System Manager Command Line Interface using patch installation the appropriate local OS user with root level permission. the System 9. Copy (System_Manager_06_02_ServicePack1_Patch1.bin) from Manager your system to the system on which you have installed System services (web Manager Release. access to 10. Verify md5sum of System System_Manager_06_02_ServicePack1_Patch1.bin with the value Manager) will be from PLDS. disrupted for 11. Navigate to the directory where you copied the patch installer and approximately grant execute permissions to the file using the following command: 20+ minutes. # chmod +x System_Manager_06_02_ServicePack1_Patch1.bin 12. Run the patch installer using the following command: # sh System_Manager_06_02_ServicePack1_Patch1.bin 13. Wait for the system to execute the patch installer and display the installer prompt. 14. Log on to System Manager Console, and verify whether the System Manager UI is displayed correctly Verification To verify the successful installation Patch: 1. On successful completion of the patch you will see following message on your console: Installing MMCS Hot Fix - Done 2. Log on to System Manager Console, and verify that extension pack was installed successfully: On System Manager Dashboard on Services field click Configurations -> Extension Packs, find com.avaya.mgmt.upm.mmcs.ep and verify that version is and status success(confirmed) Page 7 of 15

8 3. A log file /opt/avaya/mmcs/mmcs_fix_install.log is created with more details on installation. Failure In case of issues with the patch, you can: 1. Retry the action. Carefully follow the instructions in this document. 2. Contact Avaya Support, with following information: Problem description, detailed steps to reproduce the problem, if any and the release version in which the issue occurs Patch rollback instructions Re install System Manager again and restore System Manager with the backup taken prior to patch installation. 6.3 System Manager R6.1 to R6.2 upgrade Single Sign On parameter needs to be manually turned on Issue: When upgrading from SMGR R6.1 to R6.2 the default setting for Single Sign On get set to False. Workaround You have to manually open the OpenSSO console. Go to Configuration -> Servers and sites -> Default server settings and Set c66encode to true and click save. - Note: This step is NOT required when upgrading to System Manager R6.2 SP2 or greater 6.4 Alarm for WCMS resynch failure Issue: If the alarm is seen on one of the instances deployed on your system, use the workaround steps. Workaround: 1. In the example shown below the alarm is seen on the instance called WCMS2. From the EM GUI, find the address on which instance WCMS2 is deployed, this can be retrieved using the Addresses option on the EMGUI. The WCMS2 in this case is on the WCSSvr2IntOAMAddr address. 2. Log into the server at address identified in step 1 using a program like putty using root privileges. 3. Run the command "chage --maxdays -1 rsyncappsw" as root Page 8 of 15

9 Page 9 of 15

10 6.5 After a fresh install DCS file uploads can hang if proper procedure to download the DCS load is not followed Issue: We need to ensure that the DCS load is copied directly from the DVD image or the PLDS web site directly onto the DCS SERVER. If in case the DCS software is copied over to the DCS server by other means it can result in DCS file uploads to get stuck. Workaround: To ensure that the DCS software (zip file) is marked safe, follow the instructions below: 1. Right click the downloaded ZIP downloaded that's been marked unsafe. 2. Click Properties, choose General Tab, then you'll see at the bottom of the window the "Security" message saying "This file came from another computer and might be blocked to help protect this computer". 3. Click "Unblock to make the file safe again. 4. Extract the files and they will run successfully. 6.6 Adhoc conference calls initiated by Avaya Flare Experience or 96x1 sets require 8 call appearances configured for Avaya Flare Experience and 96x1 sets Issue: In CM you will need to administer up to 8 call appearances for Avaya Flare Experience clients (windows and ipad) and 96x1 sets in order for adhoc conference call to work with Avaya Flare Experience and other set types. There are 3 ways to reduce the administrative effort: In System Manager, you can create a Flare station template and then replicate that template. Communication Manager allows the administrator to duplicate a layout of a station. Service R&D has a ProVision tool that will allow bulk administration of users. Workaround: None 6.7 Cannot add user in SMGR with 4 specific Time Zones Issue: The following time zones cannot be selected when creating or modifying a user that has a Conferencing Profile: (-11:0)Midway Island, Samoa; (0:0)Monrovia, Reykjavik; (+3:0)Baghdad, Kuwait, Riyadh, Nairobi, Tbilisi; (+8:0)Perth; Irkutsk, Ulaan Bataar Workaround: The work around until this problem is addressed is to select a time zone with the same or similar GMT off-set as you location. 6.8 Checkpoint versioning on redundant systems is not supported so these swerrs can be ignored AS1_1 SWERR 799 ALERT Mnthxx 12:10:47:657 MCP_ Page 10 of 15

11 com.nortelnetworks.ims.cap.prtcl.checkpoint.callpcp: Error in decoding Checkpoint java.lang.illegalstateexception 6.9 Call server failover will cause active Avaya Aura Conferencing calls to be terminated Issue: If the CM or CS1K does a failover the active Avaya Aura Conferencing7 calls will get dropped. This issue will be addressed in a future release. Workaround: None 6.10 Supported JAVA versions Issue: If you are running Java 1.7 update versions 1, 2 and 3, a warning appears stating that this version is not supported for desktop sharing. This Java version has inherent issues as mentioned by the vendors. You can continue to use it for sharing but you might experience issues, especially, annotation tools will not work as expected. Workaround: Downgrade to Java 1.6 or upgrade to Java 1.7 update version Excel documents cannot be uploaded using My Library Issue: MS Excel documents cannot be uploaded to My Library for sharing. Workaround: These document types need to be shared using Desktop or Application sharing modes Supported Flash versions with Firefox 13 Issue: Avaya does not recommend the usage of Firefox with Adobe Flash player 11.3 with Windows 7, (note: this is not an issue with Windows XP). With this setup there may be issues with resizing of the Collaboration Agent and the Firefox browser may be non-responsive if the user selects the logout button in the CA window to exit from the conference login page. Note: FF14.0 and later with Adobe Flash Player 11.4.x do not have this issue. The Adobe flash upgrade procedure is located at the following link: Workaround: If the user requires FF with Flash player 11.3 Avaya recommends to either revert back to an earlier version of flash player or temporarily disable the Protected mode in Flash. To revert to a previous version of Flash Player, please see this Adobe FAQ: How do I revert to a previous version of Flash Player? To disable Protected Mode in Adobe Flash player, please see the following Adobe FAQ (last section): How do I troubleshoot Flash Players Protected Mode for Firefox? Page 11 of 15

12 6.13 Avaya Flare Experience moderator on an Avaya Aura Conferencing 7 bridge dial out to a CS1000 Mobile-X client not supported Issue: If an Avaya Flare Experience 1.0 moderator has dialed into an Avaya Aura Conferencing 7.0 bridge attempts to dial out to a CS1000 Mobile X phone which is twinned to a CS1000 desk phone for simultaneous ringing, the CS1000 desk phone will be able to join the conference call as expected. But if the dial out call is received by the Mobile-X phone then they will not hear a prompt to press 1 to join the conference and the call will be terminated. This is a known limitation. Workaround: User must receive the call on the CS1K set Participants can access operator when in an active call Issue: Participants can dial *0 to get access to an operator only when they are in an active conference call. They will not be able to do so when dialing into the bridge. Workaround: Participant has to dial into an Avaya Aura Conferencing bridge and then press *0 to get access to an operator Invited participant will not hear audible feedback prompt when they enter adhoc conference which is starting lecture mode Issue: In Adhoc audio conference, when moderator turns on lecture mode successfully then invites participant to join in conference, participant joining in conference will not hear the prompt "You enter a conference starting with lecture mode". Workaround: None 6.16 Roster list is not updated when moderator dials out to user who is call forwarded to PSTN Issue: If moderator A dials out to add user B who is configured to have CFAC to PSTN user C - > User C can join the conference successfully but user B is added in Roster list of the other users (roster list on Avaya Flare Experience or SIP 96x1 R6.2 client) instead of user C. The issue only happens if Call forward is set to a PSTN number. Workaround: None 6.17 Avaya Flare Experience - Carousel of participant does NOT update status when participant puts the call on hold Issue: On the spotlight of Moderator, Carousel of Participant does NOT update status when participant puts the call on hold. Workaround: None Page 12 of 15

13 6.18 Add Location field to AAC Conferencing Profile This change is to provide a location field in the AAC Conferencing profile to allow configuration of location without the need for an SM profile. The location data is pushed to AAC DB as is it today with the SM Profile field. Please refer to the Administering Avaya Aura Conferencing 7.0 guide for details Page 13 of 15

14 7 Technical Support Support for Avaya Aura Conferencing is available through Avaya Technical Support. If you encounter trouble with Avaya Aura Conferencing: 1. Retry the action. Carefully follow the instructions in written or online documentation. 2. Check the documentation that came with your hardware for maintenance or hardwarerelated problems. 3. Note the sequence of events that led to the problem and the exact messages displayed. Have the Avaya documentation available. 4. If you continue to have a problem, contact Avaya Technical Support by doing one of the following: a. Logging into the Avaya Support Web site b. Calling or faxing Avaya Technical Support at one of the telephone numbers in the Support Directory listings on the Avaya support Web site. You may be asked to one or more files to Technical Support for analysis of your application and its environment. Note: If you have difficulty reaching Avaya Technical Support through the above URL or address, please go to for further information. When you request technical support, provide the following information: Configuration settings, including Avaya Aura Conferencing configuration and browser settings. Page 14 of 15

15 Page 15 of 15