User`s guide

Dialogic
®
System Release 6.0 PCI for Windows
®
Release Update, Rev 62 — January 30, 2008 258
Dialogic Corporation
Whenever a CONFIG file has been modified, a new FCD file must be generated. This
procedure is described in detail in the Dialogic
®
DM3 Architecture PCI Products on
Windows
®
Configuration Guide.
1.73.3 Documentation
The online bookshelf provided with Dialogic
®
System Release 6.0 PCI for Windows
®
contains information about all system release features including features for application
development, configuration, administration, and diagnostics.
For more information about gc_OpenEx( ) and other Dialogic
®
Global Call API functions,
see the following documents:
• Dialogic
®
Global Call API Programming Guide
• Dialogic
®
Global Call API Library Reference
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 the Initial Alarm State (0x1626) parameter.
1.74 Extended Board Management API Support for
Dialogic
®
DM3 Boards
The Dialogic
®
Board Management API provides runtime fault monitoring and
management of boards. For example, in the event of an application or host crash,
channels can be set out-of-service to prevent the switch in the CO from sending calls to a
board if there is no application to process them. This prevents the acceptance of
unwanted calls and the potential of being unnecessarily tariffed.
Formerly, the Board Management API was supported only for T1 North American ISDN
protocols (4ESS, 5ESS, DMS100, DMS250, and NI2). The Service Update extends
support of the Board Management API to DM3 Boards using E1/T1 CAS (PDK protocols),
additional T1 ISDN (NTT and QSIG-T1), E1 ISDN (NET5 and QSIG-E1), DPNSS, and
DASS2.
These enhancements are applicable to the following boards:
• Dialogic
®
DM/V, DM/V-A, DM/V-B, and DM/VF Media Boards
• Dialogic
®
DM/IP Boards
1.74.1 Feature Description
The brd_SendAliveEnable( ) function enables host fault monitoring on the specified
board. When enabled, the board monitors the host computer for the presence of a
repeated “heartbeat,” or “ping.” The heartbeat is sent to the board by the
brd_SendAlive( ) function from an application on the host computer. If the board does not
receive the “heartbeat” or “ping” message within the required parameters defined in the