When i use cti transfer and the 1st caller disconnects the below exception is seen . Can i be sure that this same exception will be thrown every time i.e. com.avaya.sce.runtimecommon.SCERuntimeException: Merge.doOperation: Unable to perform transfer operation
Would like to use cti disconnect upon this exception.

24/02/2009 13:53:11 DEBUG - FE1259B07F7979C1A8190EF7BF3F8F7C:/CTIapp : CTICommand.execute: request to manager is http://192.168.110.72:8080/cticonnector/Transfer?heldcallid%3D490%26activeCallId%3D491%26extension%3D22014&k=HeOhNXdyzSJIp2%2F5KHaZxSqiwID2XnoEqawIA5wImao%3D
24/02/2009 13:53:11 DEBUG - FE1259B07F7979C1A8190EF7BF3F8F7C:/CTIapp : CTICommand.execute: callinfo from Manager is error:Merge.doOperation: Unable to perform transfer operation
24/02/2009 13:53:11 ERROR - FE1259B07F7979C1A8190EF7BF3F8F7C:/CTIapp : session id:gsdjvp41-2009055045249-1 | Merge.doOperation: Unable to perform transfer operation

24/02/2009 13:53:11 ERROR - FE1259B07F7979C1A8190EF7BF3F8F7C:/CTIapp : session id:gsdjvp41-2009055045249-1 |
EXCEPTION>
com.avaya.sce.runtimecommon.SCERuntimeException: Merge.doOperation: Unable to perform transfer operation
at com.avaya.sce.runtimecommon.SCESession.throwRTException(SCESession.java:1560)
at com.avaya.sce.runtime.connectivity.cti.ir.CTICommand.execute(CTICommand.java:115)
at com.avaya.sce.runtime.Data.evaluateActions(Data.java:104)
at flow.transferdestination.executeDataActions(transferdestination.java:79)
at com.avaya.sce.runtime.Data.handleRequest(Data.java:73)
at com.avaya.sce.runtime.AppServlet.processRequest(AppServlet.java:63)
at com.avaya.sce.runtime.SCEServlet.requestHandler(SCEServlet.java:214)
at com.avaya.sce.runtime.SCEServlet.doPost(SCEServlet.java:163)

Yes, the SCERuntimeException is thrown every time. You can handle the exception in the data node using try/catch.

Hi Wilson
SCERuntimeException is thrown under many situations .
How can I determine if this means 1st caller disconnected or something other cti failure ?. Thanks & Regards/ Ashok.

Ashok, right. You can only get the SCERuntimeException at the application level. That's what you get in all cases of CTIC operation failures. To tell whether the 1st caller hangs up, you can handle the connection.disconnect event in the Approot. So you need to use the try/catch to handle the SCERuntimeException to make sure this error does not interrupt the call, and let the connection.disconnect event handler take care of what you need to do.