TASKE Application

• Avaya Aura Agent Desktop Download
• Avaya Agent Desktop Client
• Avaya Aura Agent Desktop 6.0
• Avaya Aura Agent Desktop

I have a problem with the Avaya Aura Agent Desktop. I am on a AACC 6.4 sp12 and the CCMM is on a separate server. This mode was the focus of the testing done with XenDesktop and the Avaya softphone clients. Tested Softphones and Operating System Platforms. The softphones specifically tested by Citrix with XenDesktop 4 were: Avaya one-X Communicator 1.0.0.57. Avaya IP Softphone R5. Avaya IP Softphone R6.

This article describes the requirements for the server computer dedicated to running version 8.8 or 8.9 TASKE server applications in conjunction with an Avaya Communication Manager telephone system. If you have a different version of TASKE or telephone system, please refer to Article 10000 for the correct system requirements.

Summary

Note the following before selecting a TASKE server computer and installing the TASKE server applications:

Avaya Aura® Agent Desktop 30 July 2012 3. Entering an activity code. Avaya Agent for Desktop 1.6.4 Rlease (build 3004) Avaya Agent for Desktop is a contact center agent client application. As an agent, you can use Avaya Agent for Desktop for handling incoming and outgoing calls, changing work states, and managing other UI controls. As an administrator, you can manage Avaya Agent for Desktop configurations and settings.

• The requirements in this article operate on the assumption that the TASKE server computer is dedicated to TASKE server applications.
• TASKE does not support systems where the server computer is also an Active Directory Server, a Primary Domain Controller (PDC), a Backup Domain Controller (BDC), or an Exchange Server.
• The TASKE server must have a TCP/IP connection to the Avaya Application Enablement Services (AES) server with version 3.0 or later. The AES server must have Application Enablement (CTI) license with TSAPI Service and Basic TSAPI Right To Use (RTU) licenses for each device which will be monitored
• Sites using TASKE Agent Skill Management must have an Avaya AES server with version 5.2 or later.
• Although a desktop computer is acceptable for the TASKE server computer, TASKE recommends using an entry-level server computer. Regardless of the type of computer used, a Microsoft server-level operating system is recommended.
• TASKE is Enterprise Application Software and as such runs on the TASKE server and requires a user to be logged in in order to function.

The requirements in this article are the recommended configuration for sites with up to 100 agents/extensions. Sites with more than 100 agents/extensions and/or high call volume will need to increase the server computer capabilities.

TASKE Server Computer Recommended Configuration

*Refer to Article 10007 for more information on how this disk space is used

TASKE Web Portal Requirements

TASKE DisplayCentral Requirements

TASKE Desktop Requirements

TASKE Analytics Requirements

Analytics requirements vary depending on the particular configuration chosen, but in general the following items are required.

TASKE will configure the TASKE ODBC driver. Some options may require the purchase of a TASKE XML Integration license. TASKE Agent-Assist requires TASKE Desktop.

Applies to:

Telephone Systems:

• Avaya Communication Manager

Tags:

computer • requirement • server

This is not an official guide! Past performance is no guarantee of future results!

I've been lucky enough to be testing Windows 10 for some time, and have spoken to lots of Avaya engineers who were worried about using Windows 10 because of compatability with Avaya products. I thought I'd compile an unofficial list of what works and doesn't. Engineers like to tinker with new toys, so wanted to pass on my experience in case you brick your laptop just before walking on site...

Please bear in mind, this list is based on the Preview build (10162 and earlier), and may not be representative of the final version when it's released on July 29th. My testing comprises of using Windows 10 on three machines, two of which are installed on the primary partition, the third is on VirtualBox on Mac OS X Yosemite (10.10.3). The results are from all three instances unless noted.

• Provision (2014.3) - no issues found connecting to CM, MM and AAM.
• ASA (6.0.07 SP11) - no issues including Announcement backup/restore (SP12 is coming soon to support CM7, but this has not been seen/tested)
• One-X Communicator 6.2.4.07 - worked fine in H.323 and SIP mode, have not tried any presence or video, just voice
• One-X Agent 2.5.5 (not tested through VirtualBox) - registered to a CM with no issues - recommend more thorough testing
• CMS Supervisor R17 (not tested through VirtualBox) - limited testing here but worked fine

Other third party apps that have been used and found to be working:

• PuTTY 0.63
• WinSCP 5.7.3/5.7.4
• SecureCRT 7.3.4
• VMWare vSphere client 5.5 and 6.0

Firefox remains the browser of choice connecting to Avaya products. Microsoft Edge (the IE replacement) did not fare well, but truthfully I gave it 5 minutes before I realized it sucked and moved back to something tried and tested. Edge doesn't seem to have a decent PDF viewer built in...so no wonder I changed back. Will get better over time I am sure.

So far so good...now for the bad stuff:

Avaya Aura Agent Desktop Download

Avaya Agent Desktop Client

On a number of these builds, I found the upgrade process from build to build bricked my network adapters and/or prevented VPN clients (Cisco & SonicWall) from functioning at all. At this current time, 10162 has bricked both my VPN clients and even a fresh ISO install of 10162 doesn't solve the problem. This will probably go away when Windows 10 goes live, but it's been a nagging problem for a few months. Worth testing first if you rely on VPN clients for day-day or customer connectivity.

Avaya Aura Agent Desktop 6.0

Hope this helps :) and please add your experiences in the comments.

Avaya Aura Agent Desktop

Product names and trademarks used in this post are owned by their respective corporations.