User`s guide

Dialogic
®
System Release 6.0 PCI for Windows
®
Release Update, Rev 62 — January 30, 2008 363
Dialogic Corporation
Note: For the current configuration of the replaced board to be downloaded to the new
board, the replacement board must be installed in the same slot as the board that was
removed. Otherwise, the new board will be configured with the default values of the
replaced board.
• If the Detect Only option has been selected from the System/Device autostart submenu,
the Dialogic
®
System and the boards will have to be manually started using the DCM GUI
(or NCM API). The replacement board will be detected by the system and displayed in the
DCM main window, but will not be started automatically. You will have to manually start
the new board using the DCM GUI (or NCM API).
• If the Start Server Only option has been selected, the Dialogic
®
System will start
automatically when the system is restarted and the replacement board will be detected
automatically. You will, however, need to start the replacement board manually using the
DCM GUI (or NCM API).
• If the Start System option has been selected, the Dialogic
®
System will be automatically
started and the replacement board will be detected by the system, displayed in the DCM
main window, and automatically started using the existing system configuration for that
board.
3.3.5 Dialogic
®
Native Configuration Manager API Library
Reference
Updates to NCM_ApplyTrunkConfiguration( )
On the NCM_ApplyTrunkConfiguration( ) function reference page, the first two
inputs for NCM_ApplyTrunkConfiguration( ) are not pointers. Therefore the words
“pointer to a” should be deleted from the descriptions of the inputs NCMFamily*
pncmFamily and NCMDevice* pncmDeviceUnique. (PTR# 36260)
On the NCM_ApplyTrunkConfiguration( ) function reference page, the following two
parameters should be added:
Media Loads Supported
pMediaLoad pre-defined sets of supported features. A media load consists of a
configuration file set and associated firmware. Universal media loads
support voice, fax, and conferencing resources simultaneously. See the
“Media Loads Supported” table below.
pErrorMsg API provides as needed. This is a pointer to BYTE that the API fills
with an error message on return. BYTE is defined as an unsigned
character.
Boards Media Loads Protocols
DMV1200BTEP UL1 Group 1: CAS, 4ESS, 5ESS, DMS, NI2, NTT, QSIGT1,
QSIGE1, NET5, R2MF, T1CC, E1CC
Group 2: DPNSS, DASS2
UL2 Group 1: CAS, 4ESS, 5ESS, DMS, NI2, NTT, QSIGT1, QSIGE1,
NET5, R2MF, T1CC, E1CC
Group 2: DPNSS, DASS2