Avaya Aura Conferencing 8.0 Patch5 Release Notes v1. (AAC 8.0 Patch5)

Transcription

1 Avaya Aura Conferencing 8.0 Patch5 Release Notes v1 (AAC 8.0 Patch5) November 2014

2 Contents 1 Introduction 5 2 Avaya Aura Conferencing 8.0 Patch5 overview Corrective Content List New Files for AAC 8.0 Patch Full AAC 8.0 Patch5 Release Line-up (for bare metal) Full AAC 8.0 Patch5 Release Line-up (for VMWare) 7 3 Installation of AAC 8.0 Patch Supported Upgrade Paths Apply Application Patch5 (as per normal procedures): Avaya Clients Load Line-up Latest AAC Mobile Client Downloads Recommended Avaya Aura Load Line-up Minimum Avaya Aura Load Line-up Load Line-up for other servers 10 4 Technical documentation 10 5 Software updates 11 6 Technical Advisements Alarm for WCMS remote synchronization failure Ad hoc conference calls initiated by Avaya Flare Experience or 96X Checkpoint versioning on redundant systems Call server failover 14 Issue: If the CM or CS1K does a failover, the active Avaya Aura Conferencing calls will get dropped. This issue will be addressed in a future release Avaya Flare Experience moderator dial out to a CS1000 Mobile-X client Operator in an active call 14 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 dialling into the bridge Roster list Avaya Flare Experience - Carousel of participant Subscribers unable to upload documents using the Web Collaboration interface in certain scenarios Lose Conference Events when H.323 Transfers to Flare Video will not work if call held prior to conference start Use of CAMgr FQDN Conference Stays up during Avaya Aura Session Manager failover Use of Application Layer Gateways (ALGs) with AAC is Not Recommended Use of Moderator Passcode with Scopia solution not recommended Using Recording with Avaya Flare Experience Avaya Aura System Manager Multiple Device Access (MDA) Trying to perform Sharing in Avaya Aura Conferencing Web Collaboration without Java installed Re-joining a locked conference in Avaya Aura Conferencing Web Collaboration Using full screen sharing with large resolution displays Use of CD-RW for platform ISO files One-X Communicator 6.2 unable to receive SRTP Video after video mute One-X Communicator unable to transfer conference to Flare when using Video SRTP Web collaboration plug-in and 64-bit browsers Use of lecture mode with One-XC H Users using the E129 or B179 device cannot enter the conference if the user is brought into the call using dialout Playing a music file while using the IOS App will result in Audio being dropped Galaxy S5 not yet supported ios video does not resume if paused by conference moderator Excel files truncated when shown from collaboration library Dial out to a user on a B179 device fails No video when joining an IP Office endpoint into a conference via the AAC Outlook Plugin Mobile App audio only on ipad Mini Video disabled for ios Mobile App when used in Event Conference 20

3 6.35 Mobile App session terminated when taking GSM calls for over a minute Use of iphone Split video when using Logitech QuickCam Pro Video icon incorrect for receive-only video Interaction issue with Android Communicator App Add Audio/Video dialog presented when hitting Enter in Web Collaboration message window _ Patch application fails periodically AAC Alarms not covered by Avaya monitoring services 22 7 Technical Support 23

4 Revision History Date Version Reason For Update November 5, 2014 V1 Initial AAC8.0 Patch5 Release Notes. Page 4 of 23

