This is the list of error codes that the implementation may return when
invoking operations on phone devices. Consult the individual function descriptions to
determine which of these error codes each function may return.
The specified resource is already allocated.
The specified device ID is invalid or out of range.
The application requested an API version or version range that cannot be
supported by the Telephony API implementation and/or corresponding service provider.
The application requested an extension version or version range that cannot
supported by the service provider.
Because of internal inconsistencies or formatting problems in the TELEPHON.INI
file, it cannot be read and understood properly by TAPI.
The device is currently in use. The device cannot be configured.
The application's specified usage handle or registration handle is invalid.
The specified application name is invalid. If an application name is specified
by the application, it is assumed that the string does not contain any
nondisplayable characters and is NULL-terminated.
The specified button/lamp ID is out of range or invalid.
The button mode parameter is invalid.
The button states parameter is invalid.
The specified data ID is invalid.
The specified phone does not support the indicated device class.
The hookswitch device parameter is invalid.
The hookswitch mode parameter is invalid.
The specified lamp mode parameter is invalid.
A parameter, such as a row or column value or a window handle, is invalid or
out of range.
The specified device handle is invalid.
The phone device is not in a valid state for the requested operation.
One or more of the specified pointer parameters are invalid.
parameter is invalid.
The ring mode parameter is invalid.
The specified device ID, which was previously valid, is no longer accepted
because the associated device has been removed from the system since TAPI was last
The telephone service provider for the specified device found that one of its
components is missing or corrupt in a way that was not detected at
initialization time. The user should be advised to use the Telephony Control Panel to
correct the problem.
Insufficient memory to complete the requested operation, or unable to allocate
or lock memory.
The application does not have owner privilege to the specified phone device.
The operation failed for an unspecified reason.
The operation is not available.
If TAPI reinitialization has been requested, for example as a result of adding
or removing a telephony service provider, then phoneInitialize
requests are rejected with this error until the last application shuts down
its usage of the API (using phoneShutdown
), at which time the new configuration becomes effective and applications are
once again permitted to call phoneInitialize
The operation cannot be completed because of resource overcommitment.
The specified phone caps structure is too small.
The operation was invoked before any application called phoneInitialize
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 IDs.
If an application gets an error return that it does not specifically handle
(such as an error defined by a device-specific extension), it should treat the
error as a PHONEERR_OPERATIONFAILED (for an unspecified reason).
- Software for developers
Software for Android Developers
- More information resources
Unix Manual Pages