Hi,
I'd like to know why (in what kind of condition) an object is re-created after receiving a SnapshotCallConf from AES.
(JTAPI 6.1)

Call scenario: An operator has a call with a customer and makes another call to EP(IVR) for conferencing. After EP answers the call, he puts the call into conference.

In this scenario JTAPI client receives a "Conferenced" event, then it sends "SnapshotCall" request to AES. Just after it receives a SnapshotCallConf back from AES, it sometimes re-creates (delete and re-create) connection or call objects and sends CONNECTIONDISCONNECTED event to an application(aesconnector). In spite the call is still active.
This does not happen every time, but only happens around once a month. I guess the JTAPI detects some difference in the callinfo in SnapshotCallConf from a callinfo it's having. Is there any condition to cause this kind of behavior?

2018-11-26 09:48:46,109 [DistributeCSTAEvent] INFO TSAuditThread - Found conn in audit hash: TSConnection[termConn:(13867,43614)]@cf52eb6a for TSProvider[#2]@e10b2249
2018-11-26 09:48:46,109 [DistributeCSTAEvent] INFO SnapshotCallConfHandler - SnapshotCallConfHandler.handleConf(): recreating connection TSConnection[termConn:(13867,43614)]@cf52eb6a; oldConnState=89, oldTermConnState=102
2018-11-26 09:48:46,109 [DistributeCSTAEvent] INFO TSConnection - Connection object= TSConnection[termConn:(13867,43614)]@cf52eb6a being deleted for TSProvider[#2]@e10b2249
2018-11-26 09:48:46,109 [DistributeCSTAEvent] INFO TSAuditThread - NOTICE: saveConnHash.put() replaced com.avaya.jtapi.tsapi.impl.core.SavedConn@5cf7c044 for TSProvider[#2]@e10b2249
2018-11-26 09:48:46,109 [DistributeCSTAEvent] INFO TSAuditThread - AUDIT (dumpConn): removing conn TSConnection[termConn:(13867,43614)]@cf52eb6a for TSProvider[#2]@e10b2249
2018-11-26 09:48:46,109 [DistributeCSTAEvent] INFO TSAuditThread - Found call in audit hash: TSCall[13867]@d97dc850 for TSProvider[#2]@e10b2249
2018-11-26 09:48:46,109 [DistributeCSTAEvent] INFO TSAuditThread - AUDIT (dumpCall): removing call TSCall[13867]@d97dc850 for TSProvider[#2]@e10b2249
2018-11-26 09:48:46,109 [DistributeCSTAEvent] INFO TSAuditThread - AUDIT (dumpCall): removing conn TSConnection[termConn:(13867,58395)]@97cf7a5a for TSProvider[#2]@e10b2249
2018-11-26 09:48:46,109 [DistributeCSTAEvent] INFO TSAuditThread - AUDIT (dumpCall): removing conn TSConnection[conn:(13867,T12855#3)]@f5aa5451 for TSProvider[#2]@e10b2249
2018-11-26 09:48:46,109 [DistributeCSTAEvent] INFO TSCall - Constructing call TSCall[13867]@fd64e43e with ID 13867 for TSProvider[#2]@e10b2249

2018-11-26 09:48:46,110 [DistributeCSTAEvent] DEBUG TsapiCallMonitor - meta event BEGIN: cause (207) metaCode (133) for com.avaya.sce.cticonnector.servlet.server.CTIConnectorManager$CTICallObserver@ec60166c
2018-11-26 09:48:46,110 [DistributeCSTAEvent] INFO TSDevice - Recreating deleted device TSDevice[T12855#3]@883b1d8a
2018-11-26 09:48:46,110 [DistributeCSTAEvent] INFO TSProviderImpl - NOTICE: devHash.put() replaced TSDevice[T12855#3]@474593b8 for TSProvider[#2]@e10b2249
2018-11-26 09:48:46,110 [DistributeCSTAEvent] INFO TSDevice - TSDevice state transition: Deleted -> Active, device TSDevice[T12855#3]@883b1d8a
2018-11-26 09:48:46,110 [DistributeCSTAEvent] INFO TSDevice - Device T12855#3 (object= TSDevice[T12855#3]@883b1d8a) being re-added for TSProvider[#2]@e10b2249
2018-11-26 09:48:46,110 [DistributeCSTAEvent] DEBUG TsapiCallMonitor - CONNECTIONDISCONNECTEDEVENT for TSConnection[conn:(13867,T12855#3)]@f5aa5451 for observer com.avaya.sce.cticonnector.servlet.server.CTIConnectorManager$CTICallObserver@ec60166c
2018-11-26 09:48:46,110 [DistributeCSTAEvent] DEBUG TsapiCallMonitor - CONNECTIONDISCONNECTEDEVENT_CC for TSConnection[conn:(13867,T12855#3)]@f5aa5451 for observer com.avaya.sce.cticonnector.servlet.server.CTIConnectorManager$CTICallObserver@ec60166c
2018-11-26 09:48:46,110 [DistributeCSTAEvent] DEBUG TsapiCallMonitor - meta event END for com.avaya.sce.cticonnector.servlet.server.CTIConnectorManager$CTICallObserver@ec60166c eventList size=2

I think the question you are asking is better suited for a DevConnect Technical Ticket (click on Support & Forums from the menu above, and then Technical Support in the right column). Please open a ticket to initiate a dialogue with a team member who has the expertise in this product area.

Note that Technical Support through DevConnect is tiered and based on your company’s membership level different levels of support will be provided. For further information on DevConnect membership levels and the related level of support, please click the Program & Benefits tab and then DevConnect Membership Levels.

To open a discussion related to membership click on Program & Benefits and then on Membership or Program Questions in the left column.