Severity MAJOR
Description A low level driver encountered an internal software error. Consult the CallPilot server's Windows NT Event Log for further details.
Impact The application may not have full access to the given hardware resources. Consult the log for further details.
Recovery Action Contact customer support.
Technical Support Action Report the occurrence to Product Support.
Severity MAJOR
Description A bad parameter has been passed to an internal shared list. Consult the CallPilot server's Windows NT Event Log for further details.
Impact The application may not have full access to the given hardware resources. Consult the log for further details.
Recovery Action Contact customer support.
Technical Support Action Report the occurrence to Product Support.
Severity MAJOR
Description There is not enough memory to perform the operation requested. Consult the CallPilot server's Windows NT Event Log for further details.
Impact The application may not have full access to the given hardware resources. Consult the log for further details.
Recovery Action Contact customer support.
Technical Support Action Report the occurrence to Product Support.
Severity MAJOR
Description Cannot initialize the security object for a low level driver. Consult the CallPilot server's Windows NT Event Log for further details.
Impact The application may not have full access to the given hardware resources. Consult the log for further details.
Recovery Action Contact customer support.
Technical Support Action Report the occurrence to Product Support.
Severity MAJOR
Description Cannot create an internal synchronization object for a low level driver. Consult the CallPilot server's Windows NT Event Log for further details.
Impact The application may not have full access to the given hardware resources. Consult the log for further details.
Recovery Action Contact customer support.
Technical Support Action Report the occurrence to Product Support.
Severity MAJOR
Description Cannot use an internal synchronization object for a low level driver. Consult the CallPilot server's Windows NT Event Log for further details.
Impact The application may not have full access to the given hardware resources. Consult the log for further details.
Recovery Action Contact customer support.
Technical Support Action Report the occurrence to Product Support.
Severity MAJOR
Description A timeout error occurred in a low level driver. Consult the CallPilot server's Windows NT Event Log for further details.
Impact The application may not have full access to the given hardware resources. Consult the log for further details.
Recovery Action Contact customer support.
Technical Support Action Report the occurrence to Product Support.
Severity MAJOR
Description Cannot use an internal synchronization object for a low level driver. Consult the CallPilot server's Windows NT Event Log for further details.
Impact The application may not have full access to the given hardware resources. Consult the log for further details.
Recovery Action Contact customer support.
Technical Support Action Report the occurrence to Product Support.
Severity MAJOR
Description A Windows NT timeout error occurred in a low level driver. Consult the CallPilot server's Windows NT Event Log for further details.
Impact The application may not have full access to the given hardware resources. Consult the log for further details.
Recovery Action Contact Customer Support.
Technical Support Action Report the occurrence to Product Support.
Severity MAJOR
Description An internal synchronization object has been locked in a low level driver. Consult the CallPilot server's Windows NT Event Log for further details.
Impact The application may not have full access to the given hardware resources. Consult the log for further details.
Recovery Action Contact Customer Support.
Technical Support Action Report the occurrence to Product Support.
Severity MAJOR
Description Cannot create an internal synchronization object for a low level driver. Consult the CallPilot server's Windows NT Event Log for further details.
Impact The application may not have full access to the given hardware resources. Consult the log for further details.
Recovery Action Contact Customer Support.
Technical Support Action Report the occurrence to Product Support.
Severity MAJOR
Description Cannot use an internal synchronization object for a low level driver. Consult the CallPilot server's Windows NT Event Log for further details.
Impact The application may not have full access to the given hardware resources. Consult the log for further details.
Recovery Action Contact Customer Support.
Technical Support Action Report the occurrence to Product Support.
Severity MAJOR
Description Cannot initialize an internal synchronization object for a low level driver. Consult the CallPilot server's Windows NT Event Log for further details.
Impact The application may not have full access to the given hardware resources. Consult the log for further details.
Recovery Action Contact Customer Support.
Technical Support Action Contact Product Support.
Severity MAJOR
Description Cannot load a low level driver. Consult the CallPilot server's Windows NT Event Log for further details.
Impact The application may not have full access to the given hardware resources. Consult the log for further details.
Recovery Action Contact Customer Support.
Technical Support Action Ensure that the specified file exists and is located in the CallPilot application 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 low level driver library file is corrupt and cannot be used. Consult the CallPilot server's Windows NT Event Log for further details.
Impact The application may not have full access to the given hardware resources. Consult the log for further details.
Recovery Action Contact Customer Support.
Technical Support Action Check the version of the specified file, located in the CallPilot application directory. This problem should not normally occur - someone might have corrupted the required file. A reinstall might be required.
Severity MAJOR
Description A low level driver encountered an internal software error. Consult the CallPilot server's Windows NT Event Log for further details.
Impact The application may not have full access to the given hardware resources. Consult the log for further details.
Recovery Action Contact Customer Support.
Technical Support Action Contact Product Support.
Severity MAJOR
Description A low level driver could not initialize because an internal shared list is full. Consult the CallPilot server's Windows NT Event Log for further details.
Impact The application may not have full access to the given hardware resources. Consult the log for further details.
Recovery Action Contact Customer Support.
Technical Support Action Contact Product Support.
Severity MAJOR
Description A low level driver could not locate the data requested in an internal list. Consult the CallPilot server's Windows NT Event Log for further details.
Impact The application may not have full access to the given hardware resources. Consult the log for further details.
Recovery Action Contact Customer Support.
Technical Support Action Contact Product Support.
Severity INFO
Description Indicates that the HAL Monitor Service is starting.
Impact None.
Recovery Action Not applicable.
Technical Support Action Not applicable.
Severity INFO
Description Indicates that the HAL Monitor Service is up and running normally.
Impact None.
Recovery Action Not applicable.
Technical Support Action Not applicable.
Severity INFO
Description Indicates that the HAL Monitor Service is stopping.
Impact None.
Recovery Action Not applicable.
Technical Support Action Not applicable.
Severity INFO
Description Indicates that the HAL Monitor Service has shut down.
Impact None.
Recovery Action Not applicable.
Technical Support Action Not applicable.
Severity MAJOR
Description The HAL Monitor Service cannot start due to a Windows NT error.
Impact If running on an IPE platform, insertion or removal of MPC cards cannot be detected without a server reboot.
Recovery Action Contact Customer Support.
Technical Support Action Contact Product Support.
Severity MAJOR
Description The HAL Monitor service cannot report its service status to Windows NT.
Impact This is an internal Windows NT fault and the system may be severely impacted.
Recovery Action Contact Customer Support.
Technical Support Action Contact Product Support.
Severity MAJOR
Description The HAL Monitor service cannot create an internal synchronization event.
Impact This is an internal Windows NT fault and the system may be severely impacted.
Recovery Action Contact Customer Support.
Technical Support Action Contact Product Support.
Severity MAJOR
Description The HAL Monitor service cannot synchronize with the NTBUS driver.
Impact If running on an IPE platform, insertion or removal of MPC cards cannot be detected without a server reboot.
Recovery Action Use the Devices applet in the Windows NT Control Panel and ensure the CallPilot Ntbus Driver is running.
Technical Support Action Not applicable
Severity MAJOR
Description An I/O error occurred in the HAL Monitor service and the service is shutting down.
Impact If running on an IPE platform, insertion or removal of MPC cards cannot be detected without a server reboot. This is usually an internal Windows NT fault and the system may be severely impacted.
Recovery Action Contact Customer Support.
Technical Support Action Contact Product Support.
Severity MAJOR
Description The HAL Monitor service failed to initialize the detection server and the service is shutting down.
Impact Applications may not have access to multimedia hardware resources. Consult the log for further details.
Recovery Action Contact Customer Support.
Technical Support Action Please report the occurrence of this software to CallPilot designers.
Severity MAJOR
Description The HAL Monitor service failed to detect multimedia hardware and the service is shutting down.
Impact Applications may not have access to multimedia hardware resources. Consult the log for further details.
Recovery Action This is most likely caused by a configuration problem. The correct platform type information should be selected at installation time. Consult the CallPilot product documentation for instructions on how to perform this.
Technical Support Action Not applicable
Severity MAJOR
Description The HAL Monitor service failed to configure the DSP hardware and the service is shutting down.
Impact Applications may not have access to multimedia hardware resources. Consult the log for further details.
Recovery Action Contact Customer Support.
Technical Support Action Contact Product Support.
Severity MAJOR
Description An error occurred while processing a hardware detection after the insertion or removal of an MPC card.
Impact If running on an IPE platform, insertion or removal of an MPC card could not be detected reliably and a server reboot may be required to gain access to a newly inserted card.
Recovery Action Contact Customer Support.
Technical Support Action Contact Product Support.
Severity MAJOR
Description The HAL Monitor service cannot synchronize with other applications and the service is shutting down.
Impact If running on an IPE platform, insertion or removal of MPC cards cannot be detected without a server reboot. Consult the log for further details.
Recovery Action Contact Customer Support.
Technical Support Action Contact Product Support.
Severity MAJOR
Description A software error has occurred: the application did not acquire the HAL Configuration interface as required.
Impact The application may not have full access to the given hardware resources, and call processing may be impacted. Consult the log for further details.
Recovery Action Contact Customer Support.
Technical Support Action Contact Product Support.
Severity CRITICAL
Description Hardware detection has failed because of a low level driver timeout.
Impact The application cannot access the hardware resources, and call processing cannot take place. Consult the log for further details.
Recovery Action Contact Customer Support. Use the Devices applet in the Windows NT Control Panel and ensure all CallPilot device drivers are running. Try shutting down and subsequently rebooting the CallPilot server.
Technical Support Action Contact Product Support.
Severity MINOR
Description A HAL usage error has occurred in the application: an operation has been requested using an invalid device type.
Impact The application may not have full access to the given hardware resources, and call processing may be impacted. Consult the log for further details.
Recovery Action If call processing is impacted, contact Customer Support.
Technical Support Action Contact Product Support.
Severity INFO
Description The parameter has been adjusted by the DSP driver 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 CRITICAL
Description Hardware detection has failed because of an I/O control operation failed in low level driver.
Impact The application cannot access the hardware resources, and call processing cannot take place. 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 drivers directory have the correct version. This problem should not normally occur - someone might have replaced driver file[s]. A reinstall might be required.
Severity CRITICAL
Description Hardware detection has failed because the platform information cannot be read.
Impact The application cannot access the hardware resources, and call processing cannot take place. Consult the log for further details.
Recovery Action This is most likely caused by a configuration problem. The correct platform type information should be selected at installation time. Consult the CallPilot product documentation for instructions on how to perform this.
Technical Support Action This problem should not normally occur -- the registry may have been corrupted. A reinstall might be required.
Severity CRITICAL
Description Hardware detection has failed because the platform information cannot be read.
Impact The application cannot access the hardware resources, and call processing cannot take place. Consult the log for further details.
Recovery Action This is most likely caused by a configuration problem. The correct platform type information should be selected at installation time. Consult the CallPilot product documentation for instructions on how to perform this.
Technical Support Action This problem should not normally occur -- the registry may have been corrupted. A reinstall might be required.
Severity MINOR
Description The CallPilot platform information key could not be deleted from the registry.
Impact This problem must have occurred while un-installing the software. Consult the log for further details.
Recovery Action If errors occur during a subsequent install, contact Customer Support.
Technical Support Action This problem should not normally occur -- the registry may have been corrupted. A platform information key might have to be deleted manually.
Severity CRITICAL
Description Hardware detection has failed because the platform information does not match the actual hardware.
Impact This is most likely caused by a configuration problem. The correct platform type information should be selected at installation time. Consult the CallPilot product documentation for instructions on how to perform this.
Recovery Action This problem should not normally occur -- the registry may have been corrupted. A reinstall might be required.
Technical Support Action Not applicable
Severity CRITICAL
Description Hardware detection has failed because the platform information does not match the actual hardware.
Impact This is most likely caused by a configuration problem. The correct platform type information should be selected at installation time. Consult the CallPilot product documentation for instructions on how to perform this.
Recovery Action This problem should not normally occur -- the registry may have been corrupted. A reinstall might be required.
Technical Support Action Not applicable
Severity CRITICAL
Description Hardware detection has failed because the platform information does not match the actual hardware.
Impact This is most likely caused by a configuration problem. The correct platform type information should be selected at installation time. Consult the CallPilot product documentation for instructions on how to perform this.
Recovery Action This problem should not normally occur -- the registry may have been corrupted. A reinstall might be required.
Technical Support Action Not applicable
Severity CRITICAL
Description Hardware detection has failed because the platform information does not match the actual hardware.
Impact This is most likely caused by a configuration problem. The correct platform type information should be selected at installation time. Consult the CallPilot product documentation for instructions on how to perform this.
Recovery Action This problem should not normally occur -- the registry may have been corrupted. A reinstall might be required.
Technical Support Action Not applicable
Severity CRITICAL
Description Hardware detection has failed because the platform information does not match the actual hardware.
Impact This is most likely caused by a configuration problem. The correct platform type information should be selected at installation time. Consult the CallPilot product documentation for instructions on how to perform this.
Recovery Action This problem should not normally occur -- the registry may have been corrupted. A reinstall might be required.
Technical Support Action Not applicable
Severity CRITICAL
Description Hardware detection has failed because the platform information does not match the actual hardware.
Impact This is most likely caused by a configuration problem. The correct platform type information should be selected at installation time. Consult the CallPilot product documentation for instructions on how to perform this.
Recovery Action This problem should not normally occur -- the registry may have been corrupted. A reinstall might be required.
Technical Support Action Not applicable
Severity MINOR
Description A HAL usage error has occurred in the application: an operation has been requested using an invalid device.
Impact The application may not have full access to the given hardware resources, and call processing may be impacted. Consult the log for further details.
Recovery Action If call processing is impacted, contact Customer Support.
Technical Support Action Contact Product Support.
Severity INFO
Description The hardware detection module did not find any third party telephony boards.
Impact None.
Recovery Action Not applicable.
Technical Support Action Not applicable.
Severity CRITICAL
Description Hardware detection has failed because of an internal error: the device list cannot be updated.
Impact The application cannot access the hardware resources, and call processing cannot take place. Consult the log for further details.
Recovery Action Contact Customer Support. Use the Devices applet in the Windows NT Control Panel and ensure all CallPilot device drivers are running. Try shutting down and subsequently rebooting the CallPilot server.
Technical Support Action Contact Product Support.
Severity CRITICAL
Description Hardware detection has failed because of an internal error: the device list cannot be updated.
Impact The application cannot access the hardware resources, and call processing cannot take place. Consult the log for further details.
Recovery Action Contact Customer Support. Use the Devices applet in the Windows NT Control Panel and ensure all CallPilot device drivers are running. Try shutting down and subsequently rebooting the CallPilot server.
Technical Support Action Contact Product Support.
Severity CRITICAL
Description Hardware detection has failed because of an error encountered in Dialogic software.
Impact The application cannot access the hardware resources, and call processing cannot take place. Consult the log for further details.
Recovery Action Contact Customer Support. Verify that all Dialogic telephony boards are plugged in correctly and the Dialogic software has been installed and configured. Consult the Dialogic and CallPilot product documentation for instructions on how to perform this.
Technical Support Action Try shutting down and subsequently rebooting the CallPilot server. If the problem persists, a reinstall might be required.
Severity CRITICAL
Description Hardware detection has failed because of an error encountered in Dialogic software.
Impact The application cannot access the hardware resources, and call processing cannot take place. Consult the log for further details.
Recovery Action Contact Customer Support. Verify that all Dialogic telephony boards are plugged in correctly and the Dialogic software has been installed and configured. Consult the Dialogic and CallPilot product documentation for instructions on how to perform this.
Technical Support Action Try shutting down and subsequently rebooting the CallPilot server. If the problem persists, a reinstall might be required.
Severity CRITICAL
Description Hardware detection has failed because of a configuration error.
Impact The application cannot access the hardware resources, and call processing cannot take place. Consult the log for further details.
Recovery Action Contact Customer Support. If the problem is reported for a VTG library, verify that the VTG software has been installed and configured. Consult the VTG and CallPilot product documentation for instructions on how to perform this.
Technical Support Action Ensure that the specified file exists and is located in the local directory. This problem should not normally occur - someone might have deleted or moved the required file. A reinstall might be required.
Severity CRITICAL
Description Hardware detection has failed because of a configuration error.
Impact The application cannot access the hardware resources, and call processing cannot take place. Consult the log for further details.
Recovery Action Contact Customer Support. If the problem is reported for a VTG library, verify that the VTG software has been installed and configured. Consult the VTG and CallPilot product documentation for instructions on how to perform this.
Technical Support Action Ensure that the specified file exists and is located in the local directory. This problem should not normally occur - someone might have deleted or moved the required file. A reinstall might be required.
Severity MAJOR
Description The hardware detection module encountered an internal software error. Consult the CallPilot server's Windows NT Event Log for further details.
Impact The application may not have full access to the given hardware resources, and call processing may be impacted. Consult the log for further details.
Recovery Action Contact Customer Support.
Technical Support Action Contact Product Support.
Severity CRITICAL
Description Hardware detection has failed because of an error encountered in VTG software.
Impact The application cannot access the hardware resources, and call processing cannot take place. Consult the log for further details.
Recovery Action Contact Customer Support. Verify that all VTG telephony boards are plugged in correctly and the VTG software has been installed and configured. Consult the VTG and CallPilot product documentation for instructions on how to perform this.
Technical Support Action Try shutting down and subsequently rebooting the CallPilot server. If the problem persists, a reinstall might be required.
Severity MAJOR
Description A software error has occurred: the application has passed a bad parameter, and the request was failed by the detection module. Consult the CallPilot server's Windows NT Event Log for further details.
Impact The application may not have full access to the given hardware resources, and call processing may be impacted. Consult the log for further details.
Recovery Action Contact Customer Support.
Technical Support Action Contact Product Support.
Severity CRITICAL
Description An internal error occurred in the hardware detection module due to a low memory condition.
Impact The application may not have full access to the given hardware resources, and call processing may be impacted. Consult the log for further details.
Recovery Action Contact Customer Support.
Technical Support Action Contact Product Support.
Severity CRITICAL
Description An internal software error has occurred: an internal object has not been initialized and cannot be used.
Impact If the error occurred during setup, HAL has not been installed properly. If the error occurred after setup, the application may not have full access to the given hardware resources, and call processing may be impacted. Consult the log for further details.
Recovery Action Contact Customer Support.
Technical Support Action Contact Product Support.
Severity CRITICAL
Description An internal software error has occurred: a bad parameter has been passed internally.
Impact If the error occurred during setup, HAL has not been installed properly. If the error occurred after setup, the application may not have full access to the given hardware resources, and call processing may be impacted. Consult the log for further details.
Recovery Action Contact Customer Support.
Technical Support Action Contact Product Support.
Severity CRITICAL
Description An internal software error has occurred: an exception has been trapped.
Impact If the error occurred during setup, HAL has not been installed properly. If the error occurred after setup, the application may not have full access to the given hardware resources, and call processing may be impacted. Consult the log for further details.
Recovery Action Contact Customer Support.
Technical Support Action Contact Product Support.
Severity CRITICAL
Description An internal software error has occurred due to a software bug.
Impact If the error occurred during setup, HAL has not been installed properly. If the error occurred after setup, the application may not have full access to the given hardware resources, and call processing may be impacted. Consult the log for further details.
Recovery Action Contact Customer Support.
Technical Support Action Contact Product Support.
Severity CRITICAL
Description Hardware configuration has failed due to a registry access error.
Impact If the error occurred during setup, HAL has not been installed properly. If the error occurred after setup, the application may not have full access to the given hardware resources, and call processing may be impacted. Consult the log for further details.
Recovery Action Contact Customer Support.
Technical Support Action Contact Product Support.
Severity CRITICAL
Description Hardware configuration has failed due to a registry access error.
Impact If the error occurred during setup, HAL has not been installed properly. If the error occurred after setup, the application may not have full access to the given hardware resources, and call processing may be impacted. Consult the log for further details.
Recovery Action Contact Customer Support.
Technical Support Action Contact Product Support.
Severity CRITICAL
Description Hardware configuration has failed due to a registry access error.
Impact If the error occurred during setup, HAL has not been installed properly. If the error occurred after setup, the application may not have full access to the given hardware resources, and call processing may be impacted. Consult the log for further details.
Recovery Action Contact Customer Support.
Technical Support Action Contact Product Support.
Severity CRITICAL
Description Hardware configuration has failed due to a registry access error.
Impact If the error occurred during setup, HAL has not been installed properly. If the error occurred after setup, the application may not have full access to the given hardware resources, and call processing may be impacted. Consult the log for further details.
Recovery Action Contact Customer Support.
Technical Support Action Contact Product Support.
Severity CRITICAL
Description Hardware configuration has failed due to a registry access error.
Impact If the error occurred during setup, HAL has not been installed properly. If the error occurred after setup, the application may not have full access to the given hardware resources, and call processing may be impacted. Consult the log for further details.
Recovery Action Contact Customer Support.
Technical Support Action Contact Product Support.
Severity CRITICAL
Description Hardware configuration has failed due to a registry access error.
Impact If the error occurred during setup, HAL has not been installed properly. If the error occurred after setup, the application may not have full access to the given hardware resources, and call processing may be impacted. Consult the log for further details.
Recovery Action Contact Customer Support.
Technical Support Action Contact Product Support.
Severity CRITICAL
Description Hardware configuration has failed due to a registry access error.
Impact If the error occurred during setup, HAL has not been installed properly. If the error occurred after setup, the application may not have full access to the given hardware resources, and call processing may be impacted. Consult the log for further details.
Recovery Action Contact Customer Support.
Technical Support Action Contact Product Support.
Severity CRITICAL
Description Hardware configuration has failed due to a registry access error.
Impact If the error occurred during setup, HAL has not been installed properly. If the error occurred after setup, the application may not have full access to the given hardware resources, and call processing may be impacted. Consult the log for further details.
Recovery Action Contact Customer Support.
Technical Support Action Contact Product Support.
Severity CRITICAL
Description Hardware configuration has failed due to a registry access error.
Impact If the error occurred during setup, HAL has not been installed properly. If the error occurred after setup, the application may not have full access to the given hardware resources, and call processing may be impacted. Consult the log for further details.
Recovery Action Contact Customer Support.
Technical Support Action Contact Product Support.
Severity CRITICAL
Description Hardware configuration has failed due to a registry access error.
Impact If the error occurred during setup, HAL has not been installed properly. If the error occurred after setup, the application may not have full access to the given hardware resources, and call processing may be impacted. Consult the log for further details.
Recovery Action Contact Customer Support.
Technical Support Action Contact Product Support.
Severity CRITICAL
Description Hardware configuration has failed due to a registry access error.
Impact If the error occurred during setup, HAL has not been installed properly. If the error occurred after setup, the application may not have full access to the given hardware resources, and call processing may be impacted. Consult the log for further details.
Recovery Action Contact Customer Support.
Technical Support Action Contact Product Support.
Severity CRITICAL
Description An internal software error has occurred: an internal object has not been initialized and cannot be used.
Impact This error must have occurred during setup, therefore HAL has not been installed properly. Consult the log for further details.
Recovery Action Contact Customer Support.
Technical Support Action Contact Product Support.
Severity CRITICAL
Description An internal software error has occurred due to a software bug.
Impact This error must have occurred during setup, therefore HAL has not been installed properly. Consult the log for further details.
Recovery Action Contact Customer Support.
Technical Support Action Contact Product Support.
Severity CRITICAL
Description An internal software error has occurred: a bad parameter has been passed internally.
Impact This error must have occurred during setup, therefore HAL has not been installed properly. Consult the log for further details.
Recovery Action Contact Customer Support.
Technical Support Action Contact Product Support.
Severity CRITICAL
Description Hardware configuration has failed due to a resource access error.
Impact This error must have occurred during setup, therefore HAL has not been installed properly. Consult the log for further details.
Recovery Action Contact Customer Support.
Technical Support Action Contact Product Support.
Severity CRITICAL
Description Hardware configuration has failed due to a resource access error.
Impact This error must have occurred during setup, therefore HAL has not been installed properly. Consult the log for further details.
Recovery Action Contact Customer Support.
Technical Support Action Contact Product Support.
Severity CRITICAL
Description Hardware configuration has failed due to a resource access error.
Impact This error must have occurred during setup, therefore HAL has not been installed properly. Consult the log for further details.
Recovery Action Contact Customer Support.
Technical Support Action Contact Product Support.
Severity CRITICAL
Description Hardware configuration has failed due to a resource access error.
Impact This error must have occurred during setup, therefore HAL has not been installed properly. Consult the log for further details.
Recovery Action Contact Customer Support.
Technical Support Action Contact Product Support.
Severity INFO
Description The hardware configuration module did not find a service previously installed and will attempt to install it now.
Impact None.
Recovery Action Not applicable.
Technical Support Action Not applicable.
Severity CRITICAL
Description Hardware configuration has failed due to a resource access error.
Impact This error must have occurred during setup, therefore HAL has not been installed properly. Consult the log for further details.
Recovery Action Contact Customer Support.
Technical Support Action Contact Product Support.
Severity CRITICAL
Description Hardware configuration has failed due to a platform information access error.
Impact This error must have occurred during setup, therefore HAL has not been installed properly. Consult the log for further details.
Recovery Action This is most likely caused by a configuration problem. The correct platform type information should be selected at installation time. Consult the CallPilot product documentation for instructions on how to perform this.
Technical Support Action Not applicable
Severity CRITICAL
Description Hardware configuration has failed due to a platform information access error.
Impact This error must have occurred during setup, therefore HAL has not been installed properly. Consult the log for further details.
Recovery Action This is most likely caused by a configuration problem. The correct platform type information should be selected at installation time. Consult the CallPilot product documentation for instructions on how to perform this.
Technical Support Action Not applicable
Severity CRITICAL
Description Hardware configuration has failed due to a resource access error.
Impact This error must have occurred during setup, therefore HAL has not been installed properly. Consult the log for further details.
Recovery Action Contact Customer Support.
Technical Support Action Contact Product Support.
Severity CRITICAL
Description Hardware configuration has failed due to a resource access error.
Impact This error must have occurred during setup, therefore HAL has not been installed properly. Consult the log for further details.
Recovery Action Contact Customer Support.
Technical Support Action Contact Product Support.
Severity CRITICAL
Description Hardware configuration has failed due to a resource access error.
Impact This error must have occurred during setup, therefore HAL has not been installed properly. Consult the log for further details.
Recovery Action Contact Customer Support.
Technical Support Action Contact Product Support.
Severity CRITICAL
Description Hardware configuration has failed due to a resource access error.
Impact This error must have occurred during setup, therefore HAL has not been installed properly. Consult the log for further details.
Recovery Action Contact Customer Support.
Technical Support Action Contact Product Support.
Severity INFO
Description The hardware configuration module did not find a service previously installed and will attempt to install it now.
Impact None.
Recovery Action Not applicable.
Technical Support Action Not applicable.
Severity CRITICAL
Description Hardware configuration has failed due to a resource access error.
Impact This error must have occurred during setup, therefore HAL has not been installed properly. Consult the log for further details.
Recovery Action Contact Customer Support.
Technical Support Action Contact Product Support.
Severity CRITICAL
Description Hardware configuration has failed due to an internal error.
Impact This error must have occurred during setup, therefore HAL has not been installed properly. Consult the log for further details.
Recovery Action Contact Customer Support.
Technical Support Action Contact Product Support.
Severity CRITICAL
Description Hardware configuration has failed due to a resource access error.
Impact This error must have occurred during setup, therefore HAL has not been installed properly. Consult the log for further details.
Recovery Action Contact Customer Support.
Technical Support Action Contact Product Support.
Severity MINOR
Description The hardware configuration module did not find any boards with timeswtich devices to configure.
Impact This situation can happen if no multimedia hardware is detected, therefore there is no impact on call processing.
Recovery Action Not applicable.
Technical Support Action Not applicable.
Severity MINOR
Description The hardware configuration module did not find any boards with a valid telephony interface to configure.
Impact This message may indicate a hardware failure; a system without telephony interfaces cannot process any calls. Consult the log for further details.
Recovery Action Examine the event log for any diagnostic failures. Shutdown and reboot the server and re-run the timeswitch diagnostics. If the error persists, replace the IPE/carrier board.
Technical Support Action Not applicable
Severity CRITICAL
Description Hardware detection has failed because of a configuration error.
Impact The application cannot access the hardware resources, and call processing cannot take place. Consult the log for further details.
Recovery Action Use the configuration tools to re-configure the media bus for the VTG boards. Consult the VTG and CallPilot product documentation for instructions on how to perform this.
Technical Support Action Not applicable
Severity CRITICAL
Description Hardware detection has failed because of a configuration error: the speed for the media bus set for VTG boards does not match the hardware capabilities of the MPB board[s] installed.
Impact The application cannot access the hardware resources, and call processing cannot take place. Consult the log for further details.
Recovery Action Use the configuration tools to re-configure the media bus for the VTG boards. Consult the VTG and CallPilot product documentation for instructions on how to perform this.
Technical Support Action Not applicable
Severity MAJOR
Description A HAL usage error has occurred in the application: the application has already registered for hardware notification changes.
Impact If this error occurs on an IPE platform, insertion and removal of MPC cards may not be detected without a reboot. Consult the log for further details.
Recovery Action Contact Customer Support.
Technical Support Action Contact Product Support.
Severity MINOR
Description An internal software error has occurred: an un-authorized request has been made into the HAL detection module.
Impact If this error occurs on an IPE platform, insertion and removal of MPC cards may be impacted. Consult the log for further details.
Recovery Action Contact Customer Support.
Technical Support Action Contact Product Support.
Severity MAJOR
Description An internal software error has occurred: a synchronization object could not be created in the HAL detection module.
Impact If running on an IPE platform, insertion or removal of MPC cards cannot be detected without a server reboot. This is usually an internal Windows NT fault and the system may be severely impacted.
Recovery Action Contact Customer Support.
Technical Support Action Contact Product Support.
Severity MAJOR
Description An internal software error has occurred: a synchronization object could not be created in the HAL detection module.
Impact If running on an IPE platform, insertion or removal of MPC cards cannot be detected without a server reboot. This is usually an internal Windows NT fault and the system may be severely impacted.
Recovery Action Contact Customer Support.
Technical Support Action Contact Product Support.
Severity MAJOR
Description An internal software error has occurred: a synchronization object could not be created in the HAL detection module.
Impact If running on an IPE platform, insertion or removal of MPC cards cannot be detected without a server reboot. This is usually an internal Windows NT fault and the system may be severely impacted.
Recovery Action Contact Customer Support.
Technical Support Action Contact Product Support.
Severity MAJOR
Description An internal software error has occurred: a synchronization object could not be destroyed in the HAL detection module.
Impact If running on an IPE platform, insertion or removal of MPC cards cannot be detected without a server reboot. This is usually an internal Windows NT fault and the system may be severely impacted.
Recovery Action Contact Customer Support.
Technical Support Action Contact Product Support.
Severity CRITICAL
Description Hardware detection has failed because it cannot use a low level driver library.
Impact The application cannot access the hardware resources, and call processing cannot take place. Consult the log for further details.
Recovery Action Contact Customer Support.
Technical Support Action Ensure that the specified file exists and is located in the local directory. This problem should not normally occur - someone might have deleted or moved the required file. A reinstall might be required.
Severity MAJOR
Description An MPB board has failed to configure and cannot be used.
Impact The application cannot access the hardware resources on the failed board, and call processing will be impacted by running at reduced capacity. Consult the log for further details.
Recovery Action Shutdown and reboot the server. If the error persists, replace the MPB carrier board.
Technical Support Action Not applicable
Severity MAJOR
Description An internal exception has been trapped by the HAL Detection module while configuring a carrier board, and the board cannot be used.
Impact The application cannot access the hardware resources on the failed board, and call processing will be impacted by running at reduced capacity. Consult the log for further details.
Recovery Action Contact Customer Support.
Technical Support Action Contact Product Support.
Severity MAJOR
Description All DSP devices on one MPB board have failed to configure and the entire board cannot be used.
Impact The application cannot access the failed DSP resources, and call processing will be impacted by running at reduced capacity. Consult the log for further details.
Recovery Action Shutdown and reboot the server. If the error persists, replace the MPB carrier board.
Technical Support Action Not applicable
Severity MINOR
Description The DSP device hardware has failed to configure and the DSP resource cannot be used.
Impact The application cannot access the failed DSP resources, and call processing will be impacted by running at reduced capacity. Consult the log for further details.
Recovery Action Shutdown and reboot the server. If the error persists, replace the MPB carrier board.
Technical Support Action Not applicable
Severity MAJOR
Description A software error has occurred: the application did not acquire the HAL Programmer interface as required.
Impact DSP Flash programming operations fail. 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: an operation has been requested using an invalid device type.
Impact DSP Flash programming operations fail. Consult the log for further details.
Recovery Action Contact Customer Support.
Technical Support Action Contact Product Support.
Severity INFO
Description A DSP programming operation has been cancelled by the application. Consult the log for further details.
Impact None.
Recovery Action Not applicable.
Technical Support Action Not applicable.
Severity MAJOR
Description A DSP programming operation has failed because of a software error: an internal object has not been initialized.
Impact DSP Flash programming operations fail. Consult the log for further details.
Recovery Action Contact Customer Support.
Technical Support Action Contact Product Support.
Severity MAJOR
Description An internal error occurred in the programmer driver due to a low memory condition.
Impact DSP Flash programming operations fail. Consult the log for further details.
Recovery Action Contact Customer Support.
Technical Support Action Contact Product Support.
Severity MAJOR
Description A software error has occurred: the application has passed a bad parameter, and the request was failed by the programmer module. Consult the CallPilot server's Windows NT Event Log for further details.
Impact DSP Flash programming operations fail. Consult the log for further details.
Recovery Action Contact Customer Support.
Technical Support Action Contact Product Support.
Severity MAJOR
Description A DSP programming operation has failed because of a software error: an internal object has already been enabled.
Impact DSP Flash programming operations fail. Consult the log for further details.
Recovery Action Contact Customer Support.
Technical Support Action Contact Product Support.
Severity MAJOR
Description A DSP programming operation has failed because of a software error: an internal object has not been enabled.
Impact DSP Flash programming operations fail. Consult the log for further details.
Recovery Action Contact Customer Support.
Technical Support Action Contact Product Support.
Severity MAJOR
Description A DSP programming operation has failed because of an I/O control operation failed in low level driver.
Impact DSP Flash programming operations fail. Consult the log for further details.
Recovery Action Contact Customer Support.
Technical Support Action Contact Product Support.
Severity MAJOR
Description A DSP programming operation has failed because of a file access error on the programmer profile file.
Impact DSP Flash programming operations fail. Consult the log for further details.
Recovery Action Contact Customer Support.
Technical Support Action Contact Product Support.
Severity MAJOR
Description A DSP programming operation has failed because of a file access error on the programmer profile file.
Impact DSP Flash programming operations fail. Consult the log for further details.
Recovery Action Contact Customer Support.
Technical Support Action Ensure that the specified file exists and is located 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 DSP programming operation has failed because of a file access error on the programmer profile file.
Impact DSP Flash programming operations fail. Consult the log for further details.
Recovery Action Contact Customer Support.
Technical Support Action Ensure that the specified file exists and is located 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 DSP programming operation has failed because of a file access error on the programmer profile file.
Impact DSP Flash programming operations fail. Consult the log for further details.
Recovery Action Contact Customer Support.
Technical Support Action Ensure that the specified file exists and is located 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 DSP programming operation has failed because of a file access error on the programmer profile file.
Impact DSP Flash programming operations fail. Consult the log for further details.
Recovery Action Contact Customer Support.
Technical Support Action Ensure that the specified file exists and is located 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 DSP programming operation has failed because of a file access error on the programmer profile file.
Impact DSP Flash programming operations fail. Consult the log for further details.
Recovery Action Contact Customer Support.
Technical Support Action Ensure that the specified file exists and is located 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 DSP programming operation has failed because of a file access error on the programmer profile file.
Impact DSP Flash programming operations fail. Consult the log for further details.
Recovery Action Contact Customer Support.
Technical Support Action Ensure that the specified file exists and is located in the DSP hardware directory. This problem should not normally occur - someone might have corrupted the required file. A reinstall might be required.
Severity MAJOR
Description A DSP programming operation has failed because of a device access error.
Impact DSP Flash programming operations fail. Consult the log for further details.
Recovery Action Use the Devices applet in the Windows NT Control Panel and ensure the CallPilot DSP Driver is running. Consult the log for further details.
Technical Support Action Not applicable
Severity MAJOR
Description A DSP programming operation has failed because of a device access error.
Impact DSP Flash programming operations fail. 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: an operation has been requested using an invalid device type.
Impact DSP Flash programming operations fail. Consult the log for further details.
Recovery Action Contact Customer Support.
Technical Support Action Contact Product Support.
Severity MAJOR
Description A DSP programming operation has failed because the contents do not match the expected pattern.
Impact DSP Flash programming operations fail. Consult the log for further details.
Recovery Action Retry the DSP programming operation. If the error re-occurs, the DSP should be taken out of service. If the DSP is an MPC card, the MPC card needs to be replaced. If the DSP is embedded, MPB carrier board needs to be replaced.
Technical Support Action Not applicable
Severity INFO
Description An empty section has been found in the Flash directory of a DSP device.
Impact None.
Recovery Action Not applicable.
Technical Support Action Not applicable.
Severity MAJOR
Description A DSP programming operation has failed because of a hardware error: cannot erase the Flash block.
Impact DSP Flash programming operations fail. Consult the log for further details.
Recovery Action Retry the DSP programming operation. If the error re-occurs, the DSP should be taken out of service. If the DSP is an MPC card, the MPC card needs to be replaced. If the DSP is embedded, MPB carrier board needs to be replaced.
Technical Support Action Not applicable
Severity MAJOR
Description A DSP programming operation has failed because of a hardware error: cannot write into the Flash block.
Impact DSP Flash programming operations fail. Consult the log for further details.
Recovery Action Retry the DSP programming operation. If the error re-occurs, the DSP should be taken out of service. If the DSP is an MPC card, the MPC card needs to be replaced. If the DSP is embedded, MPB carrier board needs to be replaced.
Technical Support Action Not applicable
Severity MAJOR
Description A DSP programming operation has failed because of a hardware error: cannot erase the Flash block.
Impact DSP Flash programming operations fail. Consult the log for further details.
Recovery Action Retry the DSP programming operation. If the error re-occurs, the DSP should be taken out of service. If the DSP is an MPC card, the MPC card needs to be replaced. If the DSP is embedded, MPB carrier board needs to be replaced.
Technical Support Action Not applicable
Severity MAJOR
Description A DSP programming operation has failed because of a hardware error: cannot erase the Flash block.
Impact DSP Flash programming operations fail. Consult the log for further details.
Recovery Action Retry the DSP programming operation. If the error re-occurs, the DSP should be taken out of service. If the DSP is an MPC card, the MPC card needs to be replaced. If the DSP is embedded, MPB carrier board needs to be replaced.
Technical Support Action Not applicable
Severity MAJOR
Description A DSP programming operation has failed because no more directory entries can be added.
Impact DSP Flash programming operations fail. Consult the log for further details.
Recovery Action Contact Customer Support.
Technical Support Action Contact Product Support.
Severity MAJOR
Description A DSP programming operation has failed because a DSP load file has been corrupted.
Impact DSP Flash programming operations fail. Consult the log for further details.
Recovery Action Contact Customer Support.
Technical Support Action Ensure that all DSP load files exist in the DSP hardware directory and that they 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 A DSP programming operation has failed because a DSP load file has been corrupted.
Impact DSP Flash programming operations fail. Consult the log for further details.
Recovery Action Contact Customer Support.
Technical Support Action Ensure that all DSP load files exist in the DSP hardware directory and that they 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 A DSP programming operation has failed because a DSP load file has been corrupted.
Impact DSP Flash programming operations fail. Consult the log for further details.
Recovery Action Contact Customer Support.
Technical Support Action Ensure that all DSP load files exist in the DSP hardware directory and that they 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 A DSP programming operation has failed because a DSP load file has been corrupted.
Impact DSP Flash programming operations fail. Consult the log for further details.
Recovery Action Contact Customer Support.
Technical Support Action Ensure that all DSP load files exist in the DSP hardware directory and that they 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 A DSP programming operation has failed because a DSP load file has been corrupted.
Impact DSP Flash programming operations fail. Consult the log for further details.
Recovery Action Contact Customer Support.
Technical Support Action Ensure that all DSP load files exist in the DSP hardware directory and that they have the correct version. This problem should not normally occur - someone might have corrupted such a file. A reinstall might be required.
Severity INFO
Description A previous directory entry has been found in the Flash section of a DSP device.
Impact None.
Recovery Action Not applicable.
Technical Support Action Not applicable.
Severity INFO
Description The directory is full in the Flash section of a DSP device.
Impact None.
Recovery Action Not applicable.
Technical Support Action Not applicable.
Severity INFO
Description A DSP load cannot be located in the Programmer's profile file.
Impact None.
Recovery Action Not applicable.
Technical Support Action Not applicable.
Severity MAJOR
Description A DSP programming operation has failed because a DSP load file has been corrupted.
Impact DSP Flash programming operations fail. Consult the log for further details.
Recovery Action Contact Customer Support.
Technical Support Action Ensure that all DSP load files exist in the DSP hardware directory and that they 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 A DSP programming operation has failed because a DSP load file has been corrupted.
Impact DSP Flash programming operations fail. Consult the log for further details.
Recovery Action Contact Customer Support.
Technical Support Action Ensure that all DSP load files exist in the DSP hardware directory and that they 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 A DSP programming operation has failed because of a software error: an exception has been trapped from the application.
Impact DSP Flash programming operations fail. Consult the log for further details.
Recovery Action Contact Customer Support.
Technical Support Action Contact Product Support.
Severity MAJOR
Description A DSP programming operation has failed because of a software error: an internal exception has been trapped.
Impact DSP Flash programming operations fail. Consult the log for further details.
Recovery Action Contact Customer Support.
Technical Support Action Contact Product Support.
Severity MAJOR
Description A DSP programming operation has failed because of a software error: an internal exception has been trapped.
Impact DSP Flash programming operations fail. Consult the log for further details.
Recovery Action Contact Customer Support.
Technical Support Action Contact Product Support.
Severity INFO
Description An older DSP load version has been found and a new load has been programmed.
Impact None.
Recovery Action Not applicable.
Technical Support Action Not applicable.
Severity INFO
Description An older DSP load version has been found and a new load has been programmed.
Impact None.
Recovery Action Not applicable.
Technical Support Action Not applicable.
Severity INFO
Description An older DSP load version has been found and a new load has been programmed.
Impact None.
Recovery Action Not applicable.
Technical Support Action Not applicable.
Severity INFO
Description An older DSP load version has been found and a new load has been programmed.
Impact None.
Recovery Action Not applicable.
Technical Support Action Not applicable.
Severity INFO
Description An older DSP load version has been found and a new load has been programmed.
Impact None.
Recovery Action Not applicable.
Technical Support Action Not applicable.
Severity INFO
Description An older DSP load version has been found and a new load has been programmed.
Impact None.
Recovery Action Not applicable.
Technical Support Action Not applicable.
Severity INFO
Description An older DSP load version has been found and a new load has been programmed.
Impact None.
Recovery Action Not applicable.
Technical Support Action Not applicable.
Severity INFO
Description An older DSP load version has been found and a new load has been programmed.
Impact None.
Recovery Action Not applicable.
Technical Support Action Not applicable.
Severity INFO
Description The DSP load has the same version as the new one, and the programming operation has been by-passed.
Impact None.
Recovery Action Not applicable.
Technical Support Action Not applicable.
Severity MAJOR
Description A DSP programming operation has failed because of a software error: an internal exception has been trapped while accessing the header.
Impact DSP Flash programming operations fail. Consult the log for further details.
Recovery Action Contact Customer Support.
Technical Support Action Contact Product Support.
Severity MAJOR
Description A DSP programming operation has failed because of a software error: an internal exception has been trapped while accessing the header.
Impact DSP Flash programming operations fail. Consult the log for further details.
Recovery Action Contact Customer Support.
Technical Support Action Contact Product Support.