/mcpThe lineBlindTransfer function that is implemented until Cisco Unified TSP 3.3 does not comply with the TAPI specification. This function actually gets implemented as a consultation transfer and not a single-step transfer. From Cisco Unified TSP 4.0, the lineBlindTransfer complies with the TAPI specs wherein the transfer is a single-step transfer. Note If the application tries to blind transfer a call to an address that requires a FAC, CMC, or both, then the lineBlindTransfer function will return an error. If a FAC is required, the TSP will return the error LINEERR_FACREQUIRED. If a CMC is required, the TSP will return the error LINEERR_CMCREQUIRED. If both a FAC and a CMC are required, the TSP will return the error LINEERR_FACANDCMCREQUIRED. An application that wants to blind transfer a call to an address that requires a FAC, CMC, or both, should use the lineDevSpecific -BlindTransferFACCMC function. Function Details LONG lineBlindTransfer( HCALL hCall, LPCSTR lpszDestAddress, DWORD dwCountryCode ); Parameters hCall A 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 A pointer to a NULL-terminated string that identifies the location to which the call is to be transferred. The destination address uses the standard dial number format. dwCountryCode The country code of the destination. The implementation uses this parameter to select the call progress protocols for the destination address. If a value of 0 is specified, the defined default call-progress protocol is used. lineCallbackFunc The lineCallbackFunc function provides a placeholder for the application-supplied function name. Function Details VOID FAR PASCAL lineCallbackFunc( DWORD hDevice, DWORD dwMsg, DWORD dwCallbackInstance, DWORD dwParam1, DWORD dwParam2, DWORD dwParam3 ); Cisco Unified TAPI Developers Guide for Cisco Unified Communications Manager, Release 15 and SUs 149 Basic TAPI Implementation lineCallbackFunc