Dialogic 05-2239-009 User Manual

448

Dialogic Corporation

The gc_AnswerCall( ) function is used to send the Q.931 CONNECT message to the originating 
endpoint. 

The gc_AnswerCall( ) function is used to send the 200 OK message to the originating endpoint.

This function is only supported in asynchronous mode. 

The callack_blkp parameter must be a pointer to a GC_CALLACK_BLK structure that contains a 
type field with a value of GCACK_SERVICE_PROC. The following code example shows how to 
set up a GC_CALLACK_BLK structure and issue the gc_CallAck( ) function. 

GC_CALLACK_BLK gcCallAckBlk; 
memset(&gcCallAckBlk, 0, sizeof(GC_CALLACK_BLK));  
gcCallAckBlk.type = GCACK_SERVICE_PROC;
rc = gc_CallAck(crn, &gcCallAckBlk, EV_ASYNC);

The application can configure whether the Proceeding message is sent manually using the 
gc_CallAck( ) function or whether it is sent automatically by the stack. See 

, on page 141 for more information. 

The gc_CallAck( ) function is used to send the Proceeding message to the originating endpoint. 

The gc_CallAck( ) function is used to send the 100 Trying message to the originating endpoint. 

Applications should avoid closing and re-opening devices multiple times. Board devices and 
channel devices should be opened during initialization and should remain open for the duration of 
the application. 

This function is only supported in asynchronous mode. 

The cause parameter can be any of the generic cause codes documented in the gc_DropCall( ) 
function reference page in the Dialogic

 Global Call API Library Reference or a protocol-specific 

cause code as described below.