See Also
 Important: |
|---|
| This is retired content. This content is outdated and is no longer being maintained. It is provided as a courtesy for individuals who are still using these technologies. This content may contain URLs that were valid when originally published, but now link to sites or pages that no longer exist. |
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.
The following table shows the LINEANSWERMODE constants.
| Value | Description |
|---|---|
|
LINEANSWERMODE_DROP = 0x00000002 |
The currently active call will automatically be dropped. |
|
LINEANSWERMODE_HOLD = 0x00000004 |
The currently active call will automatically be placed on hold. |
|
LINEANSWERMODE_NONE = 0x00000001 |
Answering another call on the same line has no effect on the existing active call on the line. |
Remarks
These constants cannot be extended. All 32 bits are reserved.
If a call comes in (is offered) when another call is already active, the new call is connected to by invoking the lineAnswerfunction. The effect this has on the existing active call depends on the line's device capabilities. The first call may be unaffected, it may automatically be dropped, or it may automatically be placed on hold.
Requirements
| Header | tapi.h |
| Windows Embedded CE | Windows CE 3.0 and later |
| Windows Mobile | Windows Mobile Version 5.0 and later |