McDewey

TAPI structures TAPI messages CTI messages Action CallStateChangeEvent, CH = C1, State = Ringback, Reason = Direct, Calling = A, Called = C, OriginalCalled = B, LR = B TSPI LINECALLINFO dwOrigin = OUTBOUND dwReason = DIRECT dwCallerID = A dwCalledID = B dwConnectedID = NULL dwRedirectingID = B dwRedirectionID = C TSPI: LINE_CALLSTATE, hDevice = hCall-1, dwCallbackInstance = 0, dwParam1 = RINGBACK dwParam2 = 0 dwParam3 = 0 Party C TSPI LINECALLINFO dwOrigin = INTERNAL dwCallerID = A dwCalledID = C dwConnectedID = NULL dwRedirectingID = B dwRedirectionID = C TSPI: LINE_CALLSTATE, hDevice = hCall-1, dwCallbackInstance = 0, dwParam1 = OFFERING dwParam2 = 0 dwParam3 = 0 CallStateChangedEvent, CH = C3, State = Offering, Reason = BlindTransfer, Calling = A, Called = C, OriginalCalled = B, LR = B Call Control Discovery BasicCallInitiatedFromTAPIFromPhoneAonCluster1toPhoneBonCluster2 Configuration SCCP phone A(1900) are registered to cluster A Phones A are associated with the end-user cluster1 SCCP phone B(1000) registered to cluster B Phones B are associated with the end-user cluster2 CUCM learns a pattern 10XX, plus PSTN failover rule as 0:1408972 from SAF network. TAPI is observing A. Procedure Application monitors A Application sends a lineMakeCall at A to call B Cisco Unified TAPI Developers Guide for Cisco Unified Communications Manager, Release 15 and SUs 481 Message Sequence Charts Call Control Discovery