Severity MAJOR
Description A DSP programming operation has failed because of an internal software 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 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 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 A DSP programming operation has failed because of an internal software bug.
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: a DSP device object has not been found.
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 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, or the file may be corrupt. 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, or the file may be corrupt. A reinstall might be required.
Severity MAJOR
Description A DSP programming operation has failed because of a file access error on a DSP load 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, or the file may be corrupt. A reinstall might be required.
Severity MAJOR
Description A DSP programming operation has failed because of a file access error on a DSP load 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, or the file may be corrupt. A reinstall might be required.
Severity MAJOR
Description A DSP programming operation has failed because of a registry access error.
Impact DSP Flash programming operations fail. Consult the log for further details.
Recovery Action Contact Customer Support.
Technical Support Action Ensure that the Nortel key in the Windows NT registry can be read and has valid data. This problem should not normally occur - someone might have deleted or moved the required registry keys, or the registry file may be corrupt. 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, or the file may be corrupt. A reinstall might be required.
Severity MAJOR
Description FPGA hardware on the MPB board cannot be configured due to a software error in a low level driver.
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 FPGA hardware on the MPB board cannot be configured because the firmware file cannot be accessed.
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 Ensure that the specified file exists and is located in the board hardware directory. This problem should not normally occur - someone might have deleted or moved the required file, or the registry may be corrupt. A reinstall might be required.
Severity MAJOR
Description FPGA hardware on the MPB board cannot be configured because the firmware file cannot be accessed.
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 Ensure that the specified file exists and is located in the board hardware directory. This problem should not normally occur - someone might have deleted or moved the required file, or the registry may be corrupt. A reinstall might be required.
Severity MAJOR
Description FPGA hardware on the MPB board cannot be configured because the firmware file cannot be accessed.
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 Ensure that the board firmware files have the correct version and are located in the board hardware directory. This problem should not normally occur - someone might have corrupted the required file. A reinstall might be required.
Severity MAJOR
Description FPGA hardware on the MPB board cannot be configured because of a hardware failure.
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 FPGA hardware on the MPB board cannot be configured due to an memory access exception trapped in a low level driver.
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 Contact Product Support.
Severity MAJOR
Description FPGA hardware on the MPB board cannot be configured due to an memory access exception trapped in a low level driver.
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 Contact Product Support.
Severity MAJOR
Description FPGA hardware on the MPB board cannot be configured due to an memory access exception trapped in a low level driver.
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 Contact Product Support.
Severity MAJOR
Description FPGA hardware on the MPB board cannot be configured due to an memory access exception trapped in a low level driver.
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 Contact Product Support.
Severity MAJOR
Description FPGA hardware on the MPB board cannot be configured because of a hardware failure.
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 FPGA hardware on the MPB board cannot be configured because of a hardware failure.
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 A DSP programming operation has failed because of a software error: internal worker threads cannot be started.
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: internal synchronization failed.
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 The DSP device hardware has failed to configure during server startup and DSP resources on the MPB carrier 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 Ensure that the local disk drives are not full. Contact Customer Support.
Technical Support Action Contact Product Support.
Severity MINOR
Description The DSP device hardware has failed to configure during server startup and DSP resources on the MPB carrier 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 This error can be ignored if it occurs immediately after installing CallPilot and before configuring the system.
If the error occurs after the DSP have been programmed at least once and the system has been running, re-run the CallPilot configuration to re-program the DSP -- this action will re-create the DSP cache file and the error should not occur anymore after the next reboot.
Technical Support Action Not applicable
Severity MAJOR
Description The DSP device hardware has failed to configure during server startup and DSP resources on the MPB carrier 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 Ensure that the local disk drives are not full. Contact Customer Support.
Technical Support Action Contact Product Support.
Severity MAJOR
Description The DSP device hardware has failed to configure during server startup and DSP resources on the MPB carrier 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 The file may be corrupt; re-run the CallPilot configuration to re-program the DSP -- this action will re-create the DSP cache file and the error should not occur anymore after the next reboot. If the error persists, contact your technical support organization.
Technical Support Action Contact Product Support.
Severity MAJOR
Description The DSP device hardware has failed to configure during server startup and DSP resources on the MPB carrier 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 Ensure that the local disk drives are not full. Contact Customer Support.
Technical Support Action Contact Product Support.
Severity MAJOR
Description The HOST-To-DSP Data/Message Queue is full. The data message to be copied does not fit in the queue.
Impact This is most likely a DSP usage error by Middleware. Consult the log for further details.
Recovery Action Contact Customer Support. If call processing is being adversely affected and the problem persists, try shutting down and subsequently rebooting the CallPilot server. WARNING: This action will affect call processing.
Technical Support Action Contact Product Support.
Severity MAJOR
Description The DSP-To-HOST Data/Message/Event Queue us empty. There is nothing to read from the queue.
Impact This is most likely a DSP usage error by Middleware. Consult the log for further details.
Recovery Action Contact Customer Support. If call processing is being adversely affected and the problem persists, try shutting down and subsequently rebooting the CallPilot server. WARNING: This action will affect call processing.
Technical Support Action Contact Product Support.
Severity MAJOR
Description There are no available records in the block directory or the block directory is full.
Impact This is most likely a DSP usage error by Middleware. Consult the log for further details.
Recovery Action Contact Customer Support. If call processing is being adversely affected and the problem persists, try shutting down and subsequently rebooting the CallPilot server. WARNING: This action will affect call processing.
Technical Support Action Contact Product Support.
Severity MAJOR
Description Invalid Message. A zero address offset indicates an invalid message.
Impact This is most likely a DSP usage error by Middleware. Consult the log for further details.
Recovery Action Contact Customer Support. If call processing is being adversely affected and the problem persists, try shutting down and subsequently rebooting the CallPilot server. WARNING: This action will affect call processing.
Technical Support Action Contact Product Support.
Severity MAJOR
Description The message length was greater than the maximum size for the HOST-To-DSP message queue.
Impact This is most likely a DSP usage error by Middleware. Consult the log for further details.
Recovery Action Contact Customer Support. If call processing is being adversely affected and the problem persists, try shutting down and subsequently rebooting the CallPilot server. WARNING: This action will affect call processing.
Technical Support Action Contact Product Support.
Severity MAJOR
Description There is not enough space in the block area.
Impact This is most likely a DSP usage error by Middleware. Consult the log for further details.
Recovery Action Contact Customer Support. If call processing is being adversely affected and the problem persists, try shutting down and subsequently rebooting the CallPilot server. WARNING: This action will affect call processing.
Technical Support Action Contact Product Support.
Severity MAJOR
Description The number of records is greater than that allowable.
Impact This is most likely a DSP usage error by Middleware. Consult the log for further details.
Recovery Action Contact Customer Support. If call processing is being adversely affected and the problem persists, try shutting down and subsequently rebooting the CallPilot server. WARNING: This action will affect call processing.
Technical Support Action Contact Product Support.
Severity MAJOR
Description An error has occurred while querying device.
Impact This is an internal error and call processing may be affected. Consult the log for further details.
Recovery Action Contact Customer Support.
Technical Support Action Contact Product Support.
Severity MAJOR
Description A handle to the DSP could not be opened.
Impact This is an internal error and call processing may be affected. Consult the log for further details.
Recovery Action Contact Customer Support.
Technical Support Action Contact Product Support.
Severity MAJOR
Description A handle to the DSP could not be closed.
Impact This is an internal error and call processing may be affected. Consult the log for further details.
Recovery Action Contact Customer Support.
Technical Support Action Contact Product Support.
Severity MAJOR
Description There was an error accessing the DSP.
Impact This is an internal error and call processing may be affected. Consult the log for further details.
Recovery Action Contact Customer Support.
Technical Support Action Contact Product Support.
Severity MAJOR
Description The DSP is either not present on the system or is off.
Impact This is most likely a DSP usage error by Middleware. Consult the log for further details.
Recovery Action Contact Customer Support. If call processing is being adversely affected and the problem persists, try shutting down and subsequently rebooting the CallPilot server. WARNING: This action will affect call processing.
Technical Support Action Contact Product Support.
Severity MAJOR
Description The DSP has not been initialized.
Impact This is most likely a DSP usage error by Middleware. Consult the log for further details.
Recovery Action Contact Customer Support. If call processing is being adversely affected and the problem persists, try shutting down and subsequently rebooting the CallPilot server. WARNING: This action will affect call processing.
Technical Support Action Contact Product Support.
Severity MAJOR
Description The input COFF file could not be found or could not be opened.
Impact This is most likely a DSP usage error by Middleware. Consult the log for further details.
Recovery Action Contact Customer Support. If call processing is being adversely affected and the problem persists, try shutting down and subsequently rebooting the CallPilot server. WARNING: This action will affect call processing.
Technical Support Action Contact Product Support.
Severity MAJOR
Description There was an error trying to read either the header or the data of the input COFF file.
Impact DSP can not be used, as a result no call processing can take place. The system has been severely impacted.
Recovery Action Contact Customer Support.
Technical Support Action Ensure the required DSP load files exist and are 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 There is not enough memory to allocate space for an intermediate buffer.
Impact This is an internal error and call processing may be affected. Consult the log for further details.
Recovery Action Contact Customer Support.
Technical Support Action Contact Product Support.
Severity MAJOR
Description The specified Load Option Flag is invalid.
Impact This is most likely a DSP usage error by Middleware. Consult the log for further details.
Recovery Action Contact Customer Support. If call processing is being adversely affected and the problem persists, try shutting down and subsequently rebooting the CallPilot server. WARNING: This action will affect call processing.
Technical Support Action Contact Product Support.
Severity MAJOR
Description The COFF file specified is not a valid COFF file as per TI specifications.
Impact DSP can not be used, as a result no call processing can take place. The system has been severely impacted.
Recovery Action Contact Customer Support.
Technical Support Action Ensure the required DSP load files exist and are 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 The handle that was passed in was NULL.
Impact This is most likely a DSP usage error by Middleware. Consult the log for further details.
Recovery Action Contact Customer Support. If call processing is being adversely affected and the problem persists, try shutting down and subsequently rebooting the CallPilot server. WARNING: This action will affect call processing.
Technical Support Action Contact Product Support.
Severity MAJOR
Description The device handle was invalid.
Impact This is most likely a DSP usage error by Middleware. Consult the log for further details.
Recovery Action Contact Customer Support. If call processing is being adversely affected and the problem persists, try shutting down and subsequently rebooting the CallPilot server. WARNING: This action will affect call processing.
Technical Support Action Contact Product Support.
Severity MAJOR
Description The device name was invalid.
Impact This is an internal error and call processing may be affected. Consult the log for further details.
Recovery Action Contact Customer Support.
Technical Support Action Contact Product Support.
Severity MAJOR
Description The device was busy.
Impact This is most likely a DSP usage error by Middleware. Consult the log for further details.
Recovery Action Contact Customer Support. If call processing is being adversely affected and the problem persists, try shutting down and subsequently rebooting the CallPilot server. WARNING: This action will affect call processing.
Technical Support Action Contact Product Support.
Severity MAJOR
Description Software error: invalid input parameter.
Impact This is most likely a DSP usage error by Middleware. Consult the log for further details.
Recovery Action Contact Customer Support. If call processing is being adversely affected and the problem persists, try shutting down and subsequently rebooting the CallPilot server. WARNING: This action will affect call processing.
Technical Support Action Contact Product Support.
Severity MAJOR
Description A software error has occurred: the application did not acquire the DSP driver interface as required. 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 The DSP 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 bad DSP device ID has been passed by the application to the DSP 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 The DSP 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 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 MAJOR
Description A software error has occurred: the application did not acquire the HAL Timeswitch driver interface as required. 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 MAJOR
Description A software error has occurred: the application has passed a bad device ID to the Timeswitch driver, and the application request was failed by the 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, and call processing may be impacted. Consult the log for further details.
Recovery Action Contact Customer Support.
Technical Support Action Contact Product Support.
Severity MAJOR
Description The Timeswitch 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, and call processing may be impacted. Consult the log for further details.
Recovery Action Contact Customer Support.
Technical Support Action Contact Product Support.
Severity MAJOR
Description The Timeswitch driver encountered an internal software error following an application request. 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 The Timeswitch driver failed to initialize due to a low memory condition.
Impact Timeswitch software can not be used, as a result no call processing can take place. The system has been severely impacted.
Recovery Action Contact Customer Support.
Technical Support Action Contact Product Support.
Severity CRITICAL
Description The Timeswitch driver failed to initialize because it cannot use a low level driver library.
Impact Timeswitch software can not be used, as a result no call processing can take place. The system has been severely impacted.
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 CRITICAL
Description The Timeswitch driver failed to initialize because it cannot load a low level driver library.
Impact Timeswitch software can not be used, as a result no call processing can take place. The system has been severely impacted.
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 A software error has occurred: the application has passed a bad parameter to the Timeswitch driver, and the application request was failed by the 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, and call processing may be impacted. Consult the log for further details.
Recovery Action Contact Customer Support.
Technical Support Action Contact Product Support.
Severity MAJOR
Description The Timeswitch driver encountered an internal software error following an application request. 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 MAJOR
Description The Timeswitch driver encountered an internal software error following an application request. 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 Timeswitch software could not initialize because it encountered an internal software error: invalid Mutex object. Consult the CallPilot server's Windows NT Event Log for further details.
Impact Timeswitch software can not be used, as a result no call processing can take place. The system has been severely impacted.
Recovery Action Contact Customer Support.
Technical Support Action Contact Product Support.
Severity CRITICAL
Description Timeswitch software could not initialize because it encountered an internal software error: Mutex timeout. Consult the CallPilot server's Windows NT Event Log for further details.
Impact Timeswitch software can not be used, as a result no call processing can take place. The system has been severely impacted.
Recovery Action Contact Customer Support.
Technical Support Action Contact Product Support.
Severity CRITICAL
Description Timeswitch software could not initialize because it encountered an internal software error: Mutex cannot be released. Consult the CallPilot server's Windows NT Event Log for further details.
Impact Timeswitch software can not be used, as a result no call processing can take place. The system has been severely impacted.
Recovery Action Contact Customer Support.
Technical Support Action Contact Product Support.
Severity CRITICAL
Description Timeswitch software could not initialize because it encountered an internal software error: Mutex abandoned. Consult the CallPilot server's Windows NT Event Log for further details.
Impact Timeswitch software can not be used, as a result no call processing can take place. The system has been severely impacted.
Recovery Action Contact Customer Support.
Technical Support Action Contact Product Support.
Severity CRITICAL
Description A hardware error has occurred on the timeswitch device on a carrier board.
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 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 A hardware error has occurred on the timeswitch device on a carrier board.
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 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 Timeswitch software could not initialize because it encountered an internal software error: invalid timing information. Consult the CallPilot server's Windows NT Event Log for further details.
Impact Timeswitch software can not be used, as a result no call processing can take place. The system has been severely impacted.
Recovery Action Contact Customer Support.
Technical Support Action Contact Product Support.
Severity CRITICAL
Description Timeswitch software could not initialize because it encountered an internal software error: cannot create file mapping. Consult the CallPilot server's Windows NT Event Log for further details.
Impact Timeswitch software can not be used, as a result no call processing can take place. The system has been severely impacted.
Recovery Action Contact Customer Support.
Technical Support Action Contact Product Support.
Severity CRITICAL
Description Timeswitch software could not initialize because it encountered an internal software error: cannot create map file. Consult the CallPilot server's Windows NT Event Log for further details.
Impact Timeswitch software can not be used, as a result no call processing can take place. The system has been severely impacted.
Recovery Action Contact Customer Support.
Technical Support Action Contact Product Support.
Severity CRITICAL
Description Timeswitch software could not initialize because it encountered an internal software error: cannot initialize map file. Consult the CallPilot server's Windows NT Event Log for further details.
Impact Timeswitch software can not be used, as a result no call processing can take place. The system has been severely impacted.
Recovery Action Contact Customer Support.
Technical Support Action Contact Product Support.
Severity MAJOR
Description A software error occurred: the application passed an invalid board parameter and the Timeswitch driver failed the request.
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 MAJOR
Description A software error occurred: the application passed an invalid DSP parameter and the Timeswitch driver failed the request.
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 MAJOR
Description A software error occurred: the application passed an invalid DS30 parameter and the Timeswitch driver failed the request.
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 MAJOR
Description A software error occurred: the application passed an invalid BUS parameter and the Timeswitch driver failed the request.
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 MAJOR
Description A software error occurred: the application passed an invalid channel parameter and the Timeswitch driver failed the request.
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 MAJOR
Description The Timeswitch driver encountered an internal software error: invalid unused TAP channel. 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 MAJOR
Description A software error occurred: the application attempted to re-enable the timeswitch and the Timeswitch driver failed the request.
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 MAJOR
Description A software error occurred: the application did not enable the timeswitch and the Timeswitch driver failed the request.
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 MAJOR
Description A Timeswitch usage error occurred: only 50 processes can use the Timeswitch driver at any one time.
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. If call processing is being adversely affected and the problem persists, try shutting down and subsequently rebooting the CallPilot server. WARNING: This action will affect call processing.
Technical Support Action Contact Product Support.
Severity MAJOR
Description A Timeswitch usage error occurred: a request was made to disconnect a link that was not previously connected.
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. If call processing is being adversely affected and the problem persists, try shutting down and subsequently rebooting the CallPilot server. WARNING: This action will affect call processing.
Technical Support Action Contact Product Support.
Severity MAJOR
Description A Timeswitch usage error occurred: a request was made to connect a link on top of a previously established link prior to removing the previously established link.
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. If call processing is being adversely affected and the problem persists, try shutting down and subsequently rebooting the CallPilot server. WARNING: This action will affect call processing.
Technical Support Action Contact Product Support.
Severity MAJOR
Description A Timeswitch usage error occurred: an attempt was made to disable a Timeswitch while connections were still in place. The error suggests that services or applications using the Timeswitch have crashed.
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. If call processing is being adversely affected and the problem persists, try shutting down and subsequently rebooting the CallPilot server. WARNING: This action will affect call processing.
Technical Support Action Contact Product Support.
Severity MAJOR
Description A process that is using a specific Timeswitch is unresponsive and has not been terminated. The calling component is responsible for terminating all crashed processes.
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. If call processing is being adversely affected and the problem persists, try shutting down and subsequently rebooting the CallPilot server. WARNING: This action will affect call processing.
Technical Support Action Contact Product Support.
Severity MAJOR
Description A Timeswitch usage error occurred: a given Process ID was not present in the list maintained internally.
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. If call processing is being adversely affected and the problem persists, try shutting down and subsequently rebooting the CallPilot server. WARNING: This action will affect call processing.
Technical Support Action Contact Product Support.
Severity MAJOR
Description A process that is using a specific Timeswitch is unresponsive and has not been terminated. As a result, a connection previously set up by the unresponsive process can not be removed.
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. If call processing is being adversely affected and the problem persists, try shutting down and subsequently rebooting the CallPilot server. WARNING: This action will affect call processing.
Technical Support Action Contact Product Support.
Severity MAJOR
Description An error occurred in the Timeswitch driver: a board device cannot be opened.
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 MAJOR
Description An error occurred in the Timeswitch driver: the hardware resources for the requested board could not be mapped.
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 MAJOR
Description An error occurred in the Timeswitch driver: the hardware resources for the requested board could not be released.
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 MAJOR
Description A Timeswitch usage error occurred: a request was made for 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 Contact Customer Support.
Technical Support Action Contact Product Support.
Severity CRITICAL
Description Timeswitch software could not initialize because it encountered an internal software error: cannot find timing information. Consult the CallPilot server's Windows NT Event Log for further details.
Impact Timeswitch software can not be used, as a result no call processing can take place. The system has been severely impacted.
Recovery Action Contact Customer Support.
Technical Support Action Contact Product Support.
Severity CRITICAL
Description Timeswitch software could not initialize because it encountered an internal software error: a registry key holding timing information cannot be found. Consult the CallPilot server's Windows NT Event Log for further details.
Impact Timeswitch software can not be used, as a result no call processing can take place. The system has been severely impacted.
Recovery Action Contact Customer Support.
Technical Support Action Contact Product Support.
Severity CRITICAL
Description Timeswitch software could not initialize because it encountered an internal software error: a registry key holding timing information cannot be closed. Consult the CallPilot server's Windows NT Event Log for further details.
Impact Timeswitch software can not be used, as a result no call processing can take place. The system has been severely impacted.
Recovery Action Contact Customer Support.
Technical Support Action Contact Product Support.
Severity MAJOR
Description A Timeswitch usage error occurred: a request was made to connect resources located on different boards.
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 Timeswitch software could not initialize because it encountered an internal software error: cannot create a Mutex object. Consult the CallPilot server's Windows NT Event Log for further details.
Impact Timeswitch software can not be used, as a result no call processing can take place. The system has been severely impacted.
Recovery Action Contact Customer Support.
Technical Support Action Contact Product Support.
Severity CRITICAL
Description Timeswitch software could not initialize because it encountered an internal software error: cannot set the security for an internal object. Consult the CallPilot server's Windows NT Event Log for further details.
Impact Timeswitch software can not be used, as a result no call processing can take place. The system has been severely impacted.
Recovery Action Contact Customer Support.
Technical Support Action Contact Product Support.
Severity CRITICAL
Description Timeswitch software could not initialize because it encountered an internal software error: cannot initialize the security object. Consult the CallPilot server's Windows NT Event Log for further details.
Impact Timeswitch software can not be used, as a result no call processing can take place. The system has been severely impacted.
Recovery Action Contact Customer Support.
Technical Support Action Contact Product Support.
Severity CRITICAL
Description Timeswitch software could not initialize because it encountered an error: cannot open the version file. Consult the CallPilot server's Windows NT Event Log for further details.
Impact Timeswitch software can not be used, as a result no call processing can take place. The system has been severely impacted.
Recovery Action Contact Customer Support.
Technical Support Action This problem should not normally occur - someone might have deleted or corrupted the timeswitch version files. A reinstall might be required.
Severity CRITICAL
Description Timeswitch software could not initialize because it encountered an error: the version file is corrupt. Consult the CallPilot server's Windows NT Event Log for further details.
Impact Timeswitch software can not be used, as a result no call processing can take place. The system has been severely impacted.
Recovery Action Contact Customer Support.
Technical Support Action This problem should not normally occur - someone might have corrupted the timeswitch version files. A reinstall might be required.
Severity CRITICAL
Description Timeswitch software could not initialize because it encountered an error: the version file is corrupt. Consult the CallPilot server's Windows NT Event Log for further details.
Impact Timeswitch software can not be used, as a result no call processing can take place. The system has been severely impacted.
Recovery Action Contact Customer Support.
Technical Support Action This problem should not normally occur - someone might have corrupted the timeswitch version files. A reinstall might be required.
Severity CRITICAL
Description Timeswitch software could not initialize because it encountered an internal software error: the size of the version buffer is too small. Consult the CallPilot server's Windows NT Event Log for further details.
Impact Timeswitch software can not be used, as a result no call processing can take place. The system has been severely impacted.
Recovery Action Contact Customer Support.
Technical Support Action Contact Product Support.
Severity CRITICAL
Description Timeswitch software could not initialize because it encountered an error: cannot close the version file. Consult the CallPilot server's Windows NT Event Log for further details.
Impact Timeswitch software can not be used, as a result no call processing can take place. The system has been severely impacted.
Recovery Action Contact Customer Support.
Technical Support Action Contact Product Support.
Severity CRITICAL
Description Timeswitch software could not initialize because it encountered an error: cannot open the version file. Consult the CallPilot server's Windows NT Event Log for further details.
Impact Timeswitch software can not be used, as a result no call processing can take place. The system has been severely impacted.
Recovery Action Contact Customer Support.
Technical Support Action This problem should not normally occur - someone might have deleted or corrupted the timeswitch version files. A reinstall might be required.
Severity CRITICAL
Description Timeswitch software could not initialize because it encountered an error: cannot close the version file. Consult the CallPilot server's Windows NT Event Log for further details.
Impact Timeswitch software can not be used, as a result no call processing can take place. The system has been severely impacted.
Recovery Action Contact Customer Support.
Technical Support Action Contact Product Support.
Severity CRITICAL
Description Timeswitch software could not initialize because it encountered an error: the version file is corrupt. Consult the CallPilot server's Windows NT Event Log for further details.
Impact Timeswitch software can not be used, as a result no call processing can take place. The system has been severely impacted.
Recovery Action Contact Customer Support.
Technical Support Action This problem should not normally occur - someone might have corrupted the timeswitch version files. A reinstall might be required.
Severity CRITICAL
Description Timeswitch software could not initialize because it encountered an error: the version file is corrupt. Consult the CallPilot server's Windows NT Event Log for further details.
Impact Timeswitch software can not be used, as a result no call processing can take place. The system has been severely impacted.
Recovery Action Contact Customer Support.
Technical Support Action This problem should not normally occur - someone might have corrupted the timeswitch version files. A reinstall might be required.
Severity CRITICAL
Description Timeswitch software could not initialize because it encountered an error: the version file is corrupt. Consult the CallPilot server's Windows NT Event Log for further details.
Impact Timeswitch software can not be used, as a result no call processing can take place. The system has been severely impacted.
Recovery Action Contact Customer Support.
Technical Support Action This problem should not normally occur - someone might have corrupted the timeswitch version files. A reinstall might be required.
Severity CRITICAL
Description Timeswitch software could not initialize because it encountered an error: the version file is corrupt. Consult the CallPilot server's Windows NT Event Log for further details.
Impact Timeswitch software can not be used, as a result no call processing can take place. The system has been severely impacted.
Recovery Action Contact Customer Support.
Technical Support Action This problem should not normally occur - someone might have corrupted the timeswitch version files. A reinstall might be required.
Severity CRITICAL
Description Timeswitch software could not initialize because it encountered an error: the version file is corrupt. Consult the CallPilot server's Windows NT Event Log for further details.
Impact Timeswitch software can not be used, as a result no call processing can take place. The system has been severely impacted.
Recovery Action Contact Customer Support.
Technical Support Action This problem should not normally occur - someone might have corrupted the timeswitch version files. A reinstall might be required.
Severity CRITICAL
Description Timeswitch software could not initialize because it encountered an error: the platform type reported by NTBUS is invalid. Consult the CallPilot server's Windows NT Event Log for further details.
Impact Timeswitch software can not be used, as a result no call processing can take place. The system has been severely impacted.
Recovery Action Contact Customer Support.
Technical Support Action Contact Product Support.
Severity CRITICAL
Description Timeswitch software could not initialize because it encountered an error: invalid platform type found. Consult the CallPilot server's Windows NT Event Log for further details.
Impact Timeswitch software can not be used, as a result no call processing can take place. The system has been severely impacted.
Recovery Action Contact Customer Support.
Technical Support Action Contact Product Support.
Severity CRITICAL
Description Timeswitch software could not initialize because it encountered an error: cannot get the platform type. Consult the CallPilot server's Windows NT Event Log for further details.
Impact Timeswitch software can not be used, as a result no call processing can take place. The system has been severely impacted.
Recovery Action Contact Customer Support.
Technical Support Action Contact Product Support.
Severity CRITICAL
Description Timeswitch software could not initialize because it encountered an error: cannot get the timeswitch version. Consult the CallPilot server's Windows NT Event Log for further details.
Impact Timeswitch software can not be used, as a result no call processing can take place. The system has been severely impacted.
Recovery Action Contact Customer Support.
Technical Support Action Contact Product Support.
Severity CRITICAL
Description Timeswitch software could not initialize because it encountered an error: bad timeswitch version. Consult the CallPilot server's Windows NT Event Log for further details.
Impact Timeswitch software can not be used, as a result no call processing can take place. The system has been severely impacted.
Recovery Action Contact Customer Support.
Technical Support Action Contact Product Support.
Severity MAJOR
Description The Timeswitch driver encountered an internal software error: invalid register read operation.
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 MAJOR
Description The Timeswitch driver encountered an internal software error: invalid register write operation.
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 MAJOR
Description A Timeswitch usage error occurred: a request was made to connect invalid resources.
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 MAJOR
Description The Timeswitch driver encountered an internal software error: a process ID could not be found in the internal list.
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 MAJOR
Description The Timeswitch has failed an operation because the library did not initialize properly.
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 MAJOR
Description A Timeswitch usage error occurred: the maximum capacity of the timeswitch hardware has been reached.
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 MAJOR
Description A Timeswitch usage error occurred: the maximum capacity of the timeswitch hardware has been reached.
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 MAJOR
Description A Timeswitch usage error occurred: the board hardware does not support multicast connections.
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 The Timeswitch Memory Diagnostic failed to ENABLE a Timeswitch. Consult the CallPilot server's Windows NT Event Log for further details.
Impact The Timeswitch may be faulty and call processing might be severely impacted.
Recovery Action Ensure the following: the CallPilot device drivers are running (Devices Applet), the IPE/MPB is properly seated into its backplane/PCI slot. Re-run the Timeswitch Memory Diagnostic to confirm and reproduce the failure.
Shutdown and reboot the CallPilot server and re-run Timeswitch diagnostics. If the error re-occurs, replace the IPE/MPB.
Technical Support Action Not applicable
Severity MINOR
Description The Timeswitch Memory Diagnostic was run while the Timeswitch's target MPB/200i was not in an off-duty state. A usage error most likely occurred while attempting to run diagnostics from the server. Consult the Windows NT Event Log for further details.
Impact If the diagnostic was being run from the CLIENT, software may be faulty and call processing might be severely impacted. If being run from the server, there will be no impact on call processing.
Recovery Action Ensure the following: the Timeswitch's target IPE/MPB board is in an off-duty state prior to running diagnostics. If the diagnostic was being run from the CLIENT GUI, contact your technical support organization.
Technical Support Action If the diagnostic was being run from the CLIENT GUI then please report this bug to CallPilot designers.
Severity CRITICAL
Description The Timeswitch Memory Diagnostic failed to DISABLE a Timeswitch. Consult the CallPilot server's Windows NT Event Log for further details.
Impact The Timeswitch may be faulty and call processing might be severely impacted.
Recovery Action Ensure the following: the CallPilot device drivers are running (Devices Applet), the IPE/MPB is properly seated into its backplane/PCI slot. Re-run the Timeswitch Memory Diagnostic to confirm and reproduce the failure.
Shutdown and reboot the CallPilot server and re-run Timeswitch diagnostics. If the error re-occurs, replace the IPE/MPB.
Technical Support Action Not applicable
Severity CRITICAL
Description The Timeswitch Memory Diagnostic failed to write to its memory elements (Connection Memory).
Impact The Timeswitch may be faulty and call processing might be severely impacted.
Recovery Action Ensure the following: the CallPilot device drivers are running (Devices Applet), the IPE/MPB is properly seated into its backplane/PCI slot. Re-run the Timeswitch Memory Diagnostic to confirm and reproduce the failure.
Shutdown and reboot the CallPilot server and re-run Timeswitch diagnostics. If the error re-occurs, replace the IPE/MPB.
Technical Support Action Not applicable
Severity CRITICAL
Description The Timeswitch Memory Diagnostic failed to read from its memory elements (Connection Memory).
Impact The Timeswitch may be faulty and call processing might be severely impacted.
Recovery Action Ensure the following: the CallPilot device drivers are running (Devices Applet), the IPE/MPB is properly seated into its backplane/PCI slot. Re-run the Timeswitch Memory Diagnostic to confirm and reproduce the failure.
Shutdown and reboot the CallPilot server and re-run Timeswitch diagnostics. If the error re-occurs, replace the IPE/MPB.
Technical Support Action Not applicable
Severity CRITICAL
Description The Timeswitch Memory Diagnostic failed. Values were written to Timeswitch memory elements and subsequently read back. The read back values were not equal to the written values (Connection Memory).
Impact The Timeswitch may be faulty and call processing might be severely impacted.
Recovery Action Ensure the following: the CallPilot device drivers are running (Devices Applet), the IPE/MPB is properly seated into its backplane/PCI slot. Re-run the Timeswitch Memory Diagnostic to confirm and reproduce the failure.
Shutdown and reboot the CallPilot server and re-run Timeswitch diagnostics. If the error re-occurs, replace the IPE/MPB.
Technical Support Action Not applicable
Severity CRITICAL
Description The Timeswitch Memory Diagnostic failed due to a critical internal SOFTWARE error (System low on virtual memory). Consult the CallPilot server's Windows NT Event Log for further details.
Impact The Timeswitch Memory Diagnostic will not operate as expected.
Recovery Action If call processing is being affected, try shutting down and rebooting the CallPilot server and then re-running the Timeswitch Memory diagnostics. Contact Customer Support. to report the bug.
Technical Support Action Please contact CallPilot Designers to report this bug.
Severity CRITICAL
Description The Timeswitch Memory Diagnostic failed to read from its memory elements (PCM Control Register).
Impact The Timeswitch may be faulty and call processing might be severely impacted.
Recovery Action Ensure the following: the CallPilot device drivers are running (Devices Applet), the IPE/MPB is properly seated into its backplane/PCI slot. Re-run the Timeswitch Memory Diagnostic to confirm and reproduce the failure.
Shutdown and reboot the CallPilot server and re-run Timeswitch diagnostics. If the error re-occurs, replace the IPE/MPB.
Technical Support Action Not applicable
Severity CRITICAL
Description The Timeswitch Memory Diagnostic failed to write to its memory elements (PCM Control Register).
Impact The Timeswitch may be faulty and call processing might be severely impacted.
Recovery Action Ensure the following: the CallPilot device drivers are running (Devices Applet), the IPE/MPB is properly seated into its backplane/PCI slot. Re-run the Timeswitch Memory Diagnostic to confirm and reproduce the failure.
Shutdown and reboot the CallPilot server and re-run Timeswitch diagnostics. If the error re-occurs, replace the IPE/MPB.
Technical Support Action Not applicable
Severity CRITICAL
Description The Timeswitch Memory Diagnostic failed to write to its memory elements (TAP Memory).
Impact The Timeswitch may be faulty and call processing might be severely impacted.
Recovery Action Ensure the following: the CallPilot device drivers are running (Devices Applet), the IPE/MPB is properly seated into its backplane/PCI slot. Re-run the Timeswitch Memory Diagnostic to confirm and reproduce the failure.
Shutdown and reboot the CallPilot server and re-run Timeswitch diagnostics. If the error re-occurs, replace the IPE/MPB.
Technical Support Action Not applicable
Severity CRITICAL
Description The Timeswitch Memory Diagnostic failed to write to its memory elements (UNUSED TAP Memory).
Impact The Timeswitch may be faulty and call processing might be severely impacted.
Recovery Action Ensure the following: the CallPilot device drivers are running (Devices Applet), the IPE/MPB is properly seated into its backplane/PCI slot. Re-run the Timeswitch Memory Diagnostic to confirm and reproduce the failure.
Shutdown and reboot the CallPilot server and re-run Timeswitch diagnostics. If the error re-occurs, replace the IPE/MPB.
Technical Support Action Not applicable
Severity CRITICAL
Description The Timeswitch Memory Diagnostic failed to write to its memory elements (TAP2 Memory).
Impact The Timeswitch may be faulty and call processing might be severely impacted.
Recovery Action Ensure the following: the CallPilot device drivers are running (Devices Applet), the IPE/MPB is properly seated into its backplane/PCI slot. Re-run the Timeswitch Memory Diagnostic to confirm and reproduce the failure.
Shutdown and reboot the CallPilot server and re-run Timeswitch diagnostics. If the error re-occurs, replace the IPE/MPB.
Technical Support Action Not applicable
Severity CRITICAL
Description The Timeswitch Memory Diagnostic failed to write to its memory elements (UNUSED TAP2 Memory).
Impact The Timeswitch may be faulty and call processing might be severely impacted.
Recovery Action Ensure the following: the CallPilot device drivers are running (Devices Applet), the IPE/MPB is properly seated into its backplane/PCI slot. Re-run the Timeswitch Memory Diagnostic to confirm and reproduce the failure.
Shutdown and reboot the CallPilot server and re-run Timeswitch diagnostics. If the error re-occurs, replace the IPE/MPB.
Technical Support Action Not applicable
Severity CRITICAL
Description The Timeswitch Memory Diagnostic failed to read from its memory elements (TAP Memory).
Impact The Timeswitch may be faulty and call processing might be severely impacted.
Recovery Action Ensure the following: the CallPilot device drivers are running (Devices Applet), the IPE/MPB is properly seated into its backplane/PCI slot. Re-run the Timeswitch Memory Diagnostic to confirm and reproduce the failure.
Shutdown and reboot the CallPilot server and re-run Timeswitch diagnostics. If the error re-occurs, replace the IPE/MPB.
Technical Support Action Not applicable
Severity CRITICAL
Description The Timeswitch Memory Diagnostic failed. Values were written to Timeswitch memory elements and subsequently read back. The read back values were not equal to the written values(TAP Memory).
Impact The Timeswitch may be faulty and call processing might be severely impacted.
Recovery Action Ensure the following: the CallPilot device drivers are running (Devices Applet), the IPE/MPB is properly seated into its backplane/PCI slot. Re-run the Timeswitch Memory Diagnostic to confirm and reproduce the failure.
Shutdown and reboot the CallPilot server and re-run Timeswitch diagnostics. If the error re-occurs, replace the IPE/MPB.
Technical Support Action Not applicable
Severity CRITICAL
Description The Timeswitch Memory Diagnostic failed to read from its memory elements (UNUSED TAP Memory).
Impact The Timeswitch may be faulty and call processing might be severely impacted.
Recovery Action Ensure the following: the CallPilot device drivers are running (Devices Applet), the IPE/MPB is properly seated into its backplane/PCI slot. Re-run the Timeswitch Memory Diagnostic to confirm and reproduce the failure.
Shutdown and reboot the CallPilot server and re-run Timeswitch diagnostics. If the error re-occurs, replace the IPE/MPB.
Technical Support Action Not applicable
Severity CRITICAL
Description The Timeswitch Memory Diagnostic failed. Values were written to Timeswitch memory elements and subsequently read back. The read back values were not equal to the written values (UNUSED TAP Memory).
Impact The Timeswitch may be faulty and call processing might be severely impacted.
Recovery Action Ensure the following: the CallPilot device drivers are running (Devices Applet), the IPE/MPB is properly seated into its backplane/PCI slot. Re-run the Timeswitch Memory Diagnostic to confirm and reproduce the failure.
Shutdown and reboot the CallPilot server and re-run Timeswitch diagnostics. If the error re-occurs, replace the IPE/MPB.
Technical Support Action Not applicable
Severity CRITICAL
Description The Timeswitch Memory Diagnostic failed to read from its memory elements (TAP2 Memory).
Impact The Timeswitch may be faulty and call processing might be severely impacted.
Recovery Action Ensure the following: the CallPilot device drivers are running (Devices Applet), the IPE/MPB is properly seated into its backplane/PCI slot. Re-run the Timeswitch Memory Diagnostic to confirm and reproduce the failure.
Shutdown and reboot the CallPilot server and re-run Timeswitch diagnostics. If the error re-occurs, replace the IPE/MPB.
Technical Support Action Not applicable
Severity CRITICAL
Description The Timeswitch Memory Diagnostic failed. Values were written to Timeswitch memory elements and subsequently read back. The read back values were not equal to the written values(TAP2 Memory).
Impact The Timeswitch may be faulty and call processing might be severely impacted.
Recovery Action Ensure the following: the CallPilot device drivers are running (Devices Applet), the IPE/MPB is properly seated into its backplane/PCI slot. Re-run the Timeswitch Memory Diagnostic to confirm and reproduce the failure.
Shutdown and reboot the CallPilot server and re-run Timeswitch diagnostics. If the error re-occurs, replace the IPE/MPB.
Technical Support Action Not applicable
Severity CRITICAL
Description The Timeswitch Memory Diagnostic failed to read from its memory elements (UNUSED TAP2 Memory).
Impact The Timeswitch may be faulty and call processing might be severely impacted.
Recovery Action Ensure the following: the CallPilot device drivers are running (Devices Applet), the IPE/MPB is properly seated into its backplane/PCI slot. Re-run the Timeswitch Memory Diagnostic to confirm and reproduce the failure.
Shutdown and reboot the CallPilot server and re-run Timeswitch diagnostics. If the error re-occurs, replace the IPE/MPB.
Technical Support Action Not applicable
Severity CRITICAL
Description The Timeswitch Memory Diagnostic failed. Values were written to Timeswitch memory elements and subsequently read back. The read back values were not equal to the written values (UNUSED TAP2 Memory).
Impact The Timeswitch may be faulty and call processing might be severely impacted.
Recovery Action Ensure the following: the CallPilot device drivers are running (Devices Applet), the IPE/MPB is properly seated into its backplane/PCI slot. Re-run the Timeswitch Memory Diagnostic to confirm and reproduce the failure.
Shutdown and reboot the CallPilot server and re-run Timeswitch diagnostics. If the error re-occurs, replace the IPE/MPB.
Technical Support Action Not applicable
Severity MAJOR
Description A software error has occurred: the application did not acquire the HAL Dongle driver interface as required. 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 MINOR
Description A software error has occurred: the application has passed a bad parameter to the HAL Dongle driver, and the application request was failed by the driver. Consult the CallPilot server's Windows NT Event Log for further details.
Impact The security dongle cannot be read and certain administrative operations will not be available. Consult the log for further details.
Recovery Action Contact Customer Support.
Technical Support Action Contact Product Support.
Severity MINOR
Description The HAL Dongle driver cannot read the dongle information from the hardware.
Impact The security dongle cannot be read and certain administrative operations will not be available. Consult the log for further details.
Recovery Action Verify the security dongle has been installed. If installed and the problem persists, replace the dongle.
Technical Support Action Not applicable
Severity MINOR
Description The HAL Dongle driver cannot read the dongle information from the hardware because it cannot communicate with a low level driver.
Impact The security dongle cannot be read and certain administrative operations will not be available. Consult the log for further details.
Recovery Action Use the Devices applet in the Windows NT Control Panel and ensure the CallPilot 200i 8051 Driver is running. Consult the log for further details.
Technical Support Action Not applicable
Severity MINOR
Description Dongle info has not been received from a low level driver.
Impact The security dongle cannot be read and certain administrative operations will not be available. Consult the log for further details.
Recovery Action Verify the security dongle has been installed. If installed and the problem persists, replace the dongle.
Technical Support Action Not applicable
Severity MINOR
Description A low level driver received bad dongle information.
Impact The security dongle cannot be read and certain administrative operations will not be available. Consult the log for further details.
Recovery Action Verify the security dongle has been installed. If installed and the problem persists, replace the dongle.
Technical Support Action Not applicable
Severity MINOR
Description The HAL Dongle low level driver could not detect any dongle.
Impact The security dongle cannot be read and certain administrative operations will not be available. Consult the log for further details.
Recovery Action Verify the security dongle has been installed. If installed and the problem persists, replace the dongle.
Technical Support Action Not applicable
Severity MAJOR
Description The HAL Dongle driver failed to read a parameter from the registry and cannot access dongle information.
Impact The security dongle cannot be read and certain administrative operations will not be available. Consult the log for further details.
Recovery Action Contact Customer Support.
Technical Support Action This problem should not normally occur -- the registry may have been corrupted. A reinstall might be required.
Severity MAJOR
Description The HAL Dongle driver read bad data from the registry and cannot access dongle information.
Impact The security dongle cannot be read and certain administrative operations will not be available. Consult the log for further details.
Recovery Action Contact Customer Support.
Technical Support Action This problem should not normally occur -- the registry may have been corrupted. A reinstall might be required.
Severity MAJOR
Description The HAL Dongle driver cannot read data from the registry and cannot access dongle information.
Impact The security dongle cannot be read and certain administrative operations will not be available. Consult the log for further details.
Recovery Action Contact Customer Support.
Technical Support Action This problem should not normally occur -- the registry may have been corrupted. A reinstall might be required.
Severity MAJOR
Description The HAL Dongle driver cannot communicate with a low level driver to read platform and dongle information.
Impact The security dongle cannot be read and certain administrative operations will not be available. Consult the log for further details.
Recovery Action Use the Devices applet in the Windows NT Control Panel and ensure the CallPilot Ntbus Driver and the CallPilot 200i 8051 Driver are running. Consult the log for further details.
Technical Support Action Not applicable
Severity MAJOR
Description The HAL Dongle driver encountered an error from a low level driver and cannot read the dongle information.
Impact The security dongle cannot be read and certain administrative operations will not be available. Consult the log for further details.
Recovery Action Contact Customer Support.
Technical Support Action Contact Product Support.
Severity MAJOR
Description The HAL Dongle driver cannot locate a low level driver to read platform and dongle information.
Impact The security dongle cannot be read and certain administrative operations will not be available. Consult the log for further details.
Recovery Action Contact Customer Support.
Technical Support Action This problem should not normally occur -- Dallas Dongle device driver files may have been corrupted or deleted. A reinstall might be required.
Severity MAJOR
Description The HAL Dongle driver encountered an error from a low level driver and cannot read the dongle information.
Impact The security dongle cannot be read and certain administrative operations will not be available. Consult the log for further details.
Recovery Action Contact Customer Support.
Technical Support Action Contact Product Support.
Severity MINOR
Description A low level driver cannot read dongle hardware information.
Impact The security dongle cannot be read and certain administrative operations will not be available. Consult the log for further details.
Recovery Action Verify the security dongle has been installed. If installed and the problem persists, replace the dongle.
Technical Support Action Not applicable
Severity MINOR
Description A low level driver cannot read dongle hardware information.
Impact The security dongle cannot be read and certain administrative operations will not be available. Consult the log for further details.
Recovery Action Verify the security dongle has been installed. If installed and the problem persists, replace the dongle.
Technical Support Action Not applicable
Severity MINOR
Description A low level driver cannot read dongle hardware information.
Impact The security dongle cannot be read and certain administrative operations will not be available. Consult the log for further details.
Recovery Action Verify the security dongle has been installed. If installed and the problem persists, replace the dongle.
Technical Support Action Not applicable
Severity MAJOR
Description An I/O request made by the HAL Dongle driver failed. Consult the CallPilot server's Windows NT Event Log for further details.
Impact The security dongle cannot be read and certain administrative operations will not be available. Consult the log for further details.
Recovery Action Contact Customer Support.
Technical Support Action Contact Product Support.
Severity MINOR
Description A timeout has occurred while trying to read the dongle.
Impact The security dongle cannot be read and certain administrative operations will not be available. Consult the log for further details.
Recovery Action Verify the security dongle has been installed. If installed and the problem persists, replace the dongle.
Technical Support Action Not applicable
Severity MAJOR
Description An internal error occurred in the HAL Dongle driver due to a low memory condition.
Impact The security dongle cannot be read and certain administrative operations will not be available. This is the result of 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 Dongle driver encountered an internal software error following an application request. Consult the CallPilot server's Windows NT Event Log for further details.
Impact The security dongle cannot be read and certain administrative operations will not be available. Consult the log for further details.
Recovery Action Contact Customer Support.
Technical Support Action Contact Product Support.
Severity MAJOR
Description The HAL Dongle driver encountered an internal software error. Consult the CallPilot server's Windows NT Event Log for further details.
Impact The security dongle cannot be read and certain administrative operations will not be available. Consult the log for further details.
Recovery Action Contact Customer Support.
Technical Support Action Contact Product Support.
Severity MAJOR
Description The HAL Dongle driver cannot use a low level driver library.
Impact The security dongle cannot be read and certain administrative operations will not be available. Consult the log for further details.
Recovery Action Contact Customer Support.
Technical Support Action This problem should not normally occur -- Dallas Dongle device driver files may have been corrupted or deleted. A reinstall might be required.
Severity MAJOR
Description The HAL Dongle driver cannot load a low level driver library.
Impact The security dongle cannot be read and certain administrative operations will not be available. Consult the log for further details.
Recovery Action Contact Customer Support.
Technical Support Action This problem should not normally occur -- Dallas Dongle device driver files may have been corrupted or deleted. A reinstall might be required.
Severity CRITICAL
Description Indicates that the 8051 Device Driver has not started.
Impact If running on an IPE platform, call processing cannot take place.
Recovery Action Use the Devices applet in the Windows NT Control Panel and ensure the CallPilot 8051 Driver is running. Consult the log for further details.
Technical Support Action Not applicable.
Severity MAJOR
Description The host is unable to communicate with the 8051System Controller.
Impact If running on an IPE platform, call processing cannot take place.
Recovery Action Contact Customer Support.
Technical Support Action Contact Product Support.
Severity MAJOR
Description A software error has occurred, and a dongle information request cannot be processed.
Impact The security dongle cannot be read.
Recovery Action Contact Customer Support.
Technical Support Action Contact Product Support.
Severity MAJOR
Description The 8051 System Controller failed to send the requested dongle information.
Impact The security dongle cannot be read and certain administrative operations will not be available.
Recovery Action Contact Customer Support.
Technical Support Action Contact Product Support.
Severity MAJOR
Description The 8051 System Controller did not find the dongle due to either a missing dongle or a hardware malfunction.
Impact The security dongle cannot be read and certain administrative operations will not be available.
Recovery Action Verify the security dongle has been installed on the motherboard. If installed and the problem persists, replace the dongle.
Technical Support Action Not applicable
Severity MAJOR
Description The status information of the security dongle has been corrupted.
Impact The security dongle cannot be read and certain administrative operations will not be available.
Recovery Action Verify the security dongle has been installed on the motherboard. If installed and the problem persists, replace the dongle.
Technical Support Action Not applicable
Severity MINOR
Description A software error has occurred, and a hex display update request cannot be processed.
Impact Alarms cannot be displayed on the faceplate hex display.
Recovery Action Contact Customer Support.
Technical Support Action Contact Product Support.
Severity MINOR
Description Cannot create a new hex display message group.
Impact Alarms cannot be displayed on the faceplate hex display.
Recovery Action Contact Customer Support.
Technical Support Action Contact Product Support.
Severity MINOR
Description A software error has occurred and an invalid message group handle cannot be processed.
Impact Alarms cannot be displayed on the faceplate hex display.
Recovery Action Contact Customer Support.
Technical Support Action Contact Product Support.
Severity MINOR
Description A software error has occurred: none of the currently defined hex display message groups is identified by the given handle.
Impact Alarms cannot be displayed on the faceplate hex display.
Recovery Action Contact Customer Support.
Technical Support Action Contact Product Support.
Severity MINOR
Description Cannot append a new hex display message.
Impact Alarms cannot be displayed on the faceplate hex display.
Recovery Action Contact Customer Support.
Technical Support Action Contact Product Support.
Severity MINOR
Description A software error has occurred: an invalid value for a hex display message has been passed.
Impact Alarms cannot be displayed on the faceplate hex display.
Recovery Action Contact Customer Support.
Technical Support Action Contact Product Support.
Severity MINOR
Description A software error has occurred: none of the currently defined hex display messages is identified by the given handle.
Impact Alarms cannot be displayed on the faceplate hex display.
Recovery Action Contact Customer Support.
Technical Support Action Contact Product Support.
Severity MAJOR
Description A software error has occurred: the current message is not supported.
Impact Applications may not have access to the System Controller hardware resources. Consult the log for further details.
Recovery Action Contact Customer Support.
Technical Support Action Contact Product Support.
Severity MAJOR
Description Message writing error - one of the host to 8051 System Controller message queues' pointers has been corrupted.
Impact Applications may not have access to the System Controller hardware resources. Consult the log for further details.
Recovery Action Contact Customer Support.
Technical Support Action Contact Product Support.
Severity MAJOR
Description Message writing error - the 8051System Controller does not free one of the host to 8051System Controller message queues.
Impact Applications may not have access to the System Controller hardware resources. Consult the log for further details.
Recovery Action Contact Customer Support.
Technical Support Action Contact Product Support.
Severity MAJOR
Description Message reading error - one of the 8051System Controller to host message queues' pointers has been corrupted.
Impact Applications may not have access to the System Controller hardware resources. Consult the log for further details.
Recovery Action Contact Customer Support.
Technical Support Action Contact Product Support.
Severity MAJOR
Description Message reading error - the current message sent by the 8051System Controller was not defined.
Impact Applications may not have access to the System Controller hardware resources. Consult the log for further details.
Recovery Action Contact Customer Support.
Technical Support Action Contact Product Support.
Severity MAJOR
Description Message reading error - the current message sent by the 8051System Controller has been corrupted.
Impact Applications may not have access to the System Controller hardware resources. Consult the log for further details.
Recovery Action Contact Customer Support.
Technical Support Action Contact Product Support.
Severity INFO
Description The switch does not provide a CEMUX interface.
Impact None.
Recovery Action Not applicable.
Technical Support Action Not applicable.
Severity INFO
Description A CEMUX IF has been identified, even if the existing 8051 driver registry configuration does not specify it.
Impact None.
Recovery Action Not applicable.
Technical Support Action Not applicable.
Severity INFO
Description The switch does not provide a CEMUX interface (as the existing 8051 driver registry configuration specifies).
Impact None.
Recovery Action Not applicable.
Technical Support Action Not applicable.
Severity INFO
Description The CEMUX IP interface is not supported in the existing 8051 driver registry configuration.
Impact None.
Recovery Action Not applicable.
Technical Support Action Not applicable.
Severity INFO
Description Another service or application has been previously registered with the 8051 driver for the CEMUX IP addresses notification.
Impact None.
Recovery Action Not applicable.
Technical Support Action Not applicable.
Severity MAJOR
Description The 8051 System Controller device driver 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 MINOR
Description A software error has occurred: the handle used in order to get the CEMUX IP addresses is not a valid one.
Impact None.
Recovery Action Contact Customer Support.
Technical Support Action Contact Product Support.
Severity INFO
Description The switch did not send any "CEMUX IP Addresses" CEMUX message yet.
Impact None.
Recovery Action Not applicable.
Technical Support Action Not applicable.
Severity INFO
Description The switch has already been connected over CardLAN at the time a new switch connection has been requested.
Impact None.
Recovery Action Not applicable.
Technical Support Action Not applicable.
Severity INFO
Description The 8051 System Controller driver has started step 1 of the switch connection.
Impact None.
Recovery Action Not applicable.
Technical Support Action Not applicable.
Severity INFO
Description The 8051 System Controller driver has started step 2 of the switch connection.
Impact None.
Recovery Action Not applicable.
Technical Support Action Not applicable.
Severity INFO
Description The 8051 System Controller driver has started step 3 of the switch connection.
Impact None.
Recovery Action Not applicable.
Technical Support Action Not applicable.
Severity MAJOR
Description The 8051 System Controller driver has stopped during step 1 of the switch connection.
Impact The host cannot communicate with the switch using CardLAN messaging, and call processing cannot take place. Consult the log for further details.
Recovery Action Contact Customer Support.
Technical Support Action Contact Product Support.
Severity MAJOR
Description The 8051 System Controller driver has stopped during step 2 of the switch connection.
Impact The host cannot communicate with the switch using CardLAN messaging, and call processing cannot take place. Consult the log for further details.
Recovery Action Contact Customer Support.
Technical Support Action Contact Product Support.
Severity MAJOR
Description The 8051 System Controller driver has stopped during step 3 of the switch connection.
Impact The host cannot communicate with the switch using CardLAN messaging, and call processing cannot take place. Consult the log for further details.
Recovery Action Contact Customer Support.
Technical Support Action Contact Product Support.
Severity MAJOR
Description The 8051 System Controller driver failed to allocate an internal resource (DPRAM), and the driver cannot start.
Impact The host cannot communicate with the switch using CardLAN messaging, and call processing cannot take place. This is the result of 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 8051 System Controller driver failed to allocate an internal resource (interrupt register), and the driver cannot start.
Impact The host cannot communicate with the switch using CardLAN messaging, and call processing cannot take place. This is the result of 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 8051 System Controller driver failed to allocate an internal resource (interrupts), and the driver cannot start.
Impact The host cannot communicate with the switch using CardLAN messaging, and call processing cannot take place. This is the result of 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 8051 System Controller driver has encountered an error and the step 1 of the switch connection can not be started.
Impact The host cannot communicate with the switch using CardLAN messaging, and call processing cannot take place.
Recovery Action Contact Customer Support.
Technical Support Action Contact Product Support.
Severity INFO
Description There was not any previous MAS IPE successful configuration performed by the 8051 System Controller driver.
Impact None.
Recovery Action Not applicable.
Technical Support Action Not applicable.
Severity MAJOR
Description The 8051 System Controller driver has encountered a software error: the path used to query the registry is invalid.
Impact The host cannot communicate with the switch using CardLAN messaging, and call processing cannot take place.
Recovery Action Contact Customer Support.
Technical Support Action This problem should not normally occur -- the registry may have been corrupted. A reinstall might be required.
Severity MAJOR
Description The 8051 System Controller driver has encountered a software error: one of the parameters used to query the registry is invalid.
Impact The host cannot communicate with the switch using CardLAN messaging, and call processing cannot take place.
Recovery Action Contact Customer Support.
Technical Support Action This problem should not normally occur -- the registry may have been corrupted. A reinstall might be required.
Severity MAJOR
Description The 8051 System Controller driver has encountered a software error: not all the expected keys or values were found in the registry.
Impact The host cannot communicate with the switch using CardLAN messaging, and call processing cannot take place.
Recovery Action Contact Customer Support.
Technical Support Action This problem should not normally occur -- the registry may have been corrupted. A reinstall might be required.
Severity MAJOR
Description The 8051 System Controller driver cannot find a required key in the registry: Card ID.
Impact The host cannot communicate with the switch using CardLAN messaging, and call processing cannot take place.
Recovery Action Contact Customer Support.
Technical Support Action This problem should not normally occur -- the registry may have been corrupted. A reinstall might be required.
Severity MAJOR
Description The 8051 System Controller driver cannot find a required key in the registry: Signalling Type.
Impact The host cannot communicate with the switch using CardLAN messaging, and call processing cannot take place.
Recovery Action Contact Customer Support.
Technical Support Action This problem should not normally occur -- the registry may have been corrupted. A reinstall might be required.
Severity MAJOR
Description The 8051 System Controller driver cannot find a required key in the registry: TN Mapping Type.
Impact The host cannot communicate with the switch using CardLAN messaging, and call processing cannot take place.
Recovery Action Contact Customer Support.
Technical Support Action This problem should not normally occur -- the registry may have been corrupted. A reinstall might be required.
Severity MAJOR
Description The 8051 System Controller driver cannot find a required key in the registry: CemuxIPInterface.
Impact The host cannot communicate with the switch using CardLAN messaging, and call processing cannot take place.
Recovery Action Contact Customer Support.
Technical Support Action This problem should not normally occur -- the registry may have been corrupted. A reinstall might be required.
Severity MAJOR
Description The 8051 System Controller driver has encountered an internal software error and its state may be unstable.
Impact The host may lose communication with the switch via CardLAN messaging, and call processing may be impacted. Consult the log for further details.
Recovery Action Contact Customer Support.
Technical Support Action Contact Product Support.
Severity INFO
Description The switch is not connected at the time a switch disconnection has been requested.
Impact None.
Recovery Action Not applicable.
Technical Support Action Not applicable.
Severity INFO
Description The 8051 driver can not send the "Terminate Driver Communication" message to the 8051 System Controller.
Impact None.
Recovery Action Not applicable.
Technical Support Action Not applicable.
Severity INFO
Description The 8051driver has time-outed waiting for 8051System Controller to acknowledge the "Terminate Driver Communication" message.
Impact None.
Recovery Action Not applicable.
Technical Support Action Not applicable.
Severity MAJOR
Description The 8051 System Controller driver can not restart its minimum communication with the 8051 hardware.
Impact The host may lose communication with the switch via CardLAN messaging, and call processing may be impacted. Consult the log for further details.
Recovery Action Contact Customer Support.
Technical Support Action Contact Product Support.
Severity INFO
Description The 8051 System Controller driver has encountered a software error: unknown A07 (SSD) messaging related IOCTL code.
Impact None.
Recovery Action Not applicable.
Technical Support Action Not applicable.
Severity INFO
Description The 8051 System Controller driver has encountered a software error: unknown CEMUX IP Addresses message's status code.
Impact None.
Recovery Action Not applicable.
Technical Support Action Not applicable.
Severity INFO
Description The 8051 System Controller driver has encountered a software error: unknown CEMUX IP Addresses Notification related IOCTL code.
Impact None.
Recovery Action Not applicable.
Technical Support Action Not applicable.
Severity INFO
Description The 8051 System Controller driver has encountered a software error: unknown switch connection IOCTL code.
Impact None.
Recovery Action Not applicable.
Technical Support Action Not applicable.
Severity MAJOR
Description The 8051 System Controller driver failed to allocate an internal resource (DPRAM), and the driver cannot start.
Impact The host cannot communicate with the switch using CardLAN messaging, and call processing cannot take place. This is the result of 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 8051 System Controller driver failed to allocate an internal resource (interrupt register), and the driver cannot start.
Impact The host cannot communicate with the switch using CardLAN messaging, and call processing cannot take place. This is the result of 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 8051 System Controller driver failed to allocate an internal resource (interrupts), and the driver cannot start.
Impact The host cannot communicate with the switch using CardLAN messaging, and call processing cannot take place. This is the result of an internal Windows NT fault and the system may be severely impacted.
Recovery Action Contact Customer Support.
Technical Support Action Contact Product Support.
Severity INFO
Description The 8051 System Controller did not send the Firmware Version response.
Impact None.
Recovery Action Not applicable.
Technical Support Action Not applicable.
Severity MAJOR
Description A software error has occurred: the application did not acquire the System Controller driver interface as required. 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 The System Controller 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 CRITICAL
Description The System Controller driver cannot open the low level device driver.
Impact If running on an IPE platform, call processing cannot take place.
Recovery Action Use the Devices applet in the Windows NT Control Panel and ensure the CallPilot 8051 Driver is running. Consult the log for further details.
Technical Support Action Not applicable
Severity MAJOR
Description An I/O request made by the System Controller failed. 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 software error has occurred: the application has passed a bad parameter to the System Controller driver, and the application request was failed by the 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 The System Controller driver encountered an internal software error following an application request. 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.