/mcpCall info Events Action GC2: CiscoRTPOutputStoppedEv GC1: CiscoRTPOutputStoppedEv GC1: CallCtlTermConnHeldEv TA GC2:CiscoRTPInputStoppedEv GC1: CiscoRTPInputStoppedEv GC1: CiscoRTPOutputStartedEv GC2: CiscoRTPOutputStartedEv GC1: CallCtlTermConnTalking TA GC2:CiscoRTPInputStartedEv GC1: CiscoRTPInputStartedEv GC2: CallCtlTermConnDroppedEv TB GC2: ConnDisconnEv A GC1: CiscoTermConnMonitorEndEv TA GC2: ConnDisconnEv B GC2: CallInvalidEv A puts the call on hold A resumes the call B calls drop on GC2 to stop monitoring Scenario Three Monitor initiator transfers the call to Y. A is monitor target, B is monitor initiator. X calls A, A answers the call GC1 (ci1). B calls start monitor using GC2. Application has call observer on both A and B. application has monitoring capability enabled. B transfers the call to Y. Cisco Unified JTAPI Developers Guide for Cisco Unified Communications Manager, Release 15 and SUs 1276 Message Sequence Charts Message Sequence Charts