McDewey

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

Page 728

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

Expected results CTI event Action LINECALLINFO::DEVSPECIFIC would contain Unique Call Reference B2 LineGetCallInfo on B (Consultation call between B and C) LINECALLINFO::DEVSPECIFIC would contain Unique Call Reference C1 LineGetCallInfo on C (Consultation call between B and C) For C LINE_CALLDEVSPECIFIC event is received dwParam1=SLDSMT_LINECALLINFO_ DEVSPECIFICDATA dwParam2 = SLDST_UNIQUE_CALL_REF_ID_INFO dwParam3 = 0 LINECALLINFO::DEVSPECIFIC would contain Unique Call Reference C2 CallGlobalCallHandleChangedEvent received for C C answers the call. B completes transfer. LINECALLINFO::DEVSPECIFIC would contain Unique Call Reference A1 LineGetCallInfo on A (Call between A and C) LINECALLINFO::DEVSPECIFIC would contain Unique Call Reference C2 LineGetCallInfo on C2 (Consultation call between B and C) Consult Transfer Scenario: Variation 2 A calls B and B answers the call. B sets up transfer to C. Application does a LineInitialize and opens all lines with new ExtVersion 0x000A0000. Application completes the transfer. A is connected to C. Expected Results CTI events Action LineInitialize LineOpen on A , LineOpen on B, LineOpen on C with new ExtVesrion 0x000A0000 A calls B and B answers the call. B setups transfer to C and C answers the call Cisco Unified TAPI Developers Guide for Cisco Unified Communications Manager, Release 15 and SUs 696 Message Sequence Charts Consult Transfer Scenario: Variation 2

Page 728 diagram