User`s guide

Dialogic
®
System Release 6.0 PCI for Windows
®
Release Update, Rev 62 — January 30, 2008 390
Dialogic Corporation
should be added in the ISDN-Specific Operations chapter. For information about this
feature, see Section 1.47, “Support for QSIG NCAS Calls on Dialogic
®
DM3 Boards”,
on page 161 of this Release Update.
Update to Chapter 2, Global Call Architecture for ISDN (IPY00006540 = PTR# 34211)
The following information should be appended to the end of Chapter 2:
GCEV_EXTENSION Events
There are ISDN-specific Global Call events, which will eventually be mapped to
GCEV_EXTENSION. But to maintain backward compatibility, the Global Call application has the
option to choose ISDN-specific events or GCEV_EXTENSION. The default is ISDN-specific
events. For more information, refer to Section 4.2, “Operations Performed Using RTCM”.
Note: When using Dialogic
®
DM3 Boards, the GCEV_EXTENSION event is not supported. DM3
Boards use ISDN-specific events only.
If the application needs to use the new generic call model or extension features, gc_Start( ) should
be called as shown below:
CCLIB_START_STRUCT cclib_struct;
GC_START_STRUCT gc_start_struct;
GC_PARM_BLK *parmblk = NULL;
gc_util_insert_parm_val( &parmblk,
GCIS_SET_GENERIC,
GCIS_PARM_EXTENSIONEVENT,
sizeof( char ), 1);
gc_util_insert_parm_val( &parmblk,
GCIS_SET_GENERIC,
GCIS_PARM_GENERICCALLMODEL,
sizeof( char ), 1);
gc_start_struct.num_cclibs = 1;
gc_start_struct.cclib_list = &cclib_struct;
gc_start_struct.cclib_list[0].cclib_name = "GC_ISDN_LIB";
gc_start_struct.cclib_list[0].cclib_data = parmblk;
if ( gc_Start( &gc_start_struct ) != GC_SUCCESS ) {
exit(1);
}
gc_util_delete_parm_blk(parmblk);
The field extevtdatap of the METAEVENT structure points to EXTENSIONEVT_BLK.
typedef struct {
unsigned char ext_id;
GC_PARM_BLK parmblk;
} EXTENSIONEVTBLK;
The following table defines the different possible extension IDs in the GCEV_EXTENSION event.