McDewey

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

Page 921

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

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_DEVSPECIFIC hDevice = hCall-1 dwCallBackInstance = 0 dwParam1 = StartTransmission dwParam2 = IP Address dwParam3 = Port CallStartTransmissionEvent, DH = A, CH = C1 LINE_DEVSPECIFIC events are sent only if the application has requested them by using lineDevSpecific(). Note Monitoring and Recording Monitoring a Call A (agent) and B (customer) get connected. BIB on A gets set to on. TAPI structures TAPI messages CTI messages Action Party C Cisco Unified TAPI Developers Guide for Cisco Unified Communications Manager, Release 15 and SUs 889 Message Sequence Charts Monitoring and Recording

Image 1 from page 921

Page 921 diagram