Created by: Stewart Ponsford on 26-01-2011 09:12:15 AM Is it possible when receiving disconnected events when a connection drops out of a call to know who hung up? I seem to always get a connection disconnected for the connection of the address I am observing.
Subject: RE: Detecting who disconnected? Replied by: Joseph Moskie on 27-01-2011 12:35:40 AM No, there is currently no way to detect which party disconnected when you are observing a call.
Subject: RE: Detecting who disconnected? Replied by: Stewart Ponsford on 12-04-2013 08:29:03 AM Hi sorry to revisit this I have been trying to work around this problem for sometime, but there are some call flows that are very hard to handle in Cisco and this seems such a big limitation. I work with other APIs such as Avaya TSAPI and Mitel etc and we don't have this problem. It makes it impossible to determine who is leaving a conference for example. One case I have is the one monitored phone in a conference with two externals, if the monitored device drops out I get disconnecteds for the two externals first.
Subject: RE: Detecting who disconnected? Replied by: David Staudt on 17-04-2013 05:34:33 PM If your scenario is a three-party conference with one monitored party, then what you are describing sounds likely. Due to the distributed/multi-threaded/asynchronous nature of the various components in UCM, not all events can be guaranteed to arrive in a particular order. Sometimes the various reason codes (CiscoCauseCode, CiscoFeatureReason) can help in determining why certain events are occuring without necessarily depending on order.