NDIS_TAPI_ACCEPT (Windows Embedded CE 6.0)

1/6/2010

OID_TAPI_ACCEPT uses the NDIS_TAPI_ACCEPT when it 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.

Syntax

typedef struct _NDIS_TAPI_ACCEPT { 
  ULONG ulRequestID; 
  HDRV_CALL hdCall; 
  ULONG ulUserUserInfoSize; 
  UCHAR UserUserInfo[1]; 
} NDIS_TAPI_ACCEPT, *PNDIS_TAPI_ACCEPT; 

Members

• ulRequestID
  [in] Reserved.

• hdCall
  [in] 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
  [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-accept operation. 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_RESOURCEUNAVAIL
• NDIS_STATUS_TAPI_USERUSERINFOTOOBIG
• NDIS_STATUS_FAILURE

Requirements

See Also

Reference

NDIS Structures
MiniportSetInformation
NdisMIndicateStatus
OID_TAPI_ACCEPT
OID_TAPI_GET_DEV_CAPS