McDewey

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

Page 743

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

Expected results CTI events Action LINECALLINFO::DEVSPECIFIC would contain Unique Call Reference C2 LineGetCallInfo on C Three-Party Conference Drop Down to Two-Party Call Scenario Application does a LineInitialize and opens all lines with new ExtVersion 0x000A0000. A calls B and B answers the call. B sets up conference with C, C answers the call, and B completes conference. A,B and C in conference. C drops from the conference.A connected to B. Expected results CTI events Action For A LINE_CALLDEVSPECIFIC event is received dwParam1=SLDSMT_LINECALLINFO_ DEVSPECIFICDATA dwParam2 = SLDST_UNIQUE_CALL_REF_ID_INFO dwParam3 = 0 For B LINE_CALLDEVSPECIFIC event is received dwParam1=SLDSMT_LINECALLINFO_ DEVSPECIFICDATA dwParam2 = SLDST_UNIQUE_CALL_REF_ID_INFO dwParam3 = 0 NewCallEvent received for A NewCallEvent received for B LineInitialize Call lineNegotiateVersion with LineOpen on A, LineOpen on B, LineOpen on C with new ExtVesrion 0x000A0000 LINECALLINFO::DEVSPECIFIC would contain Unique Call Reference A1 LineGetCallInfo on A LINECALLINFO::DEVSPECIFIC would contain Unique Call Reference B1 LineGetCallInfo on B Cisco Unified TAPI Developers Guide for Cisco Unified Communications Manager, Release 15 and SUs 711 Message Sequence Charts Three-Party Conference Drop Down to Two-Party Call Scenario

Page 743 diagram