McDewey

Multi-vendor documentation library · semantic search · MCP endpoint at /mcp

Page 1000

↗ View in doc context
page
1000
source
cucm/v15/tapi-dev-guide/tapi-dev-guide.md
chunk_id
cucm::v15::tapi-dev-guide::tapi-dev-guide::1014

Expected result Action SRTP info will not be available Security Indicator = MEDIA_NOT_ENCRYPT CallAttributeTye = CallAttribute_SilentMonitorCall_Target Address = B’s DN, Partition = B’s Partition Device Name = B’s Device Name Transaction ID = XXXX CallAttributeTye = ‘CallAttribute_RecordedCall’ Address = D’s DN, Partition = D’s Partition Device Name = D’s Device Name Transaction ID = 0 Call Security Status = Not Authenticated LineGetCallInfo on C Shared Lines-Initiating a New Call Manually The following table describes the message sequences for Shared Lines-Initiating a new call manually where Party A and Party A’ represent shared line appearances. Also, Party A and Party A’ are idle. TAPI structures TAPI messages CTI messages Action LINECALLINFO (hCall-1) hLine = A dwCallID = T1 dwOrigin = OUTBOUND dwReason = DIRECT dwCallerID = A dwCalledID = NP dwConnectedID = NP dwRedirectionID = NP dwRedirectionID = NP LINE_APPNEWCALL hDevice = A dwCallbackInstance = 0 dwParam1 = 0 dwParam2 = hCall-1 dwParam3 = OWNER NewCallEvent, CH = C1, GCH = G1, Calling = A, Called = NP, OrigCalled = NP, LR = NP, State = Dialtone, Origin = OutBound, Reason = Direct, RIU = false

  1. Party A goes off-hook Cisco Unified TAPI Developers Guide for Cisco Unified Communications Manager, Release 15 and SUs 968 Message Sequence Charts Shared Lines-Initiating a New Call Manually

Page 1000 diagram