This article provides an overview of the hardware and software installation process for Dialogic® Diva® Media Boards and includes links to more detailed material.
1. Install the Dialogic Diva Media Board
Diva Media Board Hardware Installation
Follow these steps to install a Diva Media Board board in your machine. Common safety rules apply.
Power off the server.
Plug the board in a free PCI/PCI-X or PCIe slot depending on the type of your board. Secure the board with the slot bolts.
Connect the phone line.
Power on the Server and boot the operating system.
For Further information please see PCI slots supported
Hardware installation is successful when Windows auto-detects the Diva board as a new device.
You can also check in Windows Device Manager to see if the Diva board is detected as a network adapter.
If the Diva board is not detected, check the hardware installation guide. ( Need to add suspect hardware faults)
If the board is properly detected, proceed to step 2.
2. Install the Dialogic® Diva® System Release Software ( Need to copy more details too )
The software installation is successful when the driver installation routine detects the Diva board and installation finishes without error messages.
If the installation routine fails to start, check that the correct driver version was downloaded for your operating system and Diva Media Board. In particular, you should check that the Diva System Release Software supports your Diva Media Board.
To verify successful driver installation, open the Diva Configuration Manager.
If the Diva Configuration Manager only contains Dialogic® Diva® softIP, then the hardware Diva Media Board was not detected. Check the hardware installation guide. ( Need to add suspect hardware faults)
If the Diva Configuration Manager shows the Diva board, proceed to step 3.
3. Configure the Diva® System Release Software
The Diva software is successfully configured if your application can detect and access the board and if calls are working.
If your application detects the board but fails to make calls, check the line configuration. (check this too)
If your application fails to detect the board, verify that the appropriate interface is installed (this too )and configured.