Share via

OID_TAPI_SEND_USER_USER_INFO

  • Article

The OID_TAPI_SEND_USER_INFO OID requests the miniport driver to send user-to-user information to the remote party on the specified call.

Support for this request is optional.

This request uses an NDIS_TAPI_SEND_USER_USER_INFO structure, defined as follows:

typedef struct _NDIS_TAPI_SEND_USER_USER_INFO {         
         IN ULONG ulRequestID;
         IN HDRV_CALL hdCall;
         IN ULONG ulUserUserInfoSize;
         IN UCHAR UserUserInfo[1];
 } NDIS_TAPI_SEND_USER_USER_INFO,   *PNDIS_TAPI_SEND_USER_USER_INFO;

The members of this structure contain the following information:

  • ulRequestID
    Reserved.

  • hdCall
    Specifies the miniport driver's handle to the call on which to send user-to-user information.

  • ulUserUserInfoSize
    Specifies the size in bytes of the UserUserInfo string.

  • UserUserInfo
    Specifies a string containing user-to-user information to be sent to the remote party as part of a 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_USERUSERINFOTOOBIG

NDIS_STATUS_TAPI_OPERATIONUNAVAIL

NDIS_STATUS_TAPI_RESOURCEUNAVAIL

NDIS_STATUS_FAILURE

 

 

Send comments about this topic to Microsoft