McDewey

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

Page 567

↗ View in doc context
page
567
source
cucm/v15/tapi-dev-guide/tapi-dev-guide.md
chunk_id
cucm::v15::tapi-dev-guide::tapi-dev-guide::581

Table 67: Hunt List Call to HP1 and No Agents Logged In or Registered Expected events Action At A: LINE_CALLSTATE -DISCONNECTED CallReason = x1(Direct) ExtendedCallReason = x1(DirectCall) Caller = A Called = HP1, HuntPilot = HP1 App initiates call from A to HP1. (None of the Huntmembers are registered or logged in). Call is disconnected. FailOver or FailBack Scenario Expected events Action Line Open Successful LineIntialize OpenLines – 1000:P1 CallPickUp Group DN and Partition Information will be sent to application LineGetDevCaps with Extension Version – 000A0000 on 1000:P1 Line_Reply with success. LINE_CREATE event will sent to Application for P1:1111 Application sends CciscoLineDevSpecificRegisterCallPickupGroupForNotification with DN and Partition info of PickUpGroup P1:1111 LineOpen Successful LineOpen with new DeviceID LINE_APPNEWCALL LINE_CALLSTATE with State = LINECALLSTATE_UNKNOWN to Application on Line P1:1111 P1:4000 calls P1:1002 LINE_CALLINFO dwCallState : PickupCallState (0x10000000) dwCallerId : 4000 dwCalledID : 1002 dwCallorigin: Internal dwCallReason : Direct Check for all fields of Calling and Called Information LineGetCallInfo Cisco Unified TAPI Developers Guide for Cisco Unified Communications Manager, Release 15 and SUs 535 Message Sequence Charts FailOver or FailBack Scenario

Page 567 diagram