Re: answer call on CTI Routepoint
Jirka Novak <[email protected]>
| Newsgroups | gmane.comp.java.sun.jtapi |
|---|---|
| Message-ID | <[email protected]> |
Hi,
> Here's the respective code:
>
> (incomingTC is the CiscoTerminalConnection of the incoming call at the
> Routepoint)
>
> tcr.incomingTC.hold(); // that works -> triggers moh
> Connection[] cons = call.getConnections();
> TerminalConnection[] tcs = cons[0].getTerminalConnections();
> CallControlTerminalConnection cctc1 = (CallControlTerminalConnection)tcs[0];
> tcr.incomingCall.setTransferController(tcr.incomingTC);
> call.setTransferController(cctc1);
> call.transfer(tcr.incomingCall);
> System.out.println("transfer successful");
>
> (try/catch left out). call.transfer triggers the CCNException and that's
> that. Since the RTP parameters have been set up for both calls prior to
> trying to make the transfer, I'm at a loss to explain the exception (which
> is undocumented so I figure it should never be seen by non Cisco programmers
> anyway).
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.
But I agree that CCNExceptions are not good and that this JTAPI
implementation is not as good as can be.
Yours,
Jirka Novak
===========================================================================
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".