McDewey

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

Page 936

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

Expected events Action Park Status Event on B: At Step 4: Application will be notified about the Parked call through LINE_NEWCALL event.when ever cisco TSP recives the LINE_PARK_STATUS event for already parked call. Application does a LineGetCallInfo. LineCallInfo will contain the following: hline : LH = 1 dwCallID : CallID dwReason :LINECALLREASON_PARKED dwRedirectingIDName TransactionIDID = Sub1. dwBearerMode: ParkStatus = 2 dwCallerID : ParkDN = 5555 dwCallerName : ParkDNPartition = P1 dwcalled : ParkedParty = 3000 dwCalledIDName : ParkedPartyPartition = P1. Scenario 1: 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. Now the Line B(3001) is monitered by TSP Shared Line Scenario Setup: A(3000) ,D(3003) are Cisco Unified IP phones (future version) running SIP B(3001) and B'(3001) are shared lines for Cisco Unified IP phones (future version) running SIP C(3002) and C'(3002) are shared lines where C is a Cisco Unified IP phone (future version) running SIP and C' is a Cisco Unified IP Phone 7900 Series running SIP . For the shared lines the events will be delivered to the phone which parks the call .Events will not be delivered to the other phone though the line is shared. Cisco Unified TAPI Developers Guide for Cisco Unified Communications Manager, Release 15 and SUs 904 Message Sequence Charts Message Sequence Charts

Page 936 diagram