McDewey

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

Page 314

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

• PHONESTATE_HEADSETHOOKSWITCH • PHONESTATE_HEADSETVOLUME • PHONESTATE_HEADSETGAIN • PHONESTATE_SUSPEND • PHONESTATE_RESUMEF • PHONESTATE_DEVSPECIFIC • PHONESTATE_REINIT • PHONESTATE_CAPSCHANGE • PHONESTATE_REMOVED lpdwButtonModes A pointer to a DWORD that contains flags that specify the set of phone-button modes for which the application can receive notification messages. This parameter uses zero, one, or more of the PHONEBUTTONMODE_Constants. lpdwButtonStates A pointer to a DWORD that contains flags that specify the set of phone button state changes for which the application can receive notification messages. This parameter uses zero, one, or more of the PHONEBUTTONSTATE_ Constants. Return Values Returns zero if the request succeeds or a negative number if an error occurs. Possible return values follow: PHONEERR_INVALPHONEHANDLE PHONEERR_NOMEM PHONEERR_INVALPOINTER PHONEERR_RESOURCEUNAVAIL PHONEERR_OPERATIONFAILED PHONEERR_UNINITIALIZED. phoneInitialize Although the phoneInitialize function is obsolete, tapi.dll and tapi32.dll continue to export it for backward compatibility with applications that are using TAPI versions 1.3 and 1.4. Function Details LONG WINAPI phoneInitialize( LPHPHONEAPP lphPhoneApp, HINSTANCE hInstance, PHONECALLBACK lpfnCallback, LPCSTR lpszAppName, Cisco Unified TAPI Developers Guide for Cisco Unified Communications Manager, Release 15 and SUs 282 Basic TAPI Implementation phoneInitialize

Page 314 content