Equinox Clients 3.2 Notes Issue 1.1 September 26, 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... 5 Introduction... 5 Installation... 6 Product compatibility... 6 Recommended Minimum Load Line-up Requirements for Avaya Aura Core... 6 Product Matrix... 6 Deployment Considerations... 6 What's new... 8 3.2... 8 Fixes... 10 3.2... 10 Windows Client... 10 MacOS Client... 10 Android Client... 11 ios Client... 11 Known issues and workarounds... 13 3.2... 13 Windows Client... 13 MacOS Client... 16 Android Client... 17 ios Client... 18 Documentation & Localization... 20
Documentation errata... 20 Using Avaya Equinox for Android, ios, Mac, and Windows Document... 20 Planning for and Administering Avaya Equinox for Android, ios, Mac, and Windows Document. 21 Localization... 23 Contacting support... 24 Contact Support Checklist... 24 Contact Support Tasks... 24 Appendix A: Acronyms... 25 Notes 4
Change History Date Description 7/10/2017 July GA update for the Equinox 3.2 Clients. 9/26/2017 Recommended Minimum Load-Line-up Requirements for Avaya Aura Core expanded to indicate this is the best experience and that earlier releases are supported. Introduction This document provides late-breaking information to supplement the Avaya Equinox Clients 3.2 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 5
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 The following releases are recommended for the best experience. For supported earlier releases consult the compatibility matrix referenced above. 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 Matrix The following table lists the release build numbers of the Avaya Equinox clients and required infrastructure servers. Client/Server Build Number Date Available Avaya Equinox for Windows 3.2.0.33 10 July 2017 Avaya Equinox for MacOS 3.2.0.16 10 July 2017 Avaya Equinox for Android 3.2.0.54 10 July 2017 Avaya Equinox for ios 3.2.0.43 10 July 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.0 Build 412 10 July 2017 Deployment Considerations Although end user impact is expected to be minimal with this update, please be advised of the following: 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 6
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 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. Updated Microsoft Outlook Plugin 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 Documentation errata section related to configuration and requirements for this new Add-In. Notes 7
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 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 8
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 9
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 Windows Client Fixed in ACW-10286 Unable to Hold and then Resume a call via the headset while an 3.1 3.2 incoming call is answered on one MDA device while bridged in from another device. ACW-10313 Calendar meetings not showing even though Outlook is running. 3.1 3.2 Workaround: Restart the Outlook client. ACW-10399 Equinox Windows crashed for participant joining an AAC 3.2 conference with ~200 participants while sharing a.pdf file ACW-10437 Avaya Browser Extension is adding additional "0" between 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.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 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.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-11490 Bridged Lines do not respect Bridge Call Alerting and Per-Button 3.1 3.2 Ring Control settings MacOS Client Fixed in ACMACOS-2982 Incoming calls that were transferred by another client inconsistently present the called party and transferred by 3.2 Notes 10
Fixed in 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.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.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.2 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.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 3.2 Notes 11
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. 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.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.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.2 FI-15756 Product breakage in 3.1 for external calls with caller ID to locked iphone. 3.1 3.2 Notes 12
Known issues and workarounds 3.2 Windows Client Solution issues ACW-3291 Avaya Aura Conference Roster and Video missing if user invokes call hold before conf is not started. ACW-9443 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..0.1 Workaround: Re-join the conference as video or join from equinox first. ACW-11155 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. 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 3.2 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 Notes 13
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). 3. Regenerate AADS certificate 4. On the AADS server, run the configureaads.sh script. Re-run option 1) to re-generate the AADS identity certificate. Be sure to restart the AADS after this step is complete. ACW-11065 With Conf 9.0.2 admin has to configure the TEXT only version in order to support Equinox clients. ACW-11703 Issue on connection from Alpha to OnAvaya Scopia bridge: scopia.avaya.com Intermittent, occurs on OS X. ACW-10797 Equinox client not showing Microsoft Edge sharing content while using application sharing. Workaround: User can select full screen sharing or portion of screen ACW-11498 Auto-config doesn't work for Equinox Conferencing with Team Engagement system. 3.2 3.2 3.1 3.2 Workaround: DNS auto discovery is recommended deployment. Notes 14
Application issues ACW-9107 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. ACW-9105 Avaya Communicator application is terminated without user notification during upgrade to Avaya equinox. Calls in progress may be lost. ACW-9159 ACW-8326 Workaround: Avaya recommends that Avaya equinox upgrades should be scheduled during a maintenance window to minimize end user disruptions. Transferor name is still displayed on the incoming call notification window of instead of transferee name. Workaround: None. Call appearance will be correctly updated if call is answered. Remote Installation of Avaya equinox via Microsoft Windows Group Policy fails. Workaround: Install client locally on each workstation. ACW-6941 H323 Dual Registration client cannot unpark a parked call. ACW-10010 Some Bluetooth headsets turn off the Microphone when selecting the 3.1 Stereo Playback speaker resulting in no audio path in Equinox clients. ACW-10286 Unable to Hold and then Resume a call via the headset while an incoming 3.1 call is answered on one MDA device while bridged in from another device. ACW-11870 Intermittently the screen link search of all the available XT endpoints, the 3.2 PIN for does not get shown on the XT endpoint screen. ACW-10726 ACW-10966 Workaround: Enter empty or invalid PIN to generate one failed attempt and the PIN appears for second attempt. 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. Merge button is disabled when dragging an active call to a held call. Workaround: Drag the held call to the active call 3.2 3.2 Notes 15
MacOS Client Solution issues ACMACOS-7148 BFCP Screen Sharing fails to resume when the retrieving held call. Workaround: User can manually restart BFCP Screen Sharing. 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. Workaround: User must end call and rejoin Avaya Aura Conference. ACMACOS-2741 Audio only outbound call cannot escalate to video between Equinox client & XT5000 H.323. ACMACOS-8509 Enabling the parameter ENFORCE_SIPS_URI is not supported in this 3.2 release. ACMACOS-8423 Pickup of bridge line call after a transfer fails 3.2 ACMACOS-8545 Auto-config doesn't work for Equinox Conferencing with Team 3.2 Engagement system Workaround: DNS auto discovery is recommended deployment. Application issues ACMACOS-7118 Add as favorite is not available for contact that has multiple email addresses defined. ACMACOS-7217 MacOS client crashes when presenter ends conference call from call appearance while collaboration from his end is in progress. ACMACOS-8497 User wil can do directory search on main window and drag the participant to the conversation window. ACMACOS-7990 Garbled outgoing audio when receiving an incoming email to Outlook.0.1 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 Conf 9.0.2 admin has to configure the TEXT only version in order 3.2 Notes 16
to support Equinox clients. Android Client Solution issues FA-3381 When CES is enabled, corporate directory search does not return results if search term is last name and contains a space character. FA-15092 Moderator controls don't work after the moderator's second MDA device hangs up the call (in an Equinox Conference 9.0 enhanced conference). FA-15001 Presence still displays the stale status even after the user has updated it in CES only deployments. FA-9764 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. FA-9586 FA-14399 FA-15038 FA-15215 FA-16249 Workaround: The call is terminated when the remote party terminates the call. Audio only outbound call cannot escalate to video between client & XT5000 H.323. Failed to add participant to Scopia 8.3 conference using the dial in option. Workaround: Participant will need to dial into conference directly. A CCMP-invited participant cannot unmute self after being muted by moderator. 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. The device is only ringing on the speaker, not the bluetooth device for Vantage only..0.1.0.1 3.1.1 Application issues FA-17383 Use of Equinox for initiating outgoing calls or answering incoming calls while 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 handoff if Aura CM version is not 7.1.0.0.0 OR 7.0.1.. FA-12648 Android client in One-X CES call back mode drops call when enforced SRTP is Notes 17
FA-17061 FA-16632 ios Client enabled. Specific to users on Avaya Vantage. Users with Avaya Equinox 3.2 running on Vantage SP0 or later will not observe this issue. 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 3.1.2 3.2 Solution issues FI-13480 Failed to add participant to Scopia 8.3 conference using the dial in option. FI-13665 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. FI-11404 When the One-X CES Server is deployed in multiple CM environments, there may be issues with the display of the call log which may only show the caller number. FI-6669 When CES is enabled, corporate directory search does not return results if search term is last name and contains a space character. 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-13991 A CCMP-invited participant cannot unmute self after being muted by moderator. FI-14776 Outgoing call log is not shown on Boss when Secretary makes a Bridged Line Appearance call for Boss to customer..0.1.0.1.0.1 3.1 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 Conf 9.0.2 admin has to configure the TEXT only version in order to 3.2 Notes 18
support Equinox clients. Application issues 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-11952 Client in One-X CES call back mode drops call when enforced SRTP is enabled. FI-14187 Intermittently, there is no audio path after switching from Enterprise WiFi #1.0.1 to WiFi #2 when the ios user joined as a participant into a Scopia or Equinox Conference. FI-16229 For TCP only connections, for ios clients occasionally login can fail. 3.1.1 Workaround: Retry the login. 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. If the other call is answered and you cannot hold the current call, you may have to dial in again. 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-16380 If user is on a Presentation Only Mode call and makes another outgoing pointto-point call, the point-to-point call does not work. 3.2 3.2 3.2 Workaround: Disable integrated calls or use POM+audio+video call. Notes 19
Documentation & Localization For the Avaya Equinox 3.2, 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.1 Clients is available into the following G14 languages: English French Italian German Russian Simplified Chinese Japanese Korean Latin American Spanish Brazilian-Portuguese Documentation errata Using Avaya Equinox for Android, ios, Mac, and Windows Document Documentation errata 1 The content in the Modifying conference settings and Meetings and Meeting Room field descriptions topics is not up-to-date with the final UX. Especially, for Avaya Equinox for Mac. The Meetings and Meeting Room screens were updated in the UX builds after the content was delivered for 100% localization. This will be addressed in 3.2 FP1. 2 The Desktop Integration pane in Avaya Equinox for Windows was added in the UX builds after the content was delivered for 100% localization. This will be addressed in 3.2 FP1. Notes 20
Planning for and Administering Avaya Equinox for Android, ios, Mac, and Windows Document Documentation errata 1 The Microsoft Group Policy reference is no longer applicable and will be removed from the DSCP values section of Chapter 5: Site preparation. 2 The following note needs to be added to the LDAPv3 support section on page 63: Note: The default directory type used by Avaya Equinox desktop clients is Microsoft Active Directory. If you want to use other directory type, it is mandatory to set DIRTYPE parameter using auto configuration file. For information about the auto configuration options, see the Automatic configuration chapter in this document. 3 The content in Chapter 15: Additional setup options for Avaya Equinox for Windows and Mac Clients is not up-to-date with the new Microsoft Outlook Add-in introduced in this release. The following instructions are needed to configure the Avaya Equinox Microsoft Outlook Add-in: Microsoft Outlook Add-In Avaya Equinox 3.2 provides a new and improved Outlook Add-In for Windows that includes the following features: Add meeting details to an appointment Start and Join conferences from your calendar Avaya Equinox and Avaya Aura Conferencing meeting information can be auto-configured Avaya Equinox Conferencing meeting invite templates are retrieved from the conferencing system Initiate a call from within Outlook to a contact using Avaya Equinox Microsoft Windows IM Provider integration (optional) allowing click to IM and presence in Outlook for Avaya Equinox contacts Requirements: Outlook versions 2010 and greater are supported Exchange Web Services must be enabled to pass configuration information from Avaya Equinox for Windows to the Outlook Add-In As part of the new Outlook Add-In architecture, portions of the Add-In are hosted on the Internet and require Internet access unless hosted internally on the private network along with the OUTLOOK_ADDON_HOST_URI configuration parameter. Installation: The Outlook Add-In is installed by default. Use the custom option in the interactive installer or the silent install parameter described above to disable installation. The Add-In is enabled by default for non-guest users. Notes 21
Configuration for Avaya Equinox Conferencing The following items must be configured for Avaya Equinox Conferencing. It is recommended to use Avaya Aura Device Services to provide per-user configuration parameters. If Avaya Aura Device Services is not used, then end-users will need to update the per-user items in the Services->Meetings settings panel: Item Function Auto Configuration Parameter Setting Name in Services->Meetings Conference Access Number Used to populate the meeting invitation dial-in number for participants. Required for Equinox Conferencing 9.0.1 and older systems (Not required for CONFERENCE_ACCESS_NUMBER Conference Access Number Avaya Equinox Conferencing Portal Address Avaya Equinox Virtual Room Number 9.0.2 systems) Used to populate meeting invitation location field with URL for participants to join the meeting. Used to connect to portal to retrieve meeting invitation template. Used to populate the Meeting ID in the location field Configuration for Avaya Aura Conferencing CONFERENCE_PORTAL_URI CONFERENCE_VIRTUAL_ROOM Portal Address Notes 22 Virtual Room ID The following items must be configured for Avaya Aura Conferencing. It is recommended to use Avaya Aura Device Services to provide per-user configuration parameters. If Avaya Aura Device Services is not used, then end-users will need to update the per-user items in the Services->Meetings settings panel: Item Function Auto Configuration Parameter Setting Name in Services- >Meetings Conference Access Number Additional Access Numbers Used to populate the meeting invitation dial-in number for participants. Provides alternate dial-in numbers in the meeting invite. CONFERENCE_ACCESS_NUMBER ADDITIONAL_CONFERENCE_ACCESS_ NUMBER_LIST Use format: Label1:Number1,Label2:Number2,..., LabelN:NumberN, Conference Access Number N/A
Moderator Code Participant Code Participant URL Used to allow you to start your own meetings Populates meeting template with code for participants to join meetings Populates meeting template and location field with URL to join meeting. CONFERENCE_MODERATOR_CODE CONFERENCE_PARTI CIPANT_CODE CONFERENCE_PARTICIPANT_URL Moderator Code Participant Code Participant URL Localization For the Avaya Equinox 3.1 clients, the following languages are supported (with the below caveat): 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 CAVEAT: The new Microsoft Outlook Add-in is only available in English and German. Other languages will be available in 3.2 FP1. Notes 23
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.
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 25