(Page 22 of 23 in this chapter) Version

nccTransferCall

Description

Complete supervised transfer of two calls.

Prototype

DWORD nccTransferCall ( NCC_CALLHD callhd1,
NCC_CALLHD callhd2,
void *transferparms )
callhd1 A call in Connected call state.
callhd2 A call in Connected call state.
transferparms Pointer to protocol-dependent CT Access call transfer parameter structure. Protocol-independent applications can pass NULL for this argument to use the defaults. See protocol-specific documentation for details.

Return Values

SUCCESS
CTAERR_BAD_ARGUMENT
Call handles are not on the same line.
CTAERR_INVALID_HANDLE
A call handle is not valid. It may have been released.
CTAERR_INVALID_STATE
Line is not in the appropriate state to invoke this function.
NCCERR_INVALID_CALL_STATE
One call must be in the Connected state and be on hold. The other call must be in the Connected state and not be on hold. If these conditions are not satisfied, this error code will be returned.
NCCERR_NOT_CAPABLE
Protocol does not support the capability to perform a supervised transfer. The application can determine if the protocol supports this feature by examining the NCC_CAP_SUPERVISED_TRANSFER bit in the capabilitymask returned by nccQueryCapability.

Events

NCCEVN_CALL_DISCONNECTED
Received twice: once for each call. Indicates that the call is disconnected (from the point of view of the application). If the call transfer is successful, the NCC_DIS_TRANSFER reason code is returned with this event. Other protocol-specific reason codes may be reported for failure to complete transfer. See your protocol-specific implementation for more details. The CTA_EVENT structure containing this event also contains the first call handle (callhd1) of the nccTransferCall invocation.

Details

This function completes supervised transfer of two calls. Only one of the two call handles can be in the Connected state and not be on hold. Both calls must be on the same line (context) handle.
When the transfer is completed, the application should invoke nccReleaseCall for both call handles to release their resources.
Not all protocols support supervised call transfer. The application can determine if the protocol supports this state by examining the NCC_CAP_SUPERVISED_TRANSFER bit in the capabilitymask returned by nccQueryCapability.

See Also

nccAutomaticTransfer

(Page 22 of 23 in this chapter) Version

tech_support@nmss.com

Copyright © 1999, Natural MicroSystems, Inc. All rights reserved.