5 1 Introduction This document includes important details for Avaya Aura Conferencing (AAC) 8.0 Patch5, including the software load line-up of this product, Avaya Aura, supported Avaya clients, and other call servers with which this product interoperates. It also provides a list of advisements, limitations, and workarounds. 2 Avaya Aura Conferencing 8.0 Patch5 overview Avaya Aura Conferencing 8.0 Patch5 contains corrective content for various issues as indicated below. 2.1 Corrective Content List Key AAC-8395 AAC-8385 AAC-8383 AAC-8381 AAC-8375 AAC-8342 AAC-8282 AAC-8192 AAC-8143 AAC-8102 AAC-8100 AAC-8067 AAC-8063 AAC-8061 AAC-8054 AAC-7897 AAC-7854 AAC-8517 Summary Importing a user from LDAP with an * in the CN name will fail to update passcodes CA and Web Conf Participant clicks X to close Add Audio/Video panel and then click Audio button, this panel displays as loading. Some internet facing users may have trouble starting web collaboration On CA login and landing page, download link of AAC Web Collab Sharing Plug-in refers to 32 bit plug-in for 64 bit browsers Some participants cannot join conference (under certain timing scenarios) CA misinformation in the log file about availability of "Send logs" option CA freezes while exiting from conference on PPAPI Chrome flash player CA freezes randomly on PPAPI Chrome flash player In CA the add AV popup default devices is not remembered after change Additional debug logging for web collab CAPI raise hand does not work Event conference traffic robustness fix Update GME version to include enhancement for echo cancellation Address potential deadlock in CA plugin on audio device change VMware-Deploy AM Transaction failed causing AM patching failed Firefox version 31 has blank (empty) Participation report in CA IE doen t shows links to download plugins on login page Changing devices in CA can take 30 seconds (when selecting between many different AV devices). Page 5 of 23

6 2.2 New Files for AAC 8.0 Patch5 The following is the list of incremental new files required for AAC 8.0 Patch5. PLDS ID PLDS Name File Name PLDS Description AAC AAC8.0 GA Application Patch MCP_ _ zip Application Patch is applied on top of Application Patch (or later patch) to bring the application up to the latest patch level. MD5 = 39627B6EB024AC12F5AED524ED39295A 2.3 Full AAC 8.0 Patch5 Release Line-up (for bare metal) The following is the latest release line-up for all bare metal systems.. PLDS ID PLDS Name File Name Notes AAC (NEW) AAC AAC AAC AAC AAC8.0 GA Application Patch AAC8.0 Upgrade PrepKit AAC8.0 GA Platform Installer AAC8.0 GA Platform Patch AAC8.0 GA Application Bundle MCP_ _ zip upgradeprepkit- 0.5.tar.gz.bin mcp_core_linux_ple iso mcp_core_linux_ple patches.r- 1.ext.iso dvd_aac_mcp_ _ _coreApps.iso Application Patch is applied on top of Application Patch (or later patch) to bring the application up to the latest patch level. MD5 = 39627B6EB024AC12F5AED524ED39295A Please ensure that you have a valid AAC8.0 License Key before proceeding - This upgrade prep kit is required when upgrading the AAC platform from AAC7.2 to AAC8.0 IT64. MD5 = 5e5ab53244e8e240b2ae39b1a795f773 Please ensure that you have a valid AAC8.0 License Key before proceeding - Platform Installer is to be used for fresh installation of new AAC8.0 systems and when first upgrading from AAC7.2 SP3 systems. It is applied to each Linux server. MD5 = 6eeb1ce6ee9aa9609dddab0d6aab9bb0 Please ensure that you have a valid AAC8.0 License Key before proceeding - Platform Patch is applied to existing AAC8.0 systems that are on Platform version to bring the platform OS up to the latest version. This patch is not required if doing fresh installation using Platform Installer MD5 = 90d2a1ca89b80fd6846df0a1a6232d2a Please ensure that you have a valid AAC8.0 License Key before proceeding - Application Bundle contains various AAC8.0 applications load files. It Page 6 of 23

7 AAC AAC8.0 GA Application Patch MCP_ _ zip is used to fresh install new AAC8.0 GA installations or applied to existing AAC8.0 IT66 Beta or AAC7.2 SP3 systems to the bring them to the new GA level. In either case, you need to ensure that you upgrade to Platform first. MD5 = B9929AA6B26F60BB4B2C450003AA4BBD Please ensure that you have a valid AAC8.0 License Key before proceeding - Application Patch is applied after installing or upgrading to the GA Application Bundle to bring the application up to the latest patch level. MD5 = a7f5b462118f12ad60ffec49069c Full AAC 8.0 Patch5 Release Line-up (for VMWare) The following is the latest release line-up for all the VMWare related files. PLDS ID PLDS Name File Name Notes AAC (NEW) AAC AAC AAC8.0 GA Application Patch AAC8.0 GA Medium Simplex OVA AAC8.0 GA Medium Redundant Primary OVA MCP_ _ zip vaac_mediumsimplex _MCP_ _ vDisk150GB_8vCPU_2 4GBMemory.ova vaac_mediumprimary _MCP_ _ vDisk150GB_8vCPU_2 4GBMemory.ova Application Patch is applied on top of Application Patch (or later patch) to bring the application up to the latest patch level. MD5 = 39627B6EB024AC12F5AED524ED39295A Please ensure that you have a valid AAC8.0 License Key before proceeding - This OVA is used for the Medium Simplex deployment model. This OVA has AAC8.0 GA platform and applications (network elements, FMG, DCS etc) installed, running and ready to be deployed in Virtual environment. This is the only OVA that you need for this deployment model unless you are also deploying Cascaded Media Servers. For Cascaded Media Servers, you will also need the Small Platform OVA. Note that you will need to apply the GA Application Patch after deploying this OVA. MD5 = FBED6C9BC607AC72C19 Please ensure that you have a valid AAC8.0 License Key before proceeding - This OVA is used for the Medium Redundant deployment model. This OVA has AAC8.0 GA platform and applications (network elements, FMG, DCS etc) installed, running for Medium Redundant Page 7 of 23

8 AAC AAC AAC AAC8.0 GA Medium Redundant Secondary OVA AAC8.0 GA Small Platform OVA AAC8.0 GA Large Platform OVA vaac_mediumseconda ry_mcp_ _ vDisk150GB_8vCPU_2 4GBMemory.ova vaac_smallplatform_ MCP_ _ vDisk150GB_6vCPU_1 6GBMemory.ova vaac_largeplatform_ MCP_ _ vDisk150GB_12vCPU_ 30GBMemory.ova Primary system setup and ready to be deployed in Virtual environment. Note that this deployment model also needs the Medium Redundant Secondary OVA for redundancy and the Small Platform OVA if deploying Cascaded Media Servers. MD5 = A633F994C97163F673229E969E149B8E Please ensure that you have a valid AAC8.0 License Key before proceeding - This OVA is used for the Medium Redundant deployment model. This OVA has AAC8.0 GA platform and applications (network elements, FMG, DCS etc) installed, running for Medium redundant secondary system setup and ready to be deployed in Virtual environment. Note that this deployment model also needs the Medium Primary OVA to be installed first and also the Small Platform OVA if deploying Cascaded Media Servers. Note that you will need to apply the GA Application Patch after deploying this OVA. MD5 = CA4B6A2AF3E220D146CE944C8E Please ensure that you have a valid AAC8.0 License Key before proceeding - This OVA is used when deploying Cascaded Media Servers for AAC8.0 GA. MD5 = D5B68114E116C742F629D4AB Please ensure that you have a valid AAC8.0 License Key before proceeding - This OVA is used to create VMs for all components of the AAC8.0 GA Large Deployment model, except for any Cascaded MS. Cascaded MS uses the Small Platform OVA. MD5 = B3D2A0A38BA6355EFC9D886DC 3 Installation of AAC 8.0 Patch5 3.1 Supported Upgrade Paths Please ensure that the minimum software load is AAC 8.0 Patch2 prior to applying Patch5. You should refer to the original AAC 8.0 GA Release Notes for information about how to install new AAC 8.0 systems or how to upgrade existing 7.2 systems to AAC 8.0. The following upgrade paths are supported for AAC 8.0 Patch5. Page 8 of 23

9 AAC 8.0 -> AAC 8.0 P2 -> AAC 8.0 P5 or AAC 8.0 -> AAC 8.0 P2 -> AAC 8.0 P4 -> AAC 8.0 P5 3.2 Apply Application Patch5 (as per normal procedures): Extract Application Patch MCP_ _ zip (as per normal procedures): Put new Application Patch load on Primary EM server in the /var/mcp/loads directory Apply Application Patch: Login into Primary EM server as ntappadm Execute the mcppatch.pl command as documented in the product documentation In the Tools menu of Element Manager Console, select Patch/MR Manager From the Load or Patch box in the Patch/MR Manager window, select the patch you want to install. Green check marks should appear on both the Element Manager folder and the Logical DBs folder Select each NE type that has a Red check mark and then Click on the Patch button When the NE Maintenance window appears, click Details to display the patching steps in a status pane at the bottom of the window Verify that no failures are reported in the status pane at the bottom of the window and the patching process completes successfully Repeat steps.5 to.7 for each NE in the system and ensure all are with Green check marks. 3.3 Avaya Clients Load Line-up Please use the latest load versions published in PLDS. 3.4 Latest AAC Mobile Client Downloads Android App: ios App: Recommended Avaya Aura Load Line-up ** The table below captures the recommended version for each Aura component please use the load versions published in PLDS** Also, please be aware that this load line-up applies to the solution regardless of the Aura deployment model used. Page 9 of 23

10 SMGR SM CM SBCE 6.2 FP3 with latest patch releases in PLDS 6.2 FP3 with latest patch releases in PLDS 6.3 with latest patch releases in PLDS 6.2 FP1 with latest patch releases in PLDS 3.6 Minimum Avaya Aura Load Line-up ** The table below captures the minimum version for each Aura component please use the load versions published in PLDS** Also, please be aware that this load line-up applies to the solution regardless of the Aura deployment model used. SMGR SM CM SBCE 6.2 FP2 with latest patch releases in PLDS 6.2 FP2 with latest patch releases in PLDS 6.2 SP5 with latest patch releases in PLDS 6.2 FP1 with latest patch releases in PLDS 3.7 Load Line-up for other servers ** The table below captures the minimum version for each component please use the load versions published in PLDS** BCM050.R600.CORE-TELEPHONY-51-1 BCM450 BCM050.R600.IPTEL-52-2 CS1000 R7.5 patch: cs1000-vtrk i MPLR31809 CS1000 R7.6 Current GA Service Pack B Technical documentation The AAC 8.0 documentation available is listed below. Title Avaya Aura Conferencing Overview and Specification Guide for Aura Avaya Aura Conferencing Overview and Specification Guide for Universal Solution Description for Large Enterprises Solution Description for Medium Enterprises Solution Description for SME Deploying Avaya Aura Conferencing Upgrading Avaya Aura Conferencing Page 10 of 23

11 Using Avaya Aura Conferencing Collaboration Agent Administering Avaya Aura Conferencing Maintaining and Troubleshooting Avaya Aura Conferencing Migrating Avaya Aura Conferencing Port Matrix for AAC 8.0 Intelligent Workbook for AAC 8.0 This documentation can be accessed at the Avaya Support website or by contacting Avaya directly. 5 Software updates Regular load and patch advisements are provided on the Avaya Support website. The current line-up for AAC 8.0 can be found in section 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 Alarm for WCMS remote synchronization failure Issue: You might encounter this alarm which is caused due to the expiration of the remote synchronization password: Page 11 of 23

12 Workaround: 1. In the example shown above 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. Normally the WCMS logical names follow a pattern of WCSSvr#IntOAMAddress; using the example picture below that means that WCSSvr2IntOAMAddr has the address. Page 12 of 23

13 2. Log into the server at address identified in step 1 using a program like putty using root privileges. 3. Disable password aging on the passwords by executing the command "chage -- maxdays -1 rsyncappsw" with root permissions. 4. Change the password for the rsyncappsw account (required only to actually reset the expired password flag). 6.2 Ad hoc conference calls initiated by Avaya Flare Experience or 96X1 Issue: In CM you will need to administer between 2 and 8 call appearances for Avaya Flare Experience clients (windows and ipad) and 96X1 sets in order for ad hoc conference calls to work with Avaya Flare Experience and other set types. There are 3 ways to reduce the administrative effort: - In SMGR, you can create a Flare station template and then replicate that, - On CM, you can duplicate the layout of a station or - You can use the ProVision tool that allows bulk administration of users. Workaround: None 6.3 Checkpoint versioning on redundant systems Issue: 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_ com.nortelnetworks.ims.cap.prtcl.checkpoint.callpcp: Error in decoding Checkpoint java.lang.illegalstateexception Page 13 of 23

