PHONEERR_ Constants

This is the list of error codes that the implementation can return when invoking operations on phone devices. For more information on which error codes a specific function can return, see TSPI Functions.

PHONEERR_ALLOCATED
The specified resource is already allocated.
PHONEERR_BADDEVICEID
The specified phone device identifier is invalid or out of range.
PHONEERR_INCOMPATIBLEAPIVERSION
The passed TSPI version did not match an interface version definition supported by the service provider.
PHONEERR_INCOMPATIBLEEXTVERSION
The caller requested an extension version or a version range that cannot be supported by the service provider.
PHONEERR_INIFILECORRUPT
The telephon.ini file was corrupted.
PHONEERR_INUSE
The device is currently in use, or the phone device is in use and cannot currently be configured.
PHONEERR_INVALBUTTONLAMPID
The specified button identifier is out of range, invalid, or not supported by the service provider or phone.
PHONEERR_INVALBUTTONMODE
The button mode parameter is invalid.
PHONEERR_INVALBUTTONSTATE
The button states parameter is invalid.
PHONEERR_INVALDATAID
The specified data identifier is invalid or the number of bytes specified in dwSize cannot be read from that location.
PHONEERR_INVALDEVICECLASS
The service provider or phone does not support the indicated device class.
PHONEERR_INVALHOOKSWITCHDEV
The hookswitch device parameter is invalid or not supported by the phone or service provider.
PHONEERR_INVALLAMPMODE
The specified lamp mode parameter is invalid or not supported by the phone or service provider.
PHONEERR_INVALPARAM
The row or column parameters or window handle parameter are invalid or out of range.
PHONEERR_INVALPHONEHANDLE
The specified device handle, such as hdPhone, is invalid.
PHONEERR_INVALPHONESTATE
The phone device is not in a valid state for the requested operation, or the specified phone states parameter is invalid.
PHONEERR_INVALPOINTER
The specified pointer parameter is invalid.
PHONEERR_INVALRINGMODE
The ring mode parameter is invalid or not supported by the phone or service provider.
PHONEERR_NODRIVER
This error can be returned from a function when the driver finds that one of its components is corrupt in a way that was not detected at initialization. For example, if a service provider consists of multiple components such as a Virtual Device Driver (VxD) in addition to the usual DLL (exporting the TSPI interface and having the .TSP extension), PHONEERR_NODRIVER can be returned to indicate that the VxD component was missing.
PHONEERR_NOMEM
Unable to allocate or lock memory.
PHONEERR_OPERATIONFAILED
The operation failed for unspecified reasons.
PHONEERR_OPERATIONUNAVAIL
The operation is not available.
PHONEERR_RESOURCEUNAVAIL
There are not enough resources available to complete the request.

The values 0xC0000000 through 0xFFFFFFFF are available for device-specific extensions, the values 0x80000000 through 0xBFFFFFFF are reserved, and 0x00000000 through 0x7FFFFFFF are used as request identifiers.