McDewey

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

Page 708

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

Expected events Action A will be dropped out of conference. LINECALLSTATE Event will be sent to Application with state = Idle. 1. Application does LineRemoveFromConference on the ‘Conferenced’ CallLeg on B which is connected to A and mode is "Active". CallLegs after the Party is dropped from Conference: CallLegs on A: IDLE -(on the Connected callLeg which was connected to Conference Bridge,A-CFB) IDLE -(on the conferenced callLeg which is connected to A -B) IDLE -(on the conferenced callLeg which is connected to A -C) IDLE -(on the conferenced callLeg which is connected to A -A') Connected -to Conference Bridge (Remote in Use) Conferenced -(caller Id -A' ;Called Id -C; Connected Id -C) (Remote in Use) Conferenced -(caller Id -A' ;Called Id -B; Connected Id -B) (Remote in Use) CallLegs on A': IDLE -(on the Connected callLeg which was connected to Conference Bridge,A -CFB) IDLE -(on the conferenced callLeg which is connected to A -B) IDLE -(on the conferenced callLeg which is connected to A -C) IDLE -(on the conferenced callLeg which is connected to A -A') Connected -to Conference Bridge Conferenced -(caller Id -A' ;Called Id -C; Connected Id -C) (Active) Conferenced -(caller Id -A' ;Called Id -B; Connected Id -B) (Active) CallLegs on B: Connected -to Conference Bridge Conferenced -(caller Id -B ;Called Id -A; Connected Id -A') IDLE -(on the conferenced callLeg which was connected to B -A) Conferenced -(caller Id -B ;Called Id -C; Connected Id -C) Cisco Unified TAPI Developers Guide for Cisco Unified Communications Manager, Release 15 and SUs 676 Message Sequence Charts Message Sequence Charts

Page 708 diagram