Share via

NDIS_TAPI_ANSWER

  • Article

OID_TAPI_ANSWER uses the NDIS_TAPI_ANSWER structure when it requests the miniport driver to answer the specified call on offer. Optionally, it requests that the miniport driver send the specified user-to-user information to the calling party.

Support for this request is mandatory.

typedef struct _NDIS_TAPI_ANSWER { 
  ULONG ulRequestID; 
  HDRV_CALL hdCall; 
  ULONG ulUserUserInfoSize; 
  UCHAR UserUserInfo[1]; 
} NDIS_TAPI_ANSWER, *PNDIS_TAPI_ANSWER;

Members

  • ulRequestID
    [in] Reserved.
  • hdCall
    [in] Specifies the miniport driver's handle to the call to be answered. 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, UserUserInfo should be ignored.
  • UserUserInfo
    [in] Specifies a string containing user-to-user information to be sent to the remote party as part of the call accept. 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

Upon successful completion of the OID_TAPI_ANSWER request, the miniport driver must be prepared to respond to the OID_TAPI_GET_ID request.

The initiating application must wait for the LINECALLSTATE_CONNECTED indication before actually writing data.

Requirements

OS Versions: Windows CE .NET 4.0 and later.
Header: Ntddndis.h and Ndistapi.h.

See Also

OID_TAPI_ANSWER | MiniportSetInformation | OID_TAPI_GET_ID | OID_TAPI_GET_DEV_CAPS | NdisMIndicateStatus

 Last updated on Tuesday, May 18, 2004

© 1992-2003 Microsoft Corporation. All rights reserved.