AVAYA Workplace Client Windows Release User Manual

June 1, 2024
Avaya

**AVAYA Workplace Client Windows Release User Manual

**

INSTALLATION INSTRUCTION

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 in varying mediums which may include product information, operating instructions and performance specifications that are generally made available to users of 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 or on the express behalf of 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 Avaya hardware and  software. 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: https://support.avaya.com/helpcenter/getGenericDetails? detailId=C20091120112456651010 under the link “Warranty & Product Lifecycle” or such successor site as designated by Avaya. Please note that if You acquired the product(s) from an authorized Avaya Channel Partner outside of the United States and Canada, the warranty is provided to You by said Avaya Channel Partner and not by Avaya.

“Hosted Service” means an Avaya hosted service subscription that You acquire from either Avaya or an authorized Avaya Channel Partner (as applicable) and which is described further in Hosted SAS or other service description documentation regarding the applicable hosted service. If You purchase a Hosted Service subscription, the foregoing limited warranty may not apply but You may be entitled to support services in connection with the Hosted Service as described further in your service description documents for the applicable Hosted Service. Contact Avaya or Avaya Channel Partner (as applicable) for more information.

Hosted Service

THE FOLLOWING APPLIES ONLY IF YOU PURCHASE AN AVAYA HOSTED SERVICE SUBSCRIPTION FROM AVAYA OR AN AVAYA CHANNEL PARTNER (AS APPLICABLE), THE TERMS OF USE FOR HOSTED SERVICES ARE AVAILABLE ON THE AVAYA WEBSITE, HTTPS://SUPPORT.AVAYA.COM/LICENSEINFO UNDER THE LINK “Avaya Terms of Use for Hosted Services” OR SUCH SUCCESSOR SITE AS DESIGNATED BY AVAYA, AND ARE APPLICABLE TO ANYONE WHO ACCESSES OR USES THE HOSTED SERVICE. BY ACCESSING OR USING THE HOSTED SERVICE, OR AUTHORIZING OTHERS TO DO SO, YOU, ON BEHALF OF YOURSELF AND THE ENTITY FOR WHOM YOU ARE DOING SO (HEREINAFTER REFERRED TO INTERCHANGEABLY AS “YOU” AND “END USER”), AGREE TO THE TERMS OF USE. IF YOU ARE ACCEPTING THE TERMS OF USE ON BEHALF A COMPANY OR OTHER LEGAL ENTITY, YOU REPRESENT THAT YOU HAVE THE AUTHORITY TO BIND SUCH ENTITY TO THESE TERMS OF USE. IF YOU DO NOT HAVE SUCH AUTHORITY, OR IF YOU DO NOT WISH TO ACCEPT THESE TERMS OF USE, YOU MUST NOT ACCESS OR USE THE HOSTED SERVICE OR AUTHORIZE ANYONE TO ACCESS OR USE THE HOSTED SERVICE.

Licenses

THE SOFTWARE LICENSE TERMS AVAILABLE ON THE AVAYA WEBSITE, https://support.avaya.com/LICENSEINFO, UNDER THE LINK “AVAYA SOFTWARE LICENSE TERMS (Avaya Products)” OR SUCH SUCCESSOR SITE AS DESIGNATED BY AVAYA, ARE APPLICABLE TO ANYONE WHO DOWNLOADS, USES AND/OR INSTALLS AVAYA SOFTWARE, PURCHASED FROM

AVAYA INC., ANY AVAYA AFFILIATE, OR AN AVAYA CHANNEL PARTNER (AS APPLICABLE) UNDER A COMMERCIAL AGREEMENT WITH AVAYA OR AN AVAYA CHANNEL PARTNER. 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 CHANNEL PARTNER; 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 OTHERS TO 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. “Software” means computer programs in object code, provided by Avaya or an Avaya Channel Partner, whether as stand-alone products, pre-installed on hardware products, and any upgrades, updates, patches, bug fixes, or modified versions thereto. “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. “Instance” means a single copy of the Software executing at a particular time: (i) on one physical machine; or (ii) on one deployed software virtual machine (“VM”) or similar deployment.

