Share via

NDIS_TAPI_PROVIDER_INITIALIZE

  • Article

OID_TAPI_PROVIDER_INITIALIZE uses the NDIS_TAPI_PROVIDER_INITITIALIZE structure when it requests that the miniport driver initialize itself as a TAPI provider. The driver should set up whatever internal state it uses to track incoming requests from TAPI.

Support for this request is mandatory.

typedef struct _NDIS_TAPI_PROVIDER_INITIALIZE { 
  ULONG ulRequestID; 
  ULONG ulDeviceIDBase; 
  ULONG ulNumLineDevs; 
  ULONG ulProviderID; 
} NDIS_TAPI_PROVIDER_INITIALIZE, *PNDIS_TAPI_PROVIDER_INITIALIZE;

Members

  • ulRequestID
    [in] Reserved.
  • ulDeviceIDBase
    [in] Specifies the lowest device identifier for the line devices supported by the miniport driver. Subsequent to this request, the driver uses this value as the zero-based line device identifier value. That is, if ulNumLineDevs is greater than one, the ulDeviceID values subsequently passed in requests such as OID_TAPI_OPEN, contains this value for the first line, this value plus one for the second line, and so forth.
  • ulNumLineDevs
    [out] Specifies the number of line devices supported by the miniport driver to complete this request successfully.
  • ulProviderID
    [out] Specifies an identifier for the WAN NIC driver if this request is completed successfully. This value must be unique within the set of WAN drivers that support TAPI; the NdisMiniportContext handle passed in to the MiniportInitialize function can be used to provide a guaranteed unique value.

Remarks

The MiniportQueryInformation function can return one of the following:

  • NDIS_STATUS_SUCCESS
  • NDIS_STATUS_PENDING
  • NDIS_STATUS_TAPI_RESOURCEUNAVAIL
  • NDIS_STATUS_FAILURE

Requirements

OS Versions: Windows CE .NET 4.0 and later.
Header: Ntddndis.h and Ndistapi.h.

See Also

OID_TAPI_OPEN | OID_TAPI_PROVIDER_INITIALIZE | MiniportQueryInformation

 Last updated on Tuesday, May 18, 2004

© 1992-2003 Microsoft Corporation. All rights reserved.