McDewey

Fields Event Call Meta Event Cause 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 CCallInvalidEv C Call2 META_CALL_TRANSFERRING CallObservationEndedEv Call2 META_UNKNOWN transferredCall = Call2 FinalCall = Call1 transferController = TermConnB CiscoTransferEndEv Call1 META_UNKNOWN Arbitrary Transfer; A Is the Transfer Controller In an arbitrary transfer, one call can get transferred to another call, irrespective of how either call was created. Unlike consult transfer, no need exists to first create one of the calls by using the consult method. • A calls B on call Call1. • A puts Call1 on hold. • A calls C on call Call2. • A transfers Call1 to Call2. To do this type of transfer, use the following JTAPI methods: • Call2.transfer(Call1) to transfer call Call1 to final call Call2, or • Call1.transfer(Call2) to transfer call Call2 to final call Call1 Assuming Call1.transfer(Call2) was called, the following table lists the core events that observers on A and C receive between CiscoTransferStartEv and CiscoTransferEndEv. Table 9: Core Events for Observers of A and C Fields Event Call Meta Event Cause transferredCall = Call2 finalCall = Call1 transferController = TermConnB CiscoTransferStartEv Call1 META_UNKNOWN Cisco Unified JTAPI Developers Guide for Cisco Unified Communications Manager, Release 15 and SUs 195 Features Supported by Cisco Unified JTAPI Transfer Scenarios