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 2014 © 2014 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: http://www.avaya.com/support 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 pre- installed on hardware products, and any upgrades, updates, bug fixes, or modified versions thereto. Licenses THE SOFTWARE LICENSE TERMS AVAILABLE ON THE AVAYA WEBSITE, http://support.avaya.com/Licenseinfo 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 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 e-mail 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 2009. The Heritage Nortel Software currently available for license from Avaya is the software contained within the list of Heritage Nortel Products located at http://support.avaya.com/LicenseInfo/ 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: http://support.avaya.com/ThirdPartyLicense/. 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 +1-800-643-2353 for the United States and Canada. For additional support telephone numbers, see the Avaya Support website: http://www.avaya.com/support. Suspected security vulnerabilities with Avaya products should be reported to Avaya by sending mail to: [email protected]. 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: http://www.avaya.com/support Contact Avaya Support See the Avaya Support website: http://support.avaya.com 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: http://support.avaya.com, scroll to the bottom of the page, and select Contact Avaya Support. 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 ...... 10 Finding documents on the Avaya Support site ...... 10
Appendix B ...... 10 Collaboration Services ...... 10
Support for Google Applications ...... 10
Support for Office 365 ...... 11
Avaya Communicator for Windows 2.0 Release Notes
1 About Avaya Communicator for Windows 2 “Avaya Communicator for Windows enables you to log into your company's server and make and receive voice and 3 video calls from your telephone extension via your PC. Using the Avaya Communicator for Windows client, you can 4 also send instant messages, access your call history, access your Avaya Aura® contacts and Microsoft Outlook 5 contacts, share information with web collaboration, perform an enterprise search, and manage your presence status. 6 Avaya Communicator for Windows provides enterprise users with simple access to all the communication tools in a 7 single interface.”
8 What’s new
9 Available with this release 10 Message Waiting Indicator integration allows users to call voice mail clicking on MWI button. 11 Desktop Integration (Collaboration Services) – Click to Call from Microsoft Office suite (including Outlook) 12 and from an Internet Explorer or Google Chrome browser. 13 Enhancements to server certificate validation(Required) 14 Avaya Communicator validates the server identity certificate during the TLS connection 15 establishment process. If the application cannot establish a TLS connection because of an inability of 16 the personal computer to validate the certificate, the application displays an error message. 17 Web Collaboration - Launch Collaboration from the pop-up notification informing you that Collaboration has 18 started. 19 Scopia 8.3 Integration [support limited to TCP link between Aura and iView] 20 Scopia MCU Conferencing support [Support limited to direct dialing. No VIVR support] 21 Auto configuration via URL (User configuration settings provisioning) 22 A URL is populated in the user's registry file that points to the location of the user's settings file for 23 auto-configuration. If there is no URL, the client will launch as normal without using the URL. If there 24 is an error in loading the parameters, the client launches as before with no user settings populated. 25 Selecting call from alternate numbers 26 To do this, right-click on user’s contact card in the call setup area. 27 Main window resize 28 As part of this release Avaya Communicator for Windows main windows is resizable. 29 Volume Control 30 Call stats 31 Call stats will be available from the call appearance menu in the redesigned UI. 32 Keyboard shortcuts 33 Contact Fan Navigation 34 Jump to typed letter. 35 Page up/down. 36 Error handling for unsupported features 37 Feature to ensure that dialogs are provided for any error conditions 38 Contact Fan Robustness 39 Dual Registration (H.323 and SIP) 40 – Use Avaya Communicator as a SIP client in conjunction with your H.323 desk phone or soft-client. 41 Note: This is not shared control. 42 Basic Multiple Device Access 43 – Allows users to login on up to 10 SIP endpoints (Configurable from System Manager). 44 New User Interface - Compact UI replaces immersive “spotlight” UI 45 Multi-stream Continuous Presence video with grid layout - Up to 4 streams 46 Secure Media (SRTP) for Video 47 – Secure audio and video for point-to-point calls and conferences. This includes support for remote 48 workers via Avaya SBCE
Avaya Proprietary – Use pursuant to Company Instructions Page 1
49 Consultative Call Transfer - Transfer a call from one party to another. Only voice call transfer is currently 50 supported. 51 Contact Filtering by Source 52 – Easily switch views between “all contacts”, “local Outlook contacts” and “Communicator contacts” 53 Windows 8 & 8.1 Support (Desktop Mode with mouse/keyboard) 54 Multi-party Messaging 55 Language Selection in Settings
56 Inherited from previous release (Flare Experience 1.1) 57 58 Below mentioned features from previous releases are also included in Avaya Communicator for Windows 2.0: 59 Configuration 60 – Service configuration 61 – Dialing rules 62 – Contact preference 63 Login/logout 64 Contact fan 65 – Local Outlook contacts 66 – Aura contacts 67 – Aggregated Contact 68 – Remove/Delete Contacts 69 – Index, scrolling 70 – Live contact filtering 71 Make call/drag and drop 72 – Make call (Audio or Video) from contact card: primary/select a number 73 – Make call (Audio or Video) by dragging and dropping a contact onto the conversation 'setup' area 74 – Receive call (Audio or Video) 75 – Dial pad 76 – Make call (Audio or Video) from History and IM card 77 Mid call control 78 – Mute/Unmute 79 – Pause/Unpause 80 – Hold/Resume 81 – DTMF 82 Escalate / De-escalate from a point to point audio call to a point to point video call 83 Multiple Call sessions 84 – Allows up to 3 concurrent call sessions 85 Local call history 86 Basic Call History Filtering based on Call types (Incoming, Outgoing, Missed, and All) 87 IM and Presence 88 LDAP Search 89 Conference (Audio + Video) 90 – Adhoc Conference / Call Merging 91 – Meet-me Conference 92 – Moderator controls 93 – Active talker 94 – Escalate / De-escalate a conferencing session from voice to video 95 – Mid call controls in audio/video conference 96 Collaboration 97 – Document sharing 98 – Screen sharing for the entire screen and a portion of the screen) 99 – Application sharing 100 – Whiteboard sharing 101 – Share previous document 102 – Delegate Moderator starting collaboration. 103 – Escalate point to point video call to a conference via Collaboration button
Avaya Communicator for Windows 2.0 Release Notes
104 Combined container for Collaboration and Video Conferencing 105 Point-to-Point Audio and Audio conference calls on SRTP 106
107 Removed from this release 108 Email contacts within the application is no longer supported. 109 Interoperability with ADVD.
110 Not supported in this release 111 Point-to-Point Video on Bridged Line Appearance (Primary line support only) 112 Video conferencing on Bridged Line Appearance (Primary line support only) 113 Video on Aura Communication Manager based conference 114 Point-to-Point Video and Video conferencing scenarios when a call is answered on EC500 number and then 115 Avaya Communicator for Windows bridges into the call 116 Transferring Video calls/Conferences 117 Blind Call Transfer 118 Windows 8.1 - Metro mode, Touch screen. 119 Avaya Communicator for Windows on Windows 8 Tablet 120 Automatic Session Manager Failover is not supported in Avaya Communicator for Windows Release 2.0. 121
122 Obtaining Avaya Communicator for Windows release 2.0 Software 123 124 Users can find Avaya Communicator for Windows 2.0 files from https://plds.avaya.com 125 126 PLDS ID : FE000000010 127 File Name : “communicatorwin-2.0.0.19-dist.zip” 128 129 Follow below steps: 130 1. After login to PLDS site click on downloads. 131 2. To search for downloads, you must first select a company. Either type the company name in the field 132 shown on web page or use the find icon to search for and select the company. 133 3. After selecting the company, click Apply Company. 134 4. Enter PLDS ID under “Download Pub ID” field and click on “search downloads”. 135 5. Now click on download link to download the “Avaya Communicator for windows 2.0” software. 136
137 For Installing Avaya Communicator Release 2.0 follow steps below 138 For information about installation, see "Installing the application" in document “Using Avaya Communicator for 139 Windows”. 140 Please refer “Appendix A” on how to find document on the Avaya support site. 141 142 Note: 143 “Collaboration services” require its installation separately. 144 If you intend to login into Avaya Communicator for Windows using Avaya Session Border Controller, configure 145 the Avaya Session Border Controller address or domain name for the Phone Server Address, Directory 146 Server Address, and Presence Server Address in the Avaya Communicator Settings. The same domain 147 names can be used for these settings when Avaya Communicator is inside the enterprise network and outside 148 of the enterprise through Session Border Controllers, if the DNS servers can resolve the correct IP addresses 149 from the same domain name in these two networks. 150
Avaya Proprietary – Use pursuant to Company Instructions Page 3
151
152 For Upgrading Avaya Flare® Experience to Avaya Communicator Release 2.0 follow steps below 153 For information about upgrade, see “Upgrading Avaya Communicator for Windows” in document “Using Avaya 154 Communicator for Windows”. 155 156 Please refer “Appendix A” on how to find document on the Avaya support site. 157 158 Note: 159 1. User should also make sure that latest drivers are installed for the connected hardware / graphics and run 160 Microsoft Update on windows machine to update all of windows components. 161 2. It is recommended to upgrade Java Runtime Engine on the machine to latest version. 162
163 Avaya Communicator for Windows 2.0 CA certificate installation 164 For information about certificate installation, see “Certificate distribution and management” in document “Administering 165 Avaya Communicator”. 166 167 Please refer “Appendix A” on how to find document on the Avaya support site. 168 169 Note: If you are using 3rd party certificates, you need to install the root certificate of the CA issuing certificates for 170 servers (SM, PS) on user’s machine. Contact your lab administrator to get the certificate file as applicable. 171
172 Interoperability and requirements
173 Software and firmware compatibility matrix 174 The following table shows the supported systems by Avaya Communicator for Windows 2.0. 175 Avaya Components Supported release Avaya Aura System Manager 6.2 6.3.4 FP3 6.3.8 FP4 Avaya Aura Session Manager 6.2 6.3.4 FP3 6.3.8 FP4 Avaya Aura Communication Manager 6.2 SP8 6.3.2 FP3 6.3.6 FP4 Avaya Aura Presence Services 6.2 6.2.2 FP3 6.2.4 FP4 Avaya Aura Messaging 6.3 Avaya Aura Conferencing 7.2 7.2.2 8.0 (Legacy support only) Avaya Session Border Controller 6.2 FP1 6.2 FP2 Avaya one-X® Client Enablement Services 6.2 Meeting Exchange 6.2 Modular Messaging 5.2 Collaboration Services 6.3.3 176
Avaya Communicator for Windows 2.0 Release Notes
177 178 Note: 179 Call transfer requires Aura 6.2 FP2 or greater. 180 Video calling/conferencing requires Aura 6.2 FP2 or greater. 181 Secure video requires Aura 6.2 FP3 or greater. 182 Secure Video Conferencing requires AAC 7.2.2 or greater. 183 184 The following table shows the supported interoperable endpoints by Avaya Communicator for Windows 2.0. 185 Avaya Components Supported Release Avaya Client Applications 6.3 SP1 96x1 SIP 6.3 SP1 Avaya Communicator Android 2.0 Avaya Communicator for Ipad 1.2 SP1 Avaya one-X® Communicator 6.2 SP1 Avaya one-X® Mobile SIP for iOS 6.2.3 B100 Series Conference Phones - B179 2.3 One-X Mobile UC with CES 6.2.1 186 187 The following table shows the supported non-Avaya devices by Avaya Communicator for Windows 2.0. 188 189 190 3rd Party Components Software / Hardware Supported Release / Model LDAP Microsoft Active Directory Windows Server 2008 R2 Windows 2012 IBM Domino 8.5.3 Novell 8.8 SP8 Administration Browser Microsoft Internet Explorer 8.0, 9.0, 10 {Collaboration Services Google Chrome 24+ Support} Microsoft windows Windows 7 (x64, x86) Professional, Enterprise, Ultimate Editions Windows 8 (x64, x86) Professional, Enterprise Windows 8.1 (x64) Professional, Enterprise Microsoft Lync Lync 2010, 2013 Microsoft applications Office 2007, 2010, 2013 {Collaboration Services Outlook 2007, 2010, 2013 Support} Other Applications Office 365 Other Applications Other Applications Google Apps & enterprise Applications {Collaboration Services Support} Microsoft applications Outlook 2007, 2010, 2013 {Local contacts for windows} Polycom HDX 7K Series 3.1.0-23277 RMX 2000 7.8 Radvision Scopia Solution 8.3
Avaya Proprietary – Use pursuant to Company Instructions Page 5
191
192 Client Work Station recommendation
193 194 195
196 Known issues and workarounds
197 Caveats 198 Key Summary Workaround / Notes NGUE-13094 Windows Flare Experience installer does not indicate user if it is None upgrading from previous release or doing fresh install NGUE-17168 [defsw131236] Flare (SRTP disabled) has no video when dial into Avaya communicator for AAC conference with CM SRTP enforced, AAC SRTP best effort windows is not supported in TCP mode. Register client in TLS mode. SCAE-5458 RV MCU 5110 – AC Win does not have video after joining into The SRTP capneg not part SCOPIA meeting if SRTP is set to enforce on CM 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). FW-3214 Executive AC Win is unable to hold call second time (Hold/resume The scenario involves joining than again try to Hold call) after bridging in the call which is initiated a CM Conference type of by the assistant on the executive’s behalf. 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. 199
200 Interoperability Issues 201
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 None do not play language specific to Moderator. SCAE-4559 AAC: Cannot merge B5800 user with G722 audio codec to conference None FW- AAC Presentation mode support is not available with Avaya Targeted for next release 2122/FW- Communication for windows 2.0 release. In Panel mode active, Avaya 2122 Communicator for windows participant cannot start Web Collab SCAE-3665 AAC Conference calls are not logged in call history. None
FW-3267 ACW Roster list (Meet-Me) - Dropped participant is not updated Workaround (instead of correctly, If some of the participant drops from Audio/Video (Not from exiting Compact) is to Mute Web). (or Unmute) All from the If Moderator mute dropped participant from ACW Roster list then Call Appearance Moderator conference ends, moderator will not able to make any actions on Controls Roster list for next conferences.
203 Scopia Key Summary Workaround / Notes SCAE-5652 Intermittent issue where rejoin of ACW do not show video of other Rejoin the conference. participants. Although video statistics shows video is received from other participants. FW-3286 Can't escalate to video if you dial into Scopia virtual room with audio Dial into the same virtual first. room with video call, then everything would work fine. You can also de-escalate video and then escalate video again. FW-2244 After leaving MCU 5110 Conf & rejoins the Conf ACW show no video Not available. on video window. SCAE-5333 ACW making audio call to Scopia endpoint behind iView can’t escalate Start the a video call to video. instead of audio and then escalation. FW-3285 Lost audio when ACW does hold/unhold after joining Scopia virtual Login client as TCP. room. [Tracking JIRA RV QC: 27016] FW-2377 You cannot currently access moderator controls or share content You can access some when dialed in to a Radvision Scopia conference from Avaya limited controls Using Communicator for Windows. 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. SCAE-5399 1XC, ACWin, ACiPad joining Elite MCU via IVR do not receive Use dial-in conference on presentation from XT. Avaya soft clients do receive presentations from Elite MCU for presenting. 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. NGUE-16766 Video loops on XT5000 after Win Flare make P2P call to RADVISION None endpoint which has dialed to virtual room and established MCU trunk to AAC conference SCAE-5654 When a Scopia desktop user shares any application in non-maximized Share entire desktop or a window, ACW client displays duplicated sharing content. The issue specific application in
Avaya Proprietary – Use pursuant to Company Instructions Page 7
happens only when launching Scopia desktop sharing on PCs which maximize window. have screen ratio other than 16:9 (1280x720 resolution). 204
205 Avaya one-X® Communicator Key Summary Workaround / Notes ONEXC-5763 [Interop:Flare-1XC] Freeze moderator video stream displayed at 1XC None endpoint, when moderator (flare user) de-escalates video conference call to audio call ONEXC-6030 “1XC-Participant” name doesn’t display on the integrated video None window, when user unhold call from 1XC after converting P2P video call to conference via Collaboration button ONEXC-6062 P2P audio call from Avaya Flare Experience for Windows to video None capable 1XC H.323 endpoint not escalated to video ONEXC-6112 Flare 1.1: 1XC is using only H.263 codec. P2P video call active None between Flare and 1XC. Hold/Unhold and Pause/Un-Pause from 1XC causes Pixelization (slow update) on Flare side ONEXC-6193 In P2P audio call from iPad/Windows Flare to 1XC SIP, audio call None escalate to video automatically if hold and unhold the call from 1XC SIP endpoint ONEXC-6349 When Win-Flare user promotes P2P video call to conference via None collaboration or dragging contact from Flare, video call is de-escalated to audio from 1XC participant SCAE-5526 When Flare Win and 1XC are on a video call, 1XC stops his video. Fix is planned with later After that Flare Win also de-escalate his video and the call drops service pack/release of immediately after that. Avaya Communication Manager. NGUE-13352 Multiple contact cards displays in carousel & roster of conference, None when 1XC/96XX participant transfer its conference call to any other participant SCAE-5752 Video call is not established after 1XC (TLS/RTP) transfers a video 1) Workaround is call from AC iPad (TLS/SRTP-CAPNEG) to AC Win (TLS/SRTP- hold/un-hold call on CAPNEG) AC Windows. 2) Configure 1XC with TLS/SRTP- CAPNEG (MediaEncryptionP arameters=1,2,9) 3) 1XC user performs consultative transfer to AC Win. SCAE-5825 If ACW escalate call from audio to video, remote end party's (1XC 6.2 None H.323) video appears as black screen on ACW video window. 206
207 Avaya Communicator for Android Key Summary Workaround / Notes SCAE-5419 Call gets drop on both Avaya Communicator for Android and ACW This issue is resolved with application after making a consultative transfer at ACW application. CM 6.3 patch 21542 FW-3029 When Android participant starts audio in the conference, his audio None status is not updated in the Flare roster. 208 209
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 None
Avaya Communicator for Windows 2.0 Release Notes
1XM by Mobile
211 Polycom Key Summary Workaround / Notes ONEXC-8689 Avaya Communicator for Windows - delayed image + poor resume None after hold with RMX. 212
213 Known Issue’s Key Summary Workaround / Notes FW-2183 Client uses old time zone to generate new call logs after changing to User can logout and login system(Desktop) time zone back to reflect changed time zone. SCAE-3508 ACW does not return to normal video resolution when network Re-initiate the call once congestion was removed. network congestion is gone from the network. FW-2106 The settings should be survive an upgrade, however the Language, Change the values manually Firstname\Lastname, and Auto\Single values are not migrated. after migration. SCAE-4424 Win Flare shows Grey Video Setting Window after resuming from Close video settings window Sleep mode. and open it again. WEBRTCEN Sometimes ACW gets crashed when user is on active video call then Either try again or drop the GINE-2706 report problem on settings menu. active call before reporting logs from settings menu. SCAE-451 Flare shall ensure each negotiated video stream can meet the None minimum bitrate requirement. SCAE-5441 Call dropped from AAC Conf when tried to switch from CP auto to None single stream on my ACW after the CPU detection auto dropped a stream. SCAE-5513 Camera still acquired (Light ON) when video conference put on hold to De-escalate video manually. make audio only P2P call. This is misleading as the user is not broadcasting video. FW-2844 The instant messaging card displays the last message sent or None 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. FW-2891 When Avaya Communicator for windows send Instant Messages to None 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. SCAE-5395 Dropped packets shown on Video Stats is inaccurate for video None conferences. SCAE-5426 In AAC conference, primary ACW is bridged out unexpectedly if User A to rejoin, without secondary station bridges in call (after primary user joins into moderator controls. conference). This issue is also seen with EC-500. EC-500 answers the call, user switches to ACW Primary and the call is ended SCAE-5452 Sometimes presence status is not updated when user switch from WI- User to logout and login FI to LAN cable. again. SCAE-5544 Voice path is disconnected between 1XC H323 and ACW after de- Fix is planned with later escalating to audio call from 1XC H323 user. service pack/release of Avaya Communication Manager.
Avaya Proprietary – Use pursuant to Company Instructions Page 9
FW-3326 While creating a adhoc conf, it displays dropped in the conference None. 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”. FW-3330 After transfer one user to another user, Open Collaboration button is Open Collaboration from disabled on call line appearance. 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. 2. Get your anti-virus definitions updated. (In case of Enterprise this is automatically done.) SCAE-5841 Bridge call: Executive hold call is drop after bridging the call and None. bridging out (Drops call) by assistant on the executive’s behalf. FW-2896 Presence feature does not work if Presence server address is set as Set the Presence server IP FQDN instead of IP address. address in place of FQDN. SCAE-5550 Aura Contacts are not loaded on Contacts Fan when user deleted User should log out then log aura contact on ACW then logout and login again. in again. It takes 2 times log in and log out to make that updated for the user. FW-3292 If the recipient of the Instant Message does not have the Instant Add user to communicator Message originator as a contact, escalation to voice call fails. contact’s before escalating to voice call Or place a call directly rather escalating from IM windows. SCAE-5773 The call gets dropped immediately on ACW after receiving a Do the blind transfer. consultative transfer from SIP desk phone where Avaya Communicator for windows set to SRTP and SIP desk phone is RTP only. SCAE-5836 100% CPU usage during video call. This issue is specific to Dell None Latitude E6430 which has x64-bit Windows 7 SP1, i5 quad core 2.6Ghz CPU, 4 GB RAM. 214
215 Appendix A
216 Finding documents on the Avaya Support site 217 218 1. Navigate to the Avaya Support web site at http://support.avaya.com/. 219 2. Click the Downloads & Documents tab, and select Documents. 220 3. In the Product search box, enter the product name. 221 4. Select the appropriate release number from the Choose Release drop-down menu. 222 5. If necessary, use the Content Type filter on the left to select the type of document you are looking for. For 223 example, if you are looking for user guides, you can select User Guides from the Content Type filter. Only 224 documents in the selected category will appear in the list of documents. 225
226 Appendix B 227
228 Collaboration Services
229 Support for Google Applications 230 You can use Collaboration Services click to call and click to join or host a conference functionality within Google 231 Applications, such as Gmail, Calendar, Sheets, Documents, and Forms. 232
Avaya Communicator for Windows 2.0 Release Notes
233 The following image provides an overview of Collaboration Services support with Google 234 Applications. 235
236 237 Where number marking is nothing but highlight of the phone number. 238 239
240 Support for Office 365 241 You can use Collaboration Services click to call and click to join or host a conference functionality from Office 365 with 242 the web versions of Microsoft Word, Excel, Outlook, Calendar, SharePoint, and One Note. 243 The following image provides an overview of Collaboration Services support with Office 365 web applications. 244
Avaya Proprietary – Use pursuant to Company Instructions Page 11
245 246 247 Where number marking is nothing but highlight of the phone number.