McDewey

CiscoConferenceEndEv This event gets sent at the end of the merge process after a ConferenceStartEv is sent. It signifies the completion of the merge of the Consult (or Merged) call into the Final Conference Call. The Merged call specifies an INVALID state, and an ObservationEndedEv gets sent for the call observer. CiscoCall.setConferenceEnable() The Cisco Unified JTAPI implementation uses the CiscoCall.setConferenceEnable() and the CiscoCall.setTransferEnable() methods to control whether the consult call will be initiated via the conference or the transfer feature. If none of the features is enabled explicitly, transfer gets used by default. Conference Scenarios The following scenarios describe the two typical types of conference that can be invoked. Consult Conference; B as the Conference Controller The following sequence of steps typically describes this scenario: • A calls B (Call 1). • B answers. • B Consults C (Call 2). setConferenceEnable() call2.consult(tc, C) • C answers. • B Completes Conference. Call1.conference(Call2) You must invoke the conference() method on the original call to complete a conference after a consultation. Invoking conference in the consult call object throws an exception. Note Arbitrary Conference; B as the Conference Controller The following sequence of steps typically describe this scenario: • A calls B (Call 1). • B answers. • B places the call on hold. • B calls C (Call 2). • C answers. • B Completes Conference. Cisco Unified JTAPI Developers Guide for Cisco Unified Communications Manager, Release 15 and SUs 64 Features Supported by Cisco Unified JTAPI Conference Scenarios