/mcpBackward Compatibility This feature is backward compatible. Conference When you conference two calls together, JTAPI specifies that all the parties from one call be moved to the other call. The call whose parties are moved away and that subsequently becomes invalid gets identified as the “merged” or “consult” call. The call to which the merged parties move gets identified as the “final” call hereafter. When parties move from the merged call to the final call, the application receives events that indicate that all parties dropped from the merged call and events that indicate that the parties reappeared on the final call. To correlate the newly created connection objects with the old connection objects, use the CiscoConection.getConnectionID() method to obtain CiscoConnectionID objects for all old connections and all new connections. Matching connections will have identical CiscoConnectionID objects when you compare them by using the CiscoConnectionID.equals() method. Conference support exists for the following methods: • javax.telephony.callcontrol.CallControlCall.conference(Call) • javax.telephony.callcontrol.CallControlCall.getConferenceController() • javax.telephony.callcontrol.CallControlCall.getConferenceEnable() • javax.telephony.callcontrol.CallControlCall.setConferenceController(TerminalConnection) • javax.telephony.callcontrol.CallControlCall.setConferenceEnable(boolean) As of Cisco Unified Communications Manager Release 8.6, Cisco TelePresence MCU conference bridges are supported through JTAPI/TSP. From a JTAPI/TSP perspective, this conference bridge behaves in the same way as other supported conference bridges. Note Cisco Extensions Cisco Unified JTAPI implementation provides two extra events that signal the Start and End of Conference: CiscoConferenceStartEv and CiscoConferenceEndEv. These events get sent when Conference initiates and when it completes. They give handles to the final call, the merged conference (consult) call, and the two controlling TerminalConnections (in HELD and TALKING state). CiscoConferenceStartEv This event gets sent when call1.conference(call2) is invoked or if the Conference button is pressed for the second time on an IPphone. The ConferenceStartEv signifies the start of the merging process. A sequence of merging events that are reflected by the Conference process in Cisco Unified Communications Manager follows. Cisco Unified JTAPI Developers Guide for Cisco Unified Communications Manager, Release 15 and SUs 63 Features Supported by Cisco Unified JTAPI Conference