McDewey

Multi-vendor documentation library · semantic search · MCP endpoint at /mcp

Page 1258

↗ View in doc context
page
1258
source
cucm/v15/jtapi-dev-guide/jtapi-dev-guide.md
chunk_id
cucm::v15::jtapi-dev-guide::jtapi-dev-guide::1262

Call info Result Action Scenario N.A. Cause = CAUSE_NORMAL CiscoFeatureReason = REASON_NORMAL Cause = CAUSE_NORMAL CiscoFeatureReason = REASON_NORMAL Cause = CAUSE_NORMAL CiscoFeatureReason = REASON_NORMAL JTAPI returns CiscoPartyInfo[] with CiscoPartyInfo.getDisplayName() of “abc” and “xyz” TermConnDropEv-TA’ CallCtlTermConnDroppedEv-TA’ A(xyz), dropped out of conference. TermConnDropEv-TA CallCtlTermConnDroppedEv-TA A(abc), dropped out of conference. TermConnDropEv-TB CallCtlTermConnDroppedEv-TB ConnDisconnectedEv-B CallCtlConnDisconnectedEv-B B is disconnected from conference. Application invokes Connection.getDisplayNames() at Connection of A. Application invokes Connection.disconnect(xyz) on Connection of A. Application invokes Connection.disconnect(abc) on Connection of A. Application invokes Connection.disconnect() on Connection of B. Use Case 15 Application is observing A, A’ and B, and B is conference controller. A, A’, and B are in conference. Displayname for A is “abc”, and displayname for A’ is “xyz” Cause = CAUSE_NORMAL CiscoFeatureReason = REASON_NORMAL TermConnDropEv-TA CallCtlTermConnDroppedEv-TA TermConnDropEv-TA’ CallCtlTermConnDroppedEv-TA’ ConnDisconnectedEv-A CallCtlConnDisconnectedEv-A TermConnDropEv-TB CallCtlTermConnDroppedEv-TB ConnDisconnectedEv-B CallCtlConnDisconnectedEv-B CallInvalidEv Connections of A, and B are disconnected, A(abc) and A’(xyz) will be dropped, and since only B is left, it will also get dropped and call goes Invalid. Application invokes Connection.disconnect() on Connection of A. • JTAPI INI parameter is enabled to allow dropAnyPartyFeature. Cisco Unified JTAPI Developers Guide for Cisco Unified Communications Manager, Release 15 and SUs 1194 Message Sequence Charts Message Sequence Charts

Page 1258 diagram