Avaya Communicator for Windows 2.0 Release Notes

Transcription

1 Avaya Communicator for Windows 2.0 Release Notes Release Notes for Avaya Communicator for Windows Release 2.0 Release Notes Issue 1.7, 03 June Avaya Inc. All rights reserved. Notice While reasonable efforts have been made to ensure that the information in this document is complete and accurate at the time of printing, Avaya assumes no liability for any errors. Avaya reserves the right to make changes and corrections to the information in this document without the obligation to notify any person or organization of such changes. Documentation disclaimer Documentation means information published by Avaya in varying mediums which may include product information, operating instructions and performance specifications that Avaya generally makes available to users of its products. Documentation does not include marketing materials. Avaya shall not be responsible for any modifications, additions, or deletions to the original published version of documentation unless such modifications, additions, or deletions were performed by Avaya. End User agrees to indemnify and hold harmless Avaya, Avaya's agents, servants and employees against all claims, lawsuits, demands and judgments arising out of, or in connection with, subsequent modifications, additions or deletions to this documentation, to the extent made by End User. Link disclaimer Avaya is not responsible for the contents or reliability of any linked websites referenced within this site or documentation provided by Avaya. Avaya is not responsible for the accuracy of any information, statement or content provided on these sites and does not necessarily endorse the products, services, or information described or offered within them. Avaya does not guarantee that these links will work all the time and has no control over the availability of the linked pages. Warranty Avaya provides a limited warranty on its hardware and Software ( Product(s) ). Refer to your sales agreement to establish the terms of the limited warranty. In addition, Avaya s standard warranty language, as well as information regarding support for this Product while under warranty is available to Avaya customers and other parties through the Avaya Support website: Please note that if you acquired the Product(s) from an authorized Avaya reseller outside of the United States and Canada, the warranty is provided to you by said Avaya reseller and not by Avaya. Software means computer programs in object code, provided by Avaya or an Avaya Channel Partner, whether as stand-alone products or preinstalled on hardware products, and any upgrades, updates, bug fixes, or modified versions thereto. Licenses THE SOFTWARE LICENSE TERMS AVAILABLE ON THE AVAYA WEBSITE, ARE APPLICABLE TO ANYONE WHO DOWNLOADS, USES AND/OR INSTALLS AVAYA SOFTWARE, PURCHASED FROM AVAYA INC., ANY AVAYA AFFILIATE, OR ANAUTHORIZED AVAYA RESELLER (AS APPLICABLE) UNDER A COMMERCIAL AGREEMENT WITH AVAYA OR AN AUTHORIZED AVAYA R ESELLER. UNLESS OTHERWISE AGREED TO BY AVAYA IN WRITING, AVAYA DOES NOT EXTEND THIS LICENSE IF THE SOFTWARE WAS OBTAINED FROM ANYONE OTHER THAN AVAYA, AN AVAYA AFFILIATE OR AN AVAYA AUTHORIZED RESELLER; AVAYA RESERVES THE RIGHT TO TAKE LEGAL ACTION AGAINST YOU AND ANYONE ELSE USING OR SELLING THE SOFTWARE WITHOUT A LICENSE. BY INSTALLING, DOWNLOADING OR USING THE SOFTWARE, OR AUTHORIZING OTHERSTO DO SO, YOU, ON BEHALF OF YOURSELF AND THE ENTITY FOR WHOM YOU ARE INSTALLING, DOWNLOADING OR USING THE SOFTWARE (HEREINAFTER REFERRED TO INTERCHANGEABLY AS YOU AND END USER ), AGREE TO THESE TERMS AND CONDITIONS AND CREATE A BINDING CONTRACT BETWEEN YOU AND AVAYA INC. OR THE APPLICABLE AVAYA AFFILIATE ( AVAYA ). Avaya grants you a license within the scope of the license types described below, with the exception of Heritage Nortel Software, for which the scope of the license is detailed below. Where the order documentation does not expressly identify a license type, the applicable license will be a Designated System License. The applicable number of licenses and units of capacity for which the license is granted will be one (1), unless a different number of licenses or units of capacity is specified in the documentation or other materials available to you. Designated Processor means a single stand-alone computing device. Server means a Designated Processor that hosts a software application to be accessed by multiple users. License type(s) CPU License (CP). End User may install and use each copy of the Software on a number of Servers up to the number indicated in the order provided that the performance capacity of the Server(s) does not exceed the performance capacity specified for the Software. End User may not re-install or operate the Software on Server(s) with a larger performance capacity without Avaya s prior consent and payment of an upgrade fee. Named User License (NU). You may: (i) install and use the Software on a single Designated Processor or Server per

