User`s guide

Dialogic
®
System Release 6.0 PCI for Windows
®
Release Update, Rev 62 — January 30, 2008 178
Dialogic Corporation
For more information about configuration files, configuration parameters, and
configuration procedures, see the Dialogic
®
DM3 Architecture PCI Products on Windows
®
Configuration Guide.
Note: The online bookshelf has not been updated for this feature, so the Dialogic
®
DM3
Architecture PCI Products on Windows
®
Configuration Guide does not currently include
information about adjusting DTMF characteristics through the CONFIG file.
1.50 Single Board Start/Stop for Selected Dialogic
®
JCT
Boards
The ability to stop and start a single Dialogic
®
JCT Board (after the system has initially
started) is now supported. With this feature, it is not necessary to shut down the entire
system while repairing a defective board or resetting a blocked channel.
Related to this is another new feature, firmware assert notification for JCT Boards. With
this feature, an application can be notified when a firmware assert takes place, so the
application can stop sending calls to the board. Previously, the application had to wait for
time-outs, open failures, etc., to determine that a board was not working.
Single board start/stop is supported on the following boards:
• Dialogic
®
D/41JCT-LS Media Boards
• Dialogic
®
D/120JCT-LS Media Boards
• Dialogic
®
D/82JCT-U Media Boards
• Dialogic
®
D/480JCT-2T1 Media Boards
• Dialogic
®
D/600JCT-2E1 Media Boards
Other JCT Boards can co-exist with these boards, but they will not be capable of single
board start/stop.
1.50.1 Stopping and Starting Boards
Single boards can be stopped and started using the NCM_StopBoard( ) and
NCM_StartBoard( ) functions. Single boards can also be stopped and started using Stop
Device and Start Device in the Dialogic
®
Configuration Manager (DCM).
For single board start/stop capable boards to be stopped and started, the entire system
must be downloaded first. The system must be started, and only those boards that have
been detected, downloaded, and enabled are candidates for single board start/stop.
Boards that are disabled or did not start during the system initialization cannot be started
using the single board start/stop feature. The entire system must be stopped and then
restarted with all desired boards up and running prior to any single board start/stop
activity.