lineBlindTransfer
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 WINAPI lineBlindTransfer(
HCALL hCall,
LPCWSTR lpszDestAddress,
DWORD dwCountryCode
);
Parameters
- hCall
Handle to the call to be transferred. The application must be an owner of this call. The call state of hCall must be connected.
- lpszDestAddress
Pointer to a null-terminated string identifying where the call is to be transferred to. The destination address uses the standard dialable number format.
- dwCountryCode
Country/region code of the destination. This is used by the implementation to select the call progress protocols for the destination address. If a value of zero is specified, a default call-progress protocol defined by the service provider is used.
Return Value
Returns a positive request identifier if the function is completed asynchronously, or a negative error number if an error occurs. The dwParam2 parameter of the corresponding LINE_REPLY message is zero if the function succeeds or it is a negative 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_INVALCOUNTRYCODE |
The destination country/region code is invalid. |
LINEERR_INVALCALLSTATE |
The state of hCall is not connected. |
LINEERR_INVALPOINTER |
The pointer is invalid. |
LINEERR_NOMEM |
Not enough memory is available. |
LINEERR_OPERATIONUNAVAIL |
The operation is unavailable. |
LINEERR_NOTOWNER |
The application is not the owner of this call. |
LINEERR_RESOURCEUNAVAIL |
The resources are unavailable. |
LINEERR_INVALADDRESS |
The destination address is invalid. |
LINEERR_UNINITIALIZED |
A parameter is uniinitialized. |
LINEERR_ADDRESSBLOCKED |
The destination address is blocked. |
LINEERR_OPERATIONFAILED |
The operation failed. |
Remarks
If LINEERR_INVALADDRESS is returned, no dialing occurs.
Blind transfer differs from a consultation transfer in that no consultation call is made visible to the application. After the blind transfer successfully completes, the specified call is typically cleared from the application's line, and it transitions to the idle state.
The application's call handle remains valid after the transfer has completed. The application must deallocate its handle using the lineDeallocateCall function when it is no longer interested in the transferred call.
Note
This function is for TAPI version 2.0 and later.
Requirements
| Header | tapi.h |
| Library | coredll.lib |
| Windows Embedded CE | Windows CE 1.0 and later |
| Windows Mobile | Windows Mobile Version 5.0 and later |