14 6.4 Call server failover Issue: If the CM or CS1K does a failover, the active Avaya Aura Conferencing calls will get dropped. This issue will be addressed in a future release. Workaround: None 6.5 Avaya Flare Experience moderator dial out to a CS1000 Mobile-X client Issue: If an Avaya Flare Experience 1.0 moderator that is dialed into an Avaya Aura Conferencing conference 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 call is received by the Mobile-X phone, then the user 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 will have to receive the call on the CS1K desk set. 6.6 Operator 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 dialling into the bridge. Workaround: Participant has to dial into an Avaya Aura Conferencing bridge and then press *0 to get access to an Operator. 6.7 Roster list Issue: In a specific call scenario involving dialing out to a user who has call forwarding enabled, the original number dialed is shown on the roster, not the number to which the call was forwarded. The issue only happens if Call forward is set to a PSTN number. Workaround: None 6.8 Avaya Flare Experience - Carousel of participant Issue: When using Flare Experience as a moderator you will not be able to tell when a participant goes on hold. Workaround: None 6.9 Subscribers unable to upload documents using the Web Collaboration interface in certain scenarios. Issue: Subscribers will not be able to upload a document if they have more than 50 files in their personal library. Subscribers will not be able to upload a document in cases in which the system runs out of space on the DCS server. Subscribers will see an I/0 error in this scenario. Workaround: Page 14 of 23

15 Subscribers will need to delete some of the files from their personal library in order to upload new files. Administrators can also proactively correct this situation by monitoring the server and freeing up space when required. o The library data is stored in the /var/mcp/app/run/webcollab/library folder on the WCMS server. The AAC EM server monitor option can be used to view the current space utilization. o Minor, Major and Critical alarms will be generated by the system based on the utilization of space in the var/mcp partition. The default thresholds levels are 70%, 80% and 90% for minor, major and critical alarms respectively. The thresholds are also configurable and administrators can configure lower or higher levels based on their system needs. o When the server reaches a certain threshold level, administrators can free up space in this folder so that users can upload new files to their personal library. o The maximum number of files that a subscriber can upload is configurable and administrators can change the value based on their system needs. The default value is set to 50. A system restart is not required for the change to take effect. Increasing the value will have system performance impact and is not recommended. Search for the upload.maxfile attribute in the following files and update as required.. /var/mcp/run/mcp_18.0/<<wcsne>>/apache/www/me eting/config-dist.php /var/mcp/run/mcp_18.0/<<wcsne>>/apache/www/me eting/config.php o The maximum allowed file size that a subscriber can upload is configurable and administrators can change the value based on their system needs. The default value is set to 32 MB. A system restart is not Page 15 of 23

16 required for the change to take effect. Increasing the value will have system performance impact and is not recommended. WCS Server: Search for the upload.maxsize attribute in the following files and update as required. Value should be set in bytes. /var/mcp/run/mcp_18.0/<<wcsne>>/apache/www/me eting/config-dist.php /var/mcp/run/mcp_18.0/<<wcsne>>/apache/www/me eting/config.php WCS Server: Search for the upload_max_filesize attribute in the following file and update as required. Value should be set in bytes. /var/mcp/run/mcp_18.0/<<wcsne>>/apache/php.ini DCS: Search for the upload_max_filesize attribute in the following file and update as required. Value should be set in bytes. <<DCS InstallDir>>/php/php.ini 6.10 Lose Conference Events when H.323 Transfers to Flare Issue: When an H.323 enabled endpoint transfers a Flare endpoint to an AAC conference, the Flare endpoint will not be able to receive conference events such as active speaker and will not be able to execute conference controls. Workaround: The Flare user should join the conference manually Video will not work if call held prior to conference start Issue: If a user dials into a conference with video and then places the call on hold prior to actually being put into the conference, that user will not have video for the call. This also happens in dial-out scenarios if the user called does a hold prior to pressing 1. Putting an endpoint on hold after the user joins the conference works fine. Video resumes when the call is taken off hold. Workaround: Re-join the conference without using hold prior to being placed into the conference Use of CAMgr FQDN Issue: The Microsoft Outlook Plug-in will not work correctly unless the Fully Qualified Domain Name of the Collaboration Agent Manager network element is entered into the WebConferencingHost field. This field is available in the AAC Element Manager for the Colaboration Agent Manager network element. Workaround: Enter the data into the WebConferencingHost field. Page 16 of 23

