McDewey

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

Page 193

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

dwToneMode Defines the tone to be generated. Tones can be either standard or custom tones. A custom tone comprises a set of arbitrary frequencies. A small number of standard tones are predefined. The duration of the tone gets specified with dwDuration for both standard and custom tones. The dwToneMode parameter can have only one bit set. If no bits are set (the value 0 is passed), tone generation gets canceled. This parameter uses the following LINETONEMODE_constant: • LINETONEMODE_BEEP -The tone is a beep, as used to announce the beginning of a recording. The service provider defines the exact beep tone. dwDuration Duration in milliseconds during which the tone should be sustained. Cisco Unified TSP does not support dwDuration. Note dwNumTones The number of entries in the lpTones array. This parameter is ignored if dwToneMode ≠CUSTOM. lpTones A pointer to a LINEGENERATETONE array that specifies the components of the tone. This parameter gets ignored for non-custom tones. If lpTones is a multifrequency tone, the various tones play simultaneously. lineGetAddressCaps The lineGetAddressCaps function queries the specified address on the specified line device to determine its telephony capabilities. Function Details LONG lineGetAddressCaps( HLINEAPP hLineApp, DWORD dwDeviceID, DWORD dwAddressID, DWORD dwAPIVersion, DWORD dwExtVersion, LPLINEADDRESSCAPS lpAddressCaps ); Parameters hLineApp The handle by which the application is registered with TAPI. dwDeviceID The line device that contains the address to be queried. Only one address gets supported per line, so dwAddressID must be zero. Cisco Unified TAPI Developers Guide for Cisco Unified Communications Manager, Release 15 and SUs 161 Basic TAPI Implementation lineGetAddressCaps

Image 1 from page 193

Page 193 content