McDewey

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

Page 199

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

lineGetID, the application must set the dwTotalSize member of this structure to indicate the amount of memory that is available to TAPI for returning information. lpszDeviceClass A pointer to a NULL-terminated ASCII string that specifies the device class of the device whose identifier is requested. Device classes include wave/in, wave/out and tapi/line. Valid device class strings are those that are used in the SYSTEM.INI section to identify device classes. lineGetLineDevStatus The lineGetLineDevStatus function enables an application to query the specified open line device for its current status. Function Details LONG lineGetLineDevStatus( HLINE hLine, LPLINEDEVSTATUS lpLineDevStatus ); Parameters hLine A handle to the open line device to be queried. lpLineDevStatus A pointer to a variably sized data structure of type LINEDEVSTATUS. Upon successful completion of the request, the device status of the line fills this structure. Prior to calling lineGetLineDevStatus, the application should set the dwTotalSize member of this structure to indicate the amount of memory that is available to TAPI for returning information. lineGetMessage The lineGetMessage function returns the next TAPI message that is queued for delivery to an application that is using the Event Handle notification mechanism (see lineInitializeEx, on page 176 for more information). Function Details LONG WINAPI lineGetMessage( HLINEAPP hLineApp, LPLINEMESSAGE lpMessage, DWORD dwTimeout ); Parameters hLineApp The handle that lineInitializeEx returns. Ensure that the application has set the LINEINITIALIZEEXOPTION_USEEVENT option in the dwOptions member of the LINEINITIALIZEEXPARAMS structure. Cisco Unified TAPI Developers Guide for Cisco Unified Communications Manager, Release 15 and SUs 167 Basic TAPI Implementation lineGetLineDevStatus

Page 199 content