/mcpTAPI structures TAPI messages CTI messages Action Party A Party C is offering TSPI LINECALLINFO dwOrigin = OUTBOUND dwReason = DIRECT dwCallerID = A dwCalledID = B dwConnectedID = NULL dwRedirectingID = B dwRedirectionID = C's VMP TSPI: LINE_CALLSTATE hDevice = hCall-1 dwCallbackInstance = 0 dwParam1 = RINGBACK dwParam2 = 0 dwParam3 = 0 CallStateChangeEvent, CH = C1, State = Ringback, Reason = Direct, Calling = A, Called = C, OriginalCalled = C, LR = B 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 = Redirect, Calling = A, Called = C, OriginalCalled = C, LR = B Refer and Replace Scenarios In-Dialog Refer -Referrer in Cisco Unified Communications Manager Cluster The following table describes the message sequences for the Refer and Replaces scenario of in-dialog refer where referer is in Cisco Unified Communications Manager cluster. Cisco Unified TAPI Developers Guide for Cisco Unified Communications Manager, Release 15 and SUs 935 Message Sequence Charts Refer and Replace Scenarios