User`s guide

Dialogic
®
System Release 6.0 PCI for Windows
®
Release Update, Rev 62 — January 30, 2008 288
Dialogic Corporation
Known
(permanent)
IPY00030548 24937 Springware Voice If you call the dx_reciottdata( ) function and you
specify a DX_MAXSIL termination condition,
dx_reciottdata( ) ignores this condition and will
eventually trigger on another one (DX_MAXTIME)
even if there is silence on the line.
Workaround: Set the EC_RESOURCE feature in DCM
to ON.
Known
(permanent)
IPY00022341 14325 Springware Voice lineDial does not generate DTMF tones A, B, C, and D
if specified dial string is in uppercase during inband
dialing.
Workaround: You must use lowercase letters a, b, c, d
in a dial string that contains an escape string. The
firmware only accepts lowercase letters a, b, c, d.
The TSP provides the conversion for out-of-band
dialing (default), but does nothing when an escape
string is present in the dial string (in-band dialing).
Therefore, any uppercase letters A, B, C, D used in
a dial string that contains an escape string will be
ignored by the firmware.
Known
(permanent)
IPY00022151 23673 Springware Voice DE_RINGS is received after the TDX_RECORD if the
onhook recording begins while the ring is generated
on the line. Explanation: When using analog
Dialogic
®
Springware Boards, if a ring is generated on
the line when you begin onhook recording, the
DE_RINGS event will be received by the application
after the TDX_RECORD event, i.e. after the recording
is finished. The firmware was designed to process the
rings in this manner and suspends the ring debouncer
on issuance of commands like play and record. The
debouncer is resumed only on completion of the play
or record. Since the ring debouncer is suspended, the
firmware cannot send a DE_RINGS event to the
application. On resumption, the debouncer goes back
to its last state and will send the ring event to the host.
Known
(permanent)
IPY00022100 21760 Springware Voice Calling dx_setevtmsk( ) while a dx_play( ) is running
will cause the play to return with a TDX_ERROR,
EDX_SH_BADCMD. Explanation: Calls to
dx_setevtmsk( ) on a channel that is currently playing
a file causes an error to be returned and the channel
to get stuck in an unstable state that requires the
application to be shutdown and restarted to recover.
Workaround: Call dx_setevtmsk( ) initially with
DM_DIGITS to enable DTMF digit events.
DM_DIGITS should not be specified when making
subsequent calls to dx_getevtmsk( ), for instance,
when turning on/off silence events. This requires the
application to be modified so that the DM_DIGITS
flag is only passed to the function at initialization
time.
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