17 6.13 Conference Stays up during Avaya Aura Session Manager failover Issue: If the moderator on a conference is being served by an Avaya Aura Session Manager which either goes out of service or is taken out of service, the conference will not detect that the moderator has left the call, and the call will stay up. Workaround: There is no workaround; the call will remain up until the moderator joins the conference again and then exits the call normally Use of Application Layer Gateways (ALGs) with AAC is Not Recommended Issue: Use of an ALG with AAC results in AAC functionality no longer working due to the ALG limiting message sizes and restricting sequence numbering. Workaround: Remove the ALG from the conferencing solution 6.15 Use of Moderator Passcode with Scopia solution not recommended Issue: If a participant in an AAC conference is connecting via a Radvision MCU (either 5000 or 6000 series) and he/she uses the moderator code to join the conference, then any users hearing music while they wait for the conference to start will never be joined into the conference. Workaround: This issue does not happen if the participant code is used for people joining via a Radvision MCU. Only use of the participant code is recommended. When the participant code is used to join a call from Scopia, the AAC conference begins in fast start mode and the moderator code is not required. AAC Conference Moderators will need to join as participants if joining using the Scopia client. AAC Conference Moderators are encouraged to join via the AAC bridge in order to retain moderator controls Using Recording with Avaya Flare Experience Issue: Starting and stopping Avaya Aura Conferencing Recording can only be activated by dial pad sequences when using Avaya Flare Experience Workaround: To start or stop Recording, enter *2 in the Flare dial pad and follow the audio prompts Avaya Aura System Manager Multiple Device Access (MDA) Issue: Using Avaya Aura System Manager s Multiple Device Access functionality is not supported with Avaya Aura Conferencing. Workaround: There is no workaround; please disable this functionality for users accessing Avaya Aura Conferencing Trying to perform Sharing in Avaya Aura Conferencing Web Collaboration without Java installed Issue: If a conference participant or moderator attempts to share their screen or an application on a computer without Java installed and also without the web Page 17 of 23

18 collaboration plug-in installed, the user will receive an error: "This Webpage wants to run the following add-on: 'Control name is not available' from 'Not Available'. Workaround: Install the web collaboration plug-in Re-joining a locked conference in Avaya Aura Conferencing Web Collaboration Issue: If a conference moderator starts a web collaboration session with no audio media, also called a Standalone Web Conference, and then locks the conference, he will be unable to join the conference if he leaves the conference Workaround: There is no workaround; participants will need to leave the conference so that the session ends; once the conference ends then a new session can be started Using full screen sharing with large resolution displays Issue: If a presenter uses full screen sharing and has a display larger than 1600x1600, then the sharing may fail Workaround: Use portion-of-the-screen sharing and keep the area size below 1600 pixels wide and/or tall Use of CD-RW for platform ISO files Issue: If AAC Platform ISO files are burned onto CD-RW disks the system will not recognize the disk. Workaround: Use either CD-R or DVD media for the AAC Platform ISO files One-X Communicator 6.2 unable to receive SRTP Video after video mute Issue: When an Avaya Aura Conferencing user uses One-X Communicator 6.2 for video, the system is using SRTP Video and the user mutes their video, the user will be unable to receive video after un-muting. Workaround: None at this time One-X Communicator unable to transfer conference to Flare when using Video SRTP Issue: If a user joins a conference using the One-X Communicator and the system has SRTP Video enabled, that user will be unable to transfer the conference to another user that is using Flare. Workaround: There are no workarounds at this time Web collaboration plug-in and 64-bit browsers Issue: The AAC web collaboration plug-in will not work in 64-bit browsers. Workaround: Use the browser in 32-bit mode. Page 18 of 23

