McDewey

Call1.conference(Call2) or Call2.conference(Call1) Conference Events This table provides the sequence of Core, Call control, and Cisco Extension events when Call1.Conference(Call2) is called: Table 1: Sequence of Events Fields Event Call Meta Event Cause consultCall = Call2finalCall = Call1conference Controller = TermConnB CiscoConferenceStartEv Call1 META_UNKNOWN CallCtlTermConnTalkingEv B Call1 META_CALL_MERGING ConnCreatedEv C ConnConnectedEv C CallCtlConnEstablishedEv C TermConnCreatedEv C TermConnActiveEv C CallCtlTermConnTalkingEv C Call1 META_CALL_MERGING TermConnDroppedEv B CallCtlTermConnDroppedEv B ConnDisconnectedEv B CallCtlConnDisconnectedEv B Call2 META_CALL_MERGING consultCall = Call2finalCall = Call1conferenceController = TermConnB TermConnDroppedEv C CallCtlTermConnDroppedEv C ConnDisconnectedEv C CallCtlConnDisconnectedEv C CallInvalidEv C Call2 META_CALL_MERGING CallObservationEndedEv Call2 META_UNKNOWN CiscoConferenceEndEv Call1 META_UNKNOWN Transfer and Conference Enhancement All parties who are involved in the call transfer get sent CiscoTransferStartEv and CiscoTransferEndEv. All parties who are involved in the call conference get sent CiscoConferenceStartEv and CiscoConferenceEndEv. A call transfer still generates two events—the dropping of a connection to the first call and the creation of a connection to the second call. Cisco Unified Communications ManagerRelease3.1 changed this order of events. Connections first get created in the final call and then get dropped in the consult call. Cisco Unified JTAPI Developers Guide for Cisco Unified Communications Manager, Release 15 and SUs 65 Features Supported by Cisco Unified JTAPI Conference Events