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 the origin of a call.
The following table shows the LINECALLORIGIN constants.
| Value | Description |
|---|---|
|
LINECALLORIGIN_CONFERENCE = 0x00000040 |
The call handle is for a conference call. That is, it is the application's connection to the conference bridge in the switch. |
|
LINECALLORIGIN_EXTERNAL = 0x00000004 |
The call originated as an incoming call on an external line. |
|
LINECALLORIGIN_INBOUND = 0x00000080 |
The call originated as an incoming call, but the service provider is unable to determine whether it came from another station on the same switch or from an external line. Service providers can use this constant only when TAPI version 1.4 or later has been negotiated. Otherwise, the service provider can substitute LINECALLORIGIN_UNAVAIL. |
|
LINECALLORIGIN_INTERNAL = 0x00000002 |
The call originated as an incoming call at a station internal to the same switching environment. |
|
LINECALLORIGIN_OUTBOUND = 0x00000001 |
The call originated from this station as an outgoing call. |
|
LINECALLORIGIN_UNAVAIL = 0x00000020 |
The call origin is not available and will never become known for this call. |
|
LINECALLORIGIN_UNKNOWN = 0x00000010 |
The call origin is currently unknown but may become known later. |
Remarks
These constants cannot be extended. All 32 bits are reserved.
The origin of a call is stored in the dwOriginmember of the call's LINECALLINFOstructure.
Requirements
| Header | tapi.h |
| Windows Embedded CE | Windows CE 3.0 and later |
| Windows Mobile | Windows Mobile Version 5.0 and later |