Share via


PHONEERR (Compact 2013)

3/26/2014

The PHONEERR constants consist of a list of error codes that the implementation can return when invoking operations on phone devices. Consult the individual function descriptions to determine which of these error codes each function can return.

The following table shows the PHONEERR constants.

Value

Description

PHONEERR_ALLOCATED = 0x90000001

The specified resource is already allocated.

PHONEERR_BADDEVICEID = 0x90000002

The specified device identifier is invalid or out of range.

PHONEERR_INCOMPATIBLEAPIVERSION = 0x90000003

The application requested an API version or version range that cannot be supported by the TAPI implementation or the corresponding service provider.

PHONEERR_INCOMPATIBLEEXTVERSION = 0x90000004

The application requested an extension version or version range that cannot be supported by the service provider.

PHONEERR_INIFILECORRUPT = 0x90000005

Because of internal inconsistencies or formatting problems in the Telephon.ini file, it cannot be read and understood properly by TAPI.

PHONEERR_INUSE = 0x90000006

The device is currently in use. The device cannot be configured.

PHONEERR_INVALAPPHANDLE = 0x90000007

The application's specified usage handle or registration handle is invalid.

PHONEERR_INVALAPPNAME = 0x90000008

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.

PHONEERR_INVALBUTTONLAMPID = 0x90000009

The specified button/lamp identifier is out of range or invalid.

PHONEERR_INVALBUTTONMODE = 0x9000000A

The button mode parameter is invalid.

PHONEERR_INVALBUTTONSTATE = 0x9000000B

The button states parameter is invalid.

PHONEERR_INVALDATAID = 0x9000000C

The specified data identifier is invalid.

PHONEERR_INVALDEVICECLASS = 0x9000000D

The specified phone does not support the indicated device class.

PHONEERR_INVALEXTVERSION = 0x9000000E

The service provider extension version number is invalid.

PHONEERR_INVALHOOKSWITCHDEV = 0x9000000F

The hookswitch device parameter is invalid.

PHONEERR_INVALHOOKSWITCHMODE = 0x90000010

The hookswitch mode parameter is invalid.

PHONEERR_INVALLAMPMODE = 0x90000011

The specified lamp mode parameter is invalid.

PHONEERR_INVALPARAM = 0x90000012

A parameter, such as a row or column value or a window handle, is invalid or out of range.

PHONEERR_INVALPHONEHANDLE = 0x90000013

The specified device handle is invalid.

PHONEERR_INVALPHONESTATE = 0x90000014

The phone device is not in a valid state for the requested operation.

PHONEERR_INVALPOINTER = 0x90000015

One or more of the specified pointer parameters are invalid.

PHONEERR_INVALPRIVILEGE = 0x90000016

The dwPrivilege parameter is invalid.

PHONEERR_INVALRINGMODE = 0x90000017

The ring mode parameter is invalid.

PHONEERR_NODEVICE = 0x90000018

The specified device identifier, which was previously valid, is no longer accepted because the associated device has been removed from the system since TAPI was last initialized or is corrupt in a way that was not detected at initialization.

PHONEERR_NODRIVER = 0x90000019

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.

PHONEERR_NOMEM = 0x9000001A

Insufficient memory to complete the requested operation, or unable to allocate or lock memory.

PHONEERR_NOTOWNER = 0x9000001B

The application does not have owner privilege to the specified phone device.

PHONEERR_OPERATIONFAILED = 0x9000001C

The operation failed for an unspecified reason.

PHONEERR_OPERATIONUNAVAIL = 0x9000001D

The operation is not available.

PHONEERR_REINIT = 0x90000023

If TAPI reinitialization has been requested, for example as a result of adding or removing a telephony service provider, then phoneInitializeEx or phoneOpen 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 phoneInitializeEx.

PHONEERR_REQUESTOVERRUN = 0x90000020

The maximum number of outstanding phone requests has been exceeded.

PHONEERR_RESOURCEUNAVAIL = 0x9000001F

The operation cannot be completed because of resource overcommitment.

PHONEERR_STRUCTURETOOSMALL = 0x90000021

The specified phone caps structure is too small.

PHONEERR_UNINITIALIZED = 0x90000022

The operation was invoked before any application called phoneInitializeEx.

Remarks

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.

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 an error or type PHONEERR_OPERATIONFAILED. This implies that the error occurred for an unspecified reason

Requirements

Header

tapi.h

See Also

Reference

TAPI Constants
phoneInitializeEx
phoneOpen
phoneShutdown