2 authorized Named User (defined below); or (ii) install and use the Software on a Server so long as only authorized Named Users access and use the Software. Named User, means a user or device that has been expressly authorized by Avaya to access and use the Software. At Avaya s sole discretion, a Named User may be, without limitation, designated by name, corporate function (e.g., webmaster or helpdesk), an or voice mail account in the name of a person or corporate function, or a directory entry in the administrative database utilized by the Software that permits one user to interface with the Software. Heritage Nortel Software Heritage Nortel Software means the software that was acquired by Avaya as part of its purchase of the Nortel Enterprise Solutions Business in December The Heritage Nortel Software currently available for license from Avaya is the software contained within the list of Heritage Nortel Products located at under the link Heritage Nortel Products. For Heritage Nortel Software, Avaya grants Customer a license to use Heritage Nortel Software provided hereunder solely to the extent of the authorized activation or authorized usage level, solely for the purpose specified in the Documentation, and solely as embedded in, for execution on, or (in the event the applicable Documentation permits installation on non-avaya equipment) for communication with Avaya equipment. Charges for Heritage Nortel Software may be based on extent of activation or use authorized as specified in an order or invoice. Copyright Except where expressly stated otherwise, no use should be made of materials on this site, the Documentation, Software, or hardware provided by Avaya. All content on this site, the documentation and the Product provided by Avaya including the selection, arrangement and design of the content is owned either by Avaya or its licensors and is protected by copyright and other intellectual property laws including the sui generis rights relating to the protection of databases. You may not modify, copy, reproduce, republish, upload, post, transmit or distribute in any way any content, in whole or in part, including any code and software unless expressly authorized by Avaya. Unauthorized reproduction, transmission, dissemination, storage, and or use without the express written consent of Avaya can be a criminal, as well as a civil offense under the applicable law. Third-party components Third Party Components mean certain software programs or portions thereof included in the Software that may contain software (including open source software) distributed under third party agreements ( Third Party Components ), which contain terms regarding the rights to use certain portions of the Software ( Third Party Terms ). Information regarding distributed Linux OS source code (for those Products that have distributed Linux OS source code) and identifying the copyright holders of the Third Party Components and the Third Party Terms that apply is available in the Documentation or on Avaya s website at: You agree to the Third Party Terms for any such Third Party Components. Preventing Toll Fraud Toll Fraud is the unauthorized use of your telecommunications system by an unauthorized party (for example, a person who is not a corporate employee, agent, subcontractor, or is not working on your company's behalf). Be aware that there can be a risk of Toll Fraud associated with your system and that, if Toll Fraud occurs, it can result in substantial additional charges for your telecommunications services. Avaya Toll Fraud intervention If you suspect that you are being victimized by Toll Fraud and you need technical assistance or support, call Technical Service Center Toll Fraud Intervention Hotline at for the United States and Canada. For additional support telephone numbers, see the Avaya Support website: Suspected security vulnerabilities with Avaya products should be reported to Avaya by sending mail to: securityalerts@avaya.com. Trademarks The trademarks, logos and service marks ( Marks ) displayed in this site, the Documentation and Product(s) provided by Avaya are the registered or unregistered Marks of Avaya, its affiliates, or other third parties. Users are not permitted to use such Marks without prior written consent from Avaya or such third party which may own the Mark. Nothing contained in this site, the Documentation and Product(s) should be construed as granting, by implication, estoppel, or otherwise, any license or right in and to the Marks without the express written permission of Avaya or the applicable third party. Avaya is a registered trademark of Avaya Inc. All non-avaya trademarks are the property of their respective owners, and Linux is a registered trademark of Linus Torvalds. Downloading documents For the most current versions of documentation, see the Avaya Support website: Contact Avaya Support See the Avaya Support website: for product notices and articles, or to report a problem with your Avaya product. For a list of support telephone numbers and contact addresses, go to the Avaya Support website: scroll to the bottom of the page, and select Contact Avaya Support.

3 Avaya Communicator for Windows 2.0 Release Notes Table of Contents About Avaya Communicator for Windows... 1 What s new... 1 Available with this release... 1 Inherited from previous release (Flare Experience 1.1)... 2 Removed from this release... 3 Not supported in this release... 3 Obtaining Avaya Communicator for Windows release 2.0 Software... 3 For Installing Avaya Communicator Release 2.0 follow steps below... 3 For Upgrading Avaya Flare Experience to Avaya Communicator Release 2.0 follow steps below... 4 Avaya Communicator for Windows 2.0 CA certificate installation... 4 Interoperability and requirements... 4 Software and firmware compatibility matrix... 4 Client Work Station recommendation... 6 Known issues and workarounds... 6 Caveats... 6 Interoperability Issues... 6 Avaya Aura Conferencing... 7 Scopia... 7 Avaya one-x Communicator... 8 Avaya Communicator for Android... 8 One-X Mobile UC with CES... 8 Polycom... 9 Known Issue s... 9 Appendix A Finding documents on the Avaya Support site Appendix B Collaboration Services Support for Google Applications Support for Office

4

5 Avaya Communicator for Windows 2.0 Release Notes About Avaya Communicator for Windows Avaya Communicator for Windows enables you to log into your company's server and make and receive voice and video calls from your telephone extension via your PC. Using the Avaya Communicator for Windows client, you can also send instant messages, access your call history, access your Avaya Aura contacts and Microsoft Outlook contacts, share information with web collaboration, perform an enterprise search, and manage your presence status. Avaya Communicator for Windows provides enterprise users with simple access to all the communication tools in a single interface. What s new Available with this release Message Waiting Indicator integration allows users to call voice mail clicking on MWI button. Desktop Integration (Collaboration Services) Click to Call from Microsoft Office suite (including Outlook) and from an Internet Explorer or Google Chrome browser. Enhancements to server certificate validation(required) Avaya Communicator validates the server identity certificate during the TLS connection establishment process. If the application cannot establish a TLS connection because of an inability of the personal computer to validate the certificate, the application displays an error message. Web Collaboration - Launch Collaboration from the pop-up notification informing you that Collaboration has started. Scopia 8.3 Integration [support limited to TCP link between Aura and iview] Scopia MCU Conferencing support [Support limited to direct dialing. No VIVR support] Auto configuration via URL (User configuration settings provisioning) A URL is populated in the user's registry file that points to the location of the user's settings file for auto-configuration. If there is no URL, the client will launch as normal without using the URL. If there is an error in loading the parameters, the client launches as before with no user settings populated. Selecting call from alternate numbers To do this, right-click on user s contact card in the call setup area. Main window resize As part of this release Avaya Communicator for Windows main windows is resizable. Volume Control Call stats Call stats will be available from the call appearance menu in the redesigned UI. Keyboard shortcuts Contact Fan Navigation Jump to typed letter. Page up/down. Error handling for unsupported features Feature to ensure that dialogs are provided for any error conditions Contact Fan Robustness Dual Registration (H.323 and SIP) Use Avaya Communicator as a SIP client in conjunction with your H.323 desk phone or soft-client. Note: This is not shared control. Basic Multiple Device Access Allows users to login on up to 10 SIP endpoints (Configurable from System Manager). New User Interface - Compact UI replaces immersive spotlight UI Multi-stream Continuous Presence video with grid layout - Up to 4 streams Secure Media (SRTP) for Video Secure audio and video for point-to-point calls and conferences. This includes support for remote workers via Avaya SBCE Avaya Proprietary Use pursuant to Company Instructions Page 1

6 Consultative Call Transfer - Transfer a call from one party to another. Only voice call transfer is currently supported. Contact Filtering by Source Easily switch views between all contacts, local Outlook contacts and Communicator contacts Windows 8 & 8.1 Support (Desktop Mode with mouse/keyboard) Multi-party Messaging Language Selection in Settings Inherited from previous release (Flare Experience 1.1) Below mentioned features from previous releases are also included in Avaya Communicator for Windows 2.0: Configuration Service configuration Dialing rules Contact preference Login/logout Contact fan Local Outlook contacts Aura contacts Aggregated Contact Remove/Delete Contacts Index, scrolling Live contact filtering Make call/drag and drop Make call (Audio or Video) from contact card: primary/select a number Make call (Audio or Video) by dragging and dropping a contact onto the conversation 'setup' area Receive call (Audio or Video) Dial pad Make call (Audio or Video) from History and IM card Mid call control Mute/Unmute Pause/Unpause Hold/Resume DTMF Escalate / De-escalate from a point to point audio call to a point to point video call Multiple Call sessions Allows up to 3 concurrent call sessions Local call history Basic Call History Filtering based on Call types (Incoming, Outgoing, Missed, and All) IM and Presence LDAP Search Conference (Audio + Video) Adhoc Conference / Call Merging Meet-me Conference Moderator controls Active talker Escalate / De-escalate a conferencing session from voice to video Mid call controls in audio/video conference Collaboration Document sharing Screen sharing for the entire screen and a portion of the screen) Application sharing Whiteboard sharing Share previous document Delegate Moderator starting collaboration. Escalate point to point video call to a conference via Collaboration button

