User`s guide

Dialogic
®
System Release 6.0 PCI for Windows
®
Release Update, Rev 62 — January 30, 2008 269
Dialogic Corporation
Known IPY00007354 31617 DM/V Boards When setting CODESET_7_IE or CODESET_6_IE
together with USER_USER_IE in the setup message,
neither IE is delivered to the remote side. However,
when setting USER_USER_IE only, it is delivered to
the remote side. Currently, Dialogic
®
DM3 Boards only
support sending non-codeset 0 messages within
supplementary services, such as FACILITY and
NOTIFY.
Known DM/V Boards R4 Compatibility Flag issue: All systems running R4
applications on high density Dialogic
®
DM3 Voice and
Network Interface Boards must make sure that the R4
Compatibility Flag parameter in the [CHP] section of
the CONFIG files is set to 1 (this is the default value).
You should enable the R4 Compatibility Flag in order
to:
• Delay reporting Offered call state until DNIS and
ANI call information is available. (Only the timing is
affected.)
• Report ISDN Q.931 Cause values instead of Call
State reasons in Call State events.
• Support Q.931 Cause values as reasons in
DropCall and ReleaseCall messages (ISDN
protocols only).
Set the R4 Compatibility flag in the [CHP] section as
follows:
SetParm=0x1310,1 ! R4 Compatibility Flag
! 0-default, 1-enable,
! 2-disable
If this parameter is not set to 1, update the CONFIG
file. After you make this modification, start the
Dialogic
®
System Service for the change to take
effect.
Known IPY00024003 32882 DM/V160-LP When setting up a supervised call transfer, after the
gc_SetupTransfer( ) function is issued to obtain a
CRN for the consultation call, a permanent signal
timer (8 seconds) starts. If the consultation call is not
made within the 8 second period, the timer expires
and the application receives a
GCEV_DISCONNECTED event. The reason
associated with the GCEV_DISCONNECTED event is
“Event Caused by Protocol Error”. The reason should
indicate that the disconnect is a result of the timer
expiring.
Known IPY00006684 31690 DM/V160-LP Debug messages are being printed in DebugAngel
when opening devices.
Workaround: Ignore the messages. Despite the
warning messages all functionality should work.
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