McDewey

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

Page 333

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

hEvent If dwOptions specifies PHONEINITIALIZEEXOPTION_USEEVENT, TAPI returns the event handle in this member. hCompletionPort If dwOptions specifies PHONEINITIALIZEEXOPTION_USECOMPLETIONPORT, the application must specify, in this member, the handle of an existing completion port that is opened by using CreateIoCompletionPort. dwCompletionKey If dwOptions specifies PHONEINITIALIZEEXOPTION_USECOMPLETIONPORT, the application must specify in this field a value that is returned through the lpCompletionKey parameter of GetQueuedCompletionStatus to identify the completion message as a telephony message. PHONEMESSAGE The PHONEMESSAGE structure contains the next message that is queued for delivery to the application. The phoneGetMessage function returns the following structure. Structure Details typedef struct phonemessage_tag { DWORD hDevice; DWORD dwMessageID; DWORD_PTR dwCallbackInstance; DWORD_PTR dwParam1; DWORD_PTR dwParam2; DWORD_PTR dwParam3; } PHONEMESSAGE, FAR *LPPHONEMESSAGE; Members hDevice A handle to a phone device. dwMessageID A phone message. dwCallbackInstance Instance data that is passed back to the application, which the application specified in phoneInitializeEx. TAPI does not interpret DWORD. dwParam1 A parameter for the message. dwParam2 A parameter for the message. dwParam3 A parameter for the message. Cisco Unified TAPI Developers Guide for Cisco Unified Communications Manager, Release 15 and SUs 301 Basic TAPI Implementation PHONEMESSAGE

Page 333 content