User`s guide

Dialogic
®
System Release 6.0 PCI for Windows
®
Release Update, Rev 62 — January 30, 2008 338
Dialogic Corporation
Resolved IPY00012758 27572 -- UDD Dialogic
®
Diagnostics Software (UDD) does not work
correctly on Dialogic
®
D/600JCT-2E1 Boards.
Resolved IPY00007931 23718 115 UDD Dialogic
®
D/240JCT and D/480JCT Boards fail
Dialogic
®
Diagnostics Software (UDD) firmware
download.
Resolved IPY00007492 29714 -- VFX/41JCT Dialogic
®
VFX/41JCT Board failed with
ATFX_E STAT ( ) error code 102 - Got DCN while
waiting for DIS.
Resolved IPY00039032 -- 162 Voice Dialogic
®
DM3 Voice resources don’t go to idle state
after dx_stopch( ) function.
Resolved IPY00038991 -- 160 Voice Previously existing user-defined tones are still being
detected after deletion (i.e., call dx_deltones( )) on
the same channel in which a new set of different user-
defined tones have been created.
Resolved IPY00037777 -- 154 Voice With sr_enbhdlr( ) being used to enable handler for
all events on dxxxdev, after running dx_stopch( ) to
stop dx_playiottdata( ), the callback function didn't
run. Also, there is no TDX_PLAY event in the log.
Resolved IPY00037432 -- 148 Voice The dx_clrdigbuf( ) function overwrites area of
thread’s stack space, causing the application to crash.
Resolved IPY00036865 -- 142 Voice If a user attempts to do a play forever (specifying
io_length = -1) with UIO plays on Dialogic
®
DM3
Boards, there is still a hard upper limit on the number
of bytes that can be played, which is approximately
equal to 2.147 GB (~2 to the 31 bytes).
Resolved IPY00036345 -- 142 Voice If a user calls dx_play( ) asynchronously and then
calls dx_stopch( ) synchronously (possibly from
another thread) on the same voice device to stop the
play, the application sees different behaviors based on
whether the voice device is a Dialogic
®
DM3 or
Dialogic
®
Springware device. DM3 and Springware
devices should behave the same way with regards to
the eventing mechanism.
Note: The fix for defect IPY00036345 changed the
eventing mechanism behavior for Springware
to match that of DM3. Behavior is now such
that calling dx_stopch( ) synchronously no
longer consumes TDX_PLAY events.
Springware applications will now receive
TDX_PLAY events when calling dx_stopch( )
synchronously.
Resolved IPY00034378 -- 125 Voice dx_playiottdata( ) function does not return
TDX_PLAY event when directly followed by a
dx_pause( ) and then dx_stopch( ).
Resolved IPY00034365 -- 139 Voice While the Dialogic
®
Springware voice module in the
RTF config file is enabled, running the
gc_basic_call_model application to make an outbound
call causes a GCEV_FATALERROR.
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