TASKE Support Knowledge Base
Welcome to the TASKE Knowledge Base. Find answers and information about using TASKE products by searching our knowledge base articles.
Recent Articles
Issue When using the TASKE/IEX integration, TASKE sends IEX the state of the agent. Some of these records have agent state of 0 which is an unknown state. Reason Some versions of the Cisco UCCX send TASKE agent records in a different order. TASKE has optimized our real-time adherence to attempt to not send duplicate […]
Automatically restart device monitors when telephone system ends a monitor.
Automatically create exclusion rules for lists of resources.
SMS connection to the Communication Manager stops working.
Use Windows Task Scheduler to increase the frequency of Call XML exports.
You can reset the Not Ready state time to zero (00:00:00) in the Real-Time display when an agent changes Not Ready codes.
You can reset the AUX Work state time to zero (00:00:00) in the Real-Time display when an agent changes AUX WORK reason codes.
Instructions for showing a website as a component in TASKE DisplayCentral
Computer requirements for the server running TASKE.
Requirements for computers running DisplayCentral
Browsers that work with the latest TASKE release
Requirements specific to customers connecting to a Cisco UCCX telephone system
Requirements specific to customers connecting to an Avaya Communication Manager telephone system
Requirements specific to customers connecting to a Toshiba telephone system
Requirements specific to customers connecting to Iwatsu telephone systems
Requirements for computers running Desktop
Browser caching may interfere with the user experience for TASKE 2016.4.
If you have very large PBX files, export call data to to multiple XML files instead of one XML file.
You can hide VDN extension types listed on the extension selection page when producing reports.
If the report selection page does not appear, increase the memory buffer used by Microsoft Internet Information Service (IIS) version 7 and higher.
You can change the timeout (by default, 30 seconds) that TASKE waits for the telephone system to return results for a request.
Java 8 Update 60 and newer cause Internet Explorer applets to load very slowly
Real-time Java applets do not work with Chrome version 42 and newer
Java applets occasionally fail to load, some, not necessarily all
Search our knowledge base:
Useful Links
Manufacturers
Categories
- Archive (12)
- TASKE Contact (131)
- Administrator (15)
- Chat (1)
- Desktop (7)
- DisplayCentral (5)
- Integrations (4)
- ODBC Driver (3)
- Real-Time (17)
- Reports (22)
- Visualizer (6)
- TASKE Essential (105)
- Administrator (11)
- ODBC Driver (3)
- Real-Time (9)
- Reports (13)
- Visualizer (5)
- TASKE Reporter (83)
- Administrator (11)
- ODBC Driver (3)
- Reports (19)
- Visualizer (6)
- TASKE Visualizer (78)
- Administrator (11)
- Chat (1)
- Desktop (7)
- DisplayCentral (5)
- Visualizer (6)
- Uncategorized (1)
Popular Articles
- Changing the IP Address of the Avay...
- FAQs
- TASKE Logs Show INVALID CSTA DEVICE...
- How to Monitor and Report on ACD Ca...
- How to Turn Off Silent Monitoring I...
- Queue Reports Appear to Have Too Ma...
- Requirements for Cisco Unified Comm...
- Software Update Release Information
- Adding SSL Support to the TASKE Wid...
- TASKE Web Application Displays a Se...