 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 ordinal constants specify which event notification mechanism to use when initializing a session.
The following table shows the LINEINITIALIZEOPTION constants.
| Value | Description |
|---|---|
|
LINEINITIALIZEEXOPTION_USECOMPLETIONPORT = 0x00000003 |
The application desires to use the Completion Port event notification mechanism. This flag is exposed only to applications that negotiate a TAPI version of 2.0 or later. |
|
LINEINITIALIZEEXOPTION_USEEVENT = 0x00000002 |
The application desires to use the Event Handle event notification mechanism. This flag is exposed only to applications that negotiate a TAPI version of 2.0 or later. |
|
LINEINITIALIZEEXOPTION_USEHIDDENWINDOW = 0x00000001 |
The application desires to use the Hidden Window event notification mechanism. This flag is exposed only to applications that negotiate a TAPI version of 2.0 or later. |
Remarks
These constants are mutually exclusive. You cannot specify more than one constant at a time.
Requirements
| Header | tapi.h |
| Windows Embedded CE | Windows CE 3.0 and later |
| Windows Mobile | Windows Mobile Version 5.0 and later |
Internal Server Error
The server encountered an internal error or misconfiguration and was unable to complete your request.
Please contact the server administrator at webmaster@systemmanager.forsenergy.ru to inform them of the time this error occurred, and the actions you performed just before this error.
More information about this error may be available in the server error log.
Additionally, a 500 Internal Server Error error was encountered while trying to use an ErrorDocument to handle the request.