Partager via


NDIS_TAPI_GET_ADDRESS_ID (Windows CE 5.0)

Send Feedback

The NDIS_TAPI_GET_ADDRESS_ID structure is used by OID_TAPI_GET_ADDRESS_ID when it requests the WAN NIC driver to return the address identifier associated with the address in a different format on the specified line.

Support for this request is mandatory.

typedef struct _NDIS_TAPI_GET_ADDRESS_ID {   ULONGulRequestID;HDRV_LINEhdLine;ULONGulAddressID;ULONGulAddressMode;ULONGulAddressSize;CHARszAddress[1];} NDIS_TAPI_GET_ADDRESS_ID, *PNDIS_TAPI_GET_ADDRESS_ID; 

Members

  • ulRequestID
    [in] Reserved.

  • hdLine
    [in] Specifies the miniport driver's handle to the line for which the address identifier should be retrieved. This was set up in a preceding OID_TAPI_OPEN request.

  • ulAddressID
    [out] Specifies the requested address identifier. The miniport driver fills in this member with the address identifier corresponding to szAddress to complete this request successfully.

  • ulAddressMode
    [in] Specifies the address mode of the address contained in szAddress. This member can have only the following LINEADDRESSMODE flag set:

    LINEADDRESSMODE_DIALABLEADDR 
    
  • ulAddressSize
    [in] Specifies the size in bytes of the address in szAddress.

  • szAddress
    [in] Specifies the virtual address of variable-size structure containing an address assigned to the line device. The format of the address is determined by the ulAddressMode member. If it is LINEADDRESSMODE_DIALABLEADDR, szAddress uses the common dialable number format and is zero-terminated.

Remarks

The MiniportQueryInformation function can return one of the following:

  • NDIS_STATUS_SUCCESS
  • NDIS_STATUS_PENDING
  • NDIS_STATUS_TAPI_INVALLINEHANDLE
  • NDIS_STATUS_TAPI_INVALADDRESS
  • 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_GET_ADDRESS_ID | OID_TAPI_OPEN | MiniportQueryInformation

Send Feedback on this topic to the authors

Feedback FAQs

© 2006 Microsoft Corporation. All rights reserved.