McDewey

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

Page 1105

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

Result Scenario GC1: TermConnDroppedEv C GC1: CallCtlTermConnDroppedEv C GC1: ConnDisconnectedEv C GC1: CallCtlConnDisconnectedEv C GC1: ConnConnectedEv L GC1: CallCtlConnEstablishedEv L GC1: TermConnActiveEv L GC1: CallCtlTermConnTalkingEv TL L answers the call The following call scenarios are generally un-supported and applications are encouraged to enable the huntlist feature and adapt to the event flows described above. Following are the expected events when the feature is disabled. Scenario 23 Hunt list feature is disabled. Basic call to hunt pilot Result Scenario GC1:CallActiveEv GC1:ConnCreatedEv A GC1:ConnConnectedEv A GC1:CallCtlConnInitiatedEv A GC1:TermConnCreatedEv TermA GC1:TermConnActiveEv TermA GC1:CallCtlTermConnTalkingEv TermA GC1: CallCtlConnEstablishedEv A GC1: ConnCreatedEv P GC1: ConnOfferedEv P … GC1: ConnAlertingEv P GC1: ConnConnected P GC1: CallCtlConnEstablishedEv A A (1000) calls Hunt Pilot P (2000), call is offered at C (3001) and is answered. Application is observing A. GCID is the call is GC1. C answers the call bvHunt list feature is disabled Cisco Unified JTAPI Developers Guide for Cisco Unified Communications Manager, Release 15 and SUs 1041 Message Sequence Charts Message Sequence Charts

Page 1105 diagram