McDewey

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

Page 700

↗ View in doc context
page
700
source
cucm/v15/tapi-dev-guide/tapi-dev-guide.md
chunk_id
cucm::v15::tapi-dev-guide::tapi-dev-guide::714

Expected events Action A is dropped out of conference. CallLegs after the Party is dropped from Conference: Each line in conference will be having 4 callLegs, 2 Conferenced,1 IDLE and 1 connected 1. Application does LineRemoveFromConference on the ‘Conferenced’ callLeg on B which is connected to A. CallLegs on A: All 4 CallLegs will be in IDLE state CallLegs on B: Connected -to Conference Bridge Conferenced -(Connected Id -C) Conferenced -(Connected Id -D) IDLE -( on the conferenced callLeg which was connected to A) CallLegs on C: Connected -to Conference Bridge IDLE -( on the conferenced callLeg which was connected to A) Conferenced -(Connected Id -B) Conferenced -(Connected Id -D) CallLegs on D: Connected -to Conference Bridge IDLE -( on the conferenced callLeg which was connected to A) Conferenced -(Connected Id -B) Conferenced -(Connected Id -C) Note All IDLE CallLegs will have CallStateChange Reason as CtiDropConferee. Application does a LineOpen (A) with new Ext ver. Error Message LINEERR_OPERATIONUNAVAIL will be sent to application 1. Application does LineRemoveFromConference on the ‘Conferenced’ callLeg on A which is connected to B. Cisco Unified TAPI Developers Guide for Cisco Unified Communications Manager, Release 15 and SUs 668 Message Sequence Charts Message Sequence Charts

Page 700 diagram