User`s guide

Dialogic
®
System Release 6.0 PCI for Windows
®
Release Update, Rev 62 — January 30, 2008 321
Dialogic Corporation
Resolved IPY00016065 28992 -- PBX Integration The Called side drops a connection when trying to
connect from channel 1 to channel 2 through a PBX.
Resolved IPY00014328 26154 -- PBX Integration The Hardware Wizard continues to appear each time
the machine boots and asks for the correct device
driver when using either the Dialogic
®
D/82JCT-U or
D/42NE-PCI Board.
Resolved IPY00009506 28636 -- PBX Integration A phantom ring event is generated on the Nortel
Meridian.
Resolved IPY00009268 29354 -- PBX Integration Call id on the Dialogic
®
D/82 Board is inaccurate when
using networked Meridian switches.
Resolved IPY00009010 27123 -- PBX Integration Dialogic
®
D/42JCT-U Board Mitel integration: When
there is a T in the display, it is detected as a trunk call.
Resolved IPY00008814 29442 -- PBX Integration Setting or clearing MWIs too quickly causes a loss of
ability to dial feature codes.
Resolved IPY00008813 29388 -- PBX Integration Forwarded calls that originate on a networked Mitel
SX2000 switch are not being tagged with the correct
callid strings.
Resolved IPY00008445 29094 -- PBX Integration Host application does not receive
TD42_ASYNCCHSTATUS in Mitel 2000.
Resolved IPY00037923 -- 160 PDK Using PDK protocols on a system with Dialogic
®
Springware and DM3 Boards, T1/E1 GC Alarm
Condition: evt=0x832 occurs, causing a
GCEV_BLOCKED event. The channel remains in a
BLOCKED state.
Resolved IPY00016176 28334 -- PDK The num_rings parameter for gc_AnswerCall( ) does
not work on Dialogic
®
DM3 PDK, and always defaults
to 2.
Resolved IPY00016173 28222 -- PDK PDK Manager takes a long time to load (several
minutes per board).
Resolved IPY00016167 28077 -- PDK Single board start/stop fails on Dialogic
®
DM3 Boards
with PDK protocols.
Resolved IPY00016157 27800 -- PDK pdk_us_mf_io fails to detect busy when used on
Dialogic
®
DM3 Boards.
Resolved IPY00015569 28209 -- PDK The ml1_ds2_cas.pcd file will print the message
“timerIdx = 61166" while running test application.
Resolved IPY00031767 36021 84 Protocols pdk_r2_io.psi sets a wrong channel state after a timer
expires.
Resolved IPY00030912 33334 18 Protocols pdk_us_ls_fxs_io reports that the firmware detected a
disconnect tone while there was no disconnect tone
on the line. Calls are being falsely disconnected
because of this.
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