7 Avaya Communicator for Windows 2.0 Release Notes Combined container for Collaboration and Video Conferencing Point-to-Point Audio and Audio conference calls on SRTP Removed from this release contacts within the application is no longer supported. Interoperability with ADVD. Not supported in this release Point-to-Point Video on Bridged Line Appearance (Primary line support only) Video conferencing on Bridged Line Appearance (Primary line support only) Video on Aura Communication Manager based conference Point-to-Point Video and Video conferencing scenarios when a call is answered on EC500 number and then Avaya Communicator for Windows bridges into the call Transferring Video calls/conferences Blind Call Transfer Windows Metro mode, Touch screen. Avaya Communicator for Windows on Windows 8 Tablet Automatic Session Manager Failover is not supported in Avaya Communicator for Windows Release 2.0. Obtaining Avaya Communicator for Windows release 2.0 Software Users can find Avaya Communicator for Windows 2.0 files from PLDS ID : FE File Name : communicatorwin dist.zip Follow below steps: 1. After login to PLDS site click on downloads. 2. To search for downloads, you must first select a company. Either type the company name in the field shown on web page or use the find icon to search for and select the company. 3. After selecting the company, click Apply Company. 4. Enter PLDS ID under Download Pub ID field and click on search downloads. 5. Now click on download link to download the Avaya Communicator for windows 2.0 software. For Installing Avaya Communicator Release 2.0 follow steps below For information about installation, see "Installing the application" in document Using Avaya Communicator for Windows. Please refer Appendix A on how to find document on the Avaya support site. Note: Collaboration services require its installation separately. If you intend to login into Avaya Communicator for Windows using Avaya Session Border Controller, configure the Avaya Session Border Controller address or domain name for the Phone Server Address, Directory Server Address, and Presence Server Address in the Avaya Communicator Settings. The same domain names can be used for these settings when Avaya Communicator is inside the enterprise network and outside of the enterprise through Session Border Controllers, if the DNS servers can resolve the correct IP addresses from the same domain name in these two networks. Avaya Proprietary Use pursuant to Company Instructions Page 3

