McDewey

Expected results CTI events Action LINECALLINFO::DEVSPECIFIC would contain Unique Call Reference A1 LineGetCallInfo on A LINECALLINFO::DEVSPECIFIC would contain Unique Call Reference B1 LineGetCallInfo on B Conference Chaining Scenario Using Join Application does a LineInitialize and opens all lines with new ExtVersion 0x000A0000. A, B and C are in Conference1. C, D and E are in another Conference2. Application sends CallJoinRequest to join both the conference calls. E drops from the conference. Expected results CTI events Action For A Unique Call Reference ID = ID1 For B Unique Call Reference ID = ID2 For C Unique Call Reference ID = ID3 A, B and C are in conference For C Unique Call Reference ID = ID4 For D Unique Call Reference ID = ID5 For E Unique Call Reference ID = ID6 C, D and E are in conference No change in Unique Call Reference ID after join Application Joins two confeences For D LINE_CALLDEVSPECIFIC event is received dwParam1=SLDSMT_LINECALLINFO_ DEVSPECIFICDATA dwParam2 = SLDST_UNIQUE_CALL_REF_ID_INFO dwParam3 = 0 CallGlobalCallHandleChanged received for D E drops from Conference Cisco Unified TAPI Developers Guide for Cisco Unified Communications Manager, Release 15 and SUs 713 Message Sequence Charts Conference Chaining Scenario Using Join