/mcpExpected results CTI events Action 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 C1 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 NewCallEvent received for C CallGlobalCallHandleChangedEvent received for C C dials parkDn LINECALLINFO::DEVSPECIFIC would contain Unique Call Reference A1 LineGetCallInfo on A LINECALLINFO::DEVSPECIFIC would contain Unique Call Reference C2 LineGetCallInfo on C 3-Party Conference 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 to C, C answers the call, and B completes conference. A, B and C are in conference. For all conference scenarios, conference call leg’s Unique Call Reference ID is 0. Note Cisco Unified TAPI Developers Guide for Cisco Unified Communications Manager, Release 15 and SUs 708 Message Sequence Charts 3-Party Conference Call Scenario
