McDewey

TAPI structures TAPI messages Action LineDrop() success Call on C : LINE_CALLSTATE -Param1 = DISCONNECTED LINE_CALLSTATE -Param1 = IDLE Call on CTI Remote Device : LINE_CALLSTATE -Param1 = DISCONNECTED LINE_CALLSTATE -Param1 = IDLE Call on Enterprise Phone : LINE_CALLSTATE - Param1 = CONNECTED Param2 = 0x02 (Inactive) LINE_CALLSTATE -Param1 = IDLE LineDrop() for the call on Device A (CTI-RD) Call on Remote Destination is dropped Call on C : LINE_CALLSTATE -Param1 = CONNECTED Call on CTI Remote Device : LINE_CALLSTATE -Param1 = DISCONNECTED LINE_CALLSTATE -Param1 = IDLE Call on Enterprise Phone : LINE_CALLSTATE - Param1 = CONNECTED Variation : Answer the call on Enterprise Phone (B) LineAnswer() on the call on Device B Call on Remote Device/Remote Destination drops URI Dialing -DVO Call (Outgoing Call Initiation From 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' and C) LineOpen() with ExtVer-0x000C0000 Cisco Unified TAPI Developers Guide for Cisco Unified Communications Manager, Release 15 and SUs 633 Message Sequence Charts Message Sequence Charts