McDewey

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

Page 956

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

TAPI structures TAPI messages CTI messages Action No change LINE_DEVSPECIFIC hDevice = hCall-1 dwCallBackInstance = 0 dwParam1 = StartReception dwParam2 = IP Address dwParam3 = Port CallStartReceptionEvent, DH = A, CH = C1 No change LINE_DEVSPECIFIC1 hDevice = hCall-1 dwCallBackInstance = 0 dwParam1 = StartTransmission dwParam2 = IP Address dwParam3 = Port CallStartTransmissionEvent, DH = A, CH = C1 LINE_DEVSPECIFIC events only get sent if the application requested them by using lineDevSpecific(). Note Blind Transfer Through Translation Pattern The following table describes the message sequences for the Presentation Indication scenario of Blind Transfer through Translation Pattern. In this scenario, A calls via translation pattern B, B answers, and A and B are connected. TAPI structures TAPI messages CTI messages Action Party A Party B does a lineBlindTranfser() to blind transfer call from party A to party C via translation pattern Cisco Unified TAPI Developers Guide for Cisco Unified Communications Manager, Release 15 and SUs 924 Message Sequence Charts Blind Transfer Through Translation Pattern

Image 1 from page 956

Page 956 diagram