Aborted Calls in Historical Reports - ApplicationTaskInactiveException -
we have installed IPCCX 4.1 on a Call Center over Call Manager 4.3 and configured several teams with Extension Mobility. The problem is that when getting the applications reports such as "Application Summary Reports" or "Application Performance Analysis Report" we obtain hundreds of abandoned calls although we haven't experiended such load of traffic.
We have found the mistake on "Aborted and Rejected Call Detailed Report" in which heve detected those calls we missed on the other application reports. There is an amount of calls repeating, for each of them, an abandoned entry with the reason com.cisco.app.ApplicationTaskInactiveException.
We also noticed that only the groups implementing Extension Mobility presents that exception.
We have found nothing about that exception and nothing about how to solve it and need to get those reports.
Can you give us some suggestion or documentation about the exceptions of CRS and how to handle them on CRS scripts? We will appreciate any help.
Re: Aborted Calls in Historical Reports - ApplicationTaskInactiv
"com.cisco.app.ApplicationTaskInactiveException" error could be because of either of the following:
1. Application Time Clock continuing to process when the caller has dropped.
2. The CTI Route Point could not setup the call on a CTI port so the call could get routed to Application Time Clock. This usually happens when the CTI Route Point, CTI port and the Agents ICD ext. are not in the same Calling search space, Partition on the CallManager. It will also happen if the Jtapi client on the IPCCx sever is not the same version as the CallManager.
Are you getting this error “Installer User Interface Mode Not Supported. The installer cannot run in this UI mode. To specify the interface mode, use the -i command-line option, followed by the UI mode identifier. The value UI mode identifiers...
The below trick might come handy when you have to add a new node to a cluster but you don't have or is unsure of the security password for the publisher. This procedure has been around for ages.
1) Login into the CLI of the Publisher.