LINECALLPARAMFLAGS
These constants describe various status flags about a call.
The following table shows the LINECALLPARAMFLAGS constants.
| Value | Description |
|---|---|
| LINECALLPARAMFLAGS_BLOCKID = 0x00000004 | The originator identity should be concealed That is, block caller ID. |
| LINECALLPARAMFLAGS_DESTOFFHOOK = 0x00000010 | The called party's phone should be automatically taken offhook. |
| LINECALLPARAMFLAGS_IDLE = 0x00000002 | The call should be originated on an idle call appearance and not join a call in progress. When using the lineMakeCall function, if the LINECALLPARAMFLAGS_IDLE value is not set and there is an existing call on the line, the function breaks into the existing call if necessary to make the new call. If there is no existing call, the function makes the new call as specified. |
| LINECALLPARAMFLAGS_NOHOLDCONFERENCE = 0x00000020 | This bit is used only in conjunction with lineSetupConference and linePrepareAddToConference. The address to be conferenced with the current call is specified in the TargetAddress member in LINECALLPARAMS. The consultation call does not physically draw dial tone from the switch, but will progress through various call establishment states, for example, dialing and proceeding. When the consultation call reaches the connected state, the conference is automatically established. The original call, which had remained in the connected state, enters the conferenced state. The consultation call enters the conferenced state. The hConfCall parameter of linePrepareAddToConference enters the connected state. If the consultation call fails, enters the disconnected state followed by idle, the hConfCall also enters the idle state, and the original call, which may have been an existing conference, in the case of linePrepareAddToConference, remains in the connected state. The original party, or parties, never perceive the call has having gone onhold. TAPI version 2.0 and later. |
| LINECALLPARAMFLAGS_ONESTEPTRANSFER = 0x00000080 | This bit is used only in conjunction with lineSetupTransfer. It combines the operation of lineSetupTransfer followed by lineDial on the consultation call into a single step. The address to be dialed is specified in the TargetAddress member in LINECALLPARAMS. The original call is placed in onholdpendingtransfer state, just as if lineSetupTransfer were called normally, and the consultation call is established normally. The application must still call lineCompleteTransfer to effect the transfer. This feature is often used when invoking a transfer from a server over a third-party call control link, because such links frequently do not support the normal two-step process. TAPI version 2.0 and later. |
| LINECALLPARAMFLAGS_ORIGOFFHOOK = 0x00000008 | The originator's phone should be automatically taken offhook. |
| LINECALLPARAMFLAGS_PREDICTIVEDIAL = 0x00000040 | This bit is used only when placing a call on an address with predictive dialing capability (LINEADDRCAPFLAGS_PREDICTIVEDIALER is on in the dwAddrCapFlags member in LINEADDRESSCAPS). The bit must be on to enable the enhanced call progress and or the media device monitoring capabilities of the device. If this bit is not on, the call will be placed without enhanced call progress or media type monitoring, and no automatic transfer will be initiated based on call state. TAPI version 2.0 and later. |
| LINECALLPARAMFLAGS_SECURE = 0x00000001 | The call should be set up as secure. |
Remarks
These constants cannot be extended. All 32 bits are reserved.
Requirements
OS Versions: Windows CE 3.0 and later.
Header: Tapi.h.
See Also
lineMakeCall | lineDial | lineSetupConference | lineCompleteTransfer | linePrepareAddToConference | LINEADDRESSCAPS
Last updated on Saturday, April 10, 2004
© 1992-2003 Microsoft Corporation. All rights reserved.