Download Dialogic M7324 User`s guide

Table 9. Issues Sorted By Type, Dialogic® System Release 6.0 PCI for Windows® (Continued)
SU
No.
Dialogic®
Product(s) or
Component(s)
Defect No.
PTR
No.
Known
IPY00021978
28889
DMV160LP
DTMF termination condition issue. On the Dialogic®
DMV160LP Board, when the record operations are set
to be terminated on a DTMF, the recorded file may
contain between 30 to 50 msec of the terminating
DTMF.
Known
IPY00023977
31550
Global Call
For an object intending to use gc_MakeCall( ), all call
temporal parameters need to be settable via the make
call block.
Issue Type
Description
Workaround: Continue to use gc_SetUserInfo( )
before gc_MakeCall( ) to set parameters.
Known
IPY00022395
20083
Global Call
On Dialogic® DM3 Boards, MakeCall is not successful
after placing lines in service. Explanation: When
running ISDN through R4 on DM3, it is important to
ensure the line has been put in service and the
D channel has come up prior to making calls on any
channels.
Workaround: There are three possible ways to ensure
this happens:
• Open up the board device (e.g., dtiB1) and wait for
the event GCEV_D_CHAN_STATUS (with reason
E_LINKUP | ERR_ISDN_LIB) prior to placing any
calls.
• Prior to running the application, run the QSCRIPT
tool “lineadmin -board x” where “x” is the number of
the board and put all of the lines in service.
• Add a 3 second delay into the application between
the time the channels are opened and the first
attempt to issue a MakeCall.
Known
IPY00022135
23048
Global Call
Exception while receiving GCEV_OFFERED event.
Explanation: Customers should not use sr_putevt( )
to send any Dialogic-specific event codes. The
Dialogic® library that is usually sending this event may
need to change its internal state and may go out of
sync with other libraries that will also receive this event
using high priority handles.
Known
IPY00021408
29419
Global Call on IP
Applications running Dialogic® Global Call Software
on host-based SIP or H.323 stacks and issuing
gc_WaitCall( ) before every call produce errors at
higher call rates.
Workaround: Applications should issue
gc_WaitCall( ) only once for a given channel at the
beginning of application or after
gc_ResetLineDev( ) has been completed
(GCEV_RESETLINEDEV has been received).
Dialogic® System Release 6.0 PCI for Windows® Release Update, Rev 62 — January 30, 2008
Dialogic Corporation
272