McDewey

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

Page 734

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

Shared Line Scenario with Barge Application does a LineInitialize.Application opens all lines with new ExtVersion 0x000A0000. A calls B, B’. B answers the call. Expected results CTI events Action LineInitialize LineOpen on A , LineOpen on B, LineOpen on B’ with new ExtVesrion 0x000A0000 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 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 NewCallEvent received for B’ A calls B, B’answers the call LINECALLINFO::DEVSPECIFIC would contain Unique Call Reference A1 LineGetCallInfo on A LINECALLINFO::DEVSPECIFIC would contain Unique Call Reference B1 LineGetCallInfo on B 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 702 Message Sequence Charts Shared Line Scenario with Barge

Page 734 diagram