McDewey

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

Page 1242

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

Use case 5 getCiscoFeatureReason() returns CiscoFeatureReason. REASON_NORMAL GC1 & GC2 call will be created as normal. GC1: CallCtlTermConnHeldEv for TB GC2: CallCtlTermConnHeldEv for TB GC1: CallCtlTermConnTalkingEv for TB GC1: CiscoTransferStartEv GC1: CiscoCallChangedEv GC1: ConnCreatedEv for C GC1: ConnConnectedEv for C GC1: CallCtlConnEstablishedEv for C GC1: TermConnCreatedEv for TC GC1: TermConnActiveEvent for TC GC1: CallCtlTermConnTalkingEv TC GC2: TermConnDroppedEv for TC GC2: CallCtlTermConnDroppedEv for TC GC2: ConnDisconnectedEv for C GC2: CallCtlConnDisconnectedEv for C GC1: TermConnDroppedEv for TB GC1: CallCtlTermConnDroppedEv for TB GC1: ConnDisconnectedEv for B1 GC1: CallCtlConnDisconnectedEv for B1 GC2: TermConnDroppedEv for TB GC2: CallCtlTermConnDroppedEv for TB GC2: ConnDisconnectedEv for B2 GC2: CallCtlConnDisconnectedEv for B2 GC2: CallInvalidEvent GC2: CallObservationEndedEv GC1: CiscoTransferEndEv Consult Transfer – Swap calls A calls B, B answers – GC1 B puts A–>B call on hold B setup consult Transfer to C, C answers – GC2 User B presses Swap key, User B presses transfer to complete the transfer Cisco Unified JTAPI Developers Guide for Cisco Unified Communications Manager, Release 15 and SUs 1178 Message Sequence Charts Message Sequence Charts

Page 1242 diagram