User`s guide

Dialogic
®
System Release 6.0 PCI for Windows
®
Release Update, Rev 62 — January 30, 2008 36
Dialogic Corporation
data_size = sizeof(int)
data = One of the following values:
- GCPV_SINGLE_HKFLASH - single hookflash
- GCPV_DBL_HKFLASH - double hookflash
- GCPV_DISABLED - not set
Once the GC_PARM_BLK has been populated with the desired values, the
gc_SetConfigData( ) function can be issued to perform the configuration. The parameter
values for the gc_SetConfigData( ) function are as follows:
target_type = GCTGT_CCLIB_CRN
target_id = the call reference number (CRN) of the consultation call
target_datap = pointer to the GC_PARM_BLK structure
time_out = time-out in seconds
update_cond = when to update (GCUPDATE_IMMEDIATE or GCUPDATE_ATNULL)
request_idp = pointer to the location for storing the request ID
mode = async or sync
For more detailed information about the gc_SetConfigData( ) function parameters, see
the Dialogic
®
Global Call API Library Reference.
The gc_GetConfigData( ) function returns the value previously set by
gc_SetConfigData( ) on the same CRN. If no previous setting occurred for that CRN,
GCPV_DISABLED is returned.
Implementation Guidelines
The following guidelines apply when implementing runtime control of single or double
hookflash:
This feature is only available on Dialogic
®
DM3 Boards using the United States T1
FXS/LS Bidirectional protocol.
The GCPARM_CONSDROP_HKFLASH_OVERRIDE parameter setting via
gc_SetConfigData( ) does not take effect until a gc_DropCall( ) on the consultation
call CRN is invoked. The application must invoke the gc_DropCall( ) with the
appropriate CRN for the parameter to take effect (that is, single or double hookflash
sent).
In asynchronous mode, the application must update its state machine to wait for a
success event on the gc_SetConfigData( ) before a gc_DropCall( ) on the
consultation call is invoked.
The GCPARM_CONSDROP_HKFLASH_OVERRIDE parameter has no effect on a
CRN other than the consultation call CRN resulting from a successful
gc_SetupTransfer( ).
The setting of this parameter, and therefore the behavior for a drop on a consultation
call, is not retained for subsequent calls on the same channel, unless explicitly set on
each call.