User`s guide

Dialogic
®
System Release 6.0 PCI for Windows
®
Release Update, Rev 62 — January 30, 2008 140
Dialogic Corporation
• Post-Discovery: Reconfigure and Initialize the Boards, and Test the System for
Normal Use
Requirements for Line Adaptation
You must meet the following requirements for the line adaptation discovery phase.
• The analog telephone lines and boards that require adaptation have been identified
(referred to as the target boards/lines).
• The target boards are configured and able to function.
• The telephone lines are attached to the target boards/channels.
• There must be no inbound telephone calls during execution of the LineAdapt utility
(the incoming calls should be deactivated at the central office prior to running the
utility).
• Application and other programs must not access the target boards and telephone
lines during execution of the utility.
• Prior to line adaptation, you must perform the procedures in Set Up the System and
Configure Target Boards for Discovery. Afterwards, you must perform the procedures
in Post-Discovery: Reconfigure and Initialize the Boards, and Test the System for
Normal Use.
• The instructions in this section assume that you are familiar with the Dialogic
®
Configuration Manager (DCM). For information on using DCM, you can use the DCM
online help and you can also refer to the documentation in the Configuration Guide for
your board (separate configuration guides are provided for Dialogic
®
Springware
Boards and for Dialogic
®
DM3 Boards). The Dialogic
®
System Software for PCI
Products on Windows
®
Administration Guide may also be of use.
Set Up the System and Configure Target Boards for Discovery
Use the following procedure to configure the target boards with Continuous Speech
Processing (CSP) firmware for performing adaptation discovery:
1. If the target boards are running, use DCM to stop them.
2. Select the target board in DCM, open the “Misc” property sheet, and locate the
parameter that specifies the firmware file for the board. For DM3 Boards, the firmware
file is identified by the PCDFileName parameter, and for Springware Boards, it is
identified by the FirmwareFileName parameter.
3. Before making any changes, make note of your existing firmware file name. Then
select one of the following firmware file names that is applicable to your board (if
different from the existing file name).
Note: Proper optimization requires that one of the following firmware files, which
support CSP, be downloaded to the board for the discovery procedure.
Board
PCDFileName
(DM3 Boards)
FirmwareFileName
(Springware Boards)
D/41JCT-LS D41JCSP.FWL
D/120JCT-LS D120CSP.FWL