User`s guide

Dialogic
®
System Release 6.0 PCI for Windows
®
Release Update, Rev 62 — January 30, 2008 347
Dialogic Corporation
Update to Section 2.4, Media Loads for new Dialogic
®
DI Board feature
Because of a new feature in the Service Update, Section 2.4.1.1 about features
supported on Dialogic
®
DI Boards should be updated to indicate that conference
bridging is supported so a higher number of maximum parties per conference is
possible. For further information about this feature, see Section 1.54, “Conference
Bridging on Dialogic
®
DI Boards”, on page 221 of this Release Update.
Update to Section 2.4.1.2, Dialogic
®
DM/IP, DM/V, DM/V-A, and DM/V-B Boards
In Table 2, Channel Densities by Board and Media Load (Universal), the table
footnote about echo cancellation should be changed as follows:
• Default configuration is EEC (enhanced EC, 32 ms) for CSP supported ML, unless
otherwise indicated or set in the component named [0x2c] in the respective CONFIG file.
You can only change it to a lower EC tail length, by changing the CSP parameter 0x2c03
accordingly in the respective CONFIG file. Conferencing EC, however, will always be 16
ms, regardless of the EC parameter setting.
Update to Section 2.5, CT Bus Clock Fallback (PTR# 35769)
Reference master fallback is not supported and should be deleted from the Section
2.5 introduction and from Figure 5, Clock Fallback. The entire Section 2.5.2,
Reference Master Fallback, should be deleted.
Update to Section 3.4, [NFAS] Section
The third note about NFAS D channel backup (DCBU) supported only on ISDN NI-2
protocol is incorrect. DCBU is supported on 4ESS, 5ESS, and NI-2.
Update to Chapter 4, Configuration Procedures
Because of an enhancement in the Service Update, it is no longer necessary to use
the fcdgen utility to generate an updated FCD file. All references to fcdgen throughout
the Configuration Guide can be ignored. For information on the enhanced way to
generate an updated FCD file, see Section 1.35.2, “Automatic FCD File Generation”,
on page 107 of this Release Update.
Update to Section 4.3, Starting the Configuration Manager (DCM)
After the Note just before step 2, add the following Note:
Note: To use remote DCM across firewalls, enable the port used by the DCOM Server,
DCMObj.exe, in the firewall configuration. DCMObj.exe is located in the /Program
Files/Dialogic/bin directory. To find out the port used by DCMObj.exe, first use the Windows
®
Task Manager to find out the PID of DCMObj.exe. Once you know the PID, you can use a port
usage utility to find out the port used by DCMObj.exe. Windows
®
XP users can run netstat -o to
find the port.
Update to Section 4.4, Selecting a Configuration File Set
Because of a feature in the Service Update, it is now possible to mix ISDN and CAS
protocols on the same Dialogic
®
DMV600BTEP or DMV1200BTEP Media Board
using the Trunk Configuration property sheet of DCM. Table 5, Protocol Groups,
should be replaced by the following table: