McDewey

TAPI structures TAPI messages CTI messages Action LINECALLINFO (hCall-1) hLine = C dwCallID = T2 dwOrigin = OUTBOUND dwReason = DIRECT dwCallerID = C dwCalledID = NP dwConnectedID = NP dwRedirectionID = NP dwRedirectingID = NP LINE_CALLINFO hDevice = hCall-1 dwCallbackInstance = 0 dwParam1 = ORIGIN dwParam2 = 0 dwParam3 = 0 LINE_CALLINFO hDevice = hCall-1 dwCallbackInstance = 0 dwParam1 = REASON, CALLERID dwParam2 = 0 dwParam3 = 0 NewCallEvent, CH = C3, GCH = G2, Calling = C, Called = NP, OrigCalled = NP, LR = NP, State = Dialtone, Origin = OutBound, Reason = Direct C(supervisor) issues start monitoring req with A’s permanentLineID as input Party C A’s BIB automatically answers LINECALLINFO (hCall-1) hLine = C dwCallID = T2 dwOrigin = OUTBOUND dwReason = DIRECT dwCallerID = C dwCalledID = A dwConnectedID = A dwRedirectionID = NP dwRedirectingID = NP LINE_CALLSTATE hDevice = hCall-1 dwCallbackInstance = 0 dwParam1 = CONNECTED dwParam2 = ACTIVE dwParam3 = 0 CallStateChangedEvent, CH = C3, State = Connected, Cause = CauseNoError, Reason = Direct, Calling = C, Called = A, OrigCalled = A, LR = NP Party A Cisco Unified TAPI Developers Guide for Cisco Unified Communications Manager, Release 15 and SUs 890 Message Sequence Charts Message Sequence Charts