Our CTI application uses JTAPI (ecsjtapi.jar). JTAPI is 3.1.0 build 69. This JTAPI implementation is provided by Avaya AES.

We have tested the JTAPI exerciser tool which we downloaded from the Avaya DevConnect Site and even that is not releasing the license.

With the JTAPI exerciser tool we first created a terminal on which the callobserver is to be added. Then when we use addcallobserver on that terminal it acquires one license (TSAPI_Simultaneous_User). When we use removecallobserver method it does not release the license (we can see the CallObservationEndedEnv event but the license is not getting released). The same happens with our CTI application.

The licenses have to be released. How do we release the license?

This is problem a known issue with the 4.1 JTAPI SDK that will be fixed in the AES 4.2 JTAPI SDK which will be released at the end of May 2008. Thank you for bringing this to our attention.

During my testing the license is released when the application properly shutdown and closed its socket with the AE Services server. It was not necessary to restart the AE Services server (or TSAPI service) to achieve release of the license.

Thanks! the same happens in our case. The licenses are released when our application is shutdown and its not necessary to restart the AES Server for this.

We have downloaded AES 4.2 JTAPI sdk (ecsjtapia.jar ver 4.2.0 build 279) from Avaya Devconnect site and tested in our labs. We have AES ver 3.1.1. The TSAPI_Simultaneous_User licenses are now getting released. (Initially with our CTI application used JTAPI ecsjtapi.jar JTAPI is 3.1.0 build 69 with which the licenses were not getting released)

We tested the same at customer site where they have AES ver 3.1.4 the TSAPI_Simultaneous_User licenses are now getting released but there is an exception in make outbound call feature. (We don?t get this exception in our labs where we have AES ver 3.1.1)

Exception:
06/04/08 20:08:58.205 <DistributeCSTAEvent#3> Event Distributor Exception - shutting down provider TSProvider[#1]@719f1f

We use the call.connect method using JTAPI sdk to make an outbound call. It works fine with AES ver 3.1.1 and the ecsjtapia.jar ver 4.2.0 build 279 but throws an exception with AES ver 3.1.4 and the ecsjtapia.jar ver 4.2.0 build 279

Find below our findings:
ecsjtapia.jar ver 4.2.0 build 279 with AES ver 3.1.1 ? TSAPI_Simultaneous_User licenses getting released when we stop observing the station and call.connect also works fine no exception

ecsjtapi.jar. JTAPI is 3.1.0 build 69 with AES ver 3.1.1 and AES ver 3.1.4 ? TSAPI_Simultaneous_User licenses NOT getting released when we stop observing the station and call.connect also works fine no exception

ecsjtapia.jar ver 4.2.0 build 279 with AES ver 3.1.4 ? TSAPI_Simultaneous_User licenses getting released when we stop observing the station but call.connect throws an exception 06/04/08 20:08:58.205 <DistributeCSTAEvent#3> Event Distributor Exception - shutting down provider TSProvider[#1]@719f1f

Below is the extract from log file:

***********************MAKE _CALL***************************
MISAgent.makeOutboundCall()
mISCallImpl.transfer()->destinationtype=LITERAL
MISAgentImpl.makeOutboundCall()->destinationAddressName=09960944074
returning forced false
After Checking DestinationNumber=09960944074
call.connections=null
06/04/08 20:08:58.205 <DistributeCSTAEvent#3> Event Distributor Exception - shutting down provider TSProvider[#1]@719f1f
java.lang.NullPointerException
06/04/08 20:08:58.206 <DistributeCSTAEvent#3>    at java.lang.String.compareTo(String.java:998)
06/04/08 20:08:58.206 <DistributeCSTAEvent#3>    at com.avaya.jtapi.tsapi.dn.c(SourceFile:3600)
06/04/08 20:08:58.206 <DistributeCSTAEvent#3>    at com.avaya.jtapi.tsapi.aG.a(SourceFile:5176)
06/04/08 20:08:58.206 <DistributeCSTAEvent#3>    at com.avaya.java.tsapiInterface.u.a(SourceFile:49)
06/04/08 20:08:58.206 <DistributeCSTAEvent#3>    at com.avaya.java.tsapiInterface.l.a(SourceFile:119)
06/04/08 20:08:58.206 <DistributeCSTAEvent#3>    at com.avaya.java.tsapiInterface.v.run(SourceFile:96)
MISAgentImpl.isInboundAllowed=10000
[vishal]callEvent.getID()103
[call instanceof LucentV7Call]=false

Please enter a devconnect support ticket with the information you have provided and we will start digging into what may be the cause.