McDewey

TAPI structures TAPI messages CTI messages Action Party A’ LINECALLINFO (hCall-2) hLine = A’ dwCallID = T1 dwOrigin = OUTBOUND dwReason = DIRECT dwCallerID = A’ dwCalledID = B dwConnectedID = B dwRedirectionID = NP dwRedirectionID = NP LINE_CALLSTATE hDevice = hCall-2 dwCallbackInstance = 0 dwParam1 = CONNECTED dwParam2 = INACTIVE dwParam3 = 0 LINE_CALLINFO hDevice = hCall-2 dwCallbackInstance = 0 dwParam1 = CONNECTEDID dwParam2 = 0, dwParam3 = 0 CallStateChangedEvent, CH = C1, State = Connected, Cause = CauseNoError, Reason = Direct, Calling = A’, Called = B, OrigCalled = B, LR = NP, RIU = true SRTP Media Terminate by Application (Open Secure CTI Port or RP) • Negotiate version • Sends LineOpen with extension version as 0x8007000 • Send CciscoLineDevSpecificUserSetSRTPAlgorithmID • Send CCiscoLineDevSpecificUserControlRTPStream • Now, the CTI port or RP gets registered as secure port • Make call from secure IP phone to the CTI port or RP port • Answer the call from application • SRTP indication gets reported as LineDevSpecific event • SRTP key information get stored in LINECALLINFO::devSpecifc for retrieval Media Terminate by TSP Wave Driver (Open Secure CTI Port) • Negotiate version • Sends LineOpen with extension version as 0x4007000 • Send CciscoLineDevSpecificUserSetSRTPAlgorithmID • Send CciscoLineDevSpecificSendLineOpen Cisco Unified TAPI Developers Guide for Cisco Unified Communications Manager, Release 15 and SUs 973 Message Sequence Charts SRTP