McDewey

Multi-vendor documentation library · semantic search · MCP endpoint at /mcp

Page 1343

↗ View in doc context
page
1343
source
cucm/v15/jtapi-dev-guide/jtapi-dev-guide.md
chunk_id
cucm::v15::jtapi-dev-guide::jtapi-dev-guide::1347

Scenario Four Monitoring a barged call: A and A’ are shared lines. Caller calls A, A answers the call. A’ barge into the call. B calls start monitor. 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:CallCrlTermConnTalkingEv TA Cause: CAUSE_NORMAL CiscoRTPOutputStartedEv CiscoRTPInputStartedEv GC1: CallCtlTermConnBridgedEv TermA’ GC1: GC1:CallCrlTermConnTalkingEv TA’ Exception is thrown to startMonitor request. A answers GC1 A’ barges the call B calls start monitor using GC2 giving CI1, A and TermA from GC1 Scenario Five 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. Application has call observer on both A and B. Application has monitoring capability enabled. Cisco Unified JTAPI Developers Guide for Cisco Unified Communications Manager, Release 15 and SUs 1279 Message Sequence Charts Message Sequence Charts

Page 1343 diagram