8 For Upgrading Avaya Flare Experience to Avaya Communicator Release 2.0 follow steps below For information about upgrade, see Upgrading Avaya Communicator for Windows in document Using Avaya Communicator for Windows. Please refer Appendix A on how to find document on the Avaya support site. Note: 1. User should also make sure that latest drivers are installed for the connected hardware / graphics and run Microsoft Update on windows machine to update all of windows components. 2. It is recommended to upgrade Java Runtime Engine on the machine to latest version. Avaya Communicator for Windows 2.0 CA certificate installation For information about certificate installation, see Certificate distribution and management in document Administering Avaya Communicator. Please refer Appendix A on how to find document on the Avaya support site. Note: If you are using 3rd party certificates, you need to install the root certificate of the CA issuing certificates for servers (SM, PS) on user s machine. Contact your lab administrator to get the certificate file as applicable. Interoperability and requirements Software and firmware compatibility matrix The following table shows the supported systems by Avaya Communicator for Windows 2.0. Avaya Components Avaya Aura System Manager 6.2 Avaya Aura Session Manager 6.2 Avaya Aura Communication Manager Avaya Aura Presence Services 6.2 Avaya Aura Messaging 6.3 Avaya Aura Conferencing 7.2 Avaya Session Border Controller Supported release FP FP FP FP4 6.2 SP FP FP FP FP Avaya one-x Client Enablement Services 6.2 Meeting Exchange 6.2 Modular Messaging (Legacy support only) 6.2 FP1 6.2 FP2 Collaboration Services 6.3.3

