NDIS_TAPI_DROP (Windows CE 5.0)
OID_TAPI_DROP uses the NDIS_TAPI_DROP structure when it requests the miniport driver to drop or disconnect the specified call.
User-to-user information can optionally be transmitted as part of the call disconnect. This request can be made by the application at any time.
Support for this request is mandatory.
typedef struct _NDIS_TAPI_DROP { ULONGulRequestID;HDRV_CALLhdCall; ULONGulUserUserInfoSize; UCHARUserUserInfo[1];} NDIS_TAPI_DROP, *PNDIS_TAPI_DROP;
Members
- ulRequestID
[in] Reserved. - hdCall
[in] Specifies the miniport driver's handle to the call to be dropped. - ulUserUserInfoSize
[in] Specifies the size in bytes of the user-to-user information in UserUserInfo. If this member is zero, the miniport driver should ignore the next member. - UserUserInfo
[in] Specifies a string containing user-to-user information to be sent to the remote party as part of the call drop. User-to-user information is sent only if supported by the underlying network (see OID_TAPI_GET_DEV_CAPS).
Remarks
The MiniportSetInformation function can return one of the following:
- NDIS_STATUS_SUCCESS
- NDIS_STATUS_PENDING
- NDIS_STATUS_TAPI_INVALCALLHANDLE
- NDIS_STATUS_TAPI_INVALCALLSTATE
- NDIS_STATUS_TAPI_USERUSERINFOTOOBIG
- NDIS_STATUS_TAPI_RESOURCEUNAVAIL
- NDIS_STATUS_FAILURE
When a miniport driver completes this request successfully, the call should be in the idle state. However, the miniport driver can still receive requests, such as statistics queries, specifying the hdCall handle until it completes the OID_TAPI_CLOSE_CALL request for this handle.
Requirements
OS Versions: Windows CE .NET 4.0 and later.
Header: Ntddndis.h and Ndistapi.h.
See Also
OID_TAPI_DROP | OID_TAPI_CLOSE_CALL | MiniportSetInformation
Send Feedback on this topic to the authors