通过

OID_TAPI_GET_DEV_CONFIG

  • 项目

The OID_TAPI_GET_DEV_CONFIG OID requests the miniport driver to return the current configuration of a device associated one-to-one with a particular line.

Support for this request is mandatory.

This request uses an NDIS_TAPI_GET_DEV_CONFIG structure, defined as follows:

typedef struct _NDIS_TAPI_GET_DEV_CONFIG {         
         IN ULONG ulRequestID;
         IN ULONG ulDeviceID;
         IN ULONG ulDeviceClassSize;
         IN ULONG ulDeviceClassOffset;
         OUT VAR_STRING DeviceConfig;
 } NDIS_TAPI_GET_DEV_CONFIG,   *PNDIS_TAPI_GET_DEV_CONFIG;

The members of this structure contain the following information:

  • ulRequestID
    Reserved.

  • ulDeviceID
    Specifies the line device to be queried. This value was set up in a preceding OID_TAPI_PROVIDER_INITIALIZE request.

  • ulDeviceClassSize
    Specifies the number of bytes in the device-class string.

  • ulDeviceClassOffset
    Specifies the offset in bytes to the null-terminated, variable-size counted string specifying the class of the device whose configuration is requested. Valid device class strings are the same as those specified for the OID_TAPI_GET_ID request when it is applied to a "line" device ( ulSelect has the value LINECALLSELECT_LINE).

  • DeviceConfig
    Specifies the virtual address of a structure of type VAR_STRING to contain the device configuration information for the associated device.

    The ulStringFormat member of the VAR_STRING structure must be set to STRINGFORMAT_BINARY.

    The miniport driver fills this structure with the device configuration information to complete this request successfully.

In general, the contents of the NDIS_TAPI_GET_DEV_CONFIG structure are specific to the NIC driver's line and the device class.

The MiniportQueryInformationfunction can return one of the following:

NDIS_STATUS_SUCCESS

NNDIS_STATUS_TAPI_INVALDEVICECLASS

NDIS_STATUS_TAPI_STRUCTURETOOSMALL

NDIS_STATUS_TAPI_NODRIVER

NDIS_STATUS_TAPI_RESOURCEUNAVAIL

NDIS_STATUS_FAILURE

 

 

Send comments about this topic to Microsoft