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.
A version of this page is also available for
4/8/2010

Use the lineGetCallWaitingCapsfunction to retrieve the set of media modes for which call waiting is supported by the radio hardware. The actual set of usable modes may be smaller depending on network capabilities and the provisioning of a particular subscriber.

Syntax 

LONG WINAPI lineGetCallWaitingCaps(
  HLINE 
hLine,
  LPDWORD 
lpdwClasses
);

Parameters

hLine

The line device handle. The line device handle must have been previously obtained by a call to lineOpenwith the proper TAPI device ID specified and a device-specific extension version successfully negotiated with lineNegotiateExtVersion.

lpdwClasses

Points to a bit field DWORD that enumerates all supported line capability classes. See the Line Capability Classesconstants for possible values.

Return Value

Returns zero if the function completes successfully, or a negative error number if an error occurs. The following are possible return values:

  • LINEERR_RESOURCEUNAVAIL

  • LINEERR_INVALLINEHANDLE

  • LINEERR_STRUCTURETOOSMALL

  • LINEERR_INVALPOINTER

  • LINEERR_UNINITIALIZED

  • LINEERR_NOMEM

  • LINEERR_OPERATIONUNAVAIL

  • LINEERR_OPERATIONFAILED.

Remarks

This function is synchronous. No LINE_REPLY message is sent.

Requirements

Header extapi.h
Library cellcore.lib
Windows Embedded CE Windows Embedded CE 6.0 and later
Windows Mobile Pocket PC 2002 and later, Smartphone 2002 and later

See Also

500 Internal Server Error

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.