OID_TAPI_ACCEPT
The OID_TAPI_ACCEPT OID requests the miniport driver to accept the specified call. Optionally, it requests that the miniport driver send the specified user-to-user information to the calling party.
Support for this request is optional.
The request uses an NDIS_TAPI_ACCEPT structure, defined as follows:
typedef struct _NDIS_TAPI_ACCEPT {
IN ULONG ulRequestID;
IN HDRV_CALL hdCall;
IN ULONG ulUserUserInfoSize;
IN UCHAR UserUserInfo[1];
} NDIS_TAPI_ACCEPT, *PNDIS_TAPI_ACCEPT;
The members of this structure contain the following information:
ulRequestID
Reserved.hdCall
Specifies the miniport driver's handle to the call to be accepted. The driver set this handle up when it called NdisMIndicateStatus with the LINE_EVENT_NEWCALL indication.ulUserUserInfoSize
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
Specifies a string containing user-to-user information to be sent to the remote party as part of the call-accept operation. User-to-user information is sent only if supported by the underlying network (see OID_TAPI_GET_DEV_CAPS).
The MiniportSetInformationfunction can return one of the following:
NDIS_STATUS_SUCCESS
NDIS_STATUS_PENDING
NDIS_STATUS_TAPI_INVALCALLHANDLE
NDIS_STATUS_TAPI_INVALCALLSTATE
NDIS_STATUS_TAPI_RESOURCEUNAVAIL
NDIS_STATUS_TAPI_USERUSERINFOTOOBIG
NDIS_STATUS_FAILURE