9 Avaya Communicator for Windows 2.0 Release Notes Note: Call transfer requires Aura 6.2 FP2 or greater. Video calling/conferencing requires Aura 6.2 FP2 or greater. Secure video requires Aura 6.2 FP3 or greater. Secure Video Conferencing requires AAC or greater. The following table shows the supported interoperable endpoints by Avaya Communicator for Windows 2.0. Avaya Components Avaya Client Applications 96x1 SIP Avaya Communicator Android 2.0 Avaya Communicator for Ipad Avaya one-x Communicator Supported Release 6.3 SP1 6.3 SP1 1.2 SP1 6.2 SP1 Avaya one-x Mobile SIP for ios B100 Series Conference Phones - B One-X Mobile UC with CES The following table shows the supported non-avaya devices by Avaya Communicator for Windows rd Party Components Software / Hardware Supported Release / Model LDAP Microsoft Active Directory Windows Server 2008 R2 Administration Browser {Collaboration Services Support} IBM Domino Novell Windows SP8 Microsoft Internet Explorer 8.0, 9.0, 10 Google Chrome 24+ Microsoft windows Windows 7 (x64, x86) Professional, Enterprise, Ultimate Editions Windows 8 (x64, x86) Windows 8.1 (x64) Microsoft Lync Lync 2010, 2013 Microsoft applications {Collaboration Services Support} Other Applications {Collaboration Services Support} Microsoft applications {Local contacts for windows} Professional, Enterprise Professional, Enterprise Office 2007, 2010, 2013 Outlook 2007, 2010, 2013 Other Applications Office 365 Other Applications Outlook 2007, 2010, 2013 Polycom HDX 7K Series RMX Radvision Scopia Solution 8.3 Google Apps & enterprise Applications Avaya Proprietary Use pursuant to Company Instructions Page 5

