Ok. Thanks for your reply.

I want to create a new call and then get the call ID before I make any connections to the call. I am using the following code:

Call newCall = myprovider.createCall();
int newCallID = ((ITsapiCallIDPrivate) newCall).getTsapiCallID();

The CallID returned by the method is 0. Only when the events start coming through am I able to get the actual CallID. However I need to know the CallID before I receive any events, is this possible?

Thanks
Tom

I am having problems with the single step transfer provided by JTAPI.

I am using call.transfer(String deviceToTransferTo) to do a single step transfer. I have set the controller and everything works properly.

However, after a successful transfer, the same phone which was the transfer controller is not able to make any more transfers. I get the following exception:

com.avaya.jtapi.tsapi.TsapiResourceUnavailableException: CSTA Error: 33

The error code indicates resource busy. If I restart the application then I can make another transfer but again the second transfer is blocked. It seems like something is getting stuck inside the jtapi.jar implementation. Can you confirm that it's possible to make more than one transfer?!?

I am using AES version 4.2 and jtapi.jar version 4.2.1.
Thanks
Tom

I am seeing the same behaviour but using JTAPI. If I make a single step transfer using the JTAPI method call.transfer(String deviceToTransferTo) it works fine. But once a phone has made one single step transfer it is not able to make any more.

This is the exception:
com.avaya.jtapi.tsapi.TsapiResourceUnavailableException: CSTA Error: 33

The error code indicates resource busy.

It seems like the AES server or something underneath has a problem.

Is there a way to force the Avaya jtapi to refresh itself?

I'm having problems with the Avaya JTAPI returning invalid calls. It seems to be on outgoing calls to the trunk only.

When the call is setup I can pull the Call object out of the CallCtl Connection Established Event. This Call object will return the two Connections for the call.

If I then try and put the call on hold using the jtapi application, the same Call Object is in the INVALID state and doesn't return any connections. But the call is still ongoing. If I make an internal call then everything is ok.

What is wrong with Avaya JTAPI calls on outgoing trunks?

Thanks
Tom