2.2.3.1.24 LINECALLPARAMFLAGS_Constants
The LINECALLPARAMFLAGS_Constants bit-flag constants describe various status flags about a call.
Constant/value |
Description |
---|---|
LINECALLPARAMFLAGS_SECURE 0x00000001 |
The call is to be set up as secure. |
LINECALLPARAMFLAGS_IDLE 0x00000002 |
The call is to be originated on an idle call appearance and not join a call in progress. When using the MakeCall packet, 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_BLOCKID 0x00000004 |
The identity of the originator is to be concealed (block caller ID). |
LINECALLPARAMFLAGS_ORIGOFFHOOK 0x00000008 |
The phone of the originator is to be automatically taken off the hook. |
LINECALLPARAMFLAGS_DESTOFFHOOK 0x00000010 |
The phone of the called party is to be automatically taken off the hook. |
The following constants are present in TAPI versions 2.0, 2.1, 2.2, 3.0, and 3.1:
Constant/value |
Description |
---|---|
LINECALLPARAMFLAGS_NOHOLDCONFERENCE 0x00000020 |
This bit must be used only in conjunction with SetUpConference and PrepareAddToConference packet. The address to be conferenced with the current call must be specified in the TargetAddress member in LINECALLPARAMS. The consultation call does not physically draw the dial tone from the switch but will progress through various call establishment states (for example, dialing or 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 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 might have been an existing conference, in the case of the PrepareAddToConference packet) remains in the connected state. The original party (or parties) never perceive the call as having gone on hold. This feature is often used to add a supervisor to an ACD agent call when necessary to monitor interactions with an irate caller. |
LINECALLPARAMFLAGS_PREDICTIVEDIAL 0x00000040 |
This bit must be 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 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 the call state. |
LINECALLPARAMFLAGS_ONESTEPTRANSFER 0x00000080 |
This bit must be used only in conjunction with the SetUpTransfer packet. It combines the operation of the SetUpTransfer packet followed by the Dial packet on the consultation call into a single step. The address to be dialed must be specified in the TargetAddress member in LINECALLPARAMS. The original call must be placed in the onHoldPendingTransfer state, just as if the SetUpTransfer packet were called normally, and the consultation call must be established normally. The application must still call the CompleteTransfer packet 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. |