McDewey

TAPI structures TAPI messages Action LineDrop() success Call on CTI Remote Device : LINE_CALLSTATE -Param1 = DISCONNECTED LINE_CALLSTATE -Param1 = IDLE Drop the onHold call on CTI Remote Device LineDrop() for the call on Device A (CTI-RD) Call on Remote Destination is dropped C and EP call will not be disconnected. On C call will be in Connected state and on EP call will be in OnHold state. Expected result would be same as observed on CTI Remote Device Variation : Test the same with CSF Device in Extend Mode Transfer 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 as above test cases LineSetupTransfer returns success Primary Call on CTI Remote Device[A] [C ' A1] : LINE_CALLSTATE -Param1 = OnholdPendingTransfer Consult Call on CTI Remote Device[A] [A1 ' D]: Setup Transfer and Dial D LineSetupTransfer() on the call [C ' A1] on Device A Cisco Unified TAPI Developers Guide for Cisco Unified Communications Manager, Release 15 and SUs 619 Message Sequence Charts Message Sequence Charts