McDewey

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

Page 750

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

Expected results CTI events 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 LINECALLINFO::DEVSPECIFIC would contain Unique Call Reference C2 LineGetCallInfo on C Hunt List Scenario LineGroup LG1,LG2 and LG3 configured with A,B and C. HuntList “Hunt_List” configured with Line Groups LG1,LG2 and LG3. Hunt Pilot “99999” configured with this HuntList. Application does a LineInitialize. Application opens all lines with new ExtVersion 0x000A0000. D calls “99999”. Call is routed through A, B and C. Expected results CTI events Action LineInitialize LineOpen on A , LineOpen on B, LineOpen on C, LineOpen on D with new ExtVesrion 0x000A0000 Cisco Unified TAPI Developers Guide for Cisco Unified Communications Manager, Release 15 and SUs 718 Message Sequence Charts Hunt List Scenario

Page 750 diagram