License types

Concurrent User License (CU). End User may install and use the Software on multiple Designated Processors or one or more Servers, so long as only the licensed number of Units are accessing and using the Software at any given time as indicated in the order, Documentation, or as authorized by Avaya in writing. A “Unit” means the unit on which Avaya, at its sole discretion, bases the pricing of its licenses and can be, without limitation, an agent, port or user, an e-mail or voice mail account in the name of a person or corporate function (e.g., webmaster or helpdesk), or a directory entry in the administrative database utilized by the Software that permits one user to interface with the Software. Units may be linked to a specific, identified Server or an Instance of 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 is the software contained within the list of Heritage Nortel Products located at https://support.avaya.com/LicenseInfo/ under the link “Heritage Nortel Products,” or such successor site as designated by Avaya. 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 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, Hosted Service, or hardware provided by Avaya. All content on this site, the documentation, Hosted Service, 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.

Virtualization

The following applies if the product is deployed on a virtual machine. Each product has its own ordering code and license types. Note that each Instance of a product must be separately licensed and ordered. For example, if the end user customer or Avaya Channel Partner would like to install two Instances of the same type of products, then two products of that type must be ordered.

Third Party Components

“Third Party Components” mean certain software programs or portions thereof included in the Software or Hosted Service 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”). As required, 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 products, Documentation or on Avaya’s website at:  https://support.avaya.com/Copyright or such successor site as designated by Avaya. The open source software license terms provided as Third Party Terms are consistent with the license rights granted in these Software License Terms, and may contain additional rights benefiting You, such as modification and distribution of the open source software. The Third Party Terms shall take precedence over these Software License Terms, solely with respect to the applicable Third Party Components, to the extent that these Software License Terms impose greater restrictions on You than the applicable Third Party Terms.

The following applies only if the H.264 (AVC) codec is distributed with the product. THIS PRODUCT IS LICENSED UNDER THE AVC PATENT PORTFOLIO LICENSE FOR THE PERSONAL USE OF A CONSUMER OR OTHER USES IN WHICH IT DOES NOT RECEIVE REMUNERATION TO (i) ENCODE VIDEO IN COMPLIANCE WITH THE AVC STANDARD (“AVC VIDEO”) AND/OR (ii) DECODE AVC VIDEO THAT WAS ENCODED BY A CONSUMER ENGAGED IN A PERSONAL ACTIVITY AND/OR WAS OBTAINED FROM A VIDEO PROVIDER LICENSED TO PROVIDE AVC VIDEO. NO LICENSE IS GRANTED OR SHALL BE IMPLIED FOR ANY OTHER USE. ADDITIONAL INFORMATION MAY BE OBTAINED FROM MPEG LA, L.L.C. SEE HTTP://WWW.MPEGLA.COM

Service Provider

THE FOLLOWING APPLIES TO AVAYA CHANNEL PARTNER’S HOSTING OF AVAYA PRODUCTS OR SERVICES. THE PRODUCT OR HOSTED SERVICE MAY USE THIRD PARTY COMPONENTS SUBJECT TO THIRD PARTY TERMS AND REQUIRE A SERVICE PROVIDER TO BE INDEPENDENTLY LICENSED DIRECTLY FROM THE THIRD PARTY SUPPLIER. AN AVAYA CHANNEL PARTNER’S HOSTING OF AVAYA PRODUCTS MUST BE AUTHORIZED IN WRITING BY AVAYA AND IF THOSE HOSTED PRODUCTS USE OR EMBED CERTAIN THIRD PARTY SOFTWARE, INCLUDING BUT NOT LIMITED TO MICROSOFT SOFTWARE OR CODECS, THE AVAYA CHANNEL PARTNER IS REQUIRED TO INDEPENDENTLY OBTAIN ANY APPLICABLE LICENSE AGREEMENTS, AT THE AVAYA CHANNEL PARTNER’S EXPENSE, DIRECTLY FROM THE APPLICABLE THIRD PARTY SUPPLIER.

