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

This function is used by the WWAN miniport to call the RIL driver to send a packet through the radio interface.

Note:
This function is deprecated. The function will return E_NOTIMPL. The RIL driver will not be called.

Syntax 

HRESULT RIL_NDIS_SendPacket (
  HRIL 
hRil,
  const RILNDISPACKET*
 pPacketToSend
);

Parameters

hRil

Handle to RIL instance returned by RIL_Initialize.

pPacketToSend

Pointer to a RILNDISPACKETstructure that contains one or more buffers comprising the packet to be sent.

Return Value

An HRESULTvalue of S_OK indicates success. HRESULTvalues of E_XXX indicate an error. Errors are defined in the winerror.h file.

On success, the lpDatanotification parameter points to the pPacketToSendstructure that was passed in the original RIL_NDIS_SendPacketcall.

Remarks

The memory for the RILNDISPACKETstructure and its corresponding internal buffers are allocated by the NDIS miniport. Ownership of the memory passes to the underlying drivers until a RIL_RESULT_OK indicates that they are no longer needed and can be freed or reused by the miniport driver. The dwContextIDof the RILNDISPACKETidentifies the APN on which the packet is to be sent.

This function is synchronous. An asynchronous result callback is not called.

Requirements

Header ril.h
Library Ril.lib
Windows Embedded CE Windows CE .NET 4.2 and later

See Also

Reference

RIL Functions

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.