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.

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

Parameter Description<br />

target_type target object type<br />

target_id target object identifier. This identifier, along with target_type, uniquely<br />

specifies the target object.<br />

target_datap points to the GC_PARM_BLK structure. This structure contains the<br />

parameter configuration data to be updated. See GC_PARM_BLK, on<br />

page 443 for more information.<br />

time_out time interval (in seconds) during which the target object must be updated<br />

with the data; if the interval is exceeded, the request to update is ignored.<br />

This parameter is ignored when set to 0.<br />

This parameter is supported in synchronous mode only. If the update<br />

request is not completed in the time specified, the gc_SetConfigData( )<br />

function will return EGC_TIMEOUT.<br />

update_cond specifies when to update. Valid values are:<br />

GCUPDATE_IMMEDIATE – requires parameter to be updated<br />

immediately<br />

GCUPDATE_ATNULL – requires parameter to be updated at the Null<br />

call state. Applicable only if the target_type is associated with a call.<br />

Note: The GCUPDATE_ATNULL value should be used only if the<br />

gc_SetConfigData( ) function is called in asynchronous mode, that is,<br />

with the mode parameter set to EV_ASYNC.<br />

request_idp points to the location for storing the request ID, which is generated by<br />

<strong>Global</strong> <strong>Call</strong><br />

mode set to EV_ASYNC for asynchronous execution or to EV_SYNC for<br />

synchronous execution<br />

The parameter target_datap points to the location of the GC_PARM_BLK, which stores the<br />

configuration parameter data to be updated. Memory allocation and deallocation of the<br />

GC_PARM_BLK data block is done by the <strong>Global</strong> <strong>Call</strong> utility functions (gc_util_xxx). See<br />

Section 1.15, “GC_PARM_BLK Utility Functions”, on page 25 for more information.<br />

It is the <strong>Global</strong> <strong>Call</strong> application’s responsibility to use the <strong>Global</strong> <strong>Call</strong> utility functions to allocate<br />

an appropriate-size data block memory (GC_PARM_BLK) for the configuration parameters and to<br />

insert parameter information (such as the set ID, parm ID, value buffer size, value buffer, and value<br />

data) into the GC_PARM_BLK data block. After successfully calling the gc_SetConfigData( )<br />

function, the parameter value(s) in the GCLib or CCLib are updated with the values given in the<br />

GC_PARM_BLK (value buffer fields). After finishing its use of the GC_PARM_BLK, the <strong>Global</strong><br />

<strong>Call</strong> application should deallocate the GC_PARM_BLK data block using the<br />

gc_util_delete_parm_blk( ) function. See GC_PARM_BLK, on page 443 for more information.<br />

The function outputs a unique request ID to verify received update events and query the update<br />

results. All subsequent references to this request must be made using the request ID.<br />

The parameter configuration data can be either read-only, update immediately, or update at the Null<br />

call state. When the gc_SetConfigData( ) function is issued, the action taken by the application<br />

depends on the update condition of the parameter, as described in Table 14.<br />

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

Dialogic Corporation

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

Saved successfully!

Ooh no, something went wrong!