JCT -Detect Board and Start Service

1 Symptom
2 Reason for the problem
3 Fix / Solution
4 Workaround
5 Product List

Symptom

The Dialogic board is not detected, or the Dialogic services do not start.

Reason for the problem

There are a number of reasons that these issues can occur, but there are only 2 areas of focus: the Dialogic blade, and the system the blade resides in.

Fix / Solution

A faulty Dialogic blade

To determine if the hardware is faulty, try another blade of the same model and revision, if one is available. If a similar board is not available, then use other troubleshooting methods, such as verifying the PCI slot is functioning properly, before concluding the hardware is faulty.

An issue with the system

If Dialogic hardware is not detected in the system or services cannot be started, there are many possible causes that should be pursued, consisting of possible system hardware issues or possible system resource/configuration issues. Here is a compiled list of troubleshooting techniques to try and determine the cause of the problem:

     -- Contact the manufacturer of the system for assistance.
     -- Check if system requires some type of BIOS Configuration tool.
     -- Consult the release notes to confirm the memory and processor requirements.
     -- Disable Plug ‘N Play in the BIOS.
     -- Check for system resource issue, by disabling network board, disabling RAID Controller (if present) or any other unnecessary peripheral component. Also try lowering the screen resolution.
     -- Try different PCI slots.
     -- If multiple Dialogic blade(s) are in the sytem, make sure the CT Bus cable is appropriately attached.
     -- If multiple Dialogic blade(s) are in the sytem, try starting with just one blade before adding others.
     -- If the System Release base is SR 5.1.1, the user should upgrade to the latest System Update due to many resolved issues noted in the Release Update documentation.
     -- Dialogic blade products run in 32-bit 33MHz mode, and to meet the PCI spec, other devices that can run in 64-bit/66MHz must be backward compatible, i.e. they must scale down to 32-bit/33MHz to be
compatible w/ the rest of the devices on the PCI Bus (and if not, there is a chance we will have detection and startup issues). *
     -- With RAID enabled motherboards, the RAID Controller may need to be in a specific slot (see system documentaion, it may have to be enabled/disabled via BIOS setting).
     -- If the System Release base is SR 5.1.1, the user should download install PTR 27176 (this assumes there are no ISA components in the system).
     -- Remove the entire "Installed Boards" directory from the Registry, under HKEY_LOCAL_MACHINE | SOFTWARE | Dialogic, and restart DCM.
     -- Check that the Dialogic product is listed in Device Manager, and if so, to to "Properties" and click to "Update Driver" (allow Windows to do this automatically), and restart DCM.
     -- Reinstall the Dialogic software.

Dialogic components will function in 64-bit/66MHz slots, but will only run at 32-bit/33MHz. This means that any other component on the PCI bus must also step back to that speed and frequency.

Workaround

The above troubleshooting techniques are not necessarily intended as a final solution should the Dialogic product be detected and started. These suggestions are for information gathering in an attempt to limit the variable(s) to focus on to come up with a final solution.

Product List

JCT series PCI products on the SR 5.1.1 and SR 6.0 release lines.

Dialogic Voice Cards