User`s guide

Dialogic
®
System Release 6.0 PCI for Windows
®
Release Update, Rev 62 — January 30, 2008 309
Dialogic Corporation
Resolved IPY00031588 36770 111 Global Call Problem with gc_HoldCall( ), which sends the
SUSPEND message to the network.
Resolved IPY00028579 34569 70 Global Call gc_RetrieveCall( ) returns error “function not
supported in this state” when using
pdk_sw_e1_ntmd_io.cdp.
Resolved IPY00028560 36335 84 Global Call gc_SetupTransfer( ) fails with invalid line device.
Resolved IPY00028530 36371 87 Global Call When gc_Start( ) fails, gc_ErrorInfo( ) cannot be
used to retrieve the error code. gc_ErrorInfo( ) fails
with an error indicating that gc_Start( ) has not been
issued. The correct behavior is for gc_ErrorInfo( ) to
execute successfully and return the error code and
description.
Resolved IPY00028492 35458 62 Global Call gc_SendMoreInfo( ) is failing when using PDK
Argentina on Dialogic
®
DM3 Boards.
Resolved IPY00028478 35825 65 Global Call GCST_ONHOLD state is not returned as documented
after a successful gc_HoldCall( ); instead the
incorrect GCST_CONNECTED state is returned.
Resolved IPY00028446 35330 65 Global Call Dialogic
®
Global Call Software does not have result
values for certain SIT tone terminations when
performing call progress analysis using PDK
protocols.
Resolved IPY00028416 35839 70 Global Call Synchronous calls to gc_WaitCall( ) cause access
violation error upon exit of the function.
Resolved IPY00028384 35875 65 Global Call gc_MakeCall(SYNC) returns -1 with an
undocumented error code when an operator intercept
is received. The problem occurs when dialing a
number whose results terminate with SIT.
Resolved IPY00028207 36310 84 Global Call gc_CompleteTransfer( ) does not complete
successfully. Error returns: “Function not supported in
current state.”
Resolved IPY00021487 24364 -- Global Call Using dx_delltones( ) in connected state causes
gc_DropCall( ) to hang. This was updated in the
Dialogic
®
Global Call Analog Technology Guide.
Resolved IPY00019243 25537 -- Global Call dx_close( ) fails if called after gc_close( ) in a
Dialogic
®
R4 Library application that uses
gc_attach( ).
Resolved IPY00019149 29335 -- Global Call Running a modified gc_basic_call_model application
(play/record features added), for the first time there
are no problem. However, after ending the application
and running it a second time, errors are seen in the
DebugAngel log.
Resolved IPY00016068 29758 -- Global Call If an application exits ungracefully two times in a row,
upon a third application execution, gc_MakeCall( )
always returns with GCEV_DISCONNECTED.
Table 9. Issues Sorted By Type, Dialogic
®
System Release 6.0 PCI for Windows
®
(Continued)
Issue Type Defect No.
PTR
No.
SU
No.
Dialogic
®
Product(s) or
Component(s)
Description