Equinox Clients 3.2.1.11 (Feature Pack 1 update) Notes Issue 0.3 August 29, 2017 2017 Avaya Inc. All Rights Reserved.
Notice While reasonable efforts were made to ensure that the information in this document was complete and accurate at the time of printing, Avaya Inc. can assume no liability for any errors. Changes and corrections to the information in this document might be incorporated in future releases. Documentation disclaimer Avaya Inc. is not responsible for any modifications, additions, or deletions to the original published version of this documentation unless such modifications, additions, or deletions were performed by Avaya. Customer and/or End User agree to indemnify and hold harmless Avaya, Avaya's gents, 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 the Customer or End User. Link disclaimer Avaya Inc. is not responsible for the contents or reliability of any linked Web sites referenced elsewhere within this documentation, and Avaya does not necessarily endorse the products, services, or information described or offered within them. We cannot guarantee that these links will work all the time and we have no control over the availability of the linked pages. Warranty Avaya Inc. provides a limited warranty on this product. 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 through the Avaya Support Website: http://www.avaya.com/support License USE OR INSTALLATION OF THE PRODUCT INDICATES THE END USER'S ACCEPTANCE OF THE TERMS SET FORTH HEREIN AND THE GENERAL LICENSE TERMS AVAILABLE ON THE AVAYA WEB SITE http://support.avaya.com/licenseinfo/ ("GENERAL LICENSE TERMS"). IF YOU DO NOT WISH TO BE BOUND BY THESE TERMS, YOU MUST RETURN THE PRODUCT(S) TO THE POINT OF PURCHASE WITHIN TEN (10) DAYS OF DELIVERY FOR A REFUND OR CREDIT. Avaya grants End User a license within the scope of the license types described below. 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 End User. "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. "Software" means the computer programs in object code, originally licensed by Avaya and ultimately utilized by End User, whether as stand-alone Products or pre-installed on Hardware. "Hardware" means the standard hardware Products, originally sold by Avaya and ultimately utilized by End User. License type(s) Named User License (NU). Customer 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 Avaya Equinox 3.2 Notes (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 Product that permits one user to interface with the Product. Shrinkwrap License (SR). With respect to Software that contains elements provided by third party suppliers, End User may install and use the Software in accordance with the terms and conditions of the applicable license agreements, such as "shrinkwrap" or "clickwrap" license accompanying or applicable to the Software ("Shrinkwrap License"). The text of the Shrinkwrap License will be available from Avaya upon End User s request (see Third-party Components" for more information). Copyright Except where expressly stated otherwise, the Product is protected by copyright and other laws respecting proprietary rights. Unauthorized reproduction, transfer, and or use can be a criminal, as well as a civil, offense under the applicable law. Third-party components Certain software programs or portions thereof included in the Product may contain software distributed under third party agreements ("Third Party Components"), which may contain terms that expand or limit rights to use certain portions of the Product ("Third Party Terms"). Information identifying Third Party Components and the Third Party Terms that apply to them is available on the Avaya Support Web site: http://support.avaya.com/thirdpartylicense/ 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 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 Web site: http://www.avaya.com/support Trademarks Avaya, the Avaya logo, and COMPAS are either registered trademarks or trademarks of Avaya Inc. in the United States of America and/or other jurisdictions. All other trademarks are the property of their respective owners. Downloading documents For the most current versions of documentation, see the Avaya Support Web site: http://www.avaya.com/support Avaya support Avaya provides a telephone number for you to use to report problems or to ask questions about your product. The support telephone number is 1-800-242-2121 in the United States. For additional support telephone numbers, see the Avaya Support Web site: http://www.avaya.com/support Notes 2
Table of Contents Change History... 6 Introduction... 6 Installation... 7 Product compatibility... 7 Recommended Minimum Load Line-up Requirements for Avaya Aura Core... 7 Product Line-Up... 7 Deployment Considerations... 8 3.2.1.11 (GA update)... 8 3.2.1... 8 HTTP Tunneling... 8 Mobile Link... 8 3.2... 8 ios10 CallKit Integrated Calling... 8 Top of Mind Equinox Meetings Widget... 9 Unified Conferencing User Portal... 9 Certificate Trust Store Changes... 9 Certificate Identity Management... 10 Updated Microsoft Outlook Add-in... 10 What's new... 13 3.2.1... 13 3.2... 14 Fixes... 16
Avaya Equinox 3.2 Notes 3.2.1.11 (GA update)... 16 3.2.1... 17 Windows Client... 17 MacOS Client... 17 Android Client... 17 ios Client... 17 3.2... 18 Windows Client... 18 MacOS Client... 19 Android Client... 19 ios Client... 20 Known issues and workarounds... 21 3.2.1.11... 21 3.2.1... 21 Windows Clients... 21 MacOS Clients... 21 Android Clients... 22 ios Clients... 22 3.2... 23 Windows Client... 23 MacOS Client... 26 Android Client... 27 ios Client... 29 Notes 4
Avaya Equinox 3.2 Notes Documentation & Localization... 31 Documentation errata... 31 Localization... 32 Contacting support... 33 Contact Support Checklist... 33 Contact Support Tasks... 33 Appendix A: Acronyms... 34 Notes 5
Avaya Equinox 3.2 Notes Change History Date Description 7/10/2017 July GA update for the Equinox 3.2 Clients. 8/21/2017 August GA update for the Equinox 3.2 FP1 Clients. 8/29/2017 GA update for the Equinox 3.2.1.11 Windows client only Introduction This document provides late-breaking information to supplement the Avaya Equinox Clients 3.2.1 (Feature Pack 1) software and documentation. For updated documentation, product support notices, and service pack information, go to the Avaya Support site at http://support.avaya.com. Please refer to the latest Avaya Aura 7.1 Notes for information specific to the Avaya Aura feature and service packs. Notes 6
Avaya Equinox 3.2 Notes Installation Product compatibility For the latest and most accurate compatibility information go to: https://support.avaya.com/compatibilitymatrix/index.aspx. Recommended Minimum Load Line-up Requirements for Avaya Aura Core Component Avaya Aura System Manager Avaya Aura Session Manager Avaya Aura Presence Server 7.0.1.2 Build 44 7.1.0.0 Build 1125193 Software Update Revision No: 7.1.0.0 Build 116662 7.0.1.2 Build 701230 + patch 7.1.0.0 Build 710028 7.0.1.0 Build 864 7.1.0.0 Build 600 Product Line-Up The following Equinox solution line-up is required when enabling new features (that have a client-server dependency) introduced in this release: Client/Server Build Number Date Available Avaya Equinox for Windows 3.2.1.11 29 Aug 2017 Avaya Equinox for MacOS 3.2.1.6 21 Aug 2017 Avaya Equinox for Android 3.2.1.11 21 Aug 2017 Avaya Equinox for ios 3.2.1.12 21 Aug 2017 Avaya Multimedia Messaging 3.2.0.0 Build 372 10 July 2017 Avaya Aura Device Services 7.1.0.0 Build 363 10 July 2017 Avaya Aura Web Gateway 3.2.0.1 Build 1 21 Aug 2017 Notes 7
Avaya Equinox 3.2 Notes Deployment Considerations IMPORTANT: Client settings need to be refreshed when new parameters are added. User is notified via the Red Notification Triangle to refresh configuration. 3.2.1.11 (GA update) The 3.2.1 release for Windows is being updated and replaced on support.avaya.com and PLDS. The previous version 3.2.1.10 is being replaced with version 3.2.1.11. The updated version does not install the QoS driver by default to address a potential network connectivity issue with PCs that were not upgraded to Windows 10 Anniversary Edition but rather had a new install of build 1607 or later. 3.2.1 HTTP Tunneling HTTP Tunneling will be enabled by default and can be disabled by setting the following autoconfiguration setting. SET ENABLE_MEDIA_HTTP_TUNNEL 0 Mobile Link When connected in the Equinox 9.0.2 meetings, Equinox 3.2.1 Client can only initiate mobile link with XT endpoints that are managed by the same Equinox Conference Management system (iview). The XT endpoints can register as SIP or H.323. This means that the following XT endpoints can t be connected with mobile link: Non-managed / non-registered XT endpoints; Remote XT endpoints - a guest to the meeting from a remote organization cannot pair with her local XT, since that XT is remote to the iview. All supported XT endpoints must be in the same network as iview without going through any proxy. Make sure the following iview advanced settings are set as: com.radvision.airpair.forceuseproxyip=true com.radvision.airpair.proxyip=x.x.x.x where x.x.x.x is iview's IP address 3.2 ios10 CallKit Integrated Calling With CallKit integration, also called Integrated Calling, VOIP calls now appear on the lock screen and home screen with the familiar ios interface for answering calls. This greatly improves the experience for Notes 8
Avaya Equinox 3.2 Notes users in answering calls and dealing with incoming VOIP and cellular calls during an existing call. CallKit will be enabled by default and can be disabled by end-users or by the following auto-configuration setting: SET IOS10CALLKIT_ENABLED 0 Top of Mind Equinox Meetings Widget As part of the conferencing feature set, a new Equinox Meetings widget is available in the Top of Mind home screen. If a user is provisioned with an Avaya Equinox virtual room or Avaya Aura Conferencing account, this widget provides easy access to join meetings or access the meeting portal. Users that are not configured with a conferencing system can join an Equinox meeting from this widget. This Equinox Meetings widget is enabled by default and can be disabled by end-users in the Top-of-Mind options panel or by the following auto-configuration setting: SET SHOW_EQUINOX_MEETING_PANEL_IN_TOM 0 Unified Conferencing User Portal The Unified Portal is a single solution for managing your meetings. You can plan meetings in advance, customize meeting properties, and send the details of meetings to participants. The following autoconfiguration settings are introduced to support the integration of the Equinox Clients with the Unified Portal. SET UNIFIEDPORTALENABLED 1 SET UNIFIED_PORTAL_SSO 1 SET UNIFIED_PORTAL_USERNAME <username> SET UNIFIED_PORTAL_PASSWORD <password> Certificate Trust Store Changes Prior to release 3.2, if the private trust store was enabled, the platform trust store was not used to validate any connections. In 3.2, by default both the private and platform trust stores will be used for certificate validation. To limit validation to only the private trust store, use the following autoconfiguration setting: SET TRUST_STORE 0 Note that this setting is only appropriate for specific environments and will limit capabilities such as using Avaya Equinox clients to join an Avaya Equinox conference hosted outside your organization. Notes 9
Avaya Equinox 3.2 Notes Certificate Identity Management The following auto-configuration parameters have been introduced to support the Simple Certificate Enrollment Protocol (SCEP) and PKCS12URL Mobile authentication methods. Simple Certificate Enrollment Protocol (SCEP) Parameters SET MYCERTURL SET MYCERTCN SET SCEPPASSWORD SET SCEP_USESSO 0 SET MYCERTDN SET MYCERTCAID CAIdentiifier SET MYCERTKEYLEN "2048" SET MYCERTRENEW "90" PKCS12URL Parameters SET PKCS12URL "" SET PKCS12PASSWORD "" Updated Microsoft Outlook Add-in A new and improved Outlook Add-In is provided which supports auto-configuration of conference details for meeting invites. Prior to deployment, please read the instructions in the Microsoft Outlook Add-in section in the Planning for and Administering Avaya Equinox for Android, ios, Mac, and Windows document. The following configuration settings are required to enable the Outlook Add-in in the TE + Equinox 9.0.2 Deployment: SET SIPENABLED 1 SET CONFERENCE_FQDN_SIP_DIAL_LIST <Portal-FQDN> # (i.e. confportal.example.com) SET UNIFIEDPORTALENABLED 1 Notes 10
Avaya Equinox 3.2 Notes SET CONFERENCE_PORTAL_URI <URI> # (i.e. https://confportal.example.com:8443/portal/) SET EWSENABLED 1 SET EWSDOMAIN <domain> # (i.e. example.com) Notes 11
Avaya Equinox 3.2 Notes The following configuration settings are required to enable the Outlook Add-in in the TE + AAC Deployment: SET SIPENABLED 1 SET CONFERENCE_FQDN_SIP_DIAL_LIST <AAC-FQDN> # (i.e. confportal.example.com) SET CONFERENCE_ACCESS_NUMBER <telephone number> (i.e. +13035382200) SET ADDITIONAL_CONFERENCE_ACCESS_NUMBER_LIST <[label]:[telephone number] list> (i.e. Label1:Number1,Label2:Number2,,LabelN:NumberN) SET CONFERENCE_MODERATOR_CODE <moderator code> SET CONFERENCE_PARTICIPANT_CODE <participant code> SET CONFERENCE_PARTICIPANT_URL <URL> SET EWSENABLED 1 SET EWSDOMAIN <domain> # (i.e. example.com) iview Meeting Template The default iview email template shall not be used for the Equinox client because they are for the Scopia Desktop Clients. Admin shall reconfigure the email invitation template with some simple URL without any buttons. Below is the example of email template. The key is to use hyperlink on URL. The phone numbers can be prefixed with tel: so that the number can be enabled for click-to-call on smart phones. Join the Meeting: https://meeting.example.com:8443/portal/?id=[e164] Meeting ID: [MEETING_ID] Meeting PIN: [PIN] Audio Dial-In (Smartphone Friendly): All locations: tel:+1-234-555-8000,,[meeting_id]#,,,[pin]# NA Toll Free: tel:1-800-555-7000,,[meeting_id]#,,,[pin]# Equinox XT endpoints, dial [E164] Notes 12
Avaya Equinox 3.2 Notes Enabling Equinox Outlook Add-in After the Equinox Client for Windows is installed, user needs to manually enable the Outlook Add-in from the client settings >> Desktop Integration >> Outlook Add-in. Then restart the Outlook on Windows. Note that the firewall needs allow access to https://manage1.esna.com in order to start-up the Outlook Add-in. For troubleshooting, you can just browse to https://manage1.esna.com/equinox/manifest.xml and see if you can display the xml file. What's new The following table lists the enhancements and deprecated functionality in Equinox Client 3.2 and is cumulative since the last minor release showing the most recent release first and oldest release last. 3.2.1 New features common to all platforms 1. Scopia Client Replacement Notes 13
Avaya Equinox 3.2 Notes HTTP Tunneling enable access to conferences for clients behind firewalls that block non-web protocols used for audio and video traffic Mobile Link - automatically transfer your meeting to an Avaya Equinox room system Outlook Add-in Delegate support create meeting invites on behalf of someone who has given you delegate access for their Exchange calendar 3.2 New features common to all platforms Scopia Desktop & Mobile Client Replacement, new deployment mode o HTTP Conferencing (SIP not required) Guest conference users Signed in Equinox Conferencing users Mid-conference controls Integration into Top of Mind and Click to Join o Unified Portal integration o Launch from Unified Portal o Discovery of personal virtual rooms o Enhanced conference call logs o Presentation only mode (no audio and no video call) o In-conference branding for calls Scopia Conferencing In Conference Features added this release o Sign in to passcode protected conferences o Moderator PIN / Become Moderator o One-time conference PIN's o Knock on door o Raise hand support o Conference dial in information o Far End Camera Control (FECC) o Conference recording Pause / Resume o Extend conference meeting time o Control text overlay and self-see control o Add terminal to conference by IP address Client identity certificates Third Party Call Control (3PCC) via Application Enablement Services (AES) New features specific to Android and ios platforms ios platform only - Callkit support Support for identification of a Client identity certificate with PKCS12URL configuration Simple Certificate Enrollment Protocol (SCEP) for Client Identity Certificates Notes 14
Avaya Equinox 3.2 Notes New features specific to the Windows platform New Microsoft Outlook Add-in for Windows (available in English and German only; other languages will be available in 3.2 FP1) Notes 15
Avaya Equinox 3.2 Notes Fixes The following table lists the issues fixed in this release and is cumulative since the last major (or minor) release showing the most recent release first and oldest release last. 3.2.1.11 (GA update) Fixed in ACW-12325 Disable DSCP Driver Installation on default. 3.2.x 3.2.1.11 Fixed in the updated GA version 3.2.1.11 New QoS Device Driver Avaya Equinox for Windows release 3.2 introduced a new QoS device driver that enabled more granular marking of DSCP tags on audio and video streams, specifically allowing for audio and video streams to be marked with a different QoS value. In prior versions of Avaya Equinox for Windows, Microsoft Windows APIs were used which did not allow for differentiating between audio and video streams. Microsoft Driver Signing Policy Change In build 1607, Microsoft change the policy for device drivers and new installs of the operating system require all device drivers to be signed with a new code signing process. This policy does not apply for the PCs that are upgraded to Windows 10 version 1607 or if Secure Boot is off. Upon installing Avaya Equinox 3.2 or later on Windows 10 PCs that were not upgraded to Anniversary Edition (New installs of build 1607 or later) network connectivity may be lost. To address this issue, the 3.2.1.11 update no longer will install the QoS driver by default. In this case, DSCP packet marking will use the same approach used in versions 3.0 and 3.1 of Avaya Equinox. Avaya is planning to release a Service Pack in the coming weeks that will include a device driver that is signed with the new process. For PCs that are not impacted by the new policy, the QoS driver can be installed by using the command line installation and setting the parameter NOQOS=0 in order to install the DSCP driver Example: msiexec /i "Avaya Equinox Setup 3.2.1.11.msi" NOQOS=0 Notes 16
Avaya Equinox 3.2 Notes 3.2.1 Windows Client Fixed in ACW-10975 Message notification does not get removed. 3.1 3.2.1 ACW-11876 Chat message is still marked as unread. 3.1 3.2.1 ACW-11903 Plantronics Headset not picking up after plugging in. 3.2 3.2.1 ACW-11981 Windows unable to load calendar - exception in AllCalendarList. 3.1.0.1 3.2.1 ACW-12051 After restarting laptop from a shutdown or a sleep mode, the 3.2 3.2.1 Equinox soft client defaults the microphone back to the laptop built-in microphone. ACW-12075 Pickup icon doesn't dissapear if call dropped on mobile. 3.2 3.2.1 ACW-12076 One-way speech path. 3.2 3.2.1 ACW-12083 After a conversation finished over the cell phone - the Equinox client pop up never disapeared - when you click on the pop up, it show's as failed. 3.2 3.2.1 MacOS Client None. Android Client Fixed in FA-15725 Limited VoIP service when logged in via SBC. 3.0 3.2.1 FA-17234 Mobile client loses connection to Multimedia Messaging. 3.2 3.2.1 FA-17312 When a SCEP login succeeds, the registration will not always complete. If that occurs an error triangle will be posted for the user saying login is not complete. 3.2 3.2.1 ios Client Workaround: If the user taps on the triangle and logs in, login will succeed. Fixed in FI-14607 VoIP login fails over VPN. 3.0.2 3.2.1 FI-15479 When searching contacts in Equinox, searching by ASCII string does 3.1 3.2.1 Notes 17
Avaya Equinox 3.2 Notes FI-16229 FI-16279 FI-16380 not hit double-byte string, and vice versa. For TCP only connections, for ios clients occasionally login can fail. Workaround: Retry the login. With callkit enabled, user is not aware of the 2nd incoming call while holding the phone to his ear for an audio call. Workaround is to disable callkit "integrated calling" and the additional tone support. If user is on a Presentation Only Mode call and makes another outgoing point-to-point call, the point-to-point call does not work. 3.1.1 3.2.1 3.2 3.2.1 3.2 3.2.1 Workaround: Disable integrated calls or use POM+audio+video call. FI-16486 CCertificateValidationRequest crash report. 3.2 3.2.1 3.2 Windows Client Fixed in ACW-9159 Transferor name is still displayed on the incoming call notification window of instead of transferee name. 3.0 3.2 ACW-10286 ACW-10313 Workaround: None. Call appearance will be correctly updated if call is answered. Unable to Hold and then Resume a call via the headset while an incoming call is answered on one MDA device while bridged in from another device. Calendar meetings not showing even though Outlook is running. 3.1 3.2 3.1 3.2 Workaround: Restart the Outlook client. ACW-10399 Equinox Windows crashed for participant joining an AAC 3.0 3.2 conference with ~200 participants while sharing a.pdf file ACW-10437 Avaya Browser Extension is adding additional "0" between 3.0 3.2 country code and area code for specific phone number format in Internet Explorer ACW-10438 Contact presence not shown in Messages conversation tab if 3.1 3.2 user is not added to Equinox contacts ACW-10501 Unable to do click to dial from Google Chrome 3.0 3.2 ACW-10571 Calendar list in Top of Mind tab is not sliding 3.1 3.2 ACW-10583 Mouse freezes while hovering over phone number while using 3.1 3.2 Notes 18
Avaya Equinox 3.2 Notes Avaya web extensions ACW-10784 Equinox for Windows fails to parse the meeting ID correctly 3.1 3.2 from an outlook invite ACW-11008 Merge menu option missing from call appearance 3.0 3.2 ACW-11107 Presence for contacts is missing sometimes 3.1.0.1 3.2 ACW-11245 Equinox for Windows does not tag the audio and video DSCP as 3.1 3.2 described in the document ACW-11340 Equinox Outlook Plugin is not signed. 3.1 3.2 ACW-11490 Bridged Lines do not respect Bridge Call Alerting and Per-Button 3.1 3.2 Ring Control settings ACW-11907 No contacts are shown for Domino directory search. 3.1 3.2 MacOS Client Fixed in ACMACOS-2982 Incoming calls that were transferred by another client 3.0 3.2 inconsistently present the called party and transferred by party. ACMACOS-7879 Failed to log in Exchange Web Service when the user's principle 3.1 3.2 domain name has domain part different than the Exchange Web Service domain. ACMACOS-8386 Sharing stopped on MacOS when swiped to another workspace. 3.1 3.2 Android Client Workaround: minimize the application and restore and the sharing border will be restored Fixed in FA-13564 The user will not be able to save a contact with extra characters in it 3.0 3.2 such as a '#' character, prior to the next Aura, 7.1. The issue is a solution limitation which will be addressed in the following release. FA-14448 When you bridge onto a call from a mobile device to a call you have already established with another endpoint, the mobile endpoint will not show conferencing controls. This is a limitation of the bridging solution, and will be addressed in a future release. The user will still see audio and video for the conference. 3.0 3.2 Workaround: After switching the call to the user's second client press video escalate button to see the collaboration window and moderator controls. FA-15369 Failed to add contact with Other phone number. 3.0 3.2 Notes 19
Avaya Equinox 3.2 Notes FA-16477 Auto Start feature does not work on Equinox 3.1 for Android. 3.1 3.2 FA-16735 Crash on launch after first few calls. 3.1 3.2 FA-16736 If OS Language is Arabic, contacts do not get displayed. 3.1 3.2 FA-16847 Equinox Android Exchange connection times out trying to load an 3.1 3.2 enormous calendar entry. FA-17175 Self-Presence isn't working after SBCE failover. 3.1 3.2 ios Client Fixed in FI-12872 The user will not be able to save a contact with extra characters in it 3.0 3.2 such as a '#' character, prior to the next Aura, 7.1. The issue is a solution limitation which will be addressed in the following release. FI-13502 When you bridge onto a call from a mobile device to a call you have already established with another endpoint, the mobile endpoint will not show conferencing controls. This is a limitation of the bridging solution, and will be addressed in a future release. The user will still see audio and video for the conference. 3.0 3.2 Workaround: After switching the call to the user's second client press video escalate button to see the collaboration window and moderator controls. FI-13618 When the device is locked, the notification of an incoming call is 3.0 3.2 delayed resulting in some calls not being able to be answered. FI-14777 Incorrect label in call control menu when language is Russian. 3.0 3.2 FI-14961 ios was mute but Equinox will still ring. 3.1 3.2 FI-15060 Russian strings for labels look ugly. 3.1 3.2 FI-15355 Dialing from a calendar entry does not work. 3.1 3.2 FI-15369 OverallAlertTimer set to 180 seconds expires too early. Number of 3.1 3.2 Rings set to 99. FI-15665 Failed to add contact with Other phone number. 3.0 3.2 FI-15756 Product breakage in 3.1 for external calls with caller ID to locked 3.1 3.2 iphone. Notes 20
Avaya Equinox 3.2 Notes Known issues and workarounds 3.2.1.11 ACW-12357 Equinox Win 3.2.1.11 showing popup to copy Avaya DSCP driver D:\Windows\System32 and Insert Disk (No previous version installed / Installation with NOQOS=0). Workaround is to cancel the pop-up and proceed with installation. 3.2.1.11 3.2.1 Windows Clients Solution issues ACW-12041 User cannot enter PIN for XT endpoint again after user cancels the Enter PIN dialogue. 3.2.1 Application issues Workaround: Reconnect after mobile link timer has expired (2 minutes). ACW-12216 Outlook Add-in delegate support is not enabled after upgrading from release 3.2 to release 3.2.1. 3.2.1 ACW-12275 Workaround: Restart Microsoft Outlook. The sharing button is disabled when a user joins a conference via HTTP Tunneling with BFCP enabled. 3.2.1 MacOS Clients Application issues ID Summary Found in Notes 21
Avaya Equinox 3.2 Notes ACMACOS-8801 Android Clients The sharing button is disabled when a user joins a conference via HTTP Tunneling with BFCP enabled. 3.2.1 Solution issues FA-17429 Client not downgraded to companion mode if one or two attempts failed due to wrong PIN and connect in second attempt. 3.2.1 Workarounds: 1. Enter correct password a second time (after the first time fails with the correct password). 2. Drop connection to XT defect and and then re-pair to the XT device. Application issues FA-17540 Meeting address info is not displayed after upgrading from 3.1.2 build to 3.2.1 build. 3.2.1 ios Clients Solution issues Workaround: Run the auto-config on the client. FI-16423 Client not downgraded to companion mode if one or two attempts failed due to wrong PIN and connect in second attempt. 3.2.1 Workarounds: 1. Enter correct password a second time (after the first time fails with the correct password). 2. Drop connection to XT defect and and then re-pair to the XT device. Notes 22
Avaya Equinox 3.2 Notes Application issues FI-16346 Mobile link paired call is dropped when bridging the call from an MDA device. 3.2.1 3.2 Windows Client Solution issues ID Summary Found in ACW-3291 Avaya Aura Conference Roster and Video missing if user invokes call hold before conference is not started. 3.0 ACW-9443 ACW- 10797 ACW- 11498 ACW- 11155 Workaround: User must end call and rejoin Avaya Aura Conference. Unable to get video on Scopia conference after bridge into the call from another MDA endpoint which joined the call as audio. Workaround: Re-join the conference as video or join from equinox first. Equinox client not showing Microsoft Edge sharing content while using application sharing. Workaround: User can select full screen sharing or portion of screen Auto-configuration doesn't work for Equinox Conferencing with Team Engagement system Workaround: DNS auto discovery is the recommended deployment. With Aura 7.1 Equinox Windows 3.2 not able to upgrade via web deployments via AADS. Workaround: In order to work around the issue, the following steps need to be taken: 1. DNS resolvability of OCSP FQDN: If the virtual SMGR FQDN is not already resolvable in DNS, then it needs to be added to DNS. To see the virtual SMGR FQDN being used in the OCSP URLs in SMGR: In SMGR: Services->Security->Certificates->Authority->Certification Authorities Select tmdefaultca, (Active) and click on Edit CA Scroll down to: Default CRL Dist. Point and look at the URL configured to the right. The FQDN used in the URL is the virtual SMGR FQDN. 3.0.0.1 3.1 3.2 3.2 Notes 23
Avaya Equinox 3.2 Notes ID Summary Found in OR If it is not possible to modify the DNS entry, then add the correct IP to FQDN mapping to the PC s etc/hosts file 2. Remove the X509v3 Freshest CRL URL from the certificate profile used to generate certificates a. In SMGR: Services->Security->Certificates->Authority->Certificate Profiles On the Manage Certificate Profiles screen you should see the following profiles: ENDUSER ID_CLIENT ID_CLIENT_SERVER ID_SERVER OCSPSIGNER ROOTCA SERVER SUBCA For each of the ID_CLIENT, ID_CLIENT_SERVER and ID_SERVER profiles, click on the Edit button and scroll down to FreshestCRL extension : You will see something like this: FreshestCRL extension [?] Use Use CA Defined FreshestCRL extension Use FreshestCRL extension URI Uncheck the checkbox next to FreshestCRL extension (it will automatically remove the two sub-items underneath it. Click on Save Make sure to do this for all three profiles (ID_CLIENT, ID_CLIENT_SERVER, ID_SERVER). ACW- 11759 3. Regenerate AADS certificate 4. On the AADS server, run the configureaads.sh script. Re-run option 1) to regenerate the AADS identity certificate. Be sure to restart the AADS after this step is complete. Upon installing Avaya Equinox 3.2.0.35 network connectivity is lost on few windows 10 machine. As per Microsoft, on non-upgraded fresh installations of Windows 10, version 1607 with Secure Boot ON, drivers must be signed by Microsoft or with an end-entity certificate issued prior to July 29th, 2015 that 3.2 Notes 24
Avaya Equinox 3.2 Notes ID Summary Found in chains to a supported cross-signed CA.. Workaround: Install the client by command line installation and set the parameter NOQOS=1 in order to not install the DSCP driver Example: msiexec /i "Avaya Equinox Setup 3.2.0.35.msi" NOQOS=1 Application issues ACW-6941 H323 Dual Registration client cannot unpark a parked call. 3.0 ACW-8326 Unable to install Equinox by dropping the installer file into Group Policy in Windows Server 3.0 1. Open Group Policy Management 2. Edit Default Domain Policy 3. Under Computer Configuration > Policies > Windows Settings > Scripts display properties of Startup 4. Place Avaya Equinox MSI installer inside the Scripts/Startup folder (open location by pressing 'Show Files') 5. Add new script by pressing 'Add...' 5a. Browse for Avaya Equinox MSI installer 5b. In 'Script Parameters' field add "/qn" parameter (without parentheses) and press 'Ok' 6. After user who already joined into corporate domain logon event MSI will install application ACW-9105 Avaya Communicator application is terminated without user notification during upgrade to Avaya equinox. Calls in progress may be lost. 3.0 ACW-9107 ACW-10010 Workaround: Avaya recommends that Avaya equinox upgrades should be scheduled during a maintenance window to minimize end user disruptions. Call History is cleared when upgrade from Avaya Communicator to Avaya Equinox if the upgrade is rolled back. Avaya Communicator Call History is not retained after upgrade to Avaya Equinox. Some Bluetooth headsets turn off the Microphone when selecting the Stereo Playback speaker resulting in no audio path in Equinox clients. Notes 25 3.0 3.1
Avaya Equinox 3.2 Notes ACW-10286 ACW-11870 ACW-10966 ACW-10726 Unable to Hold and then Resume a call via the headset while an incoming call is answered on one MDA device while bridged in from another device. Intermittently the screen link search of all the available XT endpoints, the PIN for does not get shown on the XT endpoint screen. Workaround: Enter empty or invalid PIN to generate one failed attempt and the PIN appears for second attempt. Merge button is disabled when dragging an active call to a held call. Workaround: Drag the held call to the active call Audio / Video settings window disappears after a few seconds after launching from the portal when Equinox Windows client isn't logged in at the time. Workaround: Open the audio/video setting panel from the Equinox Windows client. 3.1 3.2 3.2 3.2 MacOS Client Solution issues ACMACOS-7148 BFCP Screen Sharing fails to resume when the retrieving held call. 3.0 Workaround: User can manually restart BFCP Screen Sharing. ACMACOS-2741 Audio only outbound call cannot escalate to video between Equinox client & XT5000 H.323. ACMACOS-6764 BFCP screen sharing fails with black screen when all is held and retrieved multiple times. Workaround: Terminate existing call and redial to re-establish BFCP Screen Sharing. ACMACOS-4855 Avaya Aura Conference Roster and Video missing if user invokes call hold before conference is started. 3.0 3.0 3.0 Workaround: User must end call and rejoin Avaya Aura Conference. ACMACOS-8423 Pickup of bridge line call after a transfer fails. 3.2 ACMACOS-8509 Enabling the parameter ENFORCE_SIPS_URI is not supported in this 3.2 release. ACMACOS-8545 Equinox auto configure doesn't work with Equinox Conferencing portal 3.2 address as the web address. Workaround: DNS auto discovery is recommended deployment for Notes 26
Avaya Equinox 3.2 Notes ACMACOS-8729 Equinox clients. Users can manually enter the AADS auto configure URL if DNS auto discovery is not implemented. User cannot enter PIN for XT endpoint again after user cancels the Enter PIN dialogue. Workaround: Reconnect after mobile link timer has expired (2 minutes). 3.2 Application issues ACMACOS-7217 MacOS client crashes when presenter ends conference call from call 3.0 appearance while collaboration from his end is in progress. ACMACOS-7118 Add as favorite is not available for contact that has multiple email 3.0 addresses defined. ACMACOS-8497 Unable to search LDAP from the Messaging participant s screen. 3.0 Workaround: Perform a directory search on the main window and drag the participant to the conversation window. ACMACOS-7990 Garbled outgoing audio when receiving an incoming email to Outlook 2016 while on a call. Problem was the 2016 Outlook client on the Mac was indexing and syncing with the Exchange server causing network congestion. Workaround: Create a new Microsoft Outlook exchange profile. ACMACOS-8441 With Equinox Conferencing 9.0.2, the dial-in information (accessible from advanced meeting controls) is displayed with HTML tags. 3.0.0.1 3.2 Workaround: To support Equinox clients, the Equinox Conferencing 9.0.2 admin has to configure iview to use the text" version of the email template. Android Client Solution issues FA-3381 When CES is enabled, corporate directory search does not return results if 3.0 search term is last name and contains a space character. FA-14399 Failed to add participant to Scopia 8.3 conference using the dial in option. 3.0 Workaround: Participant will need to dial into conference directly. Notes 27
Avaya Equinox 3.2 Notes FA-9586 FA-15092 FA-15001 FA-9764 FA-15215 FA-15038 FA-16249 Audio only outbound call cannot escalate to video between client & XT5000 H.323. Moderator controls don't work after the moderator's second MDA device hangs up the call (in an Equinox Conference 9.0 enhanced conference). Presence still displays the stale status even after the user has updated it in CES only deployments. Calls not properly terminated when call that has been Extended to Cellular (EC 500) is terminated on the cellular device. Occurs with Aura 7.0 only. Workaround: The call is terminated when the remote party terminates the call. Unable to open video window after bridging into a call from an Android device and disconnect at desk phone device. Work around: Join call as video or join from Equinox client first. A CCMP-invited participant cannot unmute self after being muted by moderator. The device is only ringing on the speaker, not the bluetooth device for Vantage. 3.0 3.0 3.0 3.0 3.0.0.1 3.0.0.1 3.1.1 Application issues FA-12648 Android client in One-X CES call back mode drops call when enforced SRTP is 3.0 enabled. FA-17383 Use of Equinox for initiating outgoing calls or answering incoming calls while 3.0 user is already engaged in active VoIP call using any of communication apps listed above would result in inconsistent results. Users are advised to end the ongoing VoIP communications on other VoIP applications before activating Equinox calls. FA-13374 No whiteboard collaboration once call returns to the app from a cellular 3.0 handoff if Aura CM version is not 7.1.0.0.0 OR 7.0.1.3.0. FA-17061 Specific to users on Avaya Vantage. 3.1.2 Users with Avaya Equinox 3.2 running on Vantage SP0 or later will not observe this issue. FA-16632 No audio voice path when answering AAC audio-only conference invite. 3.2 Workaround: 1. Leave conference and dial back into the conference to restore audio. 2. OR Use AAC 8.0 SP9 Notes 28
Avaya Equinox 3.2 Notes ios Client Solution issues FI-13480 Failed to add participant to Scopia 8.3 conference using the dial in option. 3.0 FI-6669 When CES is enabled, corporate directory search does not return results if search term is last name and contains a space character. 3.0 FI-11404 When the One-X CES Server is deployed in multiple CM environments, there 3.0 may be issues with the display of the call log which may only show the caller number. FI-13665 Calls not properly terminated when call that has been Extended to Cellular (EC 3.0 500) is terminated on the cellular device. Occurs with Aura 7.0 only. Workaround: The call is terminated when the remote party terminates the call. FI-13991 A CCMP-invited participant cannot unmute self after being muted by moderator. FI-14010 Moderator cannot re-join a conference if dropped from conference in a locked meeting. Workaround: 1. All participants to drop and start a new meeting or 2. Any one participant can promote himself as moderator by *1 and moderator code FI-14129 Unable to open video window after bridging into a call from an ios (MDAenabled) device and then disconnecting call from desk phone device. FI-14776 Outgoing call log is not shown on Boss when Secretary makes a Bridged Line Appearance call for Boss to customer. There is no support for this call flow in CES, to correct these call logs with Bridged Line Appearances please consider using the client without CES enabled. FI-15873 With Equinox Conferencing 9.0.2, the dial-in information (accessible from advanced meeting controls) is displayed with HTML tags. 3.0.0.1 3.0.0.1 3.0.0.1 3.1 3.2 Application issues Workaround: To support Equinox clients, the Equinox Conferencing 9.0.2 admin has to configure iview to use the text" version of the email template. FI-11952 Client in One-X CES call back mode drops call when enforced SRTP is enabled. 3.0 Notes 29
Avaya Equinox 3.2 Notes FI-14851 ios does not recognize Gmail accounts as enterprise accounts, similar to exchange. This will be looked at for additional support in an upcoming release of the client. FI-14187 Intermittently, there is no audio path after switching from Enterprise WiFi #1 to WiFi #2 when the ios user joined as a participant into a Scopia or Equinox Conference. FI-15579 No audio voice path when answering AAC audio-only conference invite. Workaround: 1. Leave conference and dial back into the conference to restore audio. 2. OR Use AAC 8.0 SP9 FI-16339 While on an active HTTP call, when an incoming call arrives it may not be possible to put the HTTP call on hold to answer the other incoming call. 3.0 3.0.0.1 3.2 3.2 If the other call is answered and you cannot hold the current call, you may have to dial in again. Notes 30
Avaya Equinox 3.2 Notes Documentation & Localization For the Avaya Equinox 3.2 FP1, the following documents have been updated on the support site: Guide Using Avaya Equinox for Android, ios, Mac, and Windows Planning for and Administering Avaya Equinox for Android, ios, Mac, and Windows Avaya Equinox Overview and Specification for Android, ios, Mac, and Windows Link https://downloads.avaya.com/css/p8/documents/101041273 https://downloads.avaya.com/css/p8/documents/101041276 https://downloads.avaya.com/css/p8/documents/101041278 End user documentation for Avaya Equinox 3.2 FP1 Clients is available into the following G14 languages: English French Italian German Russian Simplified Chinese Japanese Korean Latin American Spanish Brazilian-Portuguese Documentation errata None. Notes 31
Avaya Equinox 3.2 Notes Localization For the Avaya Equinox 3.2 FP1 clients, the following languages are supported: Equinox - Equinox - Equinox - Equinox - Language Windows Mac OS ios Android English Supported Supported Supported Supported German Supported Supported Supported Supported French Supported Supported Supported Supported Spanish Supported Supported Supported Supported Italian Supported Supported Supported Supported Japanese Supported Supported Supported Supported Korean Supported Supported Supported Supported Portuguese Supported Supported Supported Supported Russian Supported Supported Supported Supported Simplified Chinese Supported Supported Supported Supported Traditional Chinese Supported Supported Supported Supported Czech Supported Supported Supported Supported Danish Supported Supported Supported Supported Hungarian Supported Supported Supported Supported Norwegian Supported Supported Supported Supported Dutch Supported Supported Supported Supported Polish Supported Supported Supported Supported Swedish Supported Supported Supported Supported Notes 32
Contacting support Contact Support Checklist If you are having trouble with an Equinox Client, you should: 1. Set log level to debug. 2. Retry the action. Carefully follow the instructions in written or online documentation. 3. Check the documentation that came with your hardware for maintenance or hardware-related problems. 4. Note the sequence of events that led to the problem and the exact messages displayed. Have the Avaya documentation available. If you continue to have a problem, contact Avaya Technical Support: 1. Log in to the Avaya Technical Support Web site https://support.avaya.com. 2. Contact Avaya Technical Support at one of the telephone numbers in the Support Directory listings on the Avaya support Web site. Avaya Global Services Escalation Management provides the means to escalate urgent service issues. For more information, see the Escalation Contacts listings on the Avaya Web site. Contact Support Tasks You may be asked to email one or more files to Technical Support for analysis of your application and its environment.
Avaya Equinox 3.2 Notes Appendix A: Acronyms AAC AADS AMM ASBCE BLA CM FP MDA POM PS SM SMGR SP SRTP TOM 3PCC TLS Avaya Aura Conferencing Avaya Aura Device Services Avaya Multimedia Messaging Avaya Session Border Controller for Enterprise Bridged Line Appearance Avaya Aura Communication Manager Feature Pack Multiple Device Access Presentation Only Mode Avaya Aura Presence Services Avaya Aura Session Manager Avaya Aura System Manager Service Pack Secure Real-Time Transport Protocol Top of Mind Third Party Call Control Transport Layer Security Notes 34