19 6.25 Use of lecture mode with One-XC H.323 Issue: If a Flare user on a conference in lecture mode dialsout to another participant who is using the One-XC H.323 client, the One-XC user will not receive video. Workaround: If the One-XC user dials into the conference themselves the video will be seen. Avaya ID: AAC Users using the E129 or B179 device cannot enter the conference if the user is brought into the call using dialout Issue: If a user is using the E129 or B179 device and they are called by the conference to join, the user is not connected. There is no issue if the user directly joins the conference by dialing in themselves. Workaround: Dial the conference directly. Avaya ID: AAC-5963, AAC Playing a music file while using the IOS App will result in Audio being dropped Issue: If a user is connected to a conference with the IOS App and is using the audio capability of the app, the audio will be dropped if the user plays a music file. Workaround: Do not play a music file while on a conference with the IOS App Avaya ID: AAC Galaxy S5 not yet supported Issue: The Samsung Galaxy S5 device is not yet supported for the Android app; while most functionality works, there are some items, such as being unable to recover AAC media after a phone call, which need to be debugged and fixed. Workaround: Use another supported Android device, specifics listed in Section Avaya ID: AAC ios video does not resume if paused by conference moderator Issue: If the conference moderator pauses the video of the ios app, when the moderator resumes video the ios video does not in fact resume Workaround: None Avaya ID: AAC Excel files truncated when shown from collaboration library Issue: If Excel files are uploaded in the collaboration library they are truncated and not fully displayed when shared. Workaround: Use screen sharing for excel files Avaya ID: AAC-6696 Page 19 of 23

20 6.31 Dial out to a user on a B179 device fails Issue: If a dial out is performed to a user who is using a B179 device, the call will fail Workaround: Have the user manually join the conference Avaya ID: AVAYAB No video when joining an IP Office endpoint into a conference via the AAC Outlook Plugin Issue: If an IP Office user joins a conference using the AAC Outlook Plugin, the user will not be able to use video Workaround: Join the conference manually Avaya ID: AAC Mobile App audio only on ipad Mini Issue: Due to a defect the app crashes on ipad mini when using video. To ensure the app is stable video has been disabled for ipad Mini. Workaround: None. This issue will be addressed in a Post GA release of the mobile apps expected end of October Avaya ID: AAC Video disabled for ios Mobile App when used in Event Conference Issue: An issue was seen with the Mobile App crashing if an Event Conference attendee was using the app, had video and was then unmuted by the moderator Workaround: Video is already disabled in the ios app when used in Event Conferences Avaya ID: AAC Mobile App session terminated when taking GSM calls for over a minute Issue: When using the ios version of the Mobile Apps and you take or place a GSM call while in a conference on the app, the app session will be terminated if the GSM call lasts longer than 1 minute. Workaround: Rejoin the conference if this occurs. Avaya ID: AAC-7617 Page 20 of 23

21 6.36 Use of iphone 4 Issue: The iphone 4 s processor has significantly less capacity than newer models and as a result the mobile app runs very slowly on this device. While it can be used, Avaya strongly recommends the use of newer iphones with this app. Workaround: None Avaya ID: AAC Split video when using Logitech QuickCam Pro 9000 Issue: When using the Logitech QuickCam Pro 9000 video camera with the AAC browser based audio/video sometimes the video stream sent from the camera appears to be split with the two halves swapped horizontally. Workaround: Drop from the conference and then rejoin the conference; the issue is sporadic and will not happen every time. There is no impact to Audio Avaya ID: WEBRTCENGINE Video icon incorrect for receive-only video Issue: When a user is using the Collaboration Agent with browser based media and elects to only receive video, the video media icon on his roster blade will show as if he is sending and receiving Workaround: None Avaya ID: AAC Interaction issue with Android Communicator App Issue: If an Android Communicator app user uses a + in their Aura Communication userid, and then launches AAC web collaboration app, the user will fail to login due to the + not being included in the userid sent to the AAC mobile app Workaround: Use a different Communication userid or join as guest Avaya ID: AAC Add Audio/Video dialog presented when hitting Enter in Web Collaboration message window Issue: If a user joins an AAC conference which requires a passcode to join the conference, if the user hits ENTER after typing in the passcode then the user will see the Add Audio/Video option presented everytime he hits ENTER in the AAC Web Collaboration message window. Workaround: Join the conference by clicking on the Join button after entering the passcode. Avaya ID: AAC-7835 Page 21 of 23

22 6.41 Patch application fails periodically Issue: Occasionally the application of an application patch to a network element will fail Workaround: Repeat the patch attempt; if it fails more than 5 times in a row please contact Avaya Avaya ID: AAC AAC Alarms not covered by Avaya monitoring services Issue: The AAC alarms are not able to be monitored by Avaya s monitoring services. This is expected to be resolved in AAC 8.0 Service Pack 2 in Q Workaround: None Page 22 of 23

23 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 hardware-related 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 23 of 23