User`s guide

Dialogic
®
System Release 6.0 PCI for Windows
®
Release Update, Rev 62 — January 30, 2008 35
Dialogic Corporation
by default.) CDP file parameters are set on a board basis. Parameter settings are static
and apply to all calls (per board).
However, some PBXs may require either a single or double hookflash depending on the
circumstances of the call. For example, a particular PBX may require:
• Single hookflash on consultation call drop if the call went through
• Double hookflash on consultation call drop if the call was in progress but did not go
through and never got connected (for example, call progress failure or call abort
before connect)
Note: These are only examples; the circumstances requiring a single or double hookflash can
vary depending the PBX. It is up to the application developer to determine when to apply a
single or double hookflash in any scenario or deployment.
For PBXs that require either a single or double hookflash, applications must be able to:
• Programmatically select either single or double hookflash when dropping a
consultation call in a supervised transfer
• Change this behavior on a call-by-call basis
Call Transfer Overview
An overview of call transfer is given elsewhere in this Release Update. See Section 1.3.1,
“Call Transfer Overview”, on page 38.
New Parameter for Single or Double Hookflash
Runtime control of single or double hookflash is implemented using the Dialogic
®
Global
Call gc_SetConfigData( ) function. The parameter settings in gc_SetConfigData( ) are
limited to the current call, that is, to the call reference number (CRN) specified as the
target_id in gc_SetConfigData( ). The CRN should be that of the consultation call. The
application should call gc_SetConfigData( ) with the correct hookflash value before
calling gc_DropCall( ) on the consultation call.
The gc_SetConfigData( ) function uses a GC_PARM_BLK data structure that contains
the configuration information. A new parmID,
GCPARM_CONSDROP_HKFLASH_OVERRIDE, is used to set the single or double
hookflash. As its name implies, this is a parameter to override the
CDP_AllowDblHookflashOnConsultationDrop parameter in the CDP file. It does so
only on a temporary basis and for a single consultation call. (See the Implementation
Guidelines section below for further information about related parameters in the CDP file.)
The GC_PARM_BLK structure is populated using the gc_util_insert_parm_val( )
function with the following values:
• parm_blkpp = pointer to the address of a valid GC_PARM_BLK structure where the
parameter and value are to be inserted
• setID = GCSET_CALLINFO
• parmID = GCPARM_CONSDROP_HKFLASH_OVERRIDE