McDewey

TAPI structures TAPI messages Action Line_Reply with error = LINEERR_OPERATIONUNAVAIL Join on the Primary Call[C ' A1]with [A2 ' D ] call as consult call CCiscoLineDevSpecificJoin() on the call [c ' A1] on Device A with CallIDstoJoin = CallID of Call [D ' A2] Or CciscoLineDevSpecificDirectTransfer on the call [c ' A1] on Device A with ConsultCallID = CallID of [D ' A2] Direct Transfer / Join Across Line is not supported on CTI Remote Device LINEERR_OPERATIONUNAVAIL Or PHONEERR_OPERATIONUNAVAIL Depending on the Line/Phone API request. Variation: On any unsupported Feature Request For Example: CallAcceptRequest CallAnswerRequest CallParkRequest LineCallUnParkRequest Expected result would be same as observed on CTI Remote Device Variation : Test the same with CSF Device in Extend Mode Cbarge 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 Cisco Unified TAPI Developers Guide for Cisco Unified Communications Manager, Release 15 and SUs 626 Message Sequence Charts Message Sequence Charts