Avaya Agent for Desktop Release Notes

Transcription

1 Avaya Agent for Desktop Release Notes Release Issue 1.0 April 2018

2 Avaya Inc. All Rights Reserved. Notice While reasonable efforts have been made to ensure that the information in this document is complete and accurate at the time of printing, Avaya assumes no liability for any errors. Avaya reserves the right to make changes and corrections to the information in this document without the obligation to notify any person or organization of such changes. Documentation disclaimer Documentation means information published by Avaya in varying mediums which may include product information, operating instructions and performance specifications that Avaya may generally make available to users of its products and Hosted Services. Documentation does not include marketing materials. Avaya shall not be responsible for any modifications, additions, or deletions to the original published version of documentation unless such modifications, additions, or deletions were performed by Avaya. End User agrees to indemnify and hold harmless Avaya, Avaya's agents, servants and employees against all claims, lawsuits, demands and judgments arising out of, or in connection with, subsequent modifications, additions or deletions to this documentation, to the extent made by End User. Link disclaimer Avaya is not responsible for the contents or reliability of any linked websites referenced within this site or documentation provided by Avaya. Avaya is not responsible for the accuracy of any information, statement or content provided on these sites and does not necessarily endorse the products, services, or information described or offered within them. Avaya does not guarantee that these links will work all the time and has no control over the availability of the linked pages. Warranty Avaya provides a limited warranty on 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: 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. Licenses THE SOFTWARE LICENSE TERMS AVAILABLE ON THE AVAYA WEBSITE, 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, preinstalled 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 type(s) 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. 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 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. 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. 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 Avaya Agent for Desktop Release Notes April

