User`s guide

Dialogic
®
System Release 6.0 PCI for Windows
®
Release Update, Rev 62 — January 30, 2008 276
Dialogic Corporation
Known IPY00023978 31618 Host Library Applications utilizing a Dialogic
®
HiZ board may take
15-20 minutes to shut down.
Workaround: Tearing down channels in parallel will
greatly reduce the shutdown time (less than 30
seconds).
Known IPY00023708 27287 Host Library When using ms_genRingCallerId( ) on a Dialogic
®
HDSI or DI/SI32 Board, with cadence
MS_RNGA_SHORTLONG, the phone rings with the
specified cadence, but does not show the caller id.
Known IPY00009177 31642 Host Library SRLGetSubDevicesOnVirtualBoard returns 0 sub
devices for Dialogic
®
D600JCT-2E1 Boards.
Known IPY00008960 31060 Host Library Applications using cached prompts will crash or be
abnormally terminated if they do not issue a
dx_close( ) before exiting the application. If this is not
adhered to, the cached prompt API will fail on the next
execution and the board will have to be re-
downloaded.
Workaround: Once cached prompt is downloaded,
close the physical board with dx_close( ) API before
exiting from application.
Known IPY00007762 31734 Host-Based H.323
Protocol Stack
Dialogic
®
Global Call Software applications that use
the host-based H.323 protocol stack may generate the
following error message in the gc_h3r.log file if the
application enables the stack to send the
PROCEEDING message automatically.
! 22:22:19.393 ! M_SIGNAL ! L_ERROR ! 1 ! <<
SIGNAL::sendProcceding: RV
cmCallSendCallProceeding Failed : [-996]
Workaround: Ignore this error message. The
PROCEEDING message is actually sent.
Known IPY00017747 29044 IP CCLIB For host-based configurations (using Dialogic
®
Global
Call or IPML API), if QoS lost packets alarms
(QOSTYPE_LOSTPACKETS) have been enabled and
out of band signaling is being used (either H.245 UII or
RFC2833), then QOSTYPE_LOSTPACKETS alarms
will be generated whenever information is sent out of
band.
Workaround: Ignore the alarm (which is for information
purposes anyway) or disable the alarm event.
Known IPY00022147 23574 ISDN cc_SetParmEx( ) fails when changing parameters
that require numerical values (e.g. BC_XFER_RATE).
This is not applicable to the parameters that require
character string values (e.g. DIRECTORY_NUMBER).
Workaround: When using cc_SetParmEx( ) to set a
parameter that requires a numerical value, set the
length field in the PARM_INFO structure to 1 and
ensure that only the first byte in the parmdata field
contains the value.
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