Hi Team,

We faced the MPP port can not disconnect issue by standard disconnect(not CTI disconnect from AES) due to changed CTI active state.
-----
@2018-11-01 19:04:07,198||FINE|Tele|26267|FileName=h323/CCMSStation.cpp,LineNumber=2793|CCMSStation::DropCall: 58473 CTI ACTIVE on Endpoint 121|tccspi6f####
-----
Actually, we are working with CM and AES engineer with SR ticket.
However we need more time to fix this issue.

Therefore we are going to add the "CTI Disconnect" request before "Standard Disconnect" like below OD call flow as work around until fix this issue.

But we can not re-produce same issue. So, could you advice how can we forceed change MPP port state to CTI active?
We tried to add "CTI Hold" before "CTI Disconnect" in OD call flow.


My Test Date/Time?2018/11/5 11:53

Expansion?40003
VDN?41026

MPP Port?46702?MPP#1?
SessionID?mpp1-2018309025334-4

=====
05/11/2018 11:53:28:886 DEBUG - CallInfo.doGetCallInfo: Got call info for extension 46702
05/11/2018 11:53:32:152 DEBUG - Hold.doHold:46702 putting on hold ext:46702
05/11/2018 11:53:32:214 DEBUG - CTICallObserver.addApplicationObserver: adding an app observer to extension:46702
05/11/2018 11:53:32:214 DEBUG - Hold.doHold 46702: Placing terminal connection 0 on hold...
05/11/2018 11:53:32:214 DEBUG - Hold.doHold 46702: Waiting....
05/11/2018 11:53:32:277 DEBUG - CTICallObserver.callChangedEvent: Number of events on extension 46702 is 1
05/11/2018 11:53:32:277 DEBUG - CTICallObserver.callChangedEvent 46702: Event: 0 is 216 for call 78 Provider:AES2
05/11/2018 11:53:32:277 DEBUG - CTICallObserver.callChangedEvent:46702: got Terminal Connection Held Event
05/11/2018 11:53:32:277 DEBUG - CTICallObserver.updateCallState 46702: setting call:78 to state:held
05/11/2018 11:53:32:277 DEBUG - CTICallObserver.updateCallState 46702: setting cached call:78 to state:held
05/11/2018 11:53:32:277 DEBUG - CTICallObserver.notifyApplicationObserver: Notifying 46702 about call event
05/11/2018 11:53:32:277 DEBUG - Hold.doHold 46702: Terminal connection 0 placed on hold
05/11/2018 11:53:32:277 DEBUG - Hold.doHold 46702: Done placing connections on hold
05/11/2018 11:53:32:277 DEBUG - CTICallObserver.removeApplicationObserver: removing an app observer from extension:46702
05/11/2018 11:53:35:292 DEBUG - getObserversFromCallId: gathering observers... done waiting on sync list size of list is 1
05/11/2018 11:53:35:292 DEBUG - getObserversFromCallId: done gathering observers
05/11/2018 11:53:35:292 DEBUG - CTIConnectorManager.dropCall: Call state of call 78 is ACTIVE
05/11/2018 11:53:35:292 DEBUG - CTIConnectorManager.dropCall: Connection 0 state is CONNECTED
05/11/2018 11:53:35:292 DEBUG - CTIConnectorManager.dropCall: Connection 0 for address 40003
05/11/2018 11:53:35:292 DEBUG - CTIConnectorManager.dropCall: Connection 1 state is CONNECTED
05/11/2018 11:53:35:292 DEBUG - CTIConnectorManager.dropCall: Connection 1 for address 46702
05/11/2018 11:53:35:292 DEBUG - CTIConnectorManager.dropCall: Disconnecting connection for address 46702...
05/11/2018 11:53:35:292 DEBUG - CTICallObserver.doDisconnect:no UUI during disconnect for cid:com.avaya.sce.cticonnector.servlet.server.CallInfoData@354d2f70
05/11/2018 11:53:35:370 ERROR - CTIConnectorManager.doDisconnect: Unable to drop call: clearConnection failure
05/11/2018 11:53:35:370 DEBUG - CTIConnectorManager.dropCall: Call com.avaya.jtapi.tsapi.impl.LucentV7CallImpl@4599034e dropped
05/11/2018 11:53:35:370 DEBUG - getObserversFromCallId: gathering observers... done waiting on sync list size of list is 1
05/11/2018 11:53:35:386 DEBUG - getObserversFromCallId: done gathering observers
05/11/2018 11:53:35:386 DEBUG - CTICallObserver.updateCallState 46702: setting call:78 to state:disconnected
05/11/2018 11:53:35:386 DEBUG - CTICallObserver.updateCallState 46702: setting cached call:78 to state:disconnected
05/11/2018 11:53:35:386 DEBUG - Ending call on extension 46702
=====

<< Session manager log >>
@2018-11-05 11:53:38,624||FINER|Tele|6228|FileName=h323/CCMSStation.cpp,LineNumber=2086|CCMSStation::LineAppearanceUpdate: 46702 CTI NOW ACTIVE on Endpoint 1|mpp1.ve.avaya.tsuzuki.co.jp####
:
@2018-11-05 11:53:41,670||FINE|Tele|6228|FileName=h323/CCMSStation.cpp,LineNumber=2785|CCMSStation::DropCall: 46702 CTI ACTIVE on Endpoint 1|mpp1.ve.avaya.tsuzuki.co.jp####

Best regards, K.Yamahara

You have all the available commands for the AES connector in the Data node palette. If you can't reproduce with any of them, I don't think there is anything you can do from the OD side.

Hi Wilson-san,

Thank you fopr your quick reply.
I understood it. So, we will try to do that.

Thank you, K.Yamahara