Hi John,
Thanks for the response.
CM Version = 8.1
AES Version = 8.1

Yes, this is 100% reproducible on every 2nd conference made. On first conference it always worked fine.

I am sharing the TSAPI logs after replicating the issue.

Hi Everyone,
I am working on SLH feature during conference.

Customer Connects with Agent
Agent take Customer in Conference with IVR for PIN Validation
Agent to put on Selective Hold to secure the PIN DTMF
Once PIN input given Customer Connect back with Agent
Selective Listening Retrieved

On the the first attempt it works like a charm. If PIN validation fails and Agent has to take customer back in conference with IVR on the same call. It didn't work and give error "Unexpected CSTA error code: 77". Below are details:

GOOD CALL
<135>Jun 2 19:35:01 uat-aes01 DmccMain[26363] +05:30 2020 708 1 com.avaya.aes | :CstaUnMarshalerNode-1: com.avaya.api.cmapi FINE - invokeID= 14 Routing request=session[session 674BF67071DF0B803E8FDFCC51A2E930-321] ch.ecma.csta.binding.ConferenceCall@a3f11e
<135>Jun 2 19:35:01 uat-aes01 DmccMain[26363] +05:30 2020 708 1 com.avaya.aes | :CstaUnMarshalerNode-1: com.avaya.api.router FINER - Invoking method=public void com.avaya.cmapi.extsvc.CallControlServicesImpl.conferenceCall(ch.ecma.csta.binding.ConferenceCall,com.avaya.api.async.AsynchronousCallback) throws ch.ecma.csta.errors.CstaException with argument=session[session 674BF67071DF0B803E8FDFCC51A2E930-321] ch.ecma.csta.binding.ConferenceCall@a3f11e publisher channel is= async [/10.9.166.84:4721/10.6.227.210:63544] invokeId=14
<135>Jun 2 19:35:01 uat-aes01 DmccMain[26363] +05:30 2020 708 1 com.avaya.aes | :CstaUnMarshalerNode-1: com.avaya.api.cmapi FINE - invokeID= 15 Routing request=session[session 674BF67071DF0B803E8FDFCC51A2E930-321] com.avaya.csta.binding.SelectiveListeningHold@1bca5a5
<135>Jun 2 19:35:01 uat-aes01 DmccMain[26363] +05:30 2020 708 1 com.avaya.aes | :CstaUnMarshalerNode-1: com.avaya.api.router FINER - Invoking method=public void com.avaya.cmapi.extsvc.CallControlServicesImpl.selectiveListeningHold(com.avaya.csta.binding.SelectiveListeningHold,com.avaya.api.async.AsynchronousCallback) throws ch.ecma.csta.errors.CstaException with argument=session[session 674BF67071DF0B803E8FDFCC51A2E930-321] com.avaya.csta.binding.SelectiveListeningHold@1bca5a5 publisher channel is= async [/10.9.166.84:4721/10.6.227.210:63544] invokeId=15
<135>Jun 2 19:35:01 uat-aes01 DmccMain[26363] +05:30 2020 795 1 com.avaya.aes | :ClearableQueuedExecutor-1: com.avaya.api.cmapi FINE - invokeID= 14 Sent response session[session 674BF67071DF0B803E8FDFCC51A2E930-321] ch.ecma.csta.binding.ConferenceCallResponse@1298012
<135>Jun 2 19:35:01 uat-aes01 DmccMain[26363] +05:30 2020 833 1 com.avaya.aes | :ClearableQueuedExecutor-1: com.avaya.api.cmapi FINE - invokeID= 15 Sent response session[session 674BF67071DF0B803E8FDFCC51A2E930-321] com.avaya.csta.binding.SelectiveListeningHoldResponse@2120b3


BAD CALL
<135>Jun 2 19:36:17 uat-aes01 DmccMain[26363] +05:30 2020 643 1 com.avaya.aes | :CstaUnMarshalerNode-1: com.avaya.api.cmapi FINE - invokeID= 21 Routing request=session[session 674BF67071DF0B803E8FDFCC51A2E930-321] ch.ecma.csta.binding.ConferenceCall@10edb88
<135>Jun 2 19:36:17 uat-aes01 DmccMain[26363] +05:30 2020 643 1 com.avaya.aes | :CstaUnMarshalerNode-1: com.avaya.api.router FINER - Invoking method=public void com.avaya.cmapi.extsvc.CallControlServicesImpl.conferenceCall(ch.ecma.csta.binding.ConferenceCall,com.avaya.api.async.AsynchronousCallback) throws ch.ecma.csta.errors.CstaException with argument=session[session 674BF67071DF0B803E8FDFCC51A2E930-321] ch.ecma.csta.binding.ConferenceCall@10edb88 publisher channel is= async [/10.9.166.84:4721/10.6.227.210:63544] invokeId=21
<135>Jun 2 19:36:17 uat-aes01 DmccMain[26363] +05:30 2020 643 1 com.avaya.aes | :CstaUnMarshalerNode-1: com.avaya.api.cmapi FINE - invokeID= 22 Routing request=session[session 674BF67071DF0B803E8FDFCC51A2E930-321] com.avaya.csta.binding.SelectiveListeningHold@19d28a6
<135>Jun 2 19:36:17 uat-aes01 DmccMain[26363] +05:30 2020 643 1 com.avaya.aes | :CstaUnMarshalerNode-1: com.avaya.api.router FINER - Invoking method=public void com.avaya.cmapi.extsvc.CallControlServicesImpl.selectiveListeningHold(com.avaya.csta.binding.SelectiveListeningHold,com.avaya.api.async.AsynchronousCallback) throws ch.ecma.csta.errors.CstaException with argument=session[session 674BF67071DF0B803E8FDFCC51A2E930-321] com.avaya.csta.binding.SelectiveListeningHold@19d28a6 publisher channel is= async [/10.9.166.84:4721/10.6.227.210:63544] invokeId=22
<135>Jun 2 19:36:17 uat-aes01 DmccMain[26363] +05:30 2020 713 1 com.avaya.aes | :ClearableQueuedExecutor-1: com.avaya.api.cmapi FINE - invokeID= 21 Sent response session[session 674BF67071DF0B803E8FDFCC51A2E930-321] ch.ecma.csta.binding.ConferenceCallResponse@398736
<132>Jun 2 19:36:17 uat-aes01 DmccMain[26363] +05:30 2020 730 1 com.avaya.aes | :DistributeCSTAEvent: com.avaya.async.impl.AsyncCallbackImpl WARNING - A service method threw an Exception when invoked!#012ServiceMethod: com.avaya.platform.broker.impl.AsyncServiceMethodImpl@1e174be[com.avaya.cmapi.extsvc.CallControlServicesImpl@173dc9c, public void com.avaya.cmapi.extsvc.CallControlServicesImpl.selectiveListeningHold(com.avaya.csta.binding.SelectiveListeningHold,com.avaya.api.async.AsynchronousCallback) throws ch.ecma.csta.errors.CstaException]#012Exception: ch.ecma.csta.errors.CstaException: Unexpected CSTA error code: 77#012Request: session[session 674BF67071DF0B803E8FDFCC51A2E930-321] com.avaya.csta.binding.SelectiveListeningHold@19d28a6
<135>Jun 2 19:36:17 uat-aes01 DmccMain[26363] +05:30 2020 730 1 com.avaya.aes | :ClearableQueuedExecutor-1: com.avaya.api.cmapi FINE - invokeID= 22 Sent response ch.ecma.csta.errors.CstaException: Unexpected CSTA error code: 77


Looking forward to have your response against. Thanks.

Thanks Appreciate your help.

Hi Everyone,
Can anyone help me in configuring an external property file. Normally all DB connections are stored in context.xml and web service URL in WSOP files. This file should be saved other than webapp folder itself, where I can store DB Connection URL, Web Service URL and related credentials to be used in IVR Application.

The purpose is to make the changes to connections on runtime without creating new build. Thanks in advance.

Thanks,
Yes I have opened the SR and waiting their response. Hope I may get the answer soon.

Hi Everyone,
We have AES Agent Application running on below platform:

Avaya Aura 8.1
ACR 15.1
AEP 7.1

This application is running fine without any issues. But ACR is upgraded to ACR15.2 and Agent Application start getting Redirect Event instead of newCall

With ACR 15.1 or if ACR 15.2 services turned off.
OnDeliveredEvent >>> OnDeliveredEvent - EventCause:newCall

With ACR 15.2
OnDeliveredEvent >>> OnDeliveredEvent - EventCause:redirected

Can you please confirm why the Event cause is changing. Is this an architectural change and working as design. Or is it some sort of bug that needs to be handled.

Looking forward to have your response. Thanks in advance.

Is there a way to update WSDL on already created Web Services rather creating these from scratch?

As I have mentioned I was building new project to test. It works like a charm. I don't know what is the issue at the old project. Even I reduce the the fetch timeout to 30s it is still working.

Really appreciate all your help.

One more question can I have this fetch timeout printed in any data node. So I would know after how much time it gives the exception. As I am unable to find the variable against.

Looking forward. Thanks.

I did exactly the same. Added property in AppRoot and set the fetch timeout as 60s
I know speech time out is set as 6000ms, I believe it has nothing to do with Web Service timeout.

AppRoot -> Property -> fetchtimout -> 60s
WebService -> Timeout-> 3s

Still getting the same behaviour. Try Catch not catching the exception.
Now I am creating new project which will not have anything else other than playing single prompt and calling web service.

Will let you know the result.

Hi WilsonYu,
Appreciate your help.

I have increased the fetch timeout to 60s. Still I am facing the same issue. I am attaching trace log and snapshot of the Web Service node how I configure it. Another point is, rather catching the exception and going to next node after catch it is going on the node when there will be a response from the web service.

Looking forward to hear back from your side. Thanks.

Please find attached snippet from trace logs.

It seems that TRY Catch is not working. Even Try Catch is there I am still having error "Error.BadFetch" when running from OD. And error "Technical Difficulty" when from AEP.

Please suggest.

Appreciate that. Will try to set the fetch timeout and revert.

Hi Ivalberto,
Thanks for the response. I am testing it via OD simulator and experiencing the same. In this scenario there is not EP involved.

Below is the node snap and trace.log snippet as well.

I am facing the same issue. Exception not caught, please help.