Re: answer call on CTI Routepoint

>I always got CCNException when call and incommingCall has no common
>terminalConnection for transfer. Try to check all terminalConnections on
both >calls and do .getTransferController on them. It will returns null.
>Try to select some terminalConnection by hand and assign it as
>transferController. If you choose bad one, you will get some JTAPI
exception. >If you choose right it may be help to avoid CCNException.

I do check for the TransferController, and it is indeed null (I just left
out that bit of the code, as well as my state checking code). And as you can
see from what I've posted, I set the transfercontroller for both calls,
using the CallControlTerminalConnection on my CTI Routepoint (tcr.incomingTC
is the CallControlTerminalConnection on the CTI Routepoint for the incoming
call, and the 2nd CallControlTerminalConnection is also from the CTI
Routepoint, but it's from the outgoing call. As far as I understand,
setTransferController requires a CCTC that is part of the call to be
transferred, so I cannot set the same CCTC for both calls (I just tried
using the same CCTC as transfer controller on both calls and that throws the
expected exception telling me that the CCTC is not associated with the call).

Note that I'm using the exact same code for call transfer on a CTI Port and
a physical device, and there it works (well, it used to not work and
suddenly like magic it started working.. kinda feels like playing the
lottery when working with the Cisco JTAPI).

===========================================================================
To unsubscribe, send email to [email protected] and include in the body
of the message "signoff JTAPI-INTEREST".  For general help, send email to
[email protected] and include in the body of the message "help".