08.01.2013 Views

Dialogic® Global Call API Library Reference

Dialogic® Global Call API Library Reference

Dialogic® Global Call API Library Reference

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

Table 14. Parameter Configuration Data Conditions and Results<br />

update the configuration data — gc_SetConfigData( )<br />

Parameter Update Condition Result when gc_SetConfigData( ) is <strong>Call</strong>ed<br />

Read-only An error is returned immediately.<br />

Update immediately Configuration data is updated immediately.<br />

Update only at Null call state Configuration data is updated when the target object does not have an<br />

active call (Null call state). A request for an immediate update may fail.<br />

To immediately update parameters that can be updated only at the Null<br />

call state, call gc_SetConfigData( ) with GCUPDATE_ATNULL and then<br />

call gc_ResetLineDev( ).<br />

The gc_SetConfigData( ) function supports both the synchronous and asynchronous modes. In the<br />

asynchronous mode, the termination events, GCEV_SETCONFIGDATA and<br />

GCEV_SETCONFIGDATA_FAIL, both have an associated GC_RTCM_EVTDATA data structure<br />

(to which the evtdatap field in METAEVENT points) that includes the request ID, additional<br />

message, etc., but without the retrieved GC_PARM_BLK field. The request ID is used by the<br />

application to trace the function call. See GC_RTCM_EVTDATA, on page 450 for more<br />

information.<br />

When the gc_SetConfigData( ) function is called to update the configuration data of a group of<br />

parameters, the request will terminate on any single parameter updating failure. Some parameters<br />

may be updated while others may not be updated. To find out what kind of error occurred and<br />

which parameter data pair (set ID, parm ID) were being updated when it occurred, use the<br />

gc_ErrorInfo( ) function to retrieve information about function return values or the<br />

gc_ResultInfo( ) function to retrieve information about termination events. (See the “Error<br />

Handling” section in the Dialogic ® <strong>Global</strong> <strong>Call</strong> <strong>API</strong> Programming Guide for more information<br />

about these error functions.) To determine which parameters were updated, use the<br />

gc_GetConfigData( ) function to retrieve the current configuration. After the error is fixed, call the<br />

gc_SetConfigData( ) function again to update the remaining parameters.<br />

Termination Events<br />

GCEV_SETCONFIGDATA<br />

indicates that the gc_SetConfigData( ) function was successful, that is, the configuration data<br />

has been successfully updated<br />

GCEV_SETCONFIGDATA_FAIL<br />

indicates that the gc_SetConfigData( ) function failed<br />

Cautions<br />

Parameters should be set with caution. Improper setting of parameters may result in<br />

unpredictable behavior. Consult the Dialogic ® <strong>Global</strong> <strong>Call</strong> <strong>API</strong> Programming Guide and the<br />

appropriate <strong>Global</strong> <strong>Call</strong> Technology Guide for the impact of changing any settings.<br />

In the synchronous mode, the function does not return until the request is completed. If the<br />

parameter is allowed to update only at the Null call state (no active call) but the current call<br />

state for the related target object is not at the Null call state, the system may be blocked. This<br />

occurs because the function waits for the Null call state while the system waits for the function<br />

to finish. To avoid this blocking, use the asynchronous mode.<br />

Dialogic ® <strong>Global</strong> <strong>Call</strong> <strong>API</strong> <strong>Library</strong> <strong>Reference</strong> — January 2008 321<br />

Dialogic Corporation

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!