McDewey

Table 125: Message Sequences for In-Dialog Refer -Referrer in Cisco Unified Communications CallState/CallInfo @Refer-to-Target (C) CallState/CallInfo @Referree (B) CallState/CallInfo @Referrer (A) Actions A-->B has a call in connected state. The call party information at B should be {calling = A, called = B, LRP = null, origCalled = B, reason = direct} TAPI CallInfo dwCallerID = A dwCalledID = B dwRedirectingID = null dwRedirectionID = null dwConnectedID = A dwReason = Direct dwOrigin = LINECALL ORIGIN_INTERNAL A-->B has a call in connected state. The call party information at A should be {calling = A, called = B, LRP = null, origCalled = B, reason = direct} TAPI CallInfo dwCallerID = A dwCalledID = B dwRedirectingID = null dwRedirectionID = null dwConnectedID = B dwReason = Direct dwOrigin = LINECALL ORIGIN_INTERNAL Referrer (A), Referee (B), and Refer-to-Target (C) exist in Cisco Unified Communications Manager cluster, and CTI is monitoring those lines NewCallEvent should be {calling = B, called = C, LRP = A, origCalled = C, reason = REFER} LINECALLSTATE_OFFERING TAPI CallInfo dwCallerID = B dwCalledID = C dwRedirectingID = A dwRedirectionID = C dwConnectedID = “” dwReason = LINECALL REASON_UNKNOWN with extended REFER dwOrigin = LINECALL ORIGIN_INTERNAL A gets LINECALLSTATE_ UNKNOWN | CLDSMT_ CALL_WAITING_STATE with extended reason = REFER TAPI CallInfo dwCallerID = A dwCalledID = B dwRedirectingID = null dwRedirectionID = null dwConnectedID = B dwReason = Direct dwOrigin = LINECALL ORIGIN_INTERNAL (A) initiates REFER (B) to (C) Cisco Unified TAPI Developers Guide for Cisco Unified Communications Manager, Release 15 and SUs 936 Message Sequence Charts Message Sequence Charts