Dialogic® Global Call API Library Reference

Parameter Description
ret_rerouting_
infopp
not used in IP; should be set to NULL
mode set to EV_ASYNC for asynchronous execution
initiate a supervised transfer — gc_InitXfer( )
After receiving GCEV_INIT_XFER to indicate that the initiate transfer request was successful, the
application at party A can obtain the rerouting destination number or address from extevtdatap in
the METAEVENT data structure associated with the GCEV_INIT_XFER event. This rerouting
destination number or address can be used in the subsequent gc_InvokeXfer( ) function that
invokes the call transfer. The application does not need to allocate or deallocate the extevtdatap.
Termination Events
GCEV_INIT_XFER
indicates that the gc_InitXfer( ) function was successful (implies that the request was
accepted by remote party C)
GCEV_INIT_XFER_FAIL
indicates that the function failed. For more information, see the “Error Handling” section in
the Dialogic ® Global Call API Programming Guide.
GCEV_INIT_XFER_REJ
indicates that the initiate transfer request was successfully invoked by party A via the
gc_InitXfer( ) function, but the request was rejected by remote party C
Cautions
Errors
For supervised call transfer, gc_InitXfer( ) must be called before gc_InvokeXfer( ).
The gc_InitXfer( ) function can be called only when the call is in the GCST_CONNECTED
call state.
After receiving GCEV_INIT_XFER_FAIL or GCEV_INIT_XFER_REJ, the application
should not call the gc_InvokeXfer( ) function to invoke the call transfer.
If this function returns