10 Client Work Station recommendation Known issues and workarounds Caveats Key Summary Workaround / Notes NGUE NGUE SCAE-5458 FW-3214 Interoperability Issues Windows Flare Experience installer does not indicate user if it is upgrading from previous release or doing fresh install [defsw131236] Flare (SRTP disabled) has no video when dial into AAC conference with CM SRTP enforced, AAC SRTP best effort RV MCU 5110 AC Win does not have video after joining into SCOPIA meeting if SRTP is set to enforce on CM Executive AC Win is unable to hold call second time (Hold/resume than again try to Hold call) after bridging in the call which is initiated by the assistant on the executive s behalf. Avaya communicator for windows is not supported in TCP mode. Register client in TLS mode. The SRTP capneg not part of Elite 5000 solution 8.3, and therefore some SRTP flows will not work by design with Aura. Customer upgrading solution to 8.3 to deploy SRTP with Aura, are recommended to use Elite 6000 (v 8.3 and above). The scenario involves joining a CM Conference type of session into AAC session. When user A joined into the meetme, user A and user B are represented as a CM conference joining AAC meetme. Such call scenario is currently not supported.

11 Avaya Communicator for Windows 2.0 Release Notes 202 Avaya Aura Conferencing Key Summary Workaround / Notes SCAE-4606 If moderator is in a non-english language then AAC announcements do not play language specific to Moderator. SCAE-4559 AAC: Cannot merge B5800 user with G722 audio codec to conference FW- 2122/FW AAC Presentation mode support is not available with Avaya Communication for windows 2.0 release. In Panel mode active, Avaya Communicator for windows participant cannot start Web Collab SCAE-3665 AAC Conference calls are not logged in call history. Targeted for next release FW-3267 ACW Roster list (Meet-Me) - Dropped participant is not updated correctly, If some of the participant drops from Audio/Video (Not from Web). If Moderator mute dropped participant from ACW Roster list then conference ends, moderator will not able to make any actions on Roster list for next conferences. Workaround (instead of exiting Compact) is to Mute (or Unmute) All from the Call Appearance Moderator Controls 203 Scopia Key Summary Workaround / Notes SCAE-5652 FW-3286 FW-2244 SCAE-5333 FW-3285 FW-2377 SCAE-5399 NGUE SCAE-5654 Intermittent issue where rejoin of ACW do not show video of other participants. Although video statistics shows video is received from other participants. Can't escalate to video if you dial into Scopia virtual room with audio first. After leaving MCU 5110 Conf & rejoins the Conf ACW show no video on video window. ACW making audio call to Scopia endpoint behind iview can t escalate to video. Lost audio when ACW does hold/unhold after joining Scopia virtual room. [Tracking JIRA RV QC: 27016] You cannot currently access moderator controls or share content when dialed in to a Radvision Scopia conference from Avaya Communicator for Windows. 1XC, ACWin, ACiPad joining Elite MCU via IVR do not receive presentation from XT. Avaya soft clients do receive presentations from XT endpoints if all are part of a direct dial-in conference on Elite MCU. However, if participants have dialed in via IVR, they don't see the presentation. Video loops on XT5000 after Win Flare make P2P call to RADVISION endpoint which has dialed to virtual room and established MCU trunk to AAC conference When a Scopia desktop user shares any application in non-maximized window, ACW client displays duplicated sharing content. The issue Rejoin the conference. Dial into the same virtual room with video call, then everything would work fine. You can also de-escalate video and then escalate video again. Not available. Start the a video call instead of audio and then escalation. Login client as TCP. You can access some limited controls Using DTMF digits on the dial pad, but the use of lecture functionality can result in disabling video for some users so its use is not recommended. Use dial-in conference on Elite MCU for presenting. Share entire desktop or a specific application in Avaya Proprietary Use pursuant to Company Instructions Page 7

