Welcome to the TASKE Knowledge Base. Find answers and information about using TASKE products by searching our knowledge base articles.
Upgrading to Java 7 Update 51 may cause TASKE applications to stop working as expected.
Change real-time to show time since log out instead of time stamp of when the agent logged out.
Error stating Java detection has failed even though you have Java installed.
Java produces a security warning and how to remedy the situation.
How to change the default location TASKE Desktop stores its configuration information.
Information for how to turn off the silent monitor (service observe) indicator.
Ensure that your TASKE, IEX and the UCCX all have the same Not Ready reason codes in order to get consistent reports.
The Avaya system must be configured to use two digit AUX work reason codes in order for TASKE to display the reason codes in the real-time area.
TASKE web sessions expire while using the web interface. Updated applets are required in order to function with Java Version 6 Update 29 and newer.
TASKE Java applets are digitally signed as secure. The certificate for version 8.9 has expired. Apply this patch to receive newly signed applets.
When TASKE is installed on a 64-bit machine, the 32-bit Registry Editor should be used to edit TASKE registry keys
The TASKE ODBC Driver is a 32-bit application which may cause some incompatibilities on a 64-bit Windows machine.
Server computer requirements for a basic 50 agent/extension installation of TASKE for an Avaya Communication Manager telephone system.
Server computer requirements for a basic 50 agent/extension installation of TASKE for a Cisco Systems telephone system.
The requirements for TASKE applications vary by the make of your telephone system and TASKE application.
TASKE versions prior to 8.7 are no longer supported
An update to Java causes users to receive a Java security warning when logging in to TASKE
Instructions detailing how to change the frequency that the TASKE server broadcasts changes made in the TASKE Administrator.
Changing the AES's IP address requires a change in Avaya Site Administration as well.
Server computer requirements for a basic 50 agent/extension installation of TASKE for an Toshiba Strata telephone system.
Server computer requirements for a basic 50 agent/extension installation of TASKE for Iwatsu ECS or ADIX APS telephone systems.
Modular messaging trunks must be identified
IIS 6.0 by default recycles worker processes which causes end users of TASKE web applications to be signed out.
Instructions for configuring TASKE web applications to be accessed using secure hypertext transfer protocol (https)