McDewey

TAPI structures TAPI messages CTI messages Action LINECALLINFO (hCall-1) hLine = C dwCallID = T2 dwOrigin = INTERNAL dwReason = DIRECT dwCallerID = B dwCalledID = C dwConnectedID = B dwRedirectionID = NP dwRedirectingID = NP Devspecific Data : CallSecurityInfo = Encrypted LINE_CALLDEVSPECIFIC hDevice = C dwCallbackInstance = 0 dwParam1 = SLDSMT_LINECALLINFO_ DEVSPECIFICDATA dwParam2 = SLDST_CALL_SECURITY_STATUS dwParam3 = 0 CallStateChangedEvent, CH = C4, GCH = G2, Calling = B, Called = C, OrigCalled = C, LR = NP, State = Connected, Origin = OutBound, Reason = Direct SecurityStaus = NotAuthenticated CtiCallSecurityStatusUpdate LH = C, CH = C4 SecurityStaus = Encrypted Party B B completes conf LINECALLINFO (hCall-1) hLine = B dwCallID = T1 dwOrigin = CONFERENCE dwReason = UNKNOWN dwCallerID = NP dwCalledID = NP dwConnectedID = NP dwRedirectionID = NP dwRedirectingID = NP Devspecific Data : CallSecurityInfo = Encrypted LINE_CALLDEVSPECIFIC hDevice = B dwCallbackInstance = 0 dwParam1 = SLDSMT_LINECALLINFO_ DEVSPECIFICDATA dwParam2 = SLDST_CALL_SECURITY_STATUS dwParam3 = 0 CtiCallSecurityStatusUpdate LH = B, CH = C2 SecurityStaus = Encrypted Hold or Resume in Secure Conference Conference bridge includes security profile. MOH gets configured. A, B, and C represent secure phones and exist in conference with overall call security status as secure. TAPI structures TAPI messages CTI messages Action Party A A does lineHold Cisco Unified TAPI Developers Guide for Cisco Unified Communications Manager, Release 15 and SUs 948 Message Sequence Charts Hold or Resume in Secure Conference