12 204 happens only when launching Scopia desktop sharing on PCs which have screen ratio other than 16:9 (1280x720 resolution). maximize window. 205 Avaya one-x Communicator Key Summary Workaround / Notes 206 ONEXC-5763 ONEXC-6030 ONEXC-6062 ONEXC-6112 ONEXC-6193 ONEXC-6349 SCAE-5526 NGUE SCAE-5752 [Interop:Flare-1XC] Freeze moderator video stream displayed at 1XC endpoint, when moderator (flare user) de-escalates video conference call to audio call 1XC-Participant name doesn t display on the integrated video window, when user unhold call from 1XC after converting P2P video call to conference via Collaboration button P2P audio call from Avaya Flare Experience for Windows to video capable 1XC H.323 endpoint not escalated to video Flare 1.1: 1XC is using only H.263 codec. P2P video call active between Flare and 1XC. Hold/Unhold and Pause/Un-Pause from 1XC causes Pixelization (slow update) on Flare side In P2P audio call from ipad/windows Flare to 1XC SIP, audio call escalate to video automatically if hold and unhold the call from 1XC SIP endpoint When Win-Flare user promotes P2P video call to conference via collaboration or dragging contact from Flare, video call is de-escalated to audio from 1XC participant When Flare Win and 1XC are on a video call, 1XC stops his video. After that Flare Win also de-escalate his video and the call drops immediately after that. Multiple contact cards displays in carousel & roster of conference, when 1XC/96XX participant transfer its conference call to any other participant Video call is not established after 1XC (TLS/RTP) transfers a video call from AC ipad (TLS/SRTP-CAPNEG) to AC Win (TLS/SRTP- CAPNEG) SCAE-5825 If ACW escalate call from audio to video, remote end party's (1XC 6.2 H.323) video appears as black screen on ACW video window. Fix is planned with later service pack/release of Avaya Communication Manager. 1) Workaround is hold/un-hold call on AC Windows. 2) Configure 1XC with TLS/SRTP- CAPNEG (MediaEncryptionP arameters=1,2,9) 3) 1XC user performs consultative transfer to AC Win. 207 Avaya Communicator for Android Key Summary Workaround / Notes SCAE-5419 Call gets drop on both Avaya Communicator for Android and ACW application after making a consultative transfer at ACW application. This issue is resolved with CM 6.3 patch FW-3029 When Android participant starts audio in the conference, his audio status is not updated in the Flare roster. 210 One-X Mobile UC with CES Key Summary Workaround / Notes SCAE-4354 Call logs are not updated on Win Flare when perform callback from

13 Avaya Communicator for Windows 2.0 Release Notes 1XM by Mobile Polycom Key Summary Workaround / Notes ONEXC-8689 Known Issue s FW-2183 Avaya Communicator for Windows - delayed image + poor resume after hold with RMX. Key Summary Workaround / Notes SCAE-3508 FW-2106 Client uses old time zone to generate new call logs after changing to system(desktop) time zone ACW does not return to normal video resolution when network congestion was removed. The settings should be survive an upgrade, however the Language, Firstname\Lastname, and Auto\Single values are not migrated. User can logout and login back to reflect changed time zone. Re-initiate the call once network congestion is gone from the network. Change the values manually after migration. SCAE-4424 WEBRTCEN GINE-2706 SCAE-451 SCAE-5441 SCAE-5513 FW-2844 FW-2891 SCAE-5395 SCAE-5426 SCAE-5452 SCAE-5544 Win Flare shows Grey Video Setting Window after resuming from Sleep mode. Sometimes ACW gets crashed when user is on active video call then report problem on settings menu. Flare shall ensure each negotiated video stream can meet the minimum bitrate requirement. Call dropped from AAC Conf when tried to switch from CP auto to single stream on my ACW after the CPU detection auto dropped a stream. Camera still acquired (Light ON) when video conference put on hold to make audio only P2P call. This is misleading as the user is not broadcasting video. The instant messaging card displays the last message sent or received during the instant messaging session. After you log out and log back in, Avaya Communicator for Windows does not preserve the entire conversation in the IM history. When Avaya Communicator for windows send Instant Messages to any client who has presence status set to Do Not disturb it shows message as Failed to send. Although messages are sent successfully and offline messages can be read by far end once user is available. Dropped packets shown on Video Stats is inaccurate for video conferences. In AAC conference, primary ACW is bridged out unexpectedly if secondary station bridges in call (after primary user joins into conference). This issue is also seen with EC-500. EC-500 answers the call, user switches to ACW Primary and the call is ended Sometimes presence status is not updated when user switch from WI- FI to LAN cable. Voice path is disconnected between 1XC H323 and ACW after deescalating to audio call from 1XC H323 user. Close video settings window and open it again. Either try again or drop the active call before reporting logs from settings menu. De-escalate video manually. User A to rejoin, without moderator controls. User to logout and login again. Fix is planned with later service pack/release of Avaya Communication Manager. Avaya Proprietary Use pursuant to Company Instructions Page 9

