McDewey

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

Page 932

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

Expected events Action Park Status Event on B: At Step 3: Application will receive the LINE_CALLSTATE event with the Park Status = Parked. At Step 4: Application will receive the LINE_CALLSTATE event with the Park Status = Abandoned. Application will receive the LINE_CALLSTATE event with callstate IDLE. Application does a LineGetCallInfo. Scenario 4:

  1. The Park Monitoring message flag is Enabled using SLDST_SET_STATUS_MESSAGES request for Line B(3001).
  2. A(3000) calls B(3001)
  3. B(3001) receives the call and parks the call
  4. A(3000) hangs up the call. LineCallInfo will contain the following: hline : LH = 1 dwCallID : CallID dwReason :LINECALLREASON_PARKED dwRedirectingIDName TransactionIDID = Sub1. dwBearerMode: ParkStatus = 4 dwCallerID : ParkDN = 5555 dwCallerName : ParkDNPartition = P1 dwcalled : ParkedParty = 3000 dwCalledIDName : ParkedPartyPartition = P1. Cisco Unified TAPI Developers Guide for Cisco Unified Communications Manager, Release 15 and SUs 900 Message Sequence Charts Message Sequence Charts

Page 932 diagram