McDewey

TAPI structures TAPI messages Action 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 Expected Result : All calls go to Disconnected/IDLE State Variation : One of the Remote Destination answers the call before the "Answer Too Soon Timer" Expected result: only Remote Destination which is set ACTIVE rings Call rings immediately and "Delay before Ringing Timer" wouldn't be effective when ACTIVE RD is set. Remote Destination can answer the call Immediately and "Answer Too Soon Timer" wouldn't be effective when ACTIVE RD is set. Variation : Active RD set on CTI Remote Device There won't be second call on Remote Destination, only at Remote Device second call will present and reported to Application. Continuation to above variation On second Incoming Call... Expected result: would be same as observed on CTI Remote Device Variation : Test with CSF Device in Extend Mode DVO Call (Outgoing Call Initiation From CTI Remote Device) Precondition: same as above usecase TAPI structures TAPI messages Action Lines are Enumerated LineInitializeEx Cisco Unified TAPI Developers Guide for Cisco Unified Communications Manager, Release 15 and SUs 607 Message Sequence Charts Message Sequence Charts