/mcpFields Event Call Meta Event Cause TermConnDroppedEv B CallCtlTermConnDroppedEv B ConnDisconnectedEv B CallCtlConnDisconnectedEv B Call1 META_CALL_TRANSFERRING ConnCreatedEv C ConnConnectedEv C CallCtlConnEstablishedEv C TermConnCreatedEv C TermConnActiveEv C CallCtlTermConnTalkingEv C Call1 META_CALL_TRANSFERRING TermConnDroppedEv B CallCtlTermConnDroppedEv B ConnDisconnectedEv B CallCtlConnDisconnectedEv B Call2 META_CALL_TRANSFERRING TermConnDroppedEv C CallCtlTermConnDroppedEv C ConnDisconnectedEv C CallCtlConnDisconnectedEv C CallInvalidEv C Call2 META_CALL_TRANSFERRING Transfer and Conference Extensions You may find that transfer and conference events are difficult to understand in JTAPI. This happens because, when the participants are moved from one call to the other, JTAPI represents this action by deleting the parties from one call and adding them to the other call. It may confuse you for an application to receive an indication that a party dropped from the call when, in reality, it is in the process of being moved. The Cisco Unified JTAPI implementation defines some extra events that make it easier for applications to deal with these functions. Transfer and DirectTransfer The transfer feature provides the ability to transfer a call. The direct transfer feature represents the ability to transfer any of the two calls that are present on the line, so controller of the call drops out, and other two parties remain active on the call. This functionality gets supported with one enhancement: this feature can be done in any state of the call and also can be redesigned to work with new CTI events. The following enhancements apply to the transfer feature: • The application can transfer two held calls. • The application can have OneHeld and OneConnected call in any order. Cisco Unified JTAPI Developers Guide for Cisco Unified Communications Manager, Release 15 and SUs 196 Features Supported by Cisco Unified JTAPI Transfer and Conference Extensions