Author Message
Sufyan
Joined: May 18, 2015
Messages: 23
Offline
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.
Filename dmcc-api.log [Disk] Download
Description dmcc-api logs
Filesize 4561 Kbytes
Downloaded: 328 time(s)

Filename dmcc-trace.log [Disk] Download
Description dmcc-trace logs
Filesize 4728 Kbytes
Downloaded: 323 time(s)

JohnBiggs
Joined: Jun 20, 2005
Messages: 949
Location: Thornton, CO
Offline
can you add some details
communication manager version
AE Services version


77 is a fairly obscure TSAPI error code

The TSAPI Service detects that it cannot
provide the service due to the failure or
shutting down of the communication link
between the Telephony Server and
Communication Manager. The TSAPI Service
sends this error for every outstanding CSTA
request for every ACS Handle affected.
Although the link is down or Communication
Manager is out of service, the TSAPI Service
remains loaded and advertised. When the
TSAPI Service is in this state, all CSTA
Service requests from a client will receive a
negative acknowledgment with this unique
error code.

Is this 100% reproducible?

The logs you provided do not shed any light on what occurred across the switch connection to communication manager from AE Services. To have us take a look at this please open a DevConnect Technical Support request, and include the TSAPI, csta and server log.YYYYMMDD trace files (https://www.devconnectprogram.com/site/global/products_resources/avaya_aura_application_enablement_services/support/faq/tsapi/index.gsp#10) the log.YYYYMMDD file should be in '/opt/mvap/logs for when you are performing these actions.
Sufyan
Joined: May 18, 2015
Messages: 23
Offline
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.
JohnBiggs
Joined: Jun 20, 2005
Messages: 949
Location: Thornton, CO
Offline
please open a technical support ticket with this information.
JohnBiggs
Joined: Jun 20, 2005
Messages: 949
Location: Thornton, CO
Offline
please also include the log.YYYYMMDD log for the interval covering your test. It will show what is happening with the switch connection between AES and CM.
Go to:   
Mobile view