McDewey

LPDWORD lpdwNumDevs ); Parameters lphPhoneApp A pointer to a location that is filled with the application usage handle for TAPI. hInstance The instance handle of the client application or DLL. lpfnCallback The address of a callback function that is invoked to determine status and events on the phone device. lpszAppName A pointer to a null-terminated string that contains displayable characters. If this parameter is non-NULL, it contains an application-supplied name of the application. This name, which is provided in the PHONESTATUS structure, indicates, in a user-friendly way, which application is the current owner of the phone device. You can use this information for logging and status reporting purposes. If lpszAppName is NULL, the application filename gets used instead. lpdwNumDevs A pointer to DWORD. This location gets loaded with the number of phone devices that are available to the application. Return Values Returns zero if the request succeeds or a negative number if an error occurs. Possible return values follow: PHONEERR_INVALAPPNAME PHONEERR_INIFILECORRUPT PHONEERR_INVALPOINTER PHONEERR_NOMEM PHONEERR_OPERATIONFAILED PHONEERR_REINIT PHONEERR_RESOURCEUNAVAIL PHONEERR_NODEVICE PHONEERR_NODRIVER PHONEERR_INVALPARAM phoneInitializeEx The phoneInitializeEx function initializes the application use of TAPI for subsequent use of the phone abstraction. It registers the application specified notification mechanism and returns the number of phone devices that are available to the application. A phone device represents any device that provides an implementation for the phone-prefixed functions in the telephony API. Cisco Unified TAPI Developers Guide for Cisco Unified Communications Manager, Release 15 and SUs 283 Basic TAPI Implementation phoneInitializeEx