2.2.4.1.3.1 Accept

The Accept packet is transmitted from a TAPI client to a TAPI server in a remote procedure call. Sending this packet accepts the specified offered call. Optionally, it can send the specified user-user information to the calling party.


0


1


2


3


4


5


6


7


8


9

1
0


1


2


3


4


5


6


7


8


9

2
0


1


2


3


4


5


6


7


8


9

3
0


1

Req_Func

Reserved1

dwRequestID

hCall

lpsUserUserInfo

dwSize

Reserved2

Reserved3

Reserved4

Reserved5

Reserved6

Reserved7

Reserved8

Reserved9

Reserved10

VarData (variable)

...

Req_Func (4 bytes): An unsigned 32-bit integer. The identifier of the function that will be invoked on the remote server. This value MUST be set to 4.

Return Values

On completion of ClientRequest, this field contains the result of the encapsulated telephony request. A nonzero request ID value indicates that the request is in progress and will complete asynchronously and a LINEERR_Constants value indicates synchronous failure.

Returns a positive request identifier if the function will be completed asynchronously or a negative error number if an error occurs. The dwParam2 parameter of the corresponding LINE_REPLY packet is zero if the function succeeds; or it is a negative error number if an error occurs. If the client specified a nonzero value in the dwRequestID field of the packet, the same MUST be used as the value for the returned positive request identifier. Common return values are as follows:

Name

Value

LINEERR_INVALCALLHANDLE

0x80000018

LINEERR_OPERATIONFAILED

0x80000048

LINEERR_INVALCALLSTATE

0x8000001C

LINEERR_RESOURCEUNAVAIL

0x8000004B

LINEERR_NOMEM

0x80000044

LINEERR_USERUSERINFOTOOBIG

0x80000051

LINEERR_OPERATIONUNAVAIL

0x80000049

Reserved1 (4 bytes): An unsigned 32-bit integer. MUST be set to zero when sent and MUST be ignored on receipt.

dwRequestID (4 bytes): The identifier of an asynchronous request.

Value

Meaning

0x00000000

The server MUST generate a unique positive request ID to return as the Ack_ReturnValue.

0x00000001 — 0x7FFFFFFF

The server MUST use this value instead of generating a unique positive request ID.

hCall (4 bytes): The handle to the call to be accepted. The application MUST be an owner of the call. The call state of hCall must be offering. The client can obtain a valid hCall from the LINE_CALLSTATE packet sent by the remote server.

lpsUserUserInfo (4 bytes): The offset, in bytes, in the VarData field of the user-user information to send to the remote party as part of the call accept. When this field is set to -1 (0xFFFFFFFF), no user-user information is to be sent.

dwSize (4 bytes): The size, in bytes, of the user-user information in lpsUserUserInfo (including the null terminator). If lpsUserUserInfo is -1 (0xFFFFFFFF), no user-user information is sent to the calling party and dwSize is ignored.

Reserved2 (4 bytes): An unsigned 32-bit integer. This field is used for padding and MUST be ignored on receipt. It can be any value.

Reserved3 (4 bytes): An unsigned 32-bit integer. This field is used for padding and MUST be ignored on receipt. It can be any value.

Reserved4 (4 bytes): An unsigned 32-bit integer. This field is used for padding and MUST be ignored on receipt. It can be any value.

Reserved5 (4 bytes): An unsigned 32-bit integer. This field is used for padding and MUST be ignored on receipt. It can be any value.

Reserved6 (4 bytes): An unsigned 32-bit integer. This field is used for padding and MUST be ignored on receipt. It can be any value.

Reserved7 (4 bytes): An unsigned 32-bit integer. This field is used for padding and MUST be ignored on receipt. It can be any value.

Reserved8 (4 bytes): An unsigned 32-bit integer. This field is used for padding and MUST be ignored on receipt. It can be any value.

Reserved9 (4 bytes): An unsigned 32-bit integer. This field is used for padding and MUST be ignored on receipt. It can be any value.

Reserved10 (4 bytes): An unsigned 32-bit integer. This field is used for padding and MUST be ignored on receipt. It can be any value.

VarData (variable): Contains the user information that is indicated in the lpsUserUserInfo field. The user information can be an ASCII or Unicode string and this data is opaque to the protocol.

The contents of this field MUST be DWORD-aligned, as specified in [MS-DTYP] section 2.2.9.