/mcpCall information Events Action GC1: CallCtlTermConnTalking TA GC1: CiscoRTPOutputStartedEv TA GC1: CiscoRTPInputStartedEv TA GC2: CiscoRTPOutputStartedEv TB GC2:CiscoRTPInputStartedEv TB A resumes the call GC2: CallCtlTermConnDroppedEv TB GC2: TermConnDroppedEv TB GC2: ConnDisconnectedEvB GC2: CallCtlConnDisconnectedEv B GC2: ConnDisconnectedEv A GC2: CallCtlConnDisconnectedEv A GC2: CallInvalidEv GC1: CiscoTermConnMonitorEndEv TA B calls drop() on GC2 to stop monitoring Use Case Two - Snapshot Use Case for Whisper Monitoring • A is monitor target. B is monitor initiator. X calls A, A answers the call GC1 (ci1). B calls start monitor using GC2. Another application adds call observer on A after monitoring session is established. Call information Events Action GC1: Calling: X Called: A LRP: null Current calling: X Current called:A CallActiveEv for callID = GC1 Cause: CAUSE_SNAPSHOT GC1:ConnCreatedEv for A Cause: CAUSE_SNAPSHOT GC1:ConnConnectedEv for A Cause: CAUSE_SNAPSHOT GC1: ConnConnectedEv X GC1:CallCrlTermConnTalkingEv TA Cause: CAUSE_SNAPSHOT GC1: CiscoTermConnMonitoringStartEv TA Cause: CAUSE_SNAPSHOT getMonitorType() = CiscoCall.WHISPER_MONITOR GC1: CiscoTermConnMonitorInitiatorInfoEv TA Cause: CAUSE_SNAPSHOT address:B, device name: TB CiscoMonitorInitiatorInfo.getMonitorType() = CiscoCall.WHISPER_MONITOR • A is monitor target and B is monitor initiator. Caller X calls A, A answers the call GC1 (ci1). B calls start monitor using GC2. Another application adds call observer on B after monitoring sessions are established. Cisco Unified JTAPI Developers Guide for Cisco Unified Communications Manager, Release 15 and SUs 1591 Message Sequence Charts Message Sequence Charts