LINEDEVCAPFLAGS (Windows Embedded CE 6.0)

1/6/2010

These bit-flag constants are a collection of Booleans describing various line device capabilities.

The following table shows the LINEDEVCAPFLAGS constants.

Value	Description
LINEDEVCAPFLAGS_CALLHUB = 0x00000400	Indicates whether call hubs are supported on this line. This flag is exposed only to applications that negotiate a TAPI version of 3.0 or later.
LINEDEVCAPFLAGS_CALLHUBTRACKING = 0x00000800	Indicates whether call hub tracking is supported on this line. This flag is exposed only to applications that negotiate a TAPI version of 3.0 or later.
LINEDEVCAPFLAGS_CLOSEDROP = 0x00000020	Specifies what happens when an open line is closed while the application has calls active on the line. If TRUE, the service provider drops, clears, all active calls on the line when the last application that has opened the line closes it with lineClose. If FALSE, the service provider does not drop active calls in such cases. Instead, the calls remain active and under control of external devices. A service provider typically sets this bit to FALSE if there is some other device that can keep the call alive, for example, if an analog line has the computer and phone set both connect directly to them in a party-line configuration, the offhook phone will automatically keep the call active even after the computer powers down. Applications should check this flag to determine whether to warn the user, with an OK/Cancel dialog box, that active calls will be lost.
LINEDEVCAPFLAGS_CROSSADDRCONF = 0x00000001	Specifies whether calls on different addresses on this line can be conferenced.
LINEDEVCAPFLAGS_DIALBILLING = 0x00000040 LINEDEVCAPFLAGS_DIALDIALTONE = 0x00000100 LINEDEVCAPFLAGS_DIALQUIET = 0x00000080	These flags indicate whether the "$", "@", or "W" dialable string modifier is supported for a given line device. It is TRUE if the modifier is supported; otherwise, FALSE. The "?", prompt user to continue dialing, is never supported by a line device. These flags allow an application to determine up front which modifiers would result in the generation of a LINEERR. The application has the choice of pre-scanning dialable strings for unsupported characters or of passing the "raw" string from lineTranslateAddress directly to the provider as part of functions such as lineMakeCall or lineDial and let the function generate an error to tell it which unsupported modifier occurs first in the string.
LINEDEVCAPFLAGS_HIGHLEVCOMP = 0x00000002	Specifies whether high-level compatibility information elements are supported on this line.
LINEDEVCAPFLAGS_LOWLEVCOMP = 0x00000004	Specifies whether low-level compatibility information elements are supported on this line.
LINEDEVCAPFLAGS_MEDIACONTROL = 0x00000008	Specifies whether media-control operations are available for calls at this line.
LINEDEVCAPFLAGS_MSP = 0x00000200	Indicates whether a Media Service Provider (MSP) is associated with the line. This flag is exposed only to applications that negotiate a TAPI version of 3.0 or later.
LINEDEVCAPFLAGS_MULTIPLEADDR = 0x00000010	Specifies whether lineMakeCall, lineDial, TSPI_lineMakeCall, or TSPI_lineDial is able to deal with multiple addresses at once, as they are for inverse multiplexing.
LINEDEVCAPFLAGS_PRIVATEOBJECTS = 0x00001000	Indicates whether provider-specific Interfaces have been implemented. This flag is exposed only to applications that negotiate a TAPI version of 3.0 or later.

Remarks

These constants cannot be extended. All 32 bits are reserved.

Requirements

Header	tapi.h
Windows Embedded CE	Windows CE 3.0 and later

See Also

Reference

TAPI Constants
lineClose
lineDial
lineMakeCall
lineTranslateAddress
TSPI_lineDial
TSPI_lineMakeCall