3 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: or such successor site as designated by Avaya. You agree to the Third Party Terms for any such Third Party Components. 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 Note to Service Provider The product or Hosted Service may use Third Party Components subject to Third Party Terms that do not allow hosting and require a Service Provider to be independently licensed for such purpose. It is your responsibility to obtain such licensing. Preventing Toll Fraud Toll Fraud is the unauthorized use of your telecommunications system by an unauthorized party (for example, a person who is not a corporate employee, agent, subcontractor, or is not working on your company's behalf). Be aware that there can be a risk of Toll Fraud associated with your system and that, if Toll Fraud occurs, it can result in substantial additional charges for your telecommunications services. Avaya Toll Fraud intervention If You suspect that You are being victimized by Toll Fraud and You need technical assistance or support, call Technical Service Center Toll Fraud Intervention Hotline at for the United States and Canada. For additional support telephone numbers, see the Avaya Support website: or such successor site as designated by Avaya. Suspected security vulnerabilities with Avaya products should be reported to Avaya by sending mail to: securityalerts@avaya.com. Downloading Documentation For the most current versions of Documentation, see the Avaya Support website: or such successor site as designated by Avaya. Contact Avaya Support See the Avaya Support website: 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: (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, 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. Avaya Agent for Desktop Release Notes April

4 Table of content Table of Content Overview... 5 New Features in Avaya Agent Enhancements in Avaya Agent Prerequisites Interoperability Avaya Aura servers and clients Platforms Deployment and configuration Supported headsets Issues fixed in Avaya Agent for Desktop Known issues in Avaya Agent Avaya Agent for Desktop Release Notes April

5 Overview Avaya Agent for Desktop is a client application for contact centers. An agent can use Avaya Agent for Desktop for handling incoming and outgoing calls, changing work states, and managing other UI controls. However, only an administrator can manage the configurations and settings of the application. Avaya Agent for Desktop supports multiple platforms and is designed to function in the following use cases: Virtual Desktop Infrastructure (VDI): Avaya Agent for Desktop provides a solution to deliver real-time media with VDI support on HP Thinpro and Dell Wyse thin clients such as WES7 and WES8. The operating systems supported on HP Thinpro and DELL Wyse systems are SUSE and Debian Linux. An administrator can use Avaya Agent for Desktop for VDI to enable desktop virtualization that encompasses the hardware and software systems required to support the virtualized environment in a contact center. Standalone Contact Center Client: Avaya Agent for Desktop provides a full set of features for a contact center agent and can be used as a primary client application on Windows 7, Windows 10. Note A new client software has also been designed for Apple Mac for use on the following versions: Mavericks 10.9, Yosemite 10.10, El Capitan 10.11, and Sierra This new software, called Avaya Agent for Desktop for Mac, is specifically developed for contact centers using Mac platform and supports both H.323 and SIP signaling protocols. Avaya Agent for Desktop uses Avaya Aura Communication Manager to store station configuration settings and manage agent profiles locally. You can also choose to use Avaya Control Manager for managing agent profiles. Avaya Agent for Desktop Release Notes April

6 New Features in Avaya Agent Enhanced USB Headset Support Avaya Agent for Desktop Release 1.7 introduces enhanced support for USB Headsets by enabling call control from the headset. This is enabled via OEM provided SDK (Plantronics, Jabra) which must be installed on Windows based deployments. Non-Windows deployments do not require the additional installation of the OEM provided SDK (Mac, Linux). Using headset buttons o Answer a call: A user can answer an incoming call in two ways: o o o NOTE: By pressing a call button on Avaya Agent for Desktop main window. By pressing a physical call button on the headset. This works only if the button is configured properly in the Configuration menu. When a user presses a call button on a headset, the call is answered and moved to an active state. Hold/Unhold a call: A user can hold/unhold an active call in two ways: By pressing a call button on Avaya Agent for Desktop main window. By pressing a physical call button on the headset. This works only if the button is configured properly in the Configuration menu. When a user presses a call button on a headset, the call is put on hold if it is active or un-hold if it is on hold. Some Jabra devices have additional hold button; but it works the same way and we do not have to make additional configuration. Drop a call: A user can drop an active call in two ways: By pressing a call button on Avaya Agent for Desktop main window. By pressing a physical call button on the headset. This works only if the button is configured properly in the Configuration menu. When a user presses a call button on a headset, the active call is dropped. Mute/unmute A user can mute/unmute an active call in two ways: By pressing a call button on Avaya Agent for Desktop main window. By pressing a physical call button on the headset. This works only if the button is configured properly in the Configuration menu. When a user presses a call button on a headset, the call is put on mute if it is active or unmute if it is on mute. Not all supported USB Headsets will have enhanced USB headset functionality available. To know more about supported headsets and operating systems, see Deploying and configuring Avaya Agent for Desktop guide. Avaya Agent for Desktop Release Notes April

7 Click-to-dial: Avaya Agent for Desktop supports click- to-dial feature using web browsers. The validation of the number for click-to-dial occurs in accordance with the country code. A user can configure the country code and their own regular expression for validation of the phone numbers. Number which satisfies the rule is placed in a frame and linked to reference "avaya-agentcall://call?to=". When user clicks on the number, Avaya Agent for Desktop starts to initiate a new call according to dialing rules. Supported Browsers Browsers Windows Mac OS Linux opensuse11 Linux thinpro Embedded browser Google Chrome Mozilla Firefox Safari Internet Explorer Microsoft Edge Note: Google Chrome version does not support any extension which were not published in a Chrome Web Store. Support for multiple levels of functionalities based on license Technology Release 1.7 of Avaya Agent for Desktop (AAfD) will introduce support of Avaya's established Official License Server. Avaya Agent for Desktop will now use Avaya's WebLM server to license AAfD software in a concurrent model. Avaya's WebLM server is a reliable server that has been in use for several years. With the Introduction of WebLM, we are also adding a dependency of a server in order to run Avaya Agent for Desktop. Though we are in a virtualized scenario, which is heavily dependents on servers, using WebLM license server will not affect the usage of Avaya Agent for Desktop. Avaya Agent for Desktop Release Notes April

8 License platform WebLM uses standard web technologies to act as a license server to Avaya products. It is a Javabased application that runs on a Java container (Being a tomcat, WebSphere, or jboss). The communication between a WebLM client library and the WebLM server is done through HTTPS. License expiration Each Avaya Agent for Desktop instance holds one license from the server, decreasing the available license count by one. When the Avaya Agent for Desktop logs out, it will release the license it currently holds and thus increasing the server license count by one, thus making it available for another agent to login using the same license. Expiration period is 1080 seconds (18 minutes). Before the timeout happens, the client must renew its acquired license allowance, allowing it to run for more 1080 minutes. In a scenario that the machine gets shut down incorrectly or Avaya Agent for Desktop crashes, thus not releasing the license through the correct process, it may take up to 1080 seconds for the held license to be released by the server. Presence feature Presence feature allows users of Avaya Agent for Desktop to: o o Publish own Presence (it includes availability, on-phone state, and notes) Observe Presence of another user To Enable Presence on Avaya Agent for Desktop, navigate to Configuration > Advanced settings, and select the Enable Presence checkbox. You need to relaunch the application to apply this setting. Presence starts only when the station is logged in (initial presence publications and subscriptions). As a user, you do not have to add presence server address or presence domain details because Avaya Agent for Desktop receives these settings already via PPM. Self-Presence Key statements: Whenever a user logs in on a station, Presence is in offline mode. Whenever a user logs in with agent Id, Presence shows away state because of Aux agent state. A user does not have any visual affect for self-presence. The user works only with the agent states, but in core of Avaya Agent for Desktop, Presence changes according to the agent state. A user can also specify an additional state, called Do not disturb. To use this state, the user needs to add aux reason code with description as Do not disturb. From an agent s point of view, Do not disturb is an aux agent state with specific reason code. Avaya Agent for Desktop Release Notes April

9 When the agent logs out or exits the application, Presence stops and shows an offline state. Contact List Presence Key statements: A user can observe Presence of other users for which Presence is configured. Observed user should also be in the same domain as observer. Key value used to observe Presence of a user is work phone. Avaya Agent for Desktop uses work phone number as a base of subscription address. To show Presence, a new column is added in the Contact list. This column displays a current Presence status with a tool tip. A tool tip is nothing but is Presence note. If a contact is added during the active agent session, Presence for that contact is initially shown as offline. But after sometime the status is updated once the session is completed. A work number of a user can be changed during an agent s active session. In this case, the presence of the modified work number is changed to offline. Once Avaya Agent for Desktop re-subscribes to the new work number, Presence in the contact list should be updated. Note: - Presence does not reset to offline when a failover occurs. - Avaya Agent for Desktop supports only Presence Server 7.0 and later versions. The earlier versions of the Presence server i.e. Presence Server 6.3 or earlier is not officially tested. - Presence works in a shared control mode only if Avaya Agent for Desktop is used on both side (Controlled and controlling). - Presence does not work in LDAP search. - Presence works in a SIP signaling mode only. UCID Avaya Agent for Desktop release 1.7 includes support of pass-through of the UCID (Universal Call Identifier). UCID is an Avaya proprietary parameter used to correlate calls. Avaya Agent for Desktop adds support of pass through of the UCID as a screen pop parameter if environment is configured for it. To configure UCID for H.323 station, the administrator should add ucid-info button on Communication Manager for the station. To configure UCID for SIP, the administrator should enable UCID in UUI page of the Trunk group configuration on Communication Manager. This allows encoding of UCID in UUI in invite and refer SIP headers. To know more about UCID for SIP, see port.html&1 ACM read-only options support Avaya Agent for Desktop Release Notes April

10 Added ability to change the parameters downloaded from ACM if read-only is disabled on the server side. Enhancements in Avaya Agent Enhancement Customer wants to customize UDP port for RTP manually through the config file WebLM License server address must be displayed after exit (or) close Avaya agent welcome window As an Agent, I would like to have more than 1 vudisplay format active at a time. Need to add ability to silent upgrade Avaya Agent for Desktop for Windows platform Skip the welcome dialog stage if the option is already present in the config file Avaya Agent for Desktop should not show submenu if there is only one reason code Description Added possibility to customize UDP port for RTP manually through the config file. Implemented functionality for applying following config parameters: "RtpPortLow" and "RtpPortRange" of config.xml file. Implemented WebLM address saving. Activate vu-display feature by timer. While timer is not expired getting vu-stats from display message. Added ability to upgrade Avaya Agent for Desktop on Windows platform without losing the previous configuration. Check Eula version, license type, and browser extension version (only for Mac). If options already present in config file, skip the welcome dialog. The aux reason code is now received from feature invocation and not from feature button. Prerequisites Server Usage Purpose Avaya Aura Communication Manager 6.3 or 7.x Mandatory SIP and H.323 based contact center features Avaya Aura System Manager 6.3 or 7.x Mandatory SIP based contact center Avaya Aura Session Manager 6.3 or 7.x Mandatory SIP based contact center Avaya Agent for Desktop Release Notes April

11 Avaya Control Manager 7.1 or later Optional Centralized administration using one- X Agent profile LDAP server Optional If you are using LDAP, you must configure LDAP Avaya Aura Messaging 6.3+ Optional Message Waiting Indicator Avaya Aura Application Enablement Services 6.3, 7.0, or 7.x Optional TSAPI and CTI integration Avaya one-x Agent 2.5.x for H.323 Optional Shared control in VDI Avaya one-x Agent for SIP Optional SIP shared control Presence Services 7.0 or later Optional Presence in VDI Avaya Agent for Desktop Release Notes April

12 Interoperability Avaya Aura servers and clients Avaya Aura Server Version Avaya Aura Communication Manager 6.3, 7.0+, Avaya Aura System Manager 6.3, 7.0+, Avaya Aura Session Manager 6.3, 7.0+, Avaya Aura Session Border Controller 6.3, 7.0+, Avaya Aura Application Enablement Server 6.3.3, 7.0+, Avaya WebLM Server 7.0+ Avaya Contact recorder 15.1 Avaya Aura Messaging server 6.3+ Avaya Aura Media Server 7.7+ Avaya Control Manager Avaya Agent for Desktop Release Notes April

13 Platforms Verified Platforms Windows 7 Windows 8.1 Windows 10 Apple Mac (10.11, and 10.13) Remarks 32 and 64 bit 64 bits 64 bit EI Capitan, Sierra, and High Sierra HP T610 Debian Linux (ThinPro 5.2) HP T620 WES 8 HP T510 WES 7 HP T520 WES 7 Dell Wyse D90D7 Dell Z50d WES7 Suse Linux Ubuntu 12.0 Avaya Agent for Desktop Release Notes April

14 Deployment and configuration To install and configure Avaya Agent for Desktop, ensure that you have access to the latest deployment and user guides. To access the latest documents, download the documents from The documents must be referred in the following order: 1. Deploying Avaya Agent 2. Using Avaya Agent 3. If you are using Avaya Control Manager, then you must refer Administering Avaya Control Manager for Avaya Agent. Note It is recommended to clean install this build by removing the previous Avaya Agent for Desktop application along with the old configurations and logs. Supported headsets Headset Model Input Output Volume up/down Mute Release / Ignore Platform Plantronics C510 M Yes Yes Yes Yes Not Supported Linux Windows Plantronics DA60 Yes Yes Yes Yes - Linux Windows Plantronics 510 Yes Yes Yes Yes - Linux Windows Plantronics C 310 Yes Yes Yes Yes Not Supported Linux Windows Jabra Link 220 Yes Yes Yes - - Linux Windows Jabra Link 280 Yes Yes Yes Yes Not Supported Linux Windows Plantronics Yes Yes Yes Yes - Linux Windows Avaya Agent for Desktop Release Notes April

15 Blackwire C520 Plantronics Blackwire Plantronic EncorePro Quick Disconnect (QD) Headset Plantronics DA80 + Plantronics EncorePro 510 Plantronics DA90 Quick Disconnect (QD) to USB adapter Yes Yes Yes Yes - Linux Windows Yes Yes Yes Yes - Linux Windows Yes Yes Yes Yes - Linux Windows Yes Yes Yes Yes - Linux Windows Jabra BIZ 2300 Yes Yes Yes Yes - Linux Windows Jabra BIZ 2400 II Yes Yes Yes Yes - Linux Windows Jabra EVOLVE 40 LINK Plantronics Blackwire C220 M Plantronics Blackwire 300 DA Yes Yes Yes Yes - Linux Windows Yes Yes Yes Yes - Linux Windows Yes Yes Yes Yes - Linux Windows Avaya Agent for Desktop Release Notes April

16 Issues fixed in Avaya Agent for Desktop Issue ID VDIA-5371 VDIA-5713 VDIA-5784 VDIA-5785 VDIA-5856 VDIA-5877 VDIA-5893 Description Call history does not match in a share control mode for a conference call. Avaya Agent for Desktop crashed on Mac "Allow Manual After call Work" option is enabled in headless mode of Avaya Agent for Desktop. No warning/error message is displayed when you login with an invalid station Id. Signaling protocol is changing from TLS to TCP The call timer freezes when a participant is added in a conference call. PPM messages are not getting downloaded on High Sierra. VDIA-5895 Avaya Agent for Desktop crashed on Mac VDIA-6009 VDIA-6030 VDIA-6047 VDIA-6059 VDIA-6071 Sample WebLM URL is not present in Avaya Agent for Desktop welcome window Avaya Agent for Desktop in SIP on CTI environment causes deadlock on Communication Manager. Unable to hold a conference call from the participant's end. The WebLM URL is not getting updated when it is provided on the Welcome window. SUSE LINUX- UI is not showing properly under the Preferences tab. VDIA-6095 The "Next" button is disabled on the End User License Agreement window if you go back from the License type screen. VDIA-6096 Avaya Agent for Desktop crashed on Windows 7 VDIA-6100 VDIA-6104 VDIA-6111 Wes- 8 - Avaya Agent for Desktop crashed while exiting the application. H323- Agent ID is not showing after the agent state is changed. Some log files are not moving to temporary log directory (User defined directory). VDIA-6115 Server IP addresses are not displaying, after upgrading Avaya agent to VDIA-6121 VDIA-6123 Ready page on Welcome dialog is empty. Avaya agent is getting crashed on Windows 7 and 10, when you try to open the About or the Configuration window before login window is displayed. Avaya Agent for Desktop Release Notes April

17 VDIA-6147 The Contact and the Call history fields are not displayed in Korean and Chinese language. VDIA-6153 Avaya Agent for Desktop crashed on Windows 7. VDIA-6155 VDIA-6160 VDIA-6238 VDIA-6201 VDIA-6192 VDIA-6178 Password is not deleted if a user cancels a login attempt. Contact List_Edit functionality should not work if no contact is selected. Agent extension is not shown on the main window if the agent logout fails. Avaya Agent for Desktop should not allow to save empty value in regular expression, if the "Use only user Regular Expression" option is enabled. Country codes are not getting updated on the browser extension, if a user regular expression contains "\". Firefox extension installation is getting failed on Mac. VDIA-6173 The agent is shown offline on desk phone mode when the user logs in as agent on my computer mode. VDIA-6172 The click-to-dial plugin provides slow response in embedded browser on Window 7. VDIA-6171 VDIA-6167 VDIA-6159 VDIA-6125 VDIA-6119 VDIA-6112 VDIA-6058 VDIA-6057 VDIA-6056 VDIA-6055 VDIA-5750 VDIA-6235 VDIA-5894 Unable to install Avaya Agent for Desktop with browser extension on Windows (32-bit) defect in Coverity detected : Pointer comparison with string literal Presence is not displaying after a contact is edited in a contact list. ACM set not persisting once accepting manual config after ACM Failure. Agent state is displayed as "Ready" on desktop mode when user changes the state to "AUX" on my computer mode. Avaya Agent for Desktop user is able to unmute and mute a call using a headset if greeting is playing. Tool tip for presence is not displayed when on an ACD/Non-ACD call. Agent state is not updated to "Ready (on a Call)" when on an ACD/Non-ACD call. Presence is not updated in a contact list after being in idle state for more than 15 mins. Unable to get the presence as "Available" after changing the agent state to "Ready". The labels for Enter and Backspace in dial pad are not displayed in Korean language. Improper error message format. Add ability to enable/disable "Reuse the TLS connection for ASM responses" feature. VDIA-6232 Avaya Agent for Desktop crashed on Windows 10. Avaya Agent for Desktop Release Notes April

18 VDIA-6210 VDIA-6175 VDIA-1026 VDIA-5753 VDIA-5884 VDIA-5784 VDIA-5898 VDIA-6108 VDIA-6169 VDIA-6226 VDIA-6239 VDIA-6242 VDIA-6249 VDIA-6267 VDIA-6272 VDIA-6273 VDIA-6278 VDIA-6284 Station unregistration proceeds even if agent logout fails. Reason code after logout does not get back to the default reason code. Button placement is incorrect. Avaya Agent for Desktop user is not able to disconnect the call at my computer mode side after the user quits Avaya Agent for Desktop at a deskphone mode side during an active call. Ringer timer resets after 60 sec at VDIA "Allow Manual After call Work" option is enabled on Headless Avaya Agent for Desktop. UI - Getting space between Secondary CM address and Number of connection attempts in local configuration if H.323 is selected. Presence is displayed as "Unknown" after network recovery. Additional popup is showing up for a millisecond when Avaya Agent for Desktop registers agent. Inconsistent feature button assignment. Avaya Agent for Desktop is getting crashed on Windows 7 and Windows 10, when a user tries to quit before login window is displayed. When an agent drops the last participant from the call using the drop-down list option, it shows the first participant s number. Intermittent issue - Registering agent spinner is not disabling after agent login. Avaya Agent for Desktop is not working with TLS 1.2 only. Wrong aux code when login through feature button. Aux code is not shown correctly when login through feature button. {Mac} Regular expression and Use only user regular expression values are not updated on Firefox browser. Wrong Presence tool tip is displaying for offline contact number. VDIA-6285 Last added participant number is displaying on call appearance, after dropping the last added participant from conference. VDIA-6290 Avaya Agent for Desktop does not get PPM data while using TLS 1.2. VDIA-6298 Loss of speech path going off hold. Avaya Agent for Desktop Release Notes April

19 VDIA-6301 VDIA-6332 VDIA-5889 VDIA-6243 VDIA-6035 VDIA-6038 VDIA-6077 VDIA-6203 VDIA-6309 VDIA-6331 VDIA-6336 VDIA-6337 VDIA-6362 VDIA-6446 VDIA-6458 VDIA-6480 VDIA-6484 VDIA-6526 VDIA-5209 VDIA-5927 VDIA-6246 VDIA-6314 Config Dialog tabs do not fit to window width. Avaya Agent for Desktop showing "Conference 2" instead of number of 2nd person to join the conference. As an agent I would like Avaya Agent for Desktop supports group MWI. Support station type 9608 for shared control using VMware Horizon. User is able to change configurations in Headless client (except Screen pop tab). Linux: No World Write or Execute Privilege. Coaching feature is not disabled for Basic WebLM license user. {Onex Profile} (%ucid), (%vdntime) and (%asai) screen pop variables are not getting converted, as, and on Avaya Agent for Desktop. SIP - Intermittent - Unregistration station spinner is not disabling without quit at deskphone side. Conference timer froze. Add 3 and 5 seconds values for stats console refresh timer. Stats console is empty. Music on hold failure. Linux - Showing multiple audio device list at Audio Output, Ringer Output, and Audio Input drop-down list. Unable to take customer off hold. State timer getting reset after getting an incoming call. Avaya Agent for Desktop is getting crashed when a headset is connected or disconnected. Avaya Agent for Desktop crashes during receiving data from ACM on SUSE. Localization is not done for "Greetings" functionalities. Greeting s auto play options are displaying in English even though Non-English UI language is selected. Browser extension tab is displayed in the English language when other language is selected. Contact list fields are displaying in English for all other languages. Avaya Agent for Desktop Release Notes April

20 VDIA-6315 VDIA-6316 VDIA-6558 "Enable Presence" is displaying in English for all other languages. Avaya Agent for Desktop Contact Error message "Please select a contact to edit " is displayed in English for all other languages. Avaya Agent for Desktop users is getting incorrect text in between EULA text. VDIA-6627 "End user License Agreement" is displaying in English for Arabic - Saudi Arabia, French - Canada, Italian-Italy, Japanese- Japan, and Korean- Republic of Korea languages. Avaya Agent for Desktop Release Notes April

21 Known issues in Avaya Agent Issue ID VDIA-6108 Description Presence is displayed as "Unknown" after network recovery. VDIA-6107 Linux -Some time mute button is not working as expected through Headset C610. VDIA-6098 VDIA-6082 VDIA-6079 VDIA-6007 VDIA-6174 "Do not disturb" reason code resets to "default" when user exits the application and re-login. Wrong Message is displaying on Avaya Agent for Desktop welcome screen, when license types are available. Error/warning message is not displaying for invalid WebLM license server address. Avaya Agent for Desktop displays "Do Not Disturb" for all auxiliary codes on SBC environment. Intermittent issue - Agent logged in successfully when Automatically login checkbox is unchecked. VDIA-6286 Avaya Agent for Desktop crashed once, during an active call on Windows 10. VDIA-6281 VDIA-6652 VDIA-6527 VDIA-6503 Error message is not displaying on Avaya Agent for Desktop welcome screen, when WebLM server is not reachable. Avaya Agent for Desktop crashed when a conference call is accepted. Avaya Agent for Desktop crashed, when receiving an incoming call. Sorting is not working properly on reason codes. VDIA-6471 Avaya Agent for Desktop crashed on Windows 7. VDIA-6440 VDIA-6439 VDIA-6436 VDIA-6430 Tab button is not working for SIP domain text box. [One time crash]: Avaya Agent for Desktop client crashed when the agent answers a transfer call. License type page error message is not updating as per the request. Headset Device Name is not displaying properly for Jabra BIZ 2300 headset. Avaya Agent for Desktop Release Notes April

22 VDIA-6409 VDIA-6395 VDIA-6644 Avaya Agent for Desktop extension is removed from Chrome browser when a silent upgrade is performed on Windows 7. Internal browser is displaying more than five SSL notifications to open a web page. Screen pop tab is displaying in English for Arabic-Saudi Arabia language. Avaya Agent for Desktop Release Notes April