McDewey

Expected events Action B 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. Drop Ad Hoc Conference = Never CallLegs on B: All 4 CallLegs will be in IDLE state CallLegs on A: Connected -to Conference Bridge Conferenced -(Connected Id -C) Conferenced -(Connected Id -D) IDLE -( on the conferenced callLeg which was connected to B) CallLegs on C: Connected -to Conference Bridge IDLE -( on the conferenced callLeg which was connected to B) Conferenced -(Connected Id -A) Conferenced -(Connected Id -D) CallLegs on D: Connected -to Conference Bridge IDLE -( on the conferenced callLeg which was connected to B) Conferenced -(Connected Id -A) Conferenced -(Connected Id -C) Note All IDLE CallLegs will have CallStateChange Reason as CtiDropConferee. B is dropped out of conference and Conference will be ended. CallLegs after the Party is dropped from Conference: Each line in conference will be having 4 callLegs, all in IDLE state CallLegs on A,B,C and D: All 4 CallLegs will be in IDLE state 1. Drop Ad Hoc Conference = ‘When Conference Controller Leaves’ Cisco Unified TAPI Developers Guide for Cisco Unified Communications Manager, Release 15 and SUs 670 Message Sequence Charts Message Sequence Charts