Severity MAJOR
Description A software error has occurred: the application did not acquire the HAL Diagnostics interface as required.
Impact Hardware diagnostics cannot be run. Consult the log for further details.
Recovery Action Contact Customer Support.
Technical Support Action Contact Product Support.
Severity MAJOR
Description A HAL usage error has occurred in the application: a diagnostic has been requested for an invalid device.
Impact Hardware diagnostics cannot run. Consult the log for further details.
Recovery Action Contact Customer Support.
Technical Support Action Contact Product Support.
Severity MAJOR
Description A HAL usage error has occurred in the application: the application has passed a bad parameter, and the request was failed by the diagnostics module. Consult the CallPilot server's Windows NT Event Log for further details.
Impact Hardware diagnostics cannot run. Consult the log for further details.
Recovery Action Contact Customer Support.
Technical Support Action Contact Product Support.
Severity MAJOR
Description A diagnostic request has failed because of an internal software bug.
Impact Hardware diagnostics cannot run. Consult the log for further details.
Recovery Action Contact Customer Support.
Technical Support Action Contact Product Support.
Severity MAJOR
Description A diagnostic request has failed because of an internal exception.
Impact Hardware diagnostics cannot run. Consult the log for further details.
Recovery Action Contact Customer Support.
Technical Support Action Contact Product Support.
Severity INFO
Description A diagnostic has been cancelled by the application. Consult the log for further details.
Impact None.
Recovery Action Not applicable.
Technical Support Action Not applicable.
Severity INFO
Description The parameter has been adjusted by the diagnostics module because the number of items passed in was too small. This is normal behaviour in response to an application request to determine the required buffer size for memory allocation purposes.
Impact None.
Recovery Action Not applicable.
Technical Support Action Not applicable.
Severity MAJOR
Description A diagnostic request has failed because there is not enough memory to complete the operation.
Impact Hardware diagnostics cannot run. Consult the log for further details.
Recovery Action Contact Customer Support.
Technical Support Action Contact Product Support.
Severity MAJOR
Description A HAL usage error has occurred in the application: a diagnostic has been requested for an invalid device.
Impact Hardware diagnostics cannot run. Consult the log for further details.
Recovery Action Contact Customer Support.
Technical Support Action Contact Product Support.
Severity MAJOR
Description A HAL usage error has occurred in the application: a diagnostic has been requested for a device which has not been taken off-duty.
Impact Hardware diagnostics cannot run. Consult the log for further details.
Recovery Action Contact Customer Support.
Technical Support Action Contact Product Support.
Severity MAJOR
Description A HAL usage error has occurred in the application: a diagnostic has been requested for a device which has not been taken off-duty.
Impact Hardware diagnostics cannot run. Consult the log for further details.
Recovery Action Contact Customer Support.
Technical Support Action Contact Product Support.
Severity MAJOR
Description A diagnostic has failed because the diagnostic support file cannot be accessed.
Impact DSP diagnostics fail. Consult the log for further details.
Recovery Action Contact Customer Support.
Technical Support Action Ensure that the DSP diagnostic COFF files exist in the DSP hardware directory. This problem should not normally occur - someone might have deleted or moved the required file. A reinstall might be required.
Severity MAJOR
Description A diagnostic has failed because the diagnostic support file cannot be accessed.
Impact DSP diagnostics fail. Consult the log for further details.
Recovery Action Contact Customer Support.
Technical Support Action Contact Product Support.
Severity MAJOR
Description A diagnostic has failed because of a low level driver fault.
Impact Hardware diagnostics fail. Consult the log for further details.
Recovery Action Contact Customer Support.
Technical Support Action Ensure that all CallPilot driver files in the Windows NT system directory have the correct version. This problem should not normally occur - someone might have corrupted such a file. A reinstall might be required.
Severity MAJOR
Description The hardware diagnostic failed due to faulty DSP hardware.
Impact MPC-8 or DSP memory could be faulty. Memory is not accessible and all multimedia channels on the DSP may not be functioning, therefore call processing on that DSP will be affected.
Recovery Action Rerun the DSP Diagnostics to confirm the result. If the error persists, contact Customer Support.
Technical Support Action Check that the MPC-8 card is present and powered on (indicated by an LED on the board). If the MPC-8 card is powered off, please refer to OAM for powering the MPC-8 on. Run the DSP tools to check for DSP status and Flash load version. Make sure the DSP is running and the Flash load is the most recent load. If all of the above fail, replace the MPC-8 card, it might be faulty.
Severity MAJOR
Description A diagnostic has failed because the diagnostic support file cannot be read or is corrupt.
Impact DSP diagnostics fail. Consult the log for further details.
Recovery Action Contact Customer Support.
Technical Support Action Ensure that the DSP diagnostic COFF files exist in the DSP hardware directory and have the correct version. This problem should not normally occur - someone might have deleted or moved the required file. A reinstall might be required.
Severity MAJOR
Description A DSP diagnostic has failed because the diagnostic support file cannot be read or is corrupt.
Impact DSP diagnostics fail. Consult the log for further details.
Recovery Action Contact Customer Support.
Technical Support Action Ensure that the DSP diagnostic COFF files exist in the DSP hardware directory and have the correct version. This problem should not normally occur - someone might have deleted or moved the required file. A reinstall might be required.
Severity MAJOR
Description A DSP diagnostic request has failed because of an internal software bug.
Impact Hardware diagnostics cannot run. Consult the log for further details.
Recovery Action Contact Customer Support.
Technical Support Action Contact Product Support.
Severity MAJOR
Description A DSP diagnostic has failed because of an error encountered in a low level driver. Consult the log for further details.
Impact MPC-8 or DSP memory could be faulty. Memory is not accessible and all multimedia channels on the DSP may not be functioning, therefore call processing on that DSP will be affected.
Recovery Action Rerun the DSP Diagnostics to confirm the result. If the error persists, contact Customer Support.
Technical Support Action Check that the MPC-8 card is present and powered on (indicated by an LED on the board). If the MPC-8 card is powered off, please refer to OAM for powering the MPC-8 on. Run the DSP tools to check for DSP status and Flash load version. Make sure the DSP is running and the Flash load is the most recent load. If all of the above fail, replace the MPC-8 card, it might be faulty.
Severity MAJOR
Description A DSP diagnostic has failed because of an error encountered in a low level driver. Consult the log for further details.
Impact MPC-8 or DSP memory could be faulty. Memory is not accessible and all multimedia channels on the DSP may not be functioning, therefore call processing on that DSP will be affected.
Recovery Action Rerun the DSP Diagnostics to confirm the result. If the error persists, contact Customer Support.
Technical Support Action Check that the MPC-8 card is present and powered on (indicated by an LED on the board). If the MPC-8 card is powered off, please refer to OAM for powering the MPC-8 on. Run the DSP tools to check for DSP status and Flash load version. Make sure the DSP is running and the Flash load is the most recent load. If all of the above fail, replace the MPC-8 card, it might be faulty.
Severity MAJOR
Description A DSP diagnostic has failed because of an error encountered in a low level driver. Consult the log for further details.
Impact MPC-8 or DSP memory could be faulty. Memory is not accessible and all multimedia channels on the DSP may not be functioning, therefore call processing on that DSP will be affected.
Recovery Action Rerun the DSP Diagnostics to confirm the result. If the error persists, contact Customer Support.
Technical Support Action Check that the MPC-8 card is present and powered on (indicated by an LED on the board). If the MPC-8 card is powered off, please refer to OAM for powering the MPC-8 on. Run the DSP tools to check for DSP status and Flash load version. Make sure the DSP is running and the Flash load is the most recent load. If all of the above fail, replace the MPC-8 card, it might be faulty.
Severity MAJOR
Description A DSP diagnostic has failed because the test pattern written does could not be verified by the host. Consult the log for further details.
Impact MPC-8 or DSP memory could be faulty. Memory is not accessible and all multimedia channels on the DSP may not be functioning, therefore call processing on that DSP will be affected.
Recovery Action Rerun the DSP Diagnostics to confirm the result. If the error persists, contact Customer Support.
Technical Support Action Check that the MPC-8 card is present and powered on (indicated by an LED on the board). If the MPC-8 card is powered off, please refer to OAM for powering the MPC-8 on. Run the DSP tools to check for DSP status and Flash load version. Make sure the DSP is running and the Flash load is the most recent load. If all of the above fail, replace the MPC-8 card, it might be faulty.
Severity MAJOR
Description A DSP diagnostic has failed because the test pattern written does could not be verified by the DSP. Consult the log for further details.
Impact MPC-8 or DSP memory could be faulty. Memory is not accessible and all multimedia channels on the DSP may not be functioning, therefore call processing on that DSP will be affected.
Recovery Action Rerun the DSP Diagnostics to confirm the result. If the error persists, contact Customer Support.
Technical Support Action Check that the MPC-8 card is present and powered on (indicated by an LED on the board). If the MPC-8 card is powered off, please refer to OAM for powering the MPC-8 on. Run the DSP tools to check for DSP status and Flash load version. Make sure the DSP is running and the Flash load is the most recent load. If all of the above fail, replace the MPC-8 card, it might be faulty.
Severity MAJOR
Description A DSP diagnostic has failed because the DSP has stopped. Consult the log for further details.
Impact MPC-8 or DSP memory could be faulty. Memory is not accessible and all multimedia channels on the DSP may not be functioning, therefore call processing on that DSP will be affected.
Recovery Action Rerun the DSP Diagnostics to confirm the result. If the error persists, contact Customer Support.
Technical Support Action Check that the MPC-8 card is present and powered on (indicated by an LED on the board). If the MPC-8 card is powered off, please refer to OAM for powering the MPC-8 on. Run the DSP tools to check for DSP status and Flash load version. Make sure the DSP is running and the Flash load is the most recent load. If all of the above fail, replace the MPC-8 card, it might be faulty.
Severity MAJOR
Description The DSP failed the Shared Memory Lock Test.
Impact MPC-8 or DSP memory could be faulty. Memory is not accessible and all multimedia channels on the DSP may not be functioning, therefore call processing on that DSP will be affected.
Recovery Action Rerun the DSP Diagnostics to confirm the result. If the error persists, contact Customer Support.
Technical Support Action Check that the MPC-8 card is present and powered on (indicated by an LED on the board). If the MPC-8 card is powered off, please refer to OAM for powering the MPC-8 on. Run the DSP tools to check for DSP status and Flash load version. Make sure the DSP is running and the Flash load is the most recent load. If all of the above fail, replace the MPC-8 card, it might be faulty.
Severity MAJOR
Description The DSP failed the Shared Memory Lock Test.
Impact MPC-8 or DSP memory could be faulty. Memory is not accessible and all multimedia channels on the DSP may not be functioning, therefore call processing on that DSP will be affected.
Recovery Action Rerun the DSP Diagnostics to confirm the result. If the error persists, contact Customer Support.
Technical Support Action Check that the MPC-8 card is present and powered on (indicated by an LED on the board). If the MPC-8 card is powered off, please refer to OAM for powering the MPC-8 on. Run the DSP tools to check for DSP status and Flash load version. Make sure the DSP is running and the Flash load is the most recent load. If all of the above fail, replace the MPC-8 card, it might be faulty.
Severity MAJOR
Description The DSP failed the Bootup Interrupt Test.
Impact MPC-8 or DSP memory could be faulty. Memory is not accessible and all multimedia channels on the DSP may not be functioning, therefore call processing on that DSP will be affected.
Recovery Action Rerun the DSP Diagnostics to confirm the result. If the error persists, contact Customer Support.
Technical Support Action Check that the MPC-8 card is present and powered on (indicated by an LED on the board). If the MPC-8 card is powered off, please refer to OAM for powering the MPC-8 on. Run the DSP tools to check for DSP status and Flash load version. Make sure the DSP is running and the Flash load is the most recent load. If all of the above fail, replace the MPC-8 card, it might be faulty.
Severity MAJOR
Description The DSP failed the Bootup Interrupt Test.
Impact MPC-8 or DSP memory could be faulty. Memory is not accessible and all multimedia channels on the DSP may not be functioning, therefore call processing on that DSP will be affected.
Recovery Action Rerun the DSP Diagnostics to confirm the result. If the error persists, contact Customer Support.
Technical Support Action Check that the MPC-8 card is present and powered on (indicated by an LED on the board). If the MPC-8 card is powered off, please refer to OAM for powering the MPC-8 on. Run the DSP tools to check for DSP status and Flash load version. Make sure the DSP is running and the Flash load is the most recent load. If all of the above fail, replace the MPC-8 card, it might be faulty.
Severity MAJOR
Description The DSP failed the Bootup Interrupt Test.
Impact MPC-8 or DSP memory could be faulty. Memory is not accessible and all multimedia channels on the DSP may not be functioning, therefore call processing on that DSP will be affected.
Recovery Action Rerun the DSP Diagnostics to confirm the result. If the error persists, contact Customer Support.
Technical Support Action Check that the MPC-8 card is present and powered on (indicated by an LED on the board). If the MPC-8 card is powered off, please refer to OAM for powering the MPC-8 on. Run the DSP tools to check for DSP status and Flash load version. Make sure the DSP is running and the Flash load is the most recent load. If all of the above fail, replace the MPC-8 card, it might be faulty.
Severity MAJOR
Description The DSP failed the Bootup Interrupt Test.
Impact MPC-8 or DSP memory could be faulty. Memory is not accessible and all multimedia channels on the DSP may not be functioning, therefore call processing on that DSP will be affected.
Recovery Action Rerun the DSP Diagnostics to confirm the result. If the error persists, contact Customer Support.
Technical Support Action Check that the MPC-8 card is present and powered on (indicated by an LED on the board). If the MPC-8 card is powered off, please refer to OAM for powering the MPC-8 on. Run the DSP tools to check for DSP status and Flash load version. Make sure the DSP is running and the Flash load is the most recent load. If all of the above fail, replace the MPC-8 card, it might be faulty.
Severity MAJOR
Description The DSP failed the Bootup Interrupt Test.
Impact MPC-8 or DSP memory could be faulty. Memory is not accessible and all multimedia channels on the DSP may not be functioning, therefore call processing on that DSP will be affected.
Recovery Action Rerun the DSP Diagnostics to confirm the result. If the error persists, contact Customer Support.
Technical Support Action Check that the MPC-8 card is present and powered on (indicated by an LED on the board). If the MPC-8 card is powered off, please refer to OAM for powering the MPC-8 on. Run the DSP tools to check for DSP status and Flash load version. Make sure the DSP is running and the Flash load is the most recent load. If all of the above fail, replace the MPC-8 card, it might be faulty.
Severity MAJOR
Description The DSP failed the Bootup Interrupt Test.
Impact MPC-8 or DSP memory could be faulty. Memory is not accessible and all multimedia channels on the DSP may not be functioning, therefore call processing on that DSP will be affected.
Recovery Action Rerun the DSP Diagnostics to confirm the result. If the error persists, contact Customer Support.
Technical Support Action Check that the MPC-8 card is present and powered on (indicated by an LED on the board). If the MPC-8 card is powered off, please refer to OAM for powering the MPC-8 on. Run the DSP tools to check for DSP status and Flash load version. Make sure the DSP is running and the Flash load is the most recent load. If all of the above fail, replace the MPC-8 card, it might be faulty.
Severity MAJOR
Description The DSP failed the Bootup Interrupt Test.
Impact MPC-8 or DSP memory could be faulty. Memory is not accessible and all multimedia channels on the DSP may not be functioning, therefore call processing on that DSP will be affected.
Recovery Action Rerun the DSP Diagnostics to confirm the result. If the error persists, contact Customer Support.
Technical Support Action Check that the MPC-8 card is present and powered on (indicated by an LED on the board). If the MPC-8 card is powered off, please refer to OAM for powering the MPC-8 on. Run the DSP tools to check for DSP status and Flash load version. Make sure the DSP is running and the Flash load is the most recent load. If all of the above fail, replace the MPC-8 card, it might be faulty.
Severity MAJOR
Description The DSP failed the Bootup Interrupt Test.
Impact MPC-8 or DSP memory could be faulty. Memory is not accessible and all multimedia channels on the DSP may not be functioning, therefore call processing on that DSP will be affected.
Recovery Action Rerun the DSP Diagnostics to confirm the result. If the error persists, contact Customer Support.
Technical Support Action Check that the MPC-8 card is present and powered on (indicated by an LED on the board). If the MPC-8 card is powered off, please refer to OAM for powering the MPC-8 on. Run the DSP tools to check for DSP status and Flash load version. Make sure the DSP is running and the Flash load is the most recent load. If all of the above fail, replace the MPC-8 card, it might be faulty.
Severity MAJOR
Description The DSP failed the Bootup Interrupt Test.
Impact MPC-8 or DSP memory could be faulty. Memory is not accessible and all multimedia channels on the DSP may not be functioning, therefore call processing on that DSP will be affected.
Recovery Action Rerun the DSP Diagnostics to confirm the result. If the error persists, contact Customer Support.
Technical Support Action Check that the MPC-8 card is present and powered on (indicated by an LED on the board). If the MPC-8 card is powered off, please refer to OAM for powering the MPC-8 on. Run the DSP tools to check for DSP status and Flash load version. Make sure the DSP is running and the Flash load is the most recent load. If all of the above fail, replace the MPC-8 card, it might be faulty.
Severity MAJOR
Description A DSP diagnostic has failed because of an internal software bug.
Impact Hardware diagnostics cannot run. Consult the log for further details.
Recovery Action Contact Customer Support.
Technical Support Action Contact Product Support.
Severity MAJOR
Description A DSP diagnostic has failed because of an internal exception.
Impact Hardware diagnostics cannot run. Consult the log for further details.
Recovery Action Contact Customer Support.
Technical Support Action Contact Product Support.
Severity MAJOR
Description A DSP diagnostic has failed because of an internal exception.
Impact Hardware diagnostics cannot run. Consult the log for further details.
Recovery Action Contact Customer Support.
Technical Support Action Contact Product Support.
Severity MAJOR
Description The DSP failed the DMA Test.
Impact MPC-8 or DSP memory could be faulty. Memory is not accessible and all multimedia channels on the DSP may not be functioning, therefore call processing on that DSP will be affected.
Recovery Action Rerun the DSP Diagnostics to confirm the result. If the error persists, contact Customer Support.
Technical Support Action Check that the MPC-8 card is present and powered on (indicated by an LED on the board). If the MPC-8 card is powered off, please refer to OAM for powering the MPC-8 on. Run the DSP tools to check for DSP status and Flash load version. Make sure the DSP is running and the Flash load is the most recent load. If all of the above fail, replace the MPC-8 card, it might be faulty.
Severity MAJOR
Description The DSP failed the DMA Test.
Impact MPC-8 or DSP memory could be faulty. Memory is not accessible and all multimedia channels on the DSP may not be functioning, therefore call processing on that DSP will be affected.
Recovery Action Rerun the DSP Diagnostics to confirm the result. If the error persists, contact Customer Support.
Technical Support Action Check that the MPC-8 card is present and powered on (indicated by an LED on the board). If the MPC-8 card is powered off, please refer to OAM for powering the MPC-8 on. Run the DSP tools to check for DSP status and Flash load version. Make sure the DSP is running and the Flash load is the most recent load. If all of the above fail, replace the MPC-8 card, it might be faulty.
Severity MAJOR
Description The DSP failed the DMA Test.
Impact MPC-8 or DSP memory could be faulty. Memory is not accessible and all multimedia channels on the DSP may not be functioning, therefore call processing on that DSP will be affected.
Recovery Action Rerun the DSP Diagnostics to confirm the result. If the error persists, contact Customer Support.
Technical Support Action Check that the MPC-8 card is present and powered on (indicated by an LED on the board). If the MPC-8 card is powered off, please refer to OAM for powering the MPC-8 on. Run the DSP tools to check for DSP status and Flash load version. Make sure the DSP is running and the Flash load is the most recent load. If all of the above fail, replace the MPC-8 card, it might be faulty.
Severity MAJOR
Description The DSP failed the DMA Test.
Impact MPC-8 or DSP memory could be faulty. Memory is not accessible and all multimedia channels on the DSP may not be functioning, therefore call processing on that DSP will be affected.
Recovery Action Rerun the DSP Diagnostics to confirm the result. If the error persists, contact Customer Support.
Technical Support Action Check that the MPC-8 card is present and powered on (indicated by an LED on the board). If the MPC-8 card is powered off, please refer to OAM for powering the MPC-8 on. Run the DSP tools to check for DSP status and Flash load version. Make sure the DSP is running and the Flash load is the most recent load. If all of the above fail, replace the MPC-8 card, it might be faulty.
Severity MAJOR
Description The DSP failed the DMA Test.
Impact MPC-8 or DSP memory could be faulty. Memory is not accessible and all multimedia channels on the DSP may not be functioning, therefore call processing on that DSP will be affected.
Recovery Action Rerun the DSP Diagnostics to confirm the result. If the error persists, contact Customer Support.
Technical Support Action Check that the MPC-8 card is present and powered on (indicated by an LED on the board). If the MPC-8 card is powered off, please refer to OAM for powering the MPC-8 on. Run the DSP tools to check for DSP status and Flash load version. Make sure the DSP is running and the Flash load is the most recent load. If all of the above fail, replace the MPC-8 card, it might be faulty.
Severity INFO
Description The HAL Diagnostics module did not find any device to perform the test requested.
Impact None.
Recovery Action Not applicable.
Technical Support Action Not applicable.
Severity MAJOR
Description A HAL usage error has occurred in the application: a timeswitch diagnostic has been requested for an invalid board.
Impact Hardware diagnostics cannot run. Consult the log for further details.
Recovery Action Contact Customer Support.
Technical Support Action Contact Product Support.
Severity MAJOR
Description A HAL usage error has occurred in the application: a timeswitch diagnostic has been requested for an invalid board.
Impact Hardware diagnostics cannot run. Consult the log for further details.
Recovery Action Contact Customer Support.
Technical Support Action Contact Product Support.
Severity MAJOR
Description A HAL usage error has occurred in the application: a timeswitch diagnostic has been requested for an invalid board.
Impact Hardware diagnostics cannot run. Consult the log for further details.
Recovery Action Contact Customer Support.
Technical Support Action Contact Product Support.
Severity MAJOR
Description A HAL usage error has occurred in the application: a timeswitch diagnostic has been requested for an invalid board.
Impact Hardware diagnostics cannot run. Consult the log for further details.
Recovery Action Contact Customer Support.
Technical Support Action Contact Product Support.
Severity MAJOR
Description The diagnostic could not run due to lack of system resources.
Impact Hardware diagnostics cannot run. Since this is a Windows NT internal error, the system may be severely impacted. Consult the log for further details.
Recovery Action Contact Customer Support.
Technical Support Action Contact Product Support.
Severity MAJOR
Description The diagnostic could not run due to lack of system resources.
Impact Hardware diagnostics cannot run. Since this is a Windows NT internal error, the system may be severely impacted. Consult the log for further details.
Recovery Action Contact Customer Support.
Technical Support Action Contact Product Support.
Severity MAJOR
Description The diagnostic could not run due to an internal software error.
Impact Hardware diagnostics cannot run. Consult the log for further details.
Recovery Action Contact Customer Support.
Technical Support Action Contact Product Support.
Severity MAJOR
Description The diagnostic could not run due to lack of system resources.
Impact Hardware diagnostics cannot run. Since this is a Windows NT internal error, the system may be severely impacted. Consult the log for further details.
Recovery Action Contact Customer Support.
Technical Support Action Contact Product Support.
Severity MAJOR
Description The diagnostic could not run due to an Windows NT internal error.
Impact Hardware diagnostics cannot run. Since this is a Windows NT internal error, the system may be severely impacted. Consult the log for further details.
Recovery Action Contact Customer Support.
Technical Support Action Contact Product Support.
Severity MAJOR
Description The diagnostic could not run because the HAL Diagnostic driver could not be loaded. Consult the log for further details.
Impact Hardware diagnostics cannot run. Consult the log for further details.
Recovery Action Contact Customer Support.
Technical Support Action Ensure that all CallPilot HAL library files are in the application directory and have the correct version. This problem should not normally occur - someone might have moved, deleted or corrupted such files. A reinstall might be required.
Severity MAJOR
Description A software error has occurred: the application passed invalid parameters to the HAL Diagnostics interface.
Impact Hardware diagnostics cannot run. Consult the log for further details.
Recovery Action Contact Customer Support.
Technical Support Action Contact Product Support.
Severity MAJOR
Description The requested diagnostic has failed. Consult the log for further details.
Impact Consult the log for details.
Recovery Action Consult the log for details.
Technical Support Action Not applicable