McDewey

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

Page 1664

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

Call information Events Action GC2: Calling: B Called: A LRP: null Current calling: B Current called:A GC2:CallActive Cause: CAUSE_NORMAL GC2: ConnCreatedEv for B Cause: CAUSE_NORMAL GC2: CallCtlConnInitiatedEv GC2: TermConnCreatedEv B(T1) GC2: TermConnActiveEv B(T1) GC2: TermConnCreatedEv for B(T2) GC2: TermConnPassiveEv for B(T2) GC2: CallCtlTermConnTalkingEv B(T1) B Cause: CAUSE_NORMAL GC2: CallCtlConnDialingEv for B GC2: CallCtlConnEstablishedEv for B Cause: CAUSE_NORMAL GC2: ConnCreatedEv A , here A.getType() = MONITORING_TARGET GC2: ConnInProgressEv A GC2: CallCtlConnOfferedEv A, GC2: ConnAlertingEv A GC2: CallCtlConnAlertingEv A GC2: ConnConnectedEv A GC2: CallCtlConnEstablishedEv A GC2: CiscoRTPInputStartedEv B(T1) getCiscoFeatureReason() = CiscoFeatureReason.REASON_CALL_MONITORING GC2:CiscoTermConnMonitorTargetInfoEv B(T1) Cause: CAUSE_NORMAL address:A, here A.getType() = MONITORING_TARGET, terminal name: TA, rtphandle = CI1 CiscoMonitorTagetInfo.getMonitorType() = CiscoCall.SILENT_MONITOR [Note: Above connection is not created on Observered address A, rather an another Address object of type MONITORING_TARGET.] GC1: CiscoTermConnMonitoringStartEv TAgetMonitorType() = CiscoCall.SILENT_MONITOR GC1: CiscoTermConnMonitorInitiatorInfoEv TA Cause: CAUSE_NORMAL address:B, device name: B(T1) CiscoMonitorInitiatorInfo.getMonitorType() = CiscoCall.SILENT_MONITOR B calls start monitor using GC2 giving CI1, A and TermA from GC1 and mode as Silent Cisco Unified JTAPI Developers Guide for Cisco Unified Communications Manager, Release 15 and SUs 1600 Message Sequence Charts Message Sequence Charts

Page 1664 diagram