/mcpTAPI structures TAPI messages Action Call model on CTI Remote Device : [C ' A1]-[ Original Call1]-[ state = Conference] [A1 ' Conference]-[ Conference Parent Call]-[State = CONNECTED] [A1 ' D]-[Consult Call]-[state -CONFERENCE] Call Model on Enterprise Phone: Same as CTI Remote Device, all calls are RIU Calls Complete Conference on the Primary Call[C ' A]with [A ' D ] call as consult call LineAddtoConference() on the call [c ' A1] on Device A All 3 parties C, D and CTI Remote Device[Remote Destination] 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 Join on Same Line 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 A1 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 624 Message Sequence Charts Message Sequence Charts