AES:CSTAUniversalFailureConfEvent error=38

Doc ID    SOLN271982
Version:    5.0
Status:    Published
Published date:    07 May 2021
Created Date:    15 Jul 2015
Author:   
Mukti Sharma
 

Details

Product: AES 5.2 SP2, 6/3.x

CM version : 6.3.x

FYI: This can be seen on any AES release.
 

Problem Clarification

Currently having alarm from logger "Single-step Conference Failed: Exception adding call party: com.swhh.cti.tsapijni.messages.CSTAUniversalFailureConfEvent error=38"

Cause

CSTAUniversalFailureConfEvent: The CSTA universal failure confirmation event provides a generic negative response from the server/switch for a previous requested service.

Error 38 means 
CONFERENCE MEMBER LIMIT EXCEEDED

These are message are seen as soon as the “CONFERENCE MEMBER LIMIT EXCEEDED” ,please see below logs from AES.This is normal message seen when limit exceeds.

 

14:02:58 ERROR:WARNING:TSAPI:G3PD:L 2484:C 1895:[EVENT.CPP:1756268] CSTA Conferenced Event connection list for call ID 4966 contains more than 6 parties.  (Number of parties=11.)

14:05:41 ERROR:WARNING:TSAPI:G3PD:L 2484:C 1895:[EVENT.CPP:1761670] CSTA Conferenced Event connection list for call ID 5474 contains more than 6 parties.  (Number of parties=9.)

14:05:42 ERROR:WARNING:TSAPI:G3PD:L 2484:C 1895:[EVENT.CPP:1761670] CSTA Conferenced Event connection list for call ID 5474 contains more than 6 parties.  (Number of parties=10.)

14:05:42 ERROR:WARNING:TSAPI:G3PD:L 2484:C 1895:[EVENT.CPP:1761670] CSTA Conferenced Event connection list for call ID 5474 contains more than 6 parties.  (Number of parties=11.)

14:05:42 ERROR:WARNING:TSAPI:G3PD:L 2484:C 1895:[EVENT.CPP:1757974] CSTA Conferenced Event connection list for call ID 5474 contains more than 6 parties.  (Number of parties=11.)

Solution

This is normal message seen when conference limit exceeds.

Additional check up: on CM side check system-parameters -> PNT on Conference calls.

NOTE: In another instance of seeing CSTA error 38, they were not trying to put more parties on the call - "The called party number was a VDN and connected number was an announcement, the MST trace showed them trying to conference in while the vector was still processing, which failed with a denial event of 1746. You cannot conference until the vector processing is done and rings to an agent".

Refer to KB article - https://kb.avaya.com/kb/index?page=content&id=SOLN211301&actp=SEARCH&actp=search&viewlocale=en_US


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