TAPI Constants (Windows Embedded CE 6.0)
1/6/2010
The following table shows the TAPI constants with a description of the purpose of each.
Programming elements | Description |
---|---|
These bit-flag constants are used in the dwAddrCapFlags member of the LINEADDRESSCAPS data structure to describe various Boolean address capabilities. |
|
These bit-flag constants describe various ways of identifying an address on a line device. |
|
These bit-flag constants describe various ways an address can be shared between lines. |
|
These bit-flag constants describe various address status items. |
|
The address type identifies address format, such as standard phone number or e-mail address. |
|
These constants list the operations that can be invoked on an address. |
|
These bit-flag constants describe how an existing active call on a line device is affected by answering another offering call on the same line. |
|
These bit-flag constants describe different bearer modes of a call. |
|
These bit-flag constants describe different busy signals that the switch or network can generate. |
|
These bit-flag constants describe the conditions under which a call can be completed. |
|
These bit-flag constants describe different ways in which a call can be completed. |
|
These constants indicate operations that can be invoked for a given address or call. |
|
These bit-flag constants describe the supplemental features available for conferencing, transferring, and parking calls. |
|
These bit-flag constants describe various call information items about which an application can be notified in the LINE_CALLINFO message. |
|
These bit-flag constants describe the origin of a call. |
|
These constants describe various status flags about a call. |
|
These bit-flag constants describe the nature of the information available about the parties involved in a call. |
|
These bit-flag constants describe the kinds of access rights or privileges an application with a call handle may have to the corresponding call. |
|
These bit-flag constants describe the reason for a call. |
|
These bit-flag constants describe which calls are to be selected. |
|
These bit-flag constants describe the call states a call can be in. |
|
These constants describe treatments for calls that are unanswered or on hold. Except for basic parameter validation, call treatment is a straight pass-through by TAPI to the service provider. |
|
These bit-flag constants describe different substates of a connected call. |
|
These bit-flag constants are a collection of Booleans describing various line device capabilities. |
|
These bit-flag constants describe various line status events. |
|
These bit-flag constants describe a collection of Boolean line device status items. |
|
These bit-flag constants describe different types of dial tones. A special dial tone typically carries a special meaning (as with message waiting). |
|
These constants describe different types of inband digit generation. |
|
These bit-flag constants describe different reasons for a remote disconnect request. |
|
The following list contains the list error codes that TAPI can return when invoking operations on lines, addresses, or calls. |
|
These constants list the operations that can be invoked on a line using this API. |
|
These bit-flag constants describe the conditions under which calls to an address can be forwarded. |
|
These bit-flag constants describe the conditions under which buffered digit gathering is terminated. |
|
These bit-flag constants describe the conditions under which digit or tone generation is terminated. |
|
These ordinal constants specify which event notification mechanism to use when initializing a session. |
|
These constants define values used in the dwOptions member of the LINELOCATIONENTRY structure returned as part of the LINETRANSLATECAPS structure returned by lineGetTranslateCaps. |
|
These bit-flag constants describe a set of generic operations on media streams. |
|
These constants describe media types (or modes) of a communications session or call. |
|
These bit-flag constants for TAPI versions 1.4 and later, describe different substates of an offering call. |
|
These constants describe the available options for opening a line. |
|
These bit-flag constants describe different ways of parking calls. |
|
These scalar constants describe how parties participating in a conference call can be removed from a conference call. |
|
These bit-flag constants describe the roaming status of a line device. |
|
These bit-flag constants describes special information signals that the network can use to report various reporting and network observation operations. |
|
These bit-flag constants describe different types of terminal devices. |
|
These bit-flag constants describe different types of events on a phone line that can be routed to a terminal device. |
|
These bit-flag constants describe different ways in which a terminal can be shared between line devices, addresses, or calls. |
|
These bit-flag constants describe options for manipulating a toll list. |
|
These constants describe different selections that are used when generating line tones. |
|
These bit-flag constants describe different ways of resolving call transfer requests. |
|
These bit-flag constant describes an option used by address translation. |
|
These bit-flag constants describe various results of an address translation. |
|
These scalar constants describe the functions commonly assigned to buttons on telephone sets. |
|
These bit-flag constants describe the button classes. |
|
These bit-flag constants describe the button's positions. |
|
The PHONEERR constants consist of a list of error codes that the implementation can return when invoking operations on phone devices. |
|
These constants list the operations that can be invoked on a phone using TAPI. |
|
These bit-flag constants describe various audio I/O devices each with its own hookswitch controllable from the computer. |
|
These bit-flag constants describe the microphone and speaker components of a hookswitch device. |
|
These constants specify which event notification mechanism to use when initializing a session. |
|
These bit-flag constants describe various ways in which a phone's lamp can be lit. |
|
These bit-flag constants describe the various ways in which a phone device can be opened. |
|
These bit-flag constants describe various status items for a phone device. |
|
These bit-flag constants describe a variety of phone device status information. |
|
These constants describe different string formats. |