Hi Team,

We performed AES connector failover test with dual active AES(AES#1 and #2) configuration.

Here are the test scenario.

- At first, AES connector conected AES#2 as active link.
- Call was established from 78121 to VDN 23001
- We disconnected all of AES#2 connected LAN cable from AES connector to occur connction failure.
- The active link was failover from AES#2 to AES#1 with Failover Event(event113).
- When we tried to generate manual transfer event from OD application.
- We confirmed the Call was transfered corectlly.
- However below error log was generated in OD trace.
- 6min later, when Generate Manual Forward Event again, No error log was generated in OD trace.

So, we would like to know the reason why below error log was generated in OD trace.
Because the Application generated the Call Forward Operation error(OE0006) as a results of below error log.
----- generated error log in OD trace -----
20180123 105901799DEBUG2e1XO4wSsVailzOacM1cpVFtb CTICommand.execute callinfo from Manager is errorMerge.doOperation Unable to perform transfer operation
-----

Therefore we tried to perform below test case and pattern.

Operation Pattern
Pattern A AES#2 Failure(Disconnect LAN Cable) occurred, then Generate Manual Forward event before AES connector perfored Failover to AES#1
Pattern B AES#2 Failure(Disconnect LAN Cable) occurred, then Generate Manual Forward event after AES connector perfored Failover to AES#1 immediately
Pattern C AES#2 Failure(Disconnect LAN Cable) occurred, then Generate Manual Forward event 3 min. later after AES connector perfored Failover to AES#1

Test Case

- Test case 1?1st time?Log file :*****_test1
Call established from Ext78121 to VDN23001
Generate Manual Forward Event before failover Message generate Case


10:54:55 Call Generated(78121)
10:56:40 AES#2 Failure(Disconnect LAN Cable) occurred
Generate Manual Forward Event before failover Message generate
10:57:41 Event113 Generated
10:58:21 Event112 Generated
6min later, when Generate Manual Forward Event again, No error log was generated in OD trace.


- Test case 1?2nd time?Log file :*****_test2
Call established from Ext78121 to VDN23001
Generate Manual Forward Event after failover Message generate immediately Case

11:28:08 Call Generated(78121)
11:29:24 AES#2 Failure(Disconnect LAN Cable) occurred
11:30:24 Event113 Generated
11:30:56 Event112 Generated
Generate Manual Forward Event after failover Message generate immediately
6min later, when Generate Manual Forward Event again, No error log was generated in OD trace.

- Test case 2?1st time?Log file :*****_test3
Call established from Ext78123 to VDN23001
Generate Manual Forward Event after failover Message generate immediately Case
Call established from Ext78121 to VDN23001
Generate Manual Forward Event before failover Message generate Case

11:39:41 Call Generated(78123)
11:39:45 Call Generated(78121)
11:42:10 AES#2 Failure(Disconnect LAN Cable) occurred
11:42:30 Generate Manual Forward Event before failover Message generate(78123)
11:43:12 Event113 Generated
11:43:52 Event112 Generated
11:44 Generate Manual Forward Event after failover Message generate immediately(78121)
6min later, when Generate Manual Forward Event again, No error log was generated in OD trace.

- Test case 3?1st time?Log file :*****_test4
Call established from Ext78121 to VDN23001
Generate Manual Forward event 3 min. later after AES connector perfored Failover to AES#1
Call established from Ext78123 to VDN23001
Generate Manual Forward Event before failover Message generate Case

11:53:33 Call Generated(78121)
11:53:36 Call Generated(78123)
11:55:05 AES#2 Failure(Disconnect LAN Cable) occurred
11:55:22 Generate Manual Forward Event before failover Message generate(78123)
11:56:09 Event113 Generated
11:56:49 Event112 Generated
12:00 Generate Manual Forward event 3 min. later after AES connector perfored Failover to AES#1(78121)
6min later, when Generate Manual Forward Event again, No error log was generated in OD trace.

Best regards, K.Yamahara

Hi Team,

As I informed that Call was transfered correctlly.
Therefore I would like to know below point if this is usual message.

1) Please explain the reason why below error log was generated in OD trace.
Is this message generate every cti transfer operation even if the Call was transfered correctly?
-----
20180123 105901430DEBUG2e1XO4wSsVailzOacM1cpVFtb CTICommand.execute setting session cookie to 2e1XO4wSsVailzOacM1cpVFtb
20180123 105901799DEBUG2e1XO4wSsVailzOacM1cpVFtb CTICommand.execute callinfo from Manager is errorMerge.doOperation Unable to perform transfer operation
20180123 105901828ERROR2e1XO4wSsVailzOacM1cpVFtb session idjnntbsymp1-2018023015455-2
EXCEPTION
com.avaya.sce.runtimecommon.SCERuntimeException Merge.doOperation Unable to perform transfer operation
at com.avaya.sce.runtimecommon.SCESession.throwRTException(SCESession.java2554)
at com.avaya.sce.runtime.connectivity.cti.ir.CTICommand.execute(CTICommand.java156)
at com.avaya.sce.runtime.Data.evaluateActions(Data.java228)
at flow.subflow.EventFlow.CallTransfer.executeDataActions(CallTransfer.java95)
at com.avaya.sce.runtime.Data.handleRequest(Data.java121)
at com.avaya.sce.runtime.AppServlet.processRequest(AppServlet.java96)
at com.avaya.sce.runtime.SCEServlet.requestHandler(SCEServlet.java247)
at com.avaya.sce.runtime.SCEServlet.doGet(SCEServlet.java140)
at javax.servlet.http.HttpServlet.service(HttpServlet.java687)
at javax.servlet.http.HttpServlet.service(HttpServlet.java790)
at com.ibm.ws.webcontainer.servlet.ServletWrapper.service(ServletWrapper.java1290)
at com.ibm.ws.webcontainer.servlet.ServletWrapper.handleRequest(ServletWrapper.java778)
at com.ibm.ws.webcontainer.servlet.ServletWrapper.handleRequest(ServletWrapper.java475)
at com.ibm.ws.webcontainer.filter.WebAppFilterManager.invokeFilters(WebAppFilterManager.java1161)
at com.ibm.ws.webcontainer.webapp.WebAppRequestDispatcher.dispatch(WebAppRequestDispatcher.java1381)
at com.ibm.ws.webcontainer.webapp.WebAppRequestDispatcher.forward(WebAppRequestDispatcher.java186)
-----

2) And 6min later, when Generate Manual Forward Event again, No error log was generated in OD trace.
Is this also usual phenomenon?

Best regards, K.Yamahara

Hi Team,

I found below similar ticket in Archive of OD forum.

https://www.devconnectprogram.com/forums/posts/list/8899.page
Subject: cti transfer disconnect by 1st caller which exception is thrown?

Then I also found below comment.
Is this also meet for my inquiry?
-----
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.
-----

If yes, please advice what kind of CTIC operation failures could you estimated?

Best regards, K.Yamahara

Hi team,

Could any one help on this?

Best regards, K.Yamahara