14 FW-3326 FW-3330 While creating a adhoc conf, it displays dropped in the conference roster at the moderator side though participant has not pick up the call. Rather message should be similar to... Calling Work for both the participants in the roster fan. After transfer one user to another user, Open Collaboration button is disabled on call line appearance.. Open Collaboration from Transferred party. SCAE-5653 ACW: Outlook Object Guard Dialog is blocking PPM request. 1. If you allow ACW to access your contacts (i.e. acknowledge the dialog), everything works fine. SCAE-5841 FW-2896 SCAE-5550 FW-3292 SCAE-5773 SCAE-5836 Appendix A Bridge call: Executive hold call is drop after bridging the call and bridging out (Drops call) by assistant on the executive s behalf. Presence feature does not work if Presence server address is set as FQDN instead of IP address. Aura Contacts are not loaded on Contacts Fan when user deleted aura contact on ACW then logout and login again. If the recipient of the Instant Message does not have the Instant Message originator as a contact, escalation to voice call fails. The call gets dropped immediately on ACW after receiving a consultative transfer from SIP desk phone where Avaya Communicator for windows set to SRTP and SIP desk phone is RTP only. 100% CPU usage during video call. This issue is specific to Dell Latitude E6430 which has x64-bit Windows 7 SP1, i5 quad core 2.6Ghz CPU, 4 GB RAM. Finding documents on the Avaya Support site 1. Navigate to the Avaya Support web site at 2. Click the Downloads & Documents tab, and select Documents. 3. In the Product search box, enter the product name. 4. Select the appropriate release number from the Choose Release drop-down menu. 2. Get your anti-virus definitions updated. (In case of Enterprise this is automatically done.). Set the Presence server IP address in place of FQDN. User should log out then log in again. It takes 2 times log in and log out to make that updated for the user. Add user to communicator contact s before escalating to voice call Or place a call directly rather escalating from IM windows. Do the blind transfer. 5. If necessary, use the Content Type filter on the left to select the type of document you are looking for. For example, if you are looking for user guides, you can select User Guides from the Content Type filter. Only documents in the selected category will appear in the list of documents. Appendix B Collaboration Services Support for Google Applications You can use Collaboration Services click to call and click to join or host a conference functionality within Google Applications, such as Gmail, Calendar, Sheets, Documents, and Forms.

15 Avaya Communicator for Windows 2.0 Release Notes The following image provides an overview of Collaboration Services support with Google Applications Where number marking is nothing but highlight of the phone number. Support for Office 365 You can use Collaboration Services click to call and click to join or host a conference functionality from Office 365 with the web versions of Microsoft Word, Excel, Outlook, Calendar, SharePoint, and One Note. The following image provides an overview of Collaboration Services support with Office 365 web applications. Avaya Proprietary Use pursuant to Company Instructions Page 11

16 Where number marking is nothing but highlight of the phone number.