McDewey

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

Page 438

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

SLDST_LINE_EXISTING_CALL, SLDSMT_OPEN_LOGICAL_CHANNEL, SLDSMT_CALL_TONE_CHANGED, SLDSMT_LINECALLINFO_ DEVSPECIFICDATA, SLDSMT_HOLD_REVERSION, SLDSMT_LINE_PROPERTY_CHANGED, SLDSMT_MONITORING_STARTED, SLDSMT_MONITORING_ENDED, SLDSMT_RECORDING_STARTED, SLDSMT_RECORDING_ENDED, SLDSMT_NUM_TYPE, SLDSMT_IP_ADDRESSING_MODE_CHANGED, SLDSMT_START_TRANSMISION_ADDRESSING_MODE, SLDSMT_START_RECEPTION_ADDRESSING_MODE, SLDSMT_DEVICE_STATE, SLDSMT_MONITORING_TERMINATED, SLDSMT_MEDIA_TO_BIB_STARTED, SLDSMT_MEDIA_TO_BIB_ENDED, SLDSMT_MONITORING_MODE_UPDATED, SLDSMT_RTP_GET_IP_PORT SLDSMT_MULTIMEDIA_STREAMSDATA, SLDSMT_ANNOUNCEMENT_STARTED, SLDSMT_ANNOUNCEMENT_ENDED, SLDSMT_RECORDING_FAILED }; Announcement Events SLDSMT_ANNOUNCEMENT_STARTED When an announcement starts, the SLDSMT_ANNOUNCEMENT_STARTED message is sent to the application. The format of the parameters follows: LINE_DEVSPECIFIC hDevice -TAPI call handle dwParam1 - SLDSMT_ANNOUNCEMENT_STARTED dwParam2 -unused dwParam3 -unused SLDSMT_ANNOUNCEMENT_ENDED When an announcement ends, the SLDSMT_ANNOUNCEMENT_ENDED message is sent to the application. If the announcement does not play, the application analyzes the cause code parameter to verify whether the announcement was successful and the failure reason. The format of the parameters follows: LINE_DEVSPECIFIC hDevice -TAPI call handle dwParam1 - SLDSMT_ANNOUNCEMENT_ENDED dwParam2 -result (0 or error code in case of failure) dwParam3 -unused Cisco Unified TAPI Developers Guide for Cisco Unified Communications Manager, Release 15 and SUs 406 Cisco Device-Specific Extensions Announcement Events

Page 438 content