Important:
This is retired content. This content is outdated and is no longer being maintained. It is provided as a courtesy for individuals who are still using these technologies. This content may contain URLs that were valid when originally published, but now link to sites or pages that no longer exist.
A version of this page is also available for
4/8/2010

This function performs a blind or single-step transfer of the specified call to the specified destination address.

Syntax 

LONG TSPIAPI TSPI_lineBlindTransfer(
  DRV_REQUESTID 
dwRequestID,
  HDRVCALL 
hdCall,
  LPCWSTR 
lpszDestAddress,
  DWORD 
dwCountryCode
);

Parameters

dwRequestID

Identifier of the asynchronous request.

hdCall

Service provider's handle to the call to be transferred. The call state of hdCallcan be connected.

lpszDestAddress

Pointer to a null-terminated Unicode string identifying where the call is to be transferred. The destination address uses the standard dialable number format.

dwCountryCode

Country/region code of the destination. The implementation should use this to select the call progress protocols for the destination address. If a value of zero is specified, the service provider should use a default. TAPI does not validate dwCountryCodewhen this function is called.

Return Value

Returns dwRequestIDor an error number if an error occurs. The lResultactual parameter of the corresponding ASYNC_COMPLETIONis zero if the function succeeds or an error number if an error occurs. The following table shows the return values for this function.

Value Description

LINEERR_INVALCALLHANDLE

The handle to the call is invalid.

LINEERR_NOMEM

Not enough memory is available.

LINEERR_INVALCALLSTATE

The call state is invalid.

LINEERR_OPERATIONFAILED

The operation failed.

LINEERR_ADDRESSBLOCKED

The address is blocked.

LINEERR_RESOURCEUNAVAIL

The resource is unavailable.

LINEERR_INVALCOUNTRYCODE

The country/region code is invalid.

Remarks

The service provider carries out no dialing if it returns LINEERR_INVALADDRESS.

Blind transfer differs from a consultation transfer in that no consultation call is made visible to TAPI. Typically, after the blind transfer successfully completes, the specified call is cleared from the line it was on and transitions to the idle state. The service provider's call handle must remain valid after the transfer has completed. TAPI causes this handle to be invalidated when it is no longer interested in the transferred call using TSPI_lineCloseCall.

Requirements

Header tapicomn.h
Library coredll.lib
Windows Embedded CE Windows CE 3.0 and later
Windows Mobile Windows Mobile Version 5.0 and later

See Also