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

This seems much more complex than can be dealt with in the forum. Please open a Tech Support ticket and one of my colleagues will try to help you.

Martin

Hi Martin-san,

Thank you for your quick reply.

I see.
I will open SR ticket.

Before that, I would like like to know below point.
Please advice.

1. Which Logs or information should we provide to SR to investigate this kind of issue?
Actually, we confirmed that the Call was transfered correctly as below logs.
However "Unable to perform transfer operation" error message was generated in OD trace.
And we can not find any related messages(error) in logs which I provided.

Or if you have any information regarding reason why "Unable to perform transfer operation" error message was generated in OD trace, please advice.
-----
23/01/2018 12:00:16:478 DEBUG - Transfer.doMerge:4400042 Updated call info to state:transferred
23/01/2018 12:00:16:478 ERROR - Merge.doOperation: Unable to perform transfer operation
....
23/01/2018 12:00:17:356 DEBUG - CTICallObserver.removeCall:clearing MRCC:2227 from ext:4400042
23/01/2018 12:00:17:356 DEBUG - CTICallObserver.removeCall:removing call:2227 from ext:4400042
23/01/2018 12:00:26:053 DEBUG - ProviderMonitor: Checking:AES#2 for availability
23/01/2018 12:00:26:054 DEBUG - ProviderMonitor:AES#2 is null in our list
-----

2. If it is not issue, and if it is working as design, please also advice.
e.g, We need to wait 5-6 min after Failover. etc,...

Because when we tryied to perform same test 5-6 min later after failover, this error message was NOT generated.

Best regards, K.Yamahara

I cannot help to interpret errors from Orchestration Designer as I do not know anything about it. There is a forum for Orchestration Designer. Maybe you can get some help there.

Martin

Hi Martin-san,

Thank you for your quick reply.

I understood.
I will ask this in forum for Orchestration Designer.

Thank you and regards, K.Yamahara