McDewey

Call info Events Action GC1: Calling: X Called: A LRP: null Current calling: X Current called: A CallActiveEv for callID = GC1 Cause: CAUSE_NEW_CALL GC1:ConnCreatedEv for A’ Cause: CAUSE_NORMAL GC1:ConnConnectedEv for A’ Cause: CAUSE_NORMAL GC1: ConnConnectedEv X … GC1:CallCrlTermConnRingingEv TA’ Cause: CAUSE_NORMAL GC1: CallCtlTermConnBridgedEv TermA’ Cause: CAUSE_NORMAL GC1: CallCrlTermConnHeldEv TA’ GC1:CallCrlTermConnTalkingEv TA’ GC1: CiscoTermConnMonitorStartEv TA’ GC1: CiscoTermConnMonitorInitiatorInfoEv TA’ Cause: CAUSE_NORMAL address:B, device name: TB A answers GC1 and B initiates monitor A puts the call on HOLD A’ answers the call B drops the call and initiates start monitor using GC3 giving the terminal connection of A’ in monitor request. Scenario Seven Snap Shot events for Monitor and recording: A is monitor target and has auto recording configured. 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 and recording sessions are established. Call info 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: CiscoTermConnRecordingStartEv TA Cause: CAUSE_SNAPSHOT GC1: CiscoTermConnRecordingTargetInfoEv TA Cause: CAUSE_SNAPSHOT GC1: CiscoTermConnMonitorStartEv TA Cause: CAUSE_SNAPSHOT GC1: CiscoTermConnMonitorInitiatorInfoEv TA Cause: CAUSE_SNAPSHOT address:B, device name: TB Cisco Unified JTAPI Developers Guide for Cisco Unified Communications Manager, Release 15 and SUs 1281 Message Sequence Charts Message Sequence Charts