User`s guide

Dialogic
®
System Release 6.0 PCI for Windows
®
Release Update, Rev 62 — January 30, 2008 262
Dialogic Corporation
The following table lists all issues that relate to this release, sorted by Issue Type. For
other sort orders, use the following links:
• View issues sorted by Service Update Number
• View issues sorted by Product or Component
• View issues sorted by Defect Number
Table 9. Issues Sorted By Type, Dialogic
®
System Release 6.0 PCI for Windows
®
Issue Type Defect No.
PTR
No.
SU
No.
Dialogic
®
Product(s) or
Component(s)
Description
Known IPY00022362 19779 Clocking When setting up mixed board configurations involving
both SCbus and CT Bus, errors may arise as the
result of the placement of the clock master.
Known Clocking In the DCM, use the TDM Bus device to configure
clocking in either SCbus or CT Bus mode. You will no
longer find the SCbusClockMaster and
SCbusClockMasterSource parameters. Instead, use
the following parameters when the bus is configured in
SCbus mode:
• Specify the SCbus clock master via the “Primary
Master FRU (User Defined)” parameter.
• Specify the SCbus clock master source via the
“Derive Primary Clock From (User Defined)”
parameter. A drop-down list will be provided so that
you can select between an internal oscillator
(equivalent to INDEPENDENT in older
implementations of SCbusClockMasterSource)
and a specific trunk to derive clock from
(equivalent to LOOP in older implementations of
SCbusClockMasterSource).
Known IPY00022145 23509 Conferencing
(DCB)
On Dialogic
®
DM3 Boards, the conference notification
tone (a tone that is generated when a party enters or
exits a conference) is enabled by default; whereas on
Dialogic
®
Springware boards, the default was to
disable conference notification tone. The two problems
with enabling this tone by default are:
• This is the opposite of what Springware provides.
• There is no API method available to indicate that
tone notification should be disabled when
establishing a conference. While the MSCA_NN bit
mask exists to disable notification to receive-only
parties or monitors, this parameter doesn't apply to
all party types.
Additionally, it is suspected that the notification tone
may be contributing to PT 23506 against noises
generated when parties enter or exit a conference (in
addition to any notification tone). As a result, if the
suggestion is that tone notification should be disabled
for better conferencing quality, by default the feature
should be disabled.
Workaround: Update the FCD/CONFIG files with a
parameter to disable conference tone notification by
default.