McDewey

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

Page 748

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

Expected results CTI events Action For B LINE_CALLDEVSPECIFIC event is received dwParam1=SLDSMT_LINECALLINFO_ DEVSPECIFICDATA dwParam2 = SLDST_UNIQUE_CALL_REF_ID_INFO dwParam3 = 0 For C LINE_CALLDEVSPECIFIC event is received dwParam1=SLDSMT_LINECALLINFO_ DEVSPECIFICDATA dwParam2 = SLDST_UNIQUE_CALL_REF_ID_INFO dwParam3 = 0 NewCallEvent received for B NewCallEvent received for C B SetupTransfer to C 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) C answers the call.B completes transfer. LINECALLINFO::DEVSPECIFIC would contain Unique Call Reference A1 LineGetCallInfo on A LINECALLINFO::DEVSPECIFIC would contain Unique Call Reference C1 LineGetCallInfo on C Transfer Call Scenario via QSIP with Path Replacement Application does a LineInitialize and opens all lines with new ExtVersion 0x000A0000. A in Cluster 1 calls B in Cluster 2, B answers the call and sets up transfer with C in Cluster 1. C answers the call amd B completes the transfer. A connected to C. Expected results CTI events Action LineInitialize LineOpen on A, LineOpen on B, LineOpen on C with new ExtVesrion 0x000A0000 Cisco Unified TAPI Developers Guide for Cisco Unified Communications Manager, Release 15 and SUs 716 Message Sequence Charts Transfer Call Scenario via QSIP with Path Replacement

Page 748 diagram