WITH RESPECT TO CODECS, IF THE AVAYA CHANNEL PARTNER IS HOSTING ANY PRODUCTS THAT USE OR EMBED THE G.729 CODEC, H.264 CODEC, OR H.265 CODEC, THE AVAYA CHANNEL PARTNER ACKNOWLEDGES AND AGREES THE AVAYA CHANNEL PARTNER IS RESPONSIBLE FOR ANY AND ALL RELATED FEES AND/OR ROYALTIES. THE G.729 CODEC IS LICENSED BY SIPRO LAB TELECOM INC. SEE WWW.SIPRO.COM/CONTACT.HTML. THE H.264 (AVC) CODEC IS LICENSED UNDER THE AVC PATENT PORTFOLIO LICENSE FOR THE PERSONAL USE OF A CONSUMER OR OTHER USES IN WHICH IT DOES NOT RECEIVE REMUNERATION TO: (I) ENCODE VIDEO IN COMPLIANCE WITH THE AVC STANDARD (“AVC VIDEO”) AND/OR (II) DECODE AVC VIDEO THAT WAS ENCODED BY A CONSUMER ENGAGED IN A PERSONAL ACTIVITY AND/OR WAS OBTAINED FROM A VIDEO PROVIDER LICENSED TO PROVIDE AVC VIDEO. NO LICENSE IS GRANTED OR SHALL BE IMPLIED FOR ANY OTHER USE. ADDITIONAL INFORMATION FOR H.264 (AVC) AND H.265 (HEVC) CODECS MAY BE OBTAINED FROM MPEG LA, L.L.C. SEE HTTP://WWW.MPEGLA.COM.

Compliance with Laws

You acknowledge and agree that it is Your responsibility for complying with any applicable laws and regulations, including, but not limited to laws and regulations related to call recording, data privacy, intellectual property, trade secret, fraud, and music performance rights, in the country or territory where the Avaya product is used.

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: https://support.avaya.com, or such successor site as designated by Avaya.

Security Vulnerabilities
Information about Avaya’s security support policies can be found in the Security Policies and Support section of  https://support.avaya.com/security Suspected Avaa product security vulnerabilities are handled per the Avaya Product Security Support Flow[(https://support.avaya.com/css/P8/documents/100161515](http://\(https://support.avaya.com/css/P8/documents/100161515)

Downloading Documentation
For the most current versions of Documentation, see the Avaya Support website: https://support.avaya.com, or such successor site as designated by Avaya.

Contact Avaya Support

See the Avaya Support website: https://support.avaya.com for product or Hosted Service notices and articles, or to report a problem with your Avaya product or Hosted Service. For a list of support telephone numbers and contact addresses, go to the Avaya Support website: https://support.avaya.com/ (or such successor site as designated by Avaya), scroll to the bottom of the page, and select Contact Avaya Support.

Trademarks

The trademarks, logos and service marks (“Marks”) displayed in this site, the Documentation, Hosted Service(s), and product(s) provided by Avaya are the registered or unregistered Marks of Avaya, its affiliates, its licensors, its suppliers, 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, Hosted Service(s) 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.

Linux® is the registered trademark of Linus Torvalds in the U.S. and other countries.

Change history

Issue Date Description
1.0 02/27/2024 3.36 GA issue for the Avaya Workplace Windows Client.
1.0 01/08/2023 3.35.1 GA issue for the Avaya Workplace Windows Client.
1.0 10/28/2023 3.35 GA issue for the Avaya Workplace Windows Client.
1.0 06/27/2023 3.34 GA issue for the Avaya Workplace Windows Client.

Introduction

This document provides late-breaking information to supplement the Avaya Workplace Windows Client 3.36 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® 8.1.3.x / 10.2.x Release Notes for information specific to the Avaya Aura® feature and service packs.

Documentation Catalog

The Documentation Catalog document lists down the various guides that are available for the Avaya Aura® solution. For details see https://downloads.avaya.com/css/P8/documents/101050513

Product Release Matrix

Product Name Release
Avaya Workplace for Windows 3.36.0.137
Avaya Workplace for MacOS 3.36.0.137
Avaya Workplace for Android 3.36.0.137
Avaya Workplace for iOS 3.36.0.137

What’s new in Avaya Workplace for Windows

Release 3.36

In addition to bug fixes, the following new features are provided with the 3.36 release.

  • Copy name/number of active call appearance to clipboard
  • Support of Pexip meeting link in Workplace client & Pexip meeting under Workplace meeting
  • Display Authorization credential pop up always on top of all applications
  • Support for Repositioning call notification pop-up window
  • User controlled enable-disable of auto-answer calls
  • Dell dynamic config of Telecommuter number for Workplace thru AADS config
  • Workplace button module labels edit option
  • Basic 3PCC Support in Other phone mode
  • Support for individual URL to video tutorials
  • Support detaching Dialpad
  • Enlarge Incoming Call Pop up notification
  • Display dummy station in near end call logs after finishing Send-NN call
  • User support switch between Button module and Feature manager
  • Restrict Users from entering duplicate telecommuter number.

Pre-Installation Requirements
In order to install the Avaya Workplace Windows Client on your Windows device, you need to have the Microsoft
.NET Framework version 4.8 installed. The download link for .NET Framework 4.8 is available
at https://dotnet.microsoft.com/download/dotnet-framework/net48.

Note:
As Microsoft has ended support for Windows7, WindowsServer2008 and 2008R2, upcoming releases of Workplace for Windows from 3.13 onwards will no longer support these operating systems. In addition, from 3.13, the click-to call browser extension will no longer be provided for the Internet Explorer web browser and Windows 8, Windows 8.1 operating systems also will not be supported.

Microsoft has ended Mainstream Support for Windows Server 2012 and Windows Server 2012 R2 as of October 2018. Due to benefits related to using modern Windows 10 APIs, upcoming releases of Workplace for Windows from 3.15 onwards will no longer support these operating systems.

Compatibility
For the latest and most accurate compatibility information, go to
https://support.avaya.com/CompatibilityMatrix/Index.aspx.

Contacting support

Contact support checklist
If you are having trouble with an Avaya product, you should:

  1. Retry the action. Carefully follow the instructions in written or online documentation.

  2. Check the documentation that came with your hardware for maintenance or hardware-related problems.

  3. Note the sequence of events that led to the problem and the exact messages displayed. Have the Avaya documentation available.
    If you continue to have a problem, contact Avaya Technical Support:

  4. Log in to the Avaya Technical Support Web site https://support.avaya.com.

  5. 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 Support site.

Contact support tasks
You may be asked to email one or more files to Technical Support for analysis of your application and its environmen.

Avaya Workplace for Windows

Required artifacts for Avaya Workplace for Windows Release 3.36
The following section provides Avaya Workplace for Windows Release 3.36 downloading information. For installation and upgrade procedure, see documents mentioned in Installation and Upgrade note. Client/Server| Artifact| Notes
---|---|---
Avaya Workplace for Windows| 3.36.0.137| Date Available: Feb 27, 2024

Required patches
For information about patches and product updates, see the Avaya Technical Support Web site
https://support.avaya.com.


New Configuration Parameters
The following new configuration parameters have been added to the 3.36 release for Avaya Aura .

Description| Client UI setting name| Avaya Workplace Client Platform Support
---|---|---
TC_NUMBER
Setting to define which Telecommuter number is used in Other Phone Mode. Admin can set only one number under this setting. This property support with Locked and obscured preference.
Default value: Blank| No client UI| Windows
ACTIVATE_OTHERPHONE_MODE_ON_STARTUP
Settings for enabling Other phone (Telecommuter) mode on startup 0 (default): Other phone mode login on startup not allowed1: User will login into Other phone mode on startup without needing to login first in This computer
Default value: 0| No client UI| Windows
ENABLE_EDIT_BUTTON_LABEL| |
Property to define if Edit layout and labels option should be available or not1 (Default): User would see ‘Button Module Options and Settings’ button on Button Module. User can use Edit layout and labels from it

0: User will not see ‘Button Module Options and Settings’ button on button module. In turn, user cannot use Edit layout and labels for configured features.Default value: 1

| No client UI| Windows

DISPLAY_AUTH_POPUP_ON_TOP| |
---|---|---
Setting to define authorization credential pop up window behavior, whether to display always on top of other applications or open in background as per current behavior
1: Always display Auth pop up on top of all other applications (default) 0: Display auth pop up as per current implementationDefault value: 1| No client UI| Windows
ONLINE_HELP_URL| |
Setting to define customized video tutorial link as per orgnization needs. This property should work in conjunction with ONLINE_HELP_ENABLED
Default value: Blank| No client UI| Windows
ENABLE_PEXIP| |
Setting to control display of Pexip meetings under ‘Meetings’ tab 0: Pexip is disabled (Default)1: Pexip is enabled
Default value: 0| No client UI| Windows
PEXIP_URL| |
Setting to configure Pexip URL for the user
Default value: Blank| No client UI| Windows
ENLARGE_INCOMING_CALL_NOTIFICATION| |
Property to control display of incoming call notification size 1: Display enlarged incoming call notification0 (default): Display normal size incoming call notifications
Default value: 0| No client UI| Windows
SIP_RESPONSE_TIMEOUT| |
Setting specific for MEGA like deployments in order to provide configurable option for response time out in seconds
Range: 32-128
Default: 32 (sec)| No client UI| Windows
SIP_MAINTENANCE_TEST_TIMEOUT| |
Property for Timeout for completion (in seconds) of test used to check the connectivity to signaling server.
Default: 3| No client UI| Windows

OUTLOOK_SEND_ERROR_POPUP| |
---|---|---
Property to define whether the send error popup feature is enabled or not. 0 indicates that the feature is disabled and 1 indicates that the feature is enabled.
Default value: 0| No client UI| Windows

For Avaya Workplace Client 3.36, the following JSON document is available:
http://downloads.dlavaya.com/AvayaAuraDeviceServices/AvayaAuraDeviceServices_misc/20240227_dynamicC onfigUpload.txt fileExt=.txt&dlmt=1584654589_d8d6c9761e14e4712cd837a016a5ef4c which can be used
to update Avaya Aura Device Services with new auto-configuration parameters supported in release 3.36.

Avaya Calling for Microsoft Teams

The Avaya Calling for Microsoft Teams makes use of the Avaya call application available in the Microsoft teams application store. The Avaya Call app provides contact information and dial pad within Microsoft teams. Users can click to dial from Microsoft teams with this solution. To have this setup users need to have the pre requisites setup before logging into the Avaya Call app

Product Release Matrix

_ Note: _The About screen on the application will display the version as 1.0.12. It is the Microsoft Teams manifest file version and corresponds to the current version of Avaya Calling Application.

What’s new in Avaya Calling for Microsoft Teams

Release 1.2.1
The following features are provided with the Avaya Calling for Microsoft Teams release 1.2.1:

  • Support for Traditional Chinese language.

Release 1.2
The following features are provided with the Avaya Calling for Microsoft Teams release 1.2:

  • Adding Contact through Enterprise Search and mark it as Favourite.
  • Display additional contact numbers through the ellipsis or Display name or picture.
  • Office 365 Contacts Enterprise Search.
  • Option to disable video through Settings file
  • Support for Danish, Norwegian and Swedish languages.
  • Tooltips for better readability and accessibility.

Pre-Installation Requirements
The Avaya Calling for Microsoft Teams has the following pre-installation requirements –

  • Avaya Aura Device Services 8.0.1 or above.
  • Avaya Workplace Client (3.13 or above) installed.

Documentation & Localization

Avaya Documentation Center ‘

Customer documentation for Avaya Workplace Client is now available on the Avaya Documentation Center at http://documentation.avaya.com/ .

Guide

|

|

Localized

---|---|---

Using Avaya Workplace Client for Android, iOS, Mac, and Windows

|

Using_Avaya_Workplace_Client_Android_iOS_Mac_Windows

|

Yes

Avaya Workplace Client              Quick Reference Guide

|

Avaya_Workplace_Client_QRG

|

Yes

**Planning for and Administering Ava ya Workplace Client for Android,

iOS, Mac, and Windows**

|

Planning_Administering_Avaya_Workplace_Client_Android_iOSMac Windows

| No
Avaya Workplace Client Overview and Specification for Android, iOS, Mac, and Windows| Avaya_Workplace_Client_Overview_Specification_Android_iOSMac Windows| No
---|---|---

These are links to the English versions of the document.
Localized versions of the above documents will be available post-GA in the following G14 languages:

  • French
  • Italian
  • German
  • Russian
  • Simplified Chinese
  • Japanese
  • Korean
  • Latin American Spanish
  • Brazilian-Portuguese

Documentation errata
None

Localization
For the Avaya Workplace Client UI, the following languages are supported:

  • English
  • German
  • French
  • Lat-Spanish
  •  Italian
  • Japanese
  • Korean
  • Brazilian-Portuguese
  • Russian
  • Simplified Chinese
  • Czech
  • Dutch
  • Polish
  • Swedish
  • Danish
  • Hungarian
  • Norwegian
  • Indonesian
  • Turkish
  • Traditional Chines
  • Malaysian
  • Thai
  • Hebrew
  • Arabic (Windows only)

Troubleshooting the installation
Support for Avaya Workplace is available through Avaya Technical Support.
If you encounter trouble with Avaya Workplace:

  1. Retry the action. Follow the instructions in written or online documentation carefully.
  2. Check the documentation that came with your hardware for maintenance or hardware-related problems.
  3. Note the sequence of events that led to the problem and the exact messages displayed. Have the Avaya  documentation available.
  4. If you continue to have a problem, contact Avaya Technical Support by:
    a. Logging on to the Avaya Technical Support Web site http://www.avaya.com/support
    b. Calling or faxing Avaya Technical Support at one of the telephone numbers in the Support Directory listings on the Avaya support Web site.

You may be asked to email one or more files to Technical Support for analysis of your application and its
environment.

Note: If you have difficulty reaching Avaya Technical Support through the above URL or email address, go to
http://www.avaya.com for further information. When you request technical support, provide the following information:

  • Configuration settings, including Avaya Workplace for Windows configuration and browser settings.
  • Usage scenario, including all steps required to reproduce the issue.
  • Screenshots, if the issue occurs in the Administration Application.
  • Copies of all logs related to the issue.
  • All other information that you gathered when you attempted to resolve the issue.

Tip: 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. For information about patches and product updates, see the Avaya Technical Support Web site  https://support.avaya.com.

Known issues and workarounds in Avaya Workplace for Windows Release 3.36 and Avaya Calling 1.2

The following table lists the Avaya Workplace known issues for this release:

ID Minimum conditions Visible symptoms Workaround
ACW-24799 Outlook        add-in: Meeting         Plugin converted
Appointment (part ofrecurring Appointment) does The user is not able to

convert the part of the recurring appointment into a meeting. Entire recurring appointment is getting  converted  into| No workaround.
ID| Minimum conditions| Visible symptoms| Workaround
---|---|---|---
| not get created on iView.| meetings    without    any issue.|
ACW-24123| Upgrade occurred from Avaya Workplace client for Windows 3.26.When Workplace client 3.26 was installed and closed before the upgrade, user has muted a speaker device using Windows Volume Controls or keypad.
This issue is not reproducible                          forupgrade from release     3.25     orbelow     to     3.26.2 release directly.| When user unmute the speaker device in the same way using Windows Volume Controls or keypad, playback from Workplace client is still muted in Windows.User is not able to hear audio notifications from Workplace or remote participant(s) when a call is established.| User needs to unmute the Workplace client application in Windows Volume Mixer once.To open the volume mixer, navigate to the taskbar and right click on speaker icon. In the opened menu select “Open Volume Mixer”, find Workplace application and click unmute.
Not Applicable| Workplace   3.26installed            with VDIENV=1 on  aVMware Horizon virtualdesktop. Workplace VDI is configured and running on the local desktop.| Launching Workplace on the virtual desktop fails to perform paired sign-in of the Workplace VDI application running on the local desktop.| Remain on Workplace 3.25 or earlier, or manually sign into Workplace VDI as required.
ACW-24286| Workplace registered          with Messaging services| Audio or Video recorded files not available while moving window while recording is going on| Set the conversation screen at one place on the  screen  and  then start record audio/video. Do not move the conversation screen when recording audio/video is in progress.
ACW-22957| Workplace            is registered             in Desk Phone mode with J1xx / AAfD| UUI Info button is greyed out after Network recovery| None
ACW-21197| Windows machine keyboard           and Workplace Client are set to Arabic language| The entered digit message is cut off and not displayed the same as what the user typed.| None
ACW-21298| Font style/format apply by right click context menu| Font- format    does    not apply on typing.| Format the text after typing and before sending

ID Minimum conditions Visible symptoms Workaround
ACW-20942 Windows version 1803 – System set as Arabic language
Languages not applied Upgrade Windows to the current released version.

The following table lists the MS Teams known issues for this release:

ACW-22292| Workplace and MS            Teams installed and logged. Log into Avaya Call using invalid credentials| When          any         new contact/updated/deleted from Workplace when the network is down, user would not see the updatesin     Avaya     Call     after network recovery.| Reload Avaya Call.
---|---|---|---
UCAPM- 28732| Workplace and MS            Teams installed and logged. Log into Avaya Call using invalid credentials| MS Teams pop-up appears to enter credentials. Though the user enters correct credentials in it, those won’t be taken up and this pop-up keeps appearingafter a few seconds of interval.| Logout of the MS Teams. (This will close the authentication pop up as well) and login back. Then log into Avaya Call Assistant with valid credentials.
ACW-22501| Workplace and MS            Teams installed    andlogged in on Browser.| Avaya Call icon is not display when MS Teams- Avaya Call. This is known issues from MS for anycustom apps.| None

Fixes in Avaya Workplace for Windows Release 3.36

The following table lists the fixes in this release:

ID Minimum Conditions Visible symptoms Release found in
ACW-24946 Avaya Workplace for Windows installed and logged in Agent
mode AGTGREETINGSTAT value does not apply immediately for the first time if
user changes it from configdata.xml file 3.34
ACW-24893 Avaya Workplace for Windows installed and configured

Workplace Windows should open the existing conversation, if AMM is initiated from Contact details screen, similar to other platforms| 3.34
ACW-25040| Avaya Workplace for Windows installed and logged in Agent mode| Workplace crashed on login with Agent CC, specifically after trying to acquire WebLM license| 3.34.1
ACW-25130| Avaya Workplace for Windows installed and logged in Agent mode| Call transfer failed error displayed when user tries to transfer a held call to active call using drag-drop, Transfer is successful, but errormessage is  displayed  Avaya| 3.33
| | workplace high CPU utilization on windows server|
---|---|---|---
ACW-25014| Avaya Workplace for Windows installed and logged in telecommuter mode| If the same phone number is stored multiple times for Telecommuter mode (User settings –> Other phones), after the switch to Telecommuter mode (Other phone) Avaya Workplace (Windows) freezes or after restarting the application, the application hang| 3.34.1
ACW-25094| Avaya Workplace for Windows installed and configured user browser extension| The contact numbers starting from 272, 346 & 849 were not getting highlighted for the US. These area codes were not present in the dial code rules.Fixed this issue by adding these area codes in the dial code rules of the US.| 3.32
ACW-24766| Outlook plugin: Deletion or modification of a meeting created by the secretary for the boss is not possible by the boss user himself.| There was a dependency of Boss’s/Secretary’s Outlook plugin on other person’s Outlook Plugin to modify or delete the meetings created by Boss/Secretary| 3.32
ACW-24695| Outlook plugin: Changing existing meeting (Prepone or Postpone) time not syncing with the meetings server.| User was not aware about the login state of the plugin which is why any updates to the meetings were not updated to the server.| 3.33
ACW-24680| Outlook plugin: Meeting will not sync to the Meetings Server because Boss Plugin cannot sync calendar.| User is not aware that the Outlook plugin has logged out from connectivity to AAWG due to various reasons including token expiry/ cache clearance/ plugin logout/ server not reachable.| 3.32
ACW-24960| Outlook plugin adds junk lines to the invitation.| There is a marker line added to the start of the email template. This marker line generates a lot of noise when the meeting template is read by the narrator. Fixed this issue by reducing the number of equal signs.| 3.32
ACW-24978| Outlook Plugin – HTTP 400 errors on updating recurring meetings.| There are HTTP errors observed in plugin logs while updating the recurring invite. Fixed the HTTP errors.| 3.32
ACW-25031| New SP with updated plug – in/manifest is causing Outlook exception when sending email by content menu.| User is getting an error popup while performing actions with the recent service pack. Fixed this issue in this service pack.| 3.32.1
ACW-25041| Avaya Workplace for Windows installed, configured, and registered as primary to SM1 and secondary to SM2 and logged in Agent mode.| Agent state stuck to Ready state after Workplace Agent answer agent call and Primary SM fails over to secondary| 3.34.1
ACW-25015| Avaya Workplace for Windows installed and configured in MDA with J179| Workplace login as MDA with J179 updated J1xx blob customization, so J179 shows duplicated buttons| 3.34
---|---|---|---
ACW-25157| Avaya Workplace for Windows installed, configured and uses JAWS as narrator| Focus should remain on Call Appearance if transfer or conference operation failed and user click on OK for error notification, focus goes on ‘Options and Settings’| 3.36

Fixes in Avaya Calling 1.2

ACW-23163| Avaya Calling installed, try searching by Phone number in the Enterprise search for Avaya Contacts and Favorites| Enterprise contacts are not displayed in search result when user enter number with spaces on Avaya Calling.| 1.2
---|---|---|---
ACW-22903| Avaya Calling installed.| Insufficient logging in Avaya Call App for O365 contact related issues and some of the failures.| 1.2
ACW-22902| Avaya Calling installed, try searching with exact strings in the Local search for Avaya Contacts and Favorites| User needs to enter complete and exact string to get the contact| 1.2
ACW-22819| Avaya Calling installed, try searching by Phone number in the Local search for Avaya Contacts and Favorites| Phone number search for local contacts only works with exact number format| 1.1

Appendix A: Acronyms

Acronym Definition
3PCC Third Party Call Control
AAC Avaya Aura® Conferencing
AADS Avaya Aura® Device Services
AAWG Avaya Aura® Web Gateway
AEMO Avaya Equinox® Meetings Online
AMM Avaya Multimedia Messaging
APNS Apple Push Notification Service
ASBCE Avaya Session Border Controller for Enterprise
BLA Bridged Line Appearance
CM Avaya Aura® Communication Manager
EC500 Extension to Cellular
FIPS Federal Information Processing Standards
FP Feature Pack
GA Generally Available
IdP Identity Provider
IM Instant Message
IPv6 Internet Protocol version 6
IX Intelligent Experience
LDAP Lightweight Directory Access Protocol
MDA Multiple Device Access
MSS Multi-Stream Switching
OAUTH Open Authorization
--- ---
OTT Over The Top
PLC Packet Loss Concealment
POM Presentation Only Mode
PS Avaya Aura® Presence Services
SAML Security Assertion Mark-up Language
SBC Session Border Controller
SIP Session Initiation Protocol
SM Avaya Aura® Session Manager
SMGR Avaya Aura® System Manager
SP Service Pack
SRTP Secure Real-Time Transport Protocol
SSO Single Sign-On
TOM Top of Mind
TLS Transport Layer Security
UC Unified Communication
URI Uniform Resource Identifier
USB Universal Serial Bus
VDI Virtual Desktop Infrastructure

References

Read User Manual Online (PDF format)

Read User Manual Online (PDF format)  >>

Download This Manual (PDF format)

Download this manual  >>

Related Manuals