AES 4.2.4 : DMCC SSC fails because some ASAI messages lose between ASAI link layer and Transport layer

Doc ID    SOLN261135
Version:    3.0
Status:    Published
Published date:    04 Jul 2019
Created Date:    18 Dec 2014
Author:   
Dongbo Zhao
 

Details

 Application Enablement Services

Version: r4-2-4-35-0 
 
DMCC SSC of recorder fails sometimes.
AES replies the  "REQUEST_TIMEOUT_REJECTION" TSAPI message to the recorder after the recorder sends  the ATT_SINGLE_STEP CONFERENCE_CALL for joining a call.
 
 

Problem Clarification

 From AES G3trace log:

 12/16/2014 20:59:36.184:TSAPI:AES4DMCC: Received CSTA Msg (CSTAREQUEST)(3) (ESCAPE_SVC)(89)

12/16/2014 20:59:36.184:TSAPI:AES4DMCC: msgoff(95)msglen(4)privoff(24)privlen(71)

12/16/2014 20:59:36.184:TSAPI:AES4DMCC: invokeID(39195)monXref(0)sessionID(3)clsOfServ(0)

12/16/2014 20:59:36.184:TSAPI:AES4DMCC: eventType(ATT_SINGLE_STEP_CONFERENCE_CALL)(65)

#AES received a SSC from recorder.

12/16/2014 20:59:36.282:TSAPI:AES4DMCC: Sent ASAI Message A3PDCInfo

12/16/2014 20:59:36.282:TSAPI:AES4DMCC: cap,prim,sao_id  C_3PDC_REQ,C_REQUEST,2301336

12/16/2014 20:59:36.282:TSAPI:AES4DMCC: extension      200021

#AES  TSAPI sent a A3PDCInfo  request to CM fro creating  a domain control association, now TSAPI is waiting the A3PDCAck or A3PDCNak from CM.

 

12/07/2014 19:40:24.344:TSAPI:Audit-AES4DMCC: Sent CSTA Msg (CSTACONFIRMATION)(5) (UNIVERSAL_FAILURE_CONF)(53)

12/07/2014 19:40:24.344:TSAPI:Audit-AES4DMCC: msgoff(24)msglen(4)privoff(0)privlen(0)

12/07/2014 19:40:24.344:TSAPI:Audit-AES4DMCC: invokeID(37341)monXref(2989)sessionID(3)clsOfServ(0)

 

12/07/2014 19:40:24.344:TSAPI:Audit-AES4DMCC: error(REQUEST_TIMEOUT_REJECTION)(78)

#after 10 sec , the timeout occurs , TSAPI did not get any reply from CM, then sent the timeout_rejection to the recorder.

 

#From AES trace out log:

12/16/2014 20:59:36.306:trans_serv:AES4DMCC-read: sslRead(af60fad6= 08 02 81 1f 62 96 1c 06 91 a2 03 02 01 05 , 14) returned 14

12/16/2014 20:59:36.306:trans_serv:AES4DMCC-read: *bytes_transferred= 14

12/16/2014 20:59:36.306:trans_serv:AES4DMCC-read: stream.recv(..., 14, recvd= 14) returned 14

 

12/16/2014 20:59:36.306:trans_serv:AES4DMCC-read: buf= 08 02 81 1f 62 96 1c 06 91 a2 03 02 01 05

#trans_serv received the replay "A3PDCAck" from CM.

12/16/2014 20:59:36.306:asailink:recvLink33: recvData failed no message available -- errno= 11

12/16/2014 20:59:36.306:asailink:recvLink33: validateConnection: Maps: 9b6bf008 9b023008 9b014008 913d500c

12/16/2014 20:59:36.306:asailink:recvLink33: validateConnection: transPid= 5560

 

12/16/2014 20:59:36.306:asailink:recvLink33: validateConnection: ServiceState= 2

# when asailink read the message "A3PDCAck" from transport layer, a error "recvData failed no message available" occured ,it means the ASAI link  failed to read the message. 

 

 

Cause

 some ASAI messages lose between ASAI link layer and Transport layer

Solution

 the AES 4.2.4 is already out of product support (End of Services Support (EOSS) as of 30 October 2018).

suggested customer have to upgrade the latest AES and CM version.

Attachment Description

NA


Avaya -- Proprietary. Use pursuant to the terms of your signed agreement or Avaya policy