McDewey

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

Page 1268

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

CallInfo Result Action Scenario 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 Communications Manager service parameter “Advanced Ad Hoc Conference Enable” is set to TRUE. • Cisco Unified Communications Manager service parameter “Drop Ad Hoc Conference” set “When controller leaves” CallInfo Result Action Scenario N.A. JTAPI returns CiscoPartyInfo[] with CiscoPartyInfo.getDisplayName() of “abc” and “xyz” Application invokes Connection.getDisplayNames () at Connection of A. Use Case 24 Application is observing A, A’ and B, and B is conference controller. A, A’, and B are in conference. Cisco Unified JTAPI Developers Guide for Cisco Unified Communications Manager, Release 15 and SUs 1204 Message Sequence Charts Message Sequence Charts

Page 1268 diagram