McDewey

TAPI structures TAPI messages Action Original Call on CTI Remote Device[A] [C ' A1]: LINE_CALSTATE = CONFERENCE Conference Parent Call on CTI Remote Device[A] : LINE_APPNEWCALL LINE_CALLSTATE -Param1 = CONNECTED Consult Call on CTI Remote Device[A] [D ' A1]: LINE_CALLSTATE -Param1 = CONFERENCE Conference Model will be created on CTI Remote Device and RIU Conference Model on EP Join on the Primary Call[C ' A1]with [A1 ' D ] call as consult call CCiscoLineDevSpecificJoin() on the call [c ' A1] on Device A with CallIDstoJoin = CallID of Call [D ' A1] CTIRemoteDevice [A -Remote Destination], D and C will be in Conference. Expected result would be same as observed on CTI Remote Device Variation : Test the same with CSF Device in Extend Mode Direct Transfer/Join Across Line on CTI Remote Device Precondition: same as above usecase TAPI structures TAPI messages Action Lines are Enumerated LineInitializeEx LineOpen() returns Success Open all Lines (A, A', A'' and C) LineOpen() with ExtVer-0x000C0000 Make Call between C and A1[Remote Destinaton], either normal incoming or DVO call on CTI Remote Device Call Info is same above test cases Make Call between D and A2 Call Info is same above Multiple Call across lines test case Cisco Unified TAPI Developers Guide for Cisco Unified Communications Manager, Release 15 and SUs 625 Message Sequence Charts Message Sequence Charts