The C52 MPC Diagnostics is an MS-DOS based process that performs tests on the TI C52 MPC processor. Tests include:
Shared, private, cross arbitration tests
MPC bootup diagnostics from Flash memory
Test on the integrity of the address and data buses
Test the shared memory XF locking mechanism
Short memory tests on both the shared and private memory areas
Severity Critical
Description Call Channel Resource Service executable initialization phase failed. Error reported is related to the reported API.
Impact Call Processing functionality not available.
Recovery Action Reboot. Call Customer Support if problem persists.
Technical Support Action Verify that the Service related to the API being reported is operational. Possible Services are: CTM, Database, TAPI
Verify that CCr is configured properly in database.
Verify that DS0 Channels are configured properly in TAPI.
Severity Critical
Description Call Channel Resource service failed to initialize with Database. Error reported is related to the reported API.
Impact Call Processing functionality not available.
Recovery Action Reboot. Call Customer Support if problem persists.
Technical Support Action Verify that the database is operational.
Severity Critical
Description Call Channel Resource Service executable initialization phase failed. Error reported is related to the reported API.
Impact Call Processing functionality not available.
Recovery Action Reboot. Call Customer Support if problem persists.
Technical Support Action Verify that the database is operational. Look up the SQLerr in ODBC Reference.
Severity Critical
Description Call Channel Resource Package Service Provider failed to be created. Error reported is related to the reported API.
Impact Call Processing functionality not available.
Recovery Action Reboot. Call Customer Support if problem persists.
Technical Support Action Verify that CTM Service is operational. Restart CTM Service and EMCI if not operational.
Severity Critical
Description Call Channel Resource Package Service Provider failed to be created due to system memory shortage. Error reported is related to the reported API.
Impact Call Processing functionality not available.
Recovery Action Reboot. Call Customer Support if problem persists.
Technical Support Action Reduce system memory usage by shutting down unnecessary programs. Increase paging file size.
Severity Major
Description Call Channel Resource MPB Service Provider failed to be created. Error reported is related to the reported API.
Impact Call Processing functionality not available from the reported MPB.
Recovery Action Reboot. Call Customer Support if problem persists.
Technical Support Action Verify that CTM Service is operational
Severity Major
Description Call Channel Resource MPB Service Provider failed to be created due to system memory shortage. Error reported is related to the reported API.
Impact Call Processing functionality not available from the MPB.
Recovery Action Check if system is under engineered. Reboot. Call Customer Support if problem persists.
Technical Support Action Reduce system memory usage by shutting down unnecessary programs. Increase paging file size.
Severity Major
Description Call Channel Resource DS30 Service Provider failed to be created. Error reported is related to the reported API.
Impact Call Processing functionality not available from the reported DS30 link.
Recovery Action Reboot. Call Customer Support if problem persists.
Technical Support Action Verify that CTM Service is operational.
Severity Major
Description Call Channel Resource DS30 Service Provider failed to be created due to system memory shortage. Error reported is related to the reported API.
Impact Call Processing functionality not available from the DS30.
Recovery Action Check if system is under engineered. Reboot. Call Customer Support if problem persists.
Technical Support Action Reduce system memory usage by shutting down unnecessary programs. Increase paging file size.
Severity Critical
Description Call Channel Resource failed to initialize with TAPI. Error reported is related to the reported API.
Impact Call Processing functionality not available.
Recovery Action Reboot. Call Customer Support if problem persists.
Technical Support Action Verify that TAPI Service is operational.
Severity Critical
Description Call Channel Resource failed to allocate memory for TAPI operation. Error reported is related to the reported API.
Impact Call Processing functionality not available.
Recovery Action Check if system is under engineered. Reboot. Call Customer Support if problem persists.
Technical Support Action Reduce system memory usage by shutting down unnecessary programs. Increase paging file size.
Severity Critical
Description System was installed with pre TAPI 2.0 version. The actual version installed is reported in the Label.
Impact Call Processing functionality not available.
Recovery Action Reboot. Call Customer Support if problem persists.
Technical Support Action Verify WinNT is installed properly. Reinstall WinNT.
Severity Critical
Description DS0 Channel not configured in TAPI.
Impact Call Processing functionality not available.
Recovery Action Reboot. Call Customer Support if problem persists.
Technical Support Action Perform Dummy Upgrade. Configure TAPI from Control Panel.
Severity Critical
Description Failed to Create thread for processing TAPI messages.
Impact Call Processing functionality not available.
Recovery Action Reboot. Call Customer Support if problem persists.
Technical Support Action Shutdown and restart EMCI Service. Check error reported. Check memory hardware.
Severity Minor
Description Failed to query TAPI LINE Device. A LINE maps to a DS0 channel. Error reported is related to the reported API.
Impact Call Processing functionality not available from the reported DS0 channel.
Recovery Action Reboot. Call Customer Support if problem persists.
Technical Support Action Check return code. Restart EMCI. Check memory hardware.
Severity Major
Description Error detected while performing operation in TAPI thread. Error reported is related to the reported API.
Impact Telephony or Media related operations may fail.
Recovery Action Call Customer Support.
Technical Support Action Call Customer Support.
Severity Major
Description Error setting up record retrieval or retrieving record from database for the report object. Error reported is related to the reported API.
Impact The report MPB, DS30 or DS0 will not be available for call processing.
Recovery Action Reboot. Call Customer Support if problem persists.
Technical Support Action Check error code. Reconfigure the Database. Verify the integrity of the database.
Severity Critical
Description Call Channel Resource Package Service Provider start up error. Error reported is related to the reported API.
Impact Call Processing functionality not available.
Recovery Action Reboot. Call Customer Support if problem persists.
Technical Support Action Check error code. Verify the operation of CTM Service. Restart CTM Service and EMCI.
Severity Critical
Description Call Channel Resource Package Service Provider start up error. Error reported is related to the reported API. Object Instance not available.
Impact Call Processing functionality not available.
Recovery Action Reboot. Call Customer Support if problem persists.
Technical Support Action Check error code. Verify the operation of CTM Service. Restart EMCI.
Severity Critical
Description Failed to allocate memory at CCr Package Service Provider (SP) start up. Error reported is related to the reported API.
Impact Call Processing functionality not available.
Recovery Action Reboot. Call Customer Support if problem persists.
Technical Support Action Reduce system memory usage by shutting down unnecessary programs. Increase paging file size.
Severity Major
Description Call Channel Resource MPB Service Provider start up error. Error reported is related to the reported API.
Impact Call Processing functionality not available for the reported MPB.
Recovery Action Reboot. Call Customer Support if problem persists.
Technical Support Action Check error code. Verify the operation of CTM Service. Restart CTM Service and EMCI.
Severity Major
Description Call Channel Resource MPB Service Provider start up error. Error reported is related to the reported API. Object Instance is not available.
Impact Call Processing functionality not available for the reported MPB.
Recovery Action Reboot. Call Customer Support if problem persists.
Technical Support Action Check error code. Verify the operation of CTM Service. Restart CTM Service and EMCI.
Severity Major
Description Failed to allocate memory at CCr MPB Service Provider (SP) start up. Error reported is related to the reported API.
Impact Call Processing functionality not available for the reported MPB.
Recovery Action Reboot. Call Customer Support if problem persists.
Technical Support Action Reduce system memory usage by shutting down unnecessary programs. Increase paging file size.
Severity Major
Description Call Channel Resource DS30 Service Provider start up error. Error reported is related to the reported API.
Impact Call Processing functionality not available for the reported DS30 link.
Recovery Action Reboot. Call Customer Support if problem persists.
Technical Support Action Check error code. Verify the operation of CTM Service. Restart CTM Service and EMCI.
Severity Major
Description Call Channel Resource DS30 Service Provider start up error. Error reported is related to the reported API. Object Instance is not available.
Impact Call Processing functionality not available for the reported DS30 link.
Recovery Action Reboot. Call Customer Support if problem persists.
Technical Support Action Check error code. Verify the operation of CTM Service. Restart CTM Service and EMCI.
Severity Major
Description Failed to allocate memory at CCr DS30 Service Provider (SP) start up. Error reported is related to the reported API.
Impact Call Processing functionality not available for the reported DS30 link.
Recovery Action Reboot. Call Customer Support if problem persists.
Technical Support Action Reduce system memory usage by shutting down unnecessary programs. Increase paging file size.
Severity Major
Description Failed to obtain number of records in table. Error reported is related to the reported API.
Impact The report MPB, DS30 or DS0 will not be available for call processing.
Recovery Action Reboot. Call Customer Support if problem persists.
Technical Support Action Verify the integrity of the database.
Severity Major
Description Call Channel Resource Service Provider start up error. Error reported is related to the reported API.
Impact The reported DS0 will not be available for call processing.
Recovery Action Reboot. Call Customer Support if problem persists.
Technical Support Action Check error code. Verify the operation of CTM Service. Restart CTM Service and EMCI.
Severity Major
Description Call Channel Resource Service Provider Creation failed. Error reported is related to the reported API.
Impact The reported DS0 will not be available for call processing.
Recovery Action Reboot. Call Customer Support if problem persists.
Technical Support Action Check error code. Verify the operation of CTM Service. Restart CTM Service and EMCI.
Severity Major
Description Call Channel Resource Service Provider Creation failed. Error reported is related to the reported API.
Impact The reported DS0 will not be available for call processing.
Recovery Action Reboot. Call Customer Support if problem persists.
Technical Support Action Reduce system memory usage by shutting down unnecessary programs. Increase paging file size.
Severity Major
Description Call Channel Resource failed to set up Run Time Control (RTC). Error reported is related to the reported API.
Impact Media processing operation problem.
Recovery Action Reboot. Call Customer Support if problem persists.
Technical Support Action Check error code. Verify the operation of CTM Service. Restart CTM Service and EMCI.
Severity Minor
Description Call Channel Resource shutdown failed.
Impact The reporting DS0 will not be available for call processing.
Recovery Action Call Customer Support if problem persists.
Technical Support Action Check error code. Verify the operation of CTM Service. Restart CTM Service and EMCI.
Severity Major
Description Call Channel Resource MPB Service Provider Maintenance failed. Error reported is related to the reported API.
Impact Maintenance operation not performed on the MPB.
Recovery Action Reboot. Call Customer Support if problem persists.
Technical Support Action Check error code. Verify the operation of CTM Service. Restart CTM Service and EMCI.
Severity Major
Description Call Channel Resource MPB Service Provider Maintenance failed. Error reported is related to the reported API. Object Instance is not available.
Impact Maintenance operation not performed.
Recovery Action Reboot. Call Customer Support if problem persists.
Technical Support Action Check error code. Verify the operation of CTM Service. Restart CTM Service and EMCI.
Severity Minor
Description Call Channel Resource DS30 Service Provider Maintenance failed. Error reported is related to the reported API.
Impact Maintenance operation not performed.
Recovery Action Call Customer Support if problem persists.
Technical Support Action Check error code. Verify the operation of CTM Service. Restart CTM Service and EMCI.
Severity Minor
Description Call Channel Resource DS30 Service Provider Maintenance failed. Error reported is related to the reported API. Object Instance is not available.
Impact Maintenance operation not performed.
Recovery Action Call Customer Support if problem persists.
Technical Support Action Check error code. Verify the operation of CTM Service. Restart CTM Service and EMCI.
Severity Minor
Description Call Channel Resource DS0 Service Provider Maintenance failed. Error reported is related to the reported API.
Impact Maintenance operation not performed.
Recovery Action Call Customer Support if problem persists.
Technical Support Action Check error code. Verify the operation of CTM Service. Restart CTM Service and EMCI.
Severity Minor
Description Call Channel Resource DS0 Service Provider Maintenance failed. Error reported is related to the reported API. Object Instance is not available.
Impact Maintenance operation not performed.
Recovery Action Call Customer Support if problem persists.
Technical Support Action Check error code. Verify the operation of CTM Service. Restart CTM Service and EMCI.
Severity Minor
Description Failed to perform maintenance operation on the DS0 channel. Error reported is related to the reported API.
Impact DS0 not available for call processing or call not answered.
Recovery Action Call Customer Support if problem persists.
Technical Support Action Verify the API and the reported component.
Severity Major
Description Failed to perform time switch operation on the reported DS0 object. Error reported is related to the reported API.
Impact Media data will not be transmitted or received properly.
Recovery Action Reboot. Call Customer Support if problem persists.
Technical Support Action Run Time Switch diagnostic.
Severity Major
Description DS30 link is disconnected or has frame slip.
Impact Media data will not be transmitted or received properly.
Recovery Action Reboot. Call Customer Support if problem persists.
Technical Support Action Run Time Switch diagnostic.
Severity Info
Description DS30 link is re-connected.
Impact Media data available.
Recovery Action Not Applicable
Technical Support Action Not Applicable
Severity Major
Description A program error occurred in starting a Media Service or Service Provider. Determine the affected object from the instance name of the event browser.
Impact Media Resources may be unavailable. Some MPC channels may not be in-service.
Recovery Action Manually shutdown and enable the affected objects and run out-of-service diagnostics.
Technical Support Action This could indicate a software problem in the media services. Restart the EMCI service. If the problem persists, it may be a hardware problem.
Severity Minor
Description A program error occurred in shutting down a Media Service or Service Provider. Determine the affected object from the instance name of the event browser.
Impact Media Resources may not be shut down properly.
Recovery Action If the affected objects are MPC channels, you can try to shutdown and re-enable their parent MPC Board.
Technical Support Action This could indicate a software problem in the media services. Restart the EMCI service or try to shutdown the affected object from the telephony utility.
Severity Major
Description A program error occurred in handling a command request by a Media Service Provider. Determine the affected object from the instance name of the event browser.
Impact Maintenance request may fail to execute on affected object.
Recovery Action Retry the command. Manually shutdown the affected object and run out-of-service diagnostics.
Technical Support Action This could indicate a software problem in the media services. Restart the EMCI service.
Severity Major
Description A program error occurred in handling a system callback by a Media Service Provider. Determine the affected object from the instance name of the event browser.
Impact Maintenance request or system action may fail to execute.
Recovery Action Retry the command. Manually shutdown the affected object and run out-of-service diagnostics.
Technical Support Action This could indicate a software problem in the media services. Restart the EMCI service.
Severity Major
Description A program error occurred in accessing the database by a Media Service Provider. Determine the affected object from the instance name of the event browser.
Impact Command request or system action may fail to execute.
Recovery Action Check that the database shows as Started from the Services Applet.
Technical Support Action Check that the database is installed and configured properly. This could indicate a software problem in the media services. Take actions based on the return code.
Severity Major
Description A Media Object fails to respond to Maintenance SP Audit.
Impact The Media Object that fails the audit is marked as faulty.
Recovery Action Manually shutdown the affected objects and run out-of-service diagnostics.
Technical Support Action This could indicate a software problem in the media services. Restart the EMCI service.
Severity Critical
Description An unhandled program exception was caught by the Middleware Media Service Provider.
Impact The Media service provider will terminate, and be restarted by the MAS EMCI service. All media channels controlled by this service provider may experience service problems. To recover, the system will automatically reboot if this recovery action has been enabled.
Recovery Action Check the event log for other DSP and disk errors reported before this event. For DSP errors, run the DSP diagnostics on the affected DSPs. Replace any faulty hardware. If disk media problems are observed, contact customer support.
Technical Support Action Ensure no DSP related events are being issued to the event log. Ensure no disk related errors are being reported to the event log. If either of these problems are observed, use the DSP diagnostics and WinNT disk analysis tools to correct them. If no problems are observed, forward the D:\WinNT\drwtsn32.log file, the D:\WinNT\user.dmp file, and the event log to product support for analysis.
Severity Debug
Description A command received by the voice handler could not be executed because it is invalid for the handler's current state. The command will be ignored.
Impact The command will not be executed. The impact to an application depends on the command and the application.
Recovery Action If the problem persists, call your customer support representative.
Technical Support Action This could indicate software problem in the DSP voice driver. If the problem persists, contact your Nortel support organization.
Severity Minor
Description The voice LLS hander has received an ignored and unexpected command from the LLS.
Impact The command is ignored.
Recovery Action If the problem persists, call your customer support representative.
Technical Support Action This could indicate software problem in the DSP voice driver. If the problem persists, contact your Nortel support organization.
Severity Debug
Description A voice play command was received but could not be started for the reason indicated by the return code. Typically, this error indicates a file in the play list could not be opened.
Impact The voice play is not started.
Recovery Action If the problem persists, call your customer support representative.
Technical Support Action This could indicate software problem in the DSP voice driver. If the problem persists, contact your Nortel support organization.
Severity Major
Description A command could not be sent to the DSP firmware. The command will not be executed.
Impact The command is not executed. The impact will depend on the particular application requesting the command.
Recovery Action This could indicate a hardware problem. Diagnostics should be run on the indicated hardware.
Technical Support Action Re-flash the indicated DSP. Use c52util to verify the DSP is operational. Replace the hardware on which the problem was reported.
Severity Minor
Description An error occurred while a DSP end-of-block message was being processed.
Impact The current play operation will be terminated.
Recovery Action Disable and re-enable the channel. If the problem persists, call your customer support representative.
Technical Support Action This could indicate software problem in the DSP voice driver. If the problem persists, contact your Nortel support organization.
Severity Debug
Description An application has requested a record be started, but the command could not be executed.
Impact The recording is not started.
Recovery Action If the problem persists, call your customer support representative.
Technical Support Action This could indicate software problem in the DSP voice driver. If the problem persists, contact your Nortel support organization.
Severity Minor
Description During a record session, an error occurred while processing an end-of-block message from the DSP firmware.
Impact The recording is terminated.
Recovery Action Disable and re-enable the channel. If the problem persists, call your customer support representative.
Technical Support Action This could indicate software problem in the DSP voice driver. If the problem persists, contact your Nortel support organization.
Severity Minor
Description An Run-Time-Control action could not be performed by a player/recorder resource.
Impact The impact will depend on the particular action that had the problem. The action may not be executed.
Recovery Action If the problem persists, call your customer support representative.
Technical Support Action This could indicate a software error.
Severity Minor
Description A player/recorder resource could not retrieve context data for a voice channel. The context data is required to execute commands on the channel.
Impact The impact will depend on the particular command that had the problem. The command will not be executed.
Recovery Action If the problem persists, call your customer support representative.
Technical Support Action This could indicate a software error. Reboot the server.
Severity Major
Description The DSP must have the VoiceTel package loaded during a play operation. The package could not be loaded by the player resource.
Impact The play command can not be executed.
Recovery Action If the problem persists, call your customer support representative.
Technical Support Action This could indicate a configuration problem. Re-flash the MPC. Verify the configuration in the nbspc database table.
Severity Debug
Description A play/record command sent by an application contained invalid RTC data. The RTC data was ignored.
Impact The play command is executed, but the RTC's will not be activated.
Recovery Action If the problem persists, call your customer support representative.
Technical Support Action This could indicate an application software error.
Severity Minor
Description The server has attempted to enable or disable a run-time-control condition that is not known to the voice resources. The enable/disable will be ignored.
Impact The player/recorder may not be operate on the MPC channel.
Recovery Action If the problem happens on all channels, reboot the server.
Technical Support Action Check for correlated application (MCE) event codes.
Severity Minor
Description A voice resource attempted to send an event to an application but the operation could not be completed.
Impact The event will be ignored.
Recovery Action Ensure that all application related services are running. Check for related application event codes.
Technical Support Action This could indicate an application or player/recorder resource software error. Reboot the server if MCE is down.
Severity Minor
Description A player or recorder resource attempted to stop a voice operation, but the stop failed.
Impact The stop will not be executed.
Recovery Action Reload the channel.
Technical Support Action Restart the EMCI service. Contact you support organization.
Severity Minor
Description A voice resource attempted to control a timer for a voice operation, but the command failed.
Impact The operation will not be timed. Timers are used to limit play and record durations.
Recovery Action Reload the channel. If the problem persists, call your customer support representative.
Technical Support Action Restart the EMCI service. This could indicate an resource software error. Contact your support organization.
Severity Minor
Description The server has attempted to enable or disable a run-time-control condition but the completion function for the operation failed.
Impact The RTC operation may not have been performed.
Recovery Action Reload the channel. If the problem occurs on all channels, reboot the server.
Technical Support Action Check for correlated application events in the event log. This could indicate an application software error. Contact your support organization.
Severity Major
Description The fax component was unable to allocate memory for setup.
Impact The fax command will not start. The system is running low on memory. Possible memory leakages occurred.
Recovery Action Use the Windows NT Performance Monitor to determine which processes are using excessive memory. Look for other event codes indicating memory allocation failures.
Technical Support Action Restart processes which are leaking memory. Restart middleware by stopping and starting the EMCI service.
Severity Minor
Description The CTM context data describing the state of a channel could not be retrieved by the FAX resource.
Impact Without channel context data, the fax command cannot proceed on a channel.
Recovery Action If the problem persists, please contact your customer support.
Technical Support Action This could indicate a software error in a middleware component. Look at the CTM return code for more information.
Severity Major
Description Before executing a FAX command, the MPC must be loaded with FAX firmware. This has failed.
Impact The FAX command will not complete.
Recovery Action This could indicate a configuration problem. Check that the MPC channel was configured for FAX. If the configuration is correct, there could be a problem with the MPC. Run 'out of service' diagnostics. If the diagnostics fail, replace the MPC.
Technical Support Action Check the MPC return code. Check the database tables for proper configuration using the support tools (ie. Isql ). Try restarting middleware by restarting the EMCI service.
Severity Minor
Description The expected parameters for the specified command could not be retrieved.
Impact The fax command cannot start.
Recovery Action If the problem persists, please contact customer service.
Technical Support Action This could indicate an application software error. Check the CTM return code for more information. Try restarting middleware by restarting the EMCI service. If the problem persists, try a dummy upgrade of the CTM dlls.
Severity Major
Description The specified command was not able to notify an application [ie. MCE, SCCS] of its completion. The application will not get the completion result from the specified command.
Impact The application [i.e. MCE, SCCS] may hang as it waits for the completion event from the fax operation.
Recovery Action If the application [i.e. MCE, SCCS] hangs, restart the application - this may require a reboot.
Technical Support Action Check the CTM return code.
Severity Minor
Description When sending a FAX event to an application, the resource could not get the address of its resource group. The event will not be sent.
Impact The application may not receive the caller ID of the remote fax machine.
Recovery Action If the problem persists, contact customer service.
Technical Support Action Check the CTM return code. Try restarting middleware by restarting the EMCI service, and the CTM Server.
Severity Minor
Description The FAX resource was unable to send an event to an application.
Impact The application may not receive the caller ID of the remote fax machine.
Recovery Action If the problem persists, contact customer service.
Technical Support Action Check the CTM return code. Try restarting middleware by restarting the EMCI service, and the CTM Server.
Severity Major
Description An MPC function call failed, the requested Fax resource operation was not completed.
Impact The impact will depend on the currently executing Fax command. The FAX command, ( i.e. transmit, receive, config, abort) will likely be abnormally terminated.
Recovery Action If the problem persists, disable and re-enable the MPC channel. Run 'out of service diagnostics'. If diagnostics fail, replace the MPC.
Technical Support Action If there is nothing wrong with the MPC, there could be a problem in the MPC dll - check the return code for more information.
Severity Minor
Description Failed to execute a FAX stream related operation. The error code is most likely a MMFS error.
Impact The transmit or receive operation will most likely fail.
Recovery Action Retry the operation. Check for other file system (MMFS) related problems.
Technical Support Action Use MMFS support tools (misa_ci, nbosa_ci, vsmup) to verify that the fax file exists, and is not corrupted.
Severity Minor
Description The requested FAX command cannot be completed because the resource is busy executing a previous command.
Impact The new request for transmit or receive will fail.
Recovery Action Retry the command on the same channel after some delay. If the channel appears stuck, disable and reenable the channel. If this does not succeed, run out of service diagnostics and replace the MPC if problems are revealed.
Technical Support Action Restart middleware by restarting the EMCI service.
Severity Minor
Description An error message is reported by the MPC (Bad block, overrun etc.).
Impact The transmit or receive command could fail, depending on the type of the error and the frequency. The impact will depend on the error message and the executing application.
Recovery Action Retry the command on the same channel. If the problem persists, disable and reenable the channel. If this does not succeed, run out of service diagnostics and replace the MPC if problems are revealed.
Technical Support Action Restart middleware by restarting the EMCI service.
Severity Minor
Description An unknown MPC event or LLS command has been received. The event is ignored.
Impact Not Applicable
Recovery Action Report the problem to customer service.
Technical Support Action This could indicate a software error in the middleware components. Check that the correct versions of nbdsp.dll or nblls_dll.dll are being used. If the versions are incorrect, replace them and restart middleware by restarting the EMCI service.
Severity Major
Description An unknown exception was caught in the FAX handler.
Impact The MPC channel will be reloaded.
Recovery Action If the problem persists, please contact customer service.
Technical Support Action This could indicate a software error in a middleware component. Try restarting middleware by restarting the EMCI service.
Severity Minor
Description During FAX transmission, the FAX LLS was unable to create a trim-tab.
Impact The FAX will not have trim-tabs.
Recovery Action Check that the length of the trim tab string requested does not exceed the maximum of 150 characters. If the problem persists, please contact customer support.
Technical Support Action This could indicate a software error. Try restarting middleware by restarting the EMCI service.
Severity Major
Description An FAX resource state is unknown - neither in send or receive states.
Impact The current commands will fail.
Recovery Action If the problem persists, please contact customer service.
Technical Support Action This could indicate a software error. Try restarting middleware by restarting the EMCI service.
Severity Critical
Description Initialization with CTMedia services failed
Impact None of the Middleware related services could be brought up.
Recovery Action Make sure CTMedia service is running. If the problem persists, call customer support.
Technical Support Action This could indicate CTMedia service related error. Contact product support.
Severity Major
Description Session creation with CTMedia services failed
Impact None of the Middleware related services could be brought up.
Recovery Action Make sure CTMedia service is running and all the necessary profiles are installed. If the problem persists, call customer support.
Technical Support Action This could indicate CTMedia service related error. Contact product support.
Severity Major
Description Initialization with Blue Database failed.
Impact None of the Middleware related services could be brought up.
Recovery Action Make sure Blue database is configured and running. If the problem persists, call customer support.
Technical Support Action This could indicate Blue Database related error. Contact product support.
Severity Major
Description Could not read from the Blue database.
Impact Details about Middleware related services will not be available for DMI.
Recovery Action Make sure Blue database is configured and running. If the problem persists, call customer support.
Technical Support Action This could indicate Blue Database related error. Contact product support.
Severity Debug
Description Could not create KV set for passing data to CTMedia server.
Impact No data can be passed to or from CTMedia services.
Recovery Action Make sure CTMedia services running. If the problem persists, call customer support.
Technical Support Action This could indicate CTMedia related error. Contact product support.
Severity Minor
Description Could not retrieve any status Information about Middleware services from CTMedia.
Impact No auditing or startup of Middleware services could be performed.
Recovery Action Check if the CTMedia server is running. If the problem persists, call customer support.
Technical Support Action This could indicate CTMedia related error. Contact product support.
Severity Minor
Description Could not perform any administration activities.
Impact No maintenance operation is possible.
Recovery Action Shutting down EMCI and CTMS and restarting should most likely clear this problem. If the problem persists, call customer support.
Technical Support Action This could indicate a problem with either EMCI or CTMS services. Contact product support.
Severity Major
Description Error registering EMCI with DMI service provider.
Impact No Middleware maintenance will be available.
Recovery Action Check if the DMI service provider is running. If the problem persists, call customer support.
Technical Support Action This could indicate problem with the DMI service provider. Contact product support.
Severity Debug
Description Error un-registering EMCI with DMI service provider.
Impact No session cleanup with DMI will be done.
Recovery Action Check if the DMI service provider is running. If the problem persists, call customer support.
Technical Support Action This could indicate problem with the DMI service provider. Contact product support.
Severity Debug
Description Problem occurred initializing tables for DMI groups.
Impact Maintenance operations could not be done.
Recovery Action Not Applicable
Technical Support Action Not Applicable
Severity Minor
Description Problem occurred initializing diagnostics interface.
Impact Start-up and off-line diagnostics will not be available.
Recovery Action Not Applicable
Technical Support Action Not Applicable
Severity Major
Description Problem occurred starting service thread for EMCI.
Impact EMCI will not be run.
Recovery Action Not Applicable
Technical Support Action Not Applicable
Severity Debug
Description Problem occurred while shutting down the EMCI.
Impact EMCI will not be shut down properly.
Recovery Action Not Applicable
Technical Support Action Not Applicable
Severity Debug
Description Problem occurred while creating table for Operation State.
Impact DMI operation will not be available for Operational state group.
Recovery Action Not Applicable
Technical Support Action Not Applicable
Severity Debug
Description Problem occurred while accessing the Operation State table.
Impact DMI operation will not be available for Operational state group.
Recovery Action Not Applicable
Technical Support Action Not Applicable
Severity Debug
Description Problem occurred while creating table for DSP group..
Impact DMI operation will not be available for DSP group
Recovery Action Not Applicable
Technical Support Action Not Applicable
Severity Debug
Description Problem occurred while creating table for DSP carrier group.
Impact DMI operation will not be available for DSP carrier group.
Recovery Action Not Applicable
Technical Support Action Not Applicable
Severity Major
Description Problem occurred while trying to startup a middleware service.
Impact Some or all middleware services provided will not be available.
Recovery Action Not Applicable
Technical Support Action Not Applicable
Severity Info
Description Problem occurred while trying to stop a middleware service.
Impact Some or all middleware services could not be stopped.
Recovery Action Not Applicable
Technical Support Action Not Applicable
Severity Info
Description A software exception detected by one of the EMCI module.
Impact Some or all middleware services may not function properly.
Recovery Action Not Applicable
Technical Support Action Not Applicable
Severity Debug
Description Problem occurred while creating table for Time switch group.
Impact DMI operation will not be available for time switch group.
Recovery Action Not Applicable
Technical Support Action Not Applicable
Severity Critical
Description Problem occurred while trying to get platform type Information.
Impact DMI operation will not be available to middleware groups.
Recovery Action Not Applicable
Technical Support Action Not Applicable
Severity Debug
Description Problem occurred while creating table for DSP channel group.
Impact DMI operation will not be available for DSP channel group.
Recovery Action Not Applicable
Technical Support Action Not Applicable
Severity Debug
Description Problem occurred while creating table for DS0 channel group.
Impact DMI operation will not be available for DS0 channel group.
Recovery Action Not Applicable
Technical Support Action Not Applicable
Severity Debug
Description Problem occurred while creating table for SCBUS group.
Impact DMI operation will not be available for SCBUS group.
Recovery Action Not Applicable
Technical Support Action Not Applicable
Severity Debug
Description Problem occurred while creating table for SCBUS cable group.
Impact DMI operation will not be available for SCBUS cable group.
Recovery Action Not Applicable
Technical Support Action Not Applicable
Severity Debug
Description Problem occurred while creating table for DS30X group.
Impact DMI operation will not be available for DS30X group.
Recovery Action Not Applicable
Technical Support Action Not Applicable
Severity Debug
Description Problem occurred while creating table for EMCI component group.
Impact DMI operation will not be available for EMCI component group.
Recovery Action Not Applicable
Technical Support Action Not Applicable
Severity Debug
Description Problem occurred while waiting for service terminate event or state change event.
Impact Service may not terminate or state change may not be reported.
Recovery Action Not Applicable
Technical Support Action Not Applicable
Severity Debug
Description Problem occurred while trying to report events to maintenance server.
Impact State change will not be reported.
Recovery Action Not Applicable
Technical Support Action Not Applicable
Severity Minor
Description Problem occurred while trying to connect to the server (Blue database, CTMS, DMI).
Impact EMCI may not function properly.
Recovery Action Not Applicable
Technical Support Action Not Applicable
Severity Debug
Description An error log is being ported from CTMS log files to fault management.
Impact Not Applicable
Recovery Action Not Applicable
Technical Support Action Not Applicable
Severity Debug
Description An error log is being ported from CTMS log files to fault management.
Impact Not Applicable
Recovery Action Not Applicable
Technical Support Action Not Applicable
Severity Debug
Description An error log is being ported from CTMS log files to fault management.
Impact Not Applicable
Recovery Action Not Applicable
Technical Support Action Not Applicable
Severity Debug
Description An error log is being ported from CTMS log files to fault management.
Impact Not Applicable
Recovery Action Not Applicable
Technical Support Action Not Applicable
Severity Info
Description EMCI has detected DMI server failure and automatic recovery is in progress.
Impact Not Applicable
Recovery Action Not Applicable
Technical Support Action Not Applicable
Severity Info
Description EMCI has detected CTMS server failure and automatic recovery is in progress.
Impact Not Applicable
Recovery Action Not Applicable
Technical Support Action Not Applicable
Severity Info
Description A complete Middleware shutdown could not be accomplished within given time.
Impact Not Applicable
Recovery Action Not Applicable
Technical Support Action Not Applicable
Severity Info
Description All services in Middleware have started.
Impact Not Applicable
Recovery Action Not Applicable
Technical Support Action Not Applicable
Severity Info
Description Middleware could not be started within given time.
Impact Not Applicable
Recovery Action Not Applicable
Technical Support Action Not Applicable
Severity Info
Description Not enough hardware present for the database configuration. One or more carrier cards may be missing or faulty.
Impact Not Applicable
Recovery Action Not Applicable
Technical Support Action Not Applicable
Severity Critical
Description Automatic System Reboot feature is not available due to an internal error.
Impact System may not recover from critical processes crash. Manual intervention may be required.
Recovery Action Not Applicable
Technical Support Action Not Applicable
Severity Info
Description Automatic System Reboot feature failed to terminate a system reboot.
Impact System will be rebooted to recover an error. User may not have a chance to investigate the error that cause the reboot.
Recovery Action Not applicable
Technical Support Action Not applicable
Severity Info
Description Automatic System Reboot feature has initiated a system reboot due to a critical process crash.
Impact System will reboot to recover an error. User may terminate this reboot if required.
Recovery Action Not applicable
Technical Support Action Not applicable
Severity Debug
Description An error occurred during the processing of a callback function for Signal Generator.
Impact Callback functions invoked by CTMS SIA may not be completed properly.
Recovery Action Not Applicable
Technical Support Action Not Applicable
Severity Major
Description The Private Memory (Static Memory) Arbitration Test failed due to an error while trying to load the DSP file
Impact The file arbit_s.c52 could be missing or corrupted. MPC-8 could also be faulty. Call processing will be affected.
Recovery Action Check that the file arbit_s.c52 is present . Rerun the DSP Diagnostics to confirm the result.
Other actions possible: Check that the drivers NTBUS and C52 are started, if not, start NTBUS then C52; or check that the MPC-8 card is present.
If problem persists, please contact your customer support representative for additional instructions.
Technical Support Action Make sure the file arbit_s.c52 is present and valid. Check that the MPC-8 card is present and powered on (indicated by an LED on the board). If the MPC-8 card is powered off, please refer to OAM for powering the MPC-8 on.
Run C52Util to check for DSP status and Flash load Version. Make sure the DSP is running and the Flash load is the most recent load. If the DSP is not running, start it from C52UTIL, then run MAT to courtesy down the DSP for running Diagnostics.
Please refer to C52Util online help for further assistance on how to operate C52Util. Run DSPFLASH on the selected DSP if the DSP Flash load is not recent. If all of the above fail, replace the MPC-8 card, it might be corrupted.
Severity Major
Description The Shared Memory (Dynamic Memory) Arbitration Test failed due to an error while trying to load the DSP file
Impact The file arbit_d.c52 could be missing or corrupted. MPC-8 could also be faulty. Call processing will be affected.
Recovery Action Check that the file arbit_d.c52 is present . Rerun the DSP Diagnostics to confirm the result.
Other actions possible: Check that the drivers NTBUS and C52 are started, if not, start NTBUS then C52; or check that the MPC-8 card is present.
If problem persists, please contact your customer support representative for additional instructions.
Technical Support Action Make sure the file arbit_d.c52 is present and valid. Check that the MPC-8 card is present and powered on (indicated by an LED on the board). If the MPC-8 card is powered off, please refer to OAM for powering the MPC-8 on.
Run C52Util to check for DSP status and Flash load Version. Make sure the DSP is running and the Flash load is the most recent load. If the DSP is not running, start it from C52UTIL, then run MAT to courtesy down the DSP for running Diagnostics.
Please refer to C52Util online help for further assistance on how to operate C52Util. Run DSPFLASH on the selected DSP if the DSP Flash load is not recent. If all of the above fail, replace the MPC-8 card, it might be corrupted.
Severity Minor
Description The CROSS (HOST accesses private memory, DSP accesses shared memory) Arbitration Test failed due to an error while trying to load the DSP file
Impact The files arbit_s.c52 and arbit_d.c52 could be missing or corrupted. MPC-8 could also be faulty. Call processing will be affected.
Recovery Action Check that the files arbit_s.c52 and arbit_d.c52 are present . Rerun the DSP Diagnostics to confirm the result.
Other actions possible: Check that the drivers NTBUS and C52 are started, if not, start NTBUS then C52; or check that the MPC-8 card is present.
If problem persists, please contact your customer support representative for additional instructions.
Technical Support Action Make sure the files arbit_s.c52 and arbit_d.c52 are present and valid. Check that the MPC-8 card is present and powered on (indicated by an LED on the board). If the MPC-8 card is powered off, please refer to OAM for powering the MPC-8 on.
Run C52Util to check for DSP status and Flash load Version. Make sure the DSP is running and the Flash load is the most recent load. If the DSP is not running, start it from C52UTIL, then run MAT to courtesy down the DSP for running Diagnostics.
Please refer to C52Util online help for further assistance on how to operate C52Util. Run DSPFLASH on the selected DSP if the DSP Flash load is not recent. If all of the above fail, replace the MPC-8 card, it might be corrupted.
Severity Major
Description The Memory Lock Test failed due to a problem in loading the DSP file
Impact The file lockxf.c52 could be missing or corrupted. MPC-8 could also be faulty. Call processing will be affected.
Recovery Action Check that the file lockxf.c52 is present . Rerun the DSP Diagnostics to confirm the result.
Other actions possible: Check that the drivers NTBUS and C52 are started, if not, start NTBUS then C52; or check that the MPC-8 card is present.
If problem persists, please contact your customer support representative for additional instructions.
Technical Support Action Make sure the file lockxf.c52 is present and valid. Check that the MPC-8 card is present and powered on (indicated by an LED on the board). If the MPC-8 card is powered off, please refer to OAM for powering the MPC-8 on.
Run C52Util to check for DSP status and Flash load Version. Make sure the DSP is running and the Flash load is the most recent load. If the DSP is not running, start it from C52UTIL, then run MAT to courtesy down the DSP for running Diagnostics.
Please refer to C52Util online help for further assistance on how to operate C52Util. Run DSPFLASH on the selected DSP if the DSP Flash load is not recent. If all of the above fail, replace the MPC-8 card, it might be corrupted.
Severity Information
Description USAGE ERROR: Duplicate Switch. A switch (/D, /S or /L) has been entered twice.
Impact The diagnostics will not run.
Recovery Action Usage Error - re-enter the command with all of the switches specified correctly.
Technical Support Action Usage Error - no Technical Support Actions are required.
Severity Information
Description USAGE ERROR: Invalid argument is entered on the command line
Impact The diagnostics will not run.
Recovery Action Usage Error - re-enter the command with all of the arguments specified correctly.
Technical Support Action Usage Error - no Technical Support Actions are required.
Severity Information
Description USAGE ERROR: Argument is missing
Impact The diagnostics will not run.
Recovery Action Usage Error - re-enter the command with all of the arguments specified correctly.
Technical Support Action Usage Error - no Technical Support Actions are required.
Severity Information
Description USAGE ERROR: An unrecognizable switch was entered
Impact The diagnostics will not run.
Recovery Action Usage Error - re-enter the command with all of the switches and arguments specified correctly.
Technical Support Action Usage Error - no Technical Support Actions are required.
Severity Information
Description USAGE ERROR: Invalid input was entered
Impact The diagnostics will not run.
Recovery Action Usage Error - re-enter the command with all of the switches and arguments specified correctly.
Technical Support Action Usage Error - no Technical Support Actions are required.
Severity Major
Description The Private Memory (Static Memory) Arbitration Test Failed.
Impact MPC-8 or DSP on the memory could be faulty. Memory is not accessible and all multimedia channels on the DSP may not be functioning, therefore call processing on that DSP will be affected.
Recovery Action Rerun the DSP Diagnostics to confirm the result. Other actions possible: Check that the drivers NTBUS and C52 are started, if not, start NTBUS then C52; or check that the MPC-8 card is present.
If problem persists, please contact your customer support representative for additional instructions.
Technical Support Action Check that the MPC-8 card is present and powered on (indicated by an LED on the board). If the MPC-8 card is powered off, please refer to OAM for powering the MPC-8 on.
Run C52Util to check for DSP status and Flash load Version. Make sure the DSP is running and the Flash load is the most recent load. If the DSP is not running, start it from C52UTIL, then run MAT to courtesy down the DSP for running Diagnostics.
Please refer to C52Util online help for further assistance on how to operate C52Util. Run DSPFLASH on the selected DSP if the DSP Flash load is not recent. If all of the above fail, replace the MPC-8 card, it might be corrupted.
Severity Major
Description The Shared Memory (Dynamic Memory) Arbitration Test Failed.
Impact MPC-8 or DSP on the memory could be faulty. Memory is not accessible and all multimedia channels on the DSP may not be functioning, therefore call processing on that DSP will be affected.
Recovery Action Rerun the DSP Diagnostics to confirm the result. Other actions possible: Check that the drivers NTBUS and C52 are started, if not, start NTBUS then C52; or check that the MPC-8 card is present.
If problem persists, please contact your customer support representative for additional instructions.
Technical Support Action Check that the MPC-8 card is present and powered on (indicated by an LED on the board). If the MPC-8 card is powered off, please refer to OAM for powering the MPC-8 on.
Run C52Util to check for DSP status and Flash load Version. Make sure the DSP is running and the Flash load is the most recent load. If the DSP is not running, start it from C52UTIL, then run MAT to courtesy down the DSP for running Diagnostics.
Please refer to C52Util online help for further assistance on how to operate C52Util. Run DSPFLASH on the selected DSP if the DSP Flash load is not recent. If all of the above fail, replace the MPC-8 card, it might be corrupted.
Severity Major
Description The CROSS (HOST accesses private memory, DSP accesses shared memory) Arbitration Test Failed.
Impact MPC-8 or DSP on the memory could be faulty. Memory is not accessible and all MultiMediamultimedia channels on the DSP may not be functioning, therefore call processing on that DSP will be affected.
Recovery Action Rerun the DSP Diagnostics to confirm the result. Other actions possible: Check that the drivers NTBUS and C52 are started, if not, start NTBUS then C52; or check that the MPC-8 card is present.
If problem persists, please contact your customer support representative for additional instructions.
Technical Support Action Check that the MPC-8 card is present and powered on (indicated by an LED on the board). If the MPC-8 card is powered off, please refer to OAM for powering the MPC-8 on.
Run C52Util to check for DSP status and Flash load Version. Make sure the DSP is running and the Flash load is the most recent load. If the DSP is not running, start it from C52UTIL, then run MAT to courtesy down the DSP for running Diagnostics.
Please refer to C52Util online help for further assistance on how to operate C52Util. Run DSPFLASH on the selected DSP if the DSP Flash load is not recent. If all of the above fail, replace the MPC-8 card, it might be corrupted.
Severity Major
Description The Data Bus Integrity Test Failed.
Impact MPC-8 or DSP on the memory could be faulty. Memory is not accessible and all multimedia channels on the DSP may not be functioning, therefore call processing on that DSP will be affected.
Recovery Action Rerun the DSP Diagnostics to confirm the result. Other actions possible: Check that the drivers NTBUS and C52 are started, if not, start NTBUS then C52; or check that the MPC-8 card is present.
If problem persists, please contact your customer support representative for additional instructions.
Technical Support Action Check that the MPC-8 card is present and powered on (indicated by an LED on the board). If the MPC-8 card is powered off, please refer to OAM for powering the MPC-8 on.
Run C52Util to check for DSP status and Flash load Version. Make sure the DSP is running and the Flash load is the most recent load. If the DSP is not running, start it from C52UTIL, then run MAT to courtesy down the DSP for running Diagnostics.
Please refer to C52Util online help for further assistance on how to operate C52Util. Run DSPFLASH on the selected DSP if the DSP Flash load is not recent. If all of the above fail, replace the MPC-8 card, it might be corrupted.
Severity Major
Description The Address Bus Integrity Test Failed.
Impact MPC-8 or DSP on the memory could be faulty. Memory is not accessible and all multimedia channels on the DSP may not be functioning, therefore call processing on that DSP will be affected.
Recovery Action Rerun the DSP Diagnostics to confirm the result. Other actions possible: Check that the drivers NTBUS and C52 are started, if not, start NTBUS then C52; or check that the MPC-8 card is present.
If problem persists, please contact your customer support representative for additional instructions.
Technical Support Action Check that the MPC-8 card is present and powered on (indicated by an LED on the board). If the MPC-8 card is powered off, please refer to OAM for powering the MPC-8 on.
Run C52Util to check for DSP status and Flash load Version. Make sure the DSP is running and the Flash load is the most recent load. If the DSP is not running, start it from C52UTIL, then run MAT to courtesy down the DSP for running Diagnostics.
Please refer to C52Util on-line help for further assistance on how to operate C52Util. Run DSPFLASH on the selected DSP if the DSP Flash load is not recent. If all of the above fail, replace the MPC-8 card, it might be corrupted.
Severity Major
Description The Memory Lock Test Failed
Impact MPC-8 or DSP on the memory could be faulty. Memory is not accessible and all multimedia channels on the DSP may not be functioning, therefore call processing on that DSP will be affected.
Recovery Action Rerun the DSP Diagnostics to confirm the result. Other actions possible: Check that the drivers NTBUS and C52 are started, if not, start NTBUS then C52; or check that the MPC-8 card is present.
If problem persists, please contact your customer support representative for additional instructions.
Technical Support Action Check that the MPC-8 card is present and powered on (indicated by an LED on the board). If the MPC-8 card is powered off, please refer to OAM for powering the MPC-8 on.
Run C52Util to check for DSP status and Flash load Version. Make sure the DSP is running and the Flash load is the most recent load. If the DSP is not running, start it from C52UTIL, then run MAT to courtesy down the DSP for running Diagnostics.
Please refer to C52Util on-line help for further assistance on how to operate C52Util. Run DSPFLASH on the selected DSP if the DSP Flash load is not recent. If all of the above fail, replace the MPC-8 card, it might be corrupted.
Severity Major
Description The Short Shared Memory (Dynamic Memory) Test Failed
Impact MPC-8 or DSP on the memory could be faulty. Memory is not accessible and all multimedia channels on the DSP may not be functioning, therefore call processing on that DSP will be affected.
Recovery Action Rerun the DSP Diagnostics to confirm the result. Other actions possible: Check that the drivers NTBUS and C52 are started, if not, start NTBUS then C52; or check that the MPC-8 card is present.
If problem persists, please contact your customer support representative for additional instructions.
Technical Support Action Check that the MPC-8 card is present and powered on (indicated by an LED on the board). If the MPC-8 card is powered off, please refer to OAM for powering the MPC-8 on.
Run C52Util to check for DSP status and Flash load Version. Make sure the DSP is running and the Flash load is the most recent load. If the DSP is not running, start it from C52UTIL, then run MAT to courtesy down the DSP for running Diagnostics.
Please refer to C52Util on-line help for further assistance on how to operate C52Util. Run DSPFLASH on the selected DSP if the DSP Flash load is not recent. If all of the above fail, replace the MPC-8 card, it might be corrupted.
Severity Major
Description The Short Private Memory (Static Memory) Test Failed
Impact MPC-8 or DSP on the memory could be faulty. Memory is not accessible and all multimedia channels on the DSP may not be functioning, therefore call processing on that DSP will be affected.
Recovery Action Rerun the DSP Diagnostics to confirm the result. Other actions possible: Check that the drivers NTBUS and C52 are started, if not, start NTBUS then C52; or check that the MPC-8 card is present.
If problem persists, please contact your customer support representative for additional instructions.
Technical Support Action Check that the MPC-8 card is present and powered on (indicated by an LED on the board). If the MPC-8 card is powered off, please refer to OAM for powering the MPC-8 on.
Run C52Util to check for DSP status and Flash load Version. Make sure the DSP is running and the Flash load is the most recent load. If the DSP is not running, start it from C52UTIL, then run MAT to courtesy down the DSP for running Diagnostics.
Please refer to C52Util on-line help for further assistance on how to operate C52Util. Run DSPFLASH on the selected DSP if the DSP Flash load is not recent. If all of the above fail, replace the MPC-8 card, it might be corrupted.
Severity Major
Description DSP Diagnostics failed due to Major System Error
Impact MPC-8 or DSP on the memory could be faulty. All multimedia channels on the DSP may not be functioning, therefore call processing on that DSP will be affected.
Recovery Action Rerun the DSP Diagnostics to confirm the result. Other actions possible: Check that the drivers NTBUS and C52 are started, if not, start NTBUS then C52; or check that the MPC-8 card is present.
If problem persists, please contact your customer support representative for additional instructions.
Technical Support Action Please refer to return code for details on the error. Check that the MPC-8 card is present and powered on (indicated by an LED on the board). If the MPC-8 card is powered off, please refer to OAM for powering the MPC-8 on.
Run C52Util to check for DSP status and Flash load Version. Make sure the DSP is running and the Flash load is the most recent load. If the DSP is not running, start it from C52UTIL, then run MAT to courtesy down the DSP for running Diagnostics.
Please refer to C52Util on-line help for further assistance on how to operate C52Util. Run DSPFLASH on the selected DSP if the DSP Flash load is not recent. If all of the above fail, replace the MPC-8 card, it might be corrupted.
Severity Minor
Description C52 Diagnostic: the target DSP is in use by other processes. Some diagnostic operations bypassed
Impact The diagnostics are not performed.
Recovery Action Ensure that call processing is stopped on the target DSP and no other process is using this DSP.
Technical Support Action Not Applicable
Severity Information
Description For testing only.
Impact Not Applicable
Recovery Action Not Applicable
Technical Support Action Not Applicable
Severity Major
Description Software Error (Win32 errors).
Impact The DSP Diagnostics Tool (NBC52DGN.EXE) will not function as expected.
Recovery Action A software error occurred while executing the diagnostics.
Technical Support Action A software error occurred while executing the diagnostics. Please look into the Win32 return code and determine actions to be taken.
Severity Not Applicable
Description The SRAM arbitration test failed due to an error when trying to reset the DSP.
Impact Not Applicable
Recovery Action Not Applicable
Technical Support Action Not Applicable
Severity Not Applicable
Description The SRAM arbitration test failed due to an error when trying to run the DSP.
Impact Not Applicable
Recovery Action Not Applicable
Technical Support Action Not Applicable
Severity Not Applicable
Description The SRAM arbitration test failed due to a host memory verification error in the test routine.
Impact Not Applicable
Recovery Action Not Applicable
Technical Support Action Not Applicable
Severity Not Applicable
Description The SRAM arbitration test failed due to a DSP memory verification error in the test routine.
Impact Not Applicable
Recovery Action Not Applicable
Technical Support Action Not Applicable
Severity Not Applicable
Description The SRAM arbitration test failed due to the DSP stopping while executing the test.
Impact Not Applicable
Recovery Action Not Applicable
Technical Support Action Not Applicable
Severity Not Applicable
Description The SRAM arbitration test failed due to an unknown error.
Impact Not Applicable
Recovery Action Not Applicable
Technical Support Action Not Applicable
Severity Not Applicable
Description The DRAM arbitration test failed due to a failure while trying to reset the DSP.
Impact Not Applicable
Recovery Action Not Applicable
Technical Support Action Not Applicable
Severity Not Applicable
Description The DRAM arbitration test failed due to an error when trying to run the DSP.
Impact Not Applicable
Recovery Action Not Applicable
Technical Support Action Not Applicable
Severity Not Applicable
Description The DRAM arbitration test failed due to a host memory verification error in the test routine.
Impact Not Applicable
Recovery Action Not Applicable
Technical Support Action Not Applicable
Severity Not Applicable
Description The DRAM arbitration test failed due to a DSP memory verification error in the test routine.
Impact Not Applicable
Recovery Action Not Applicable
Technical Support Action Not Applicable
Severity Not Applicable
Description The DRAM arbitration test failed due to the DSP stopping while executing the test.
Impact Not Applicable
Recovery Action Not Applicable
Technical Support Action Not Applicable
Severity Not Applicable
Description The DRAM arbitration test failed due to an unknown error.
Impact Not Applicable
Recovery Action Not Applicable
Technical Support Action Not Applicable
Severity Not Applicable
Description The CROSS arbitration test failed due to a failure while trying to reset the DSP.
Impact Not Applicable
Recovery Action Not Applicable
Technical Support Action Not Applicable
Severity Not Applicable
Description The CROSS arbitration test failed due to an error when trying to run the DSP.
Impact Not Applicable
Recovery Action Not Applicable
Technical Support Action Not Applicable
Severity Not Applicable
Description The CROSS arbitration test failed due to a host memory verification error in the test routine.
Impact Not Applicable
Recovery Action Not Applicable
Technical Support Action Not Applicable
Severity Not Applicable
Description The CROSS arbitration test failed due to a DSP memory verification error in the test routine.
Impact Not Applicable
Recovery Action Not Applicable
Technical Support Action Not Applicable
Severity Not Applicable
Description The CROSS arbitration test failed due to the DSP stopping while executing the test.
Impact Not Applicable
Recovery Action Not Applicable
Technical Support Action Not Applicable
Severity Not Applicable
Description The CROSS arbitration test failed due to an unknown error.
Impact Not Applicable
Recovery Action Not Applicable
Technical Support Action Not Applicable
Severity Not Applicable
Description The bootup diagnostics failed because there was an error trying to reset the DSP.
Impact Not Applicable
Recovery Action Not Applicable
Technical Support Action Not Applicable
Severity Not Applicable
Description The bootup diagnostics failed because there was an error trying to run the DSP.
Impact Not Applicable
Recovery Action Not Applicable
Technical Support Action Not Applicable
Severity Not Applicable
Description The bootup diagnostics failed due to an unknown error.
Impact Not Applicable
Recovery Action Not Applicable
Technical Support Action Not Applicable
Severity Not Applicable
Description The bootup diagnostics failed because the executive task was not running .
Impact Not Applicable
Recovery Action Not Applicable
Technical Support Action Not Applicable
Severity Not Applicable
Description The bootup diagnostics failed because Host-based Address Decoding Test (test 1) failed.
Impact Not Applicable
Recovery Action Not Applicable
Technical Support Action Not Applicable
Severity Not Applicable
Description The bootup diagnostics failed because Host-based Data Lines Integrity Test (test 2) failed.
Impact Not Applicable
Recovery Action Not Applicable
Technical Support Action Not Applicable
Severity Not Applicable
Description The bootup diagnostics failed because Host-based Short DRAM Test (test 3) failed.
Impact Not Applicable
Recovery Action Not Applicable
Technical Support Action Not Applicable
Severity Not Applicable
Description The bootup diagnostics failed because Host-based Short SRAM Test (test 4) failed.
Impact Not Applicable
Recovery Action Not Applicable
Technical Support Action Not Applicable
Severity Not Applicable
Description The bootup diagnostics failed because Host-based C52 DMA Engine Test (test 5) failed.
Impact Not Applicable
Recovery Action Not Applicable
Technical Support Action Not Applicable
Severity Not Applicable
Description The bootup diagnostics failed because Host/DSP Interactive DRAM Lock Test (test 6) failed.
Impact Not Applicable
Recovery Action Not Applicable
Technical Support Action Not Applicable
Severity Not Applicable
Description The bootup diagnostics failed because Host/DSP Interactive Arbitration SRAM Test (test 7) failed.
Impact Not Applicable
Recovery Action Not Applicable
Technical Support Action Not Applicable
Severity Not Applicable
Description The bootup diagnostics failed because Host/DSP Interactive Arbitration DRAM Test (test 8) failed.
Impact Not Applicable
Recovery Action Not Applicable
Technical Support Action Not Applicable
Severity Not Applicable
Description The bootup diagnostics failed because Host/DSP Interactive Cross Arbitration Test (test 9) failed.
Impact Not Applicable
Recovery Action Not Applicable
Technical Support Action Not Applicable
Severity Not Applicable
Description The bootup diagnostics failed because DSP-based Test (test 10) failed.
Impact Not Applicable
Recovery Action Not Applicable
Technical Support Action Not Applicable
Severity Not Applicable
Description The bootup diagnostics failed because Host-based Address Decoding Test (test 1) crashed. NBC52DGN.EXE is not responding at all.
Impact Not Applicable
Recovery Action Not Applicable
Technical Support Action Not Applicable
Severity Not Applicable
Description The bootup diagnostics failed because Host-based Data Lines Integrity Test (test 2) crashed. NBC52DGN.EXE is not responding at all.
Impact Not Applicable
Recovery Action Not Applicable
Technical Support Action Not Applicable
Severity Not Applicable
Description The bootup diagnostics failed because Host-based Short DRAM Test (test 3) crashed. NBC52DGN.EXE is not responding at all.
Impact Not Applicable
Recovery Action Not Applicable
Technical Support Action Not Applicable
Severity Not Applicable
Description The bootup diagnostics failed because Host-based Short SRAM Test (test 4) crashed. NBC52DGN.EXE is not responding at all.
Impact Not Applicable
Recovery Action Not Applicable
Technical Support Action Not Applicable
Severity Not Applicable
Description The bootup diagnostics failed because Host-based C52 DMA Engine Test (test 5) crashed. NBC52DGN.EXE is not responding at all.
Impact Not Applicable
Recovery Action Not Applicable
Technical Support Action Not Applicable
Severity Not Applicable
Description The bootup diagnostics failed because Host/DSP Interactive DRAM Lock Test (test 6) crashed. NBC52DGN.EXE is not responding at all.
Impact Not Applicable
Recovery Action Not Applicable
Technical Support Action Not Applicable
Severity Not Applicable
Description The bootup diagnostics failed because Host/DSP Interactive Arbitration SRAM Test (test 7) crashed. NBC52DGN.EXE is not responding at all.
Impact Not Applicable
Recovery Action Not Applicable
Technical Support Action Not Applicable
Severity Not Applicable
Description The bootup diagnostics failed because Host/DSP Interactive Arbitration DRAM Test (test 8) crashed. NBC52DGN.EXE is not responding at all.
Impact Not Applicable
Recovery Action Not Applicable
Technical Support Action Not Applicable
Severity Not Applicable
Description The bootup diagnostics failed because Host/DSP Interactive Cross Arbitration Test (test 9) crashed. NBC52DGN.EXE is not responding at all.
Impact Not Applicable
Recovery Action Not Applicable
Technical Support Action Not Applicable
Severity Not Applicable
Description The bootup diagnostics failed because DSP-based Test (test 10) crashed. NBC52DGN.EXE is not responding at all.
Impact Not Applicable
Recovery Action Not Applicable
Technical Support Action Not Applicable
Severity Not Applicable
Description The data bus integrity test failed due to an error in resetting the DSP.
Impact Not Applicable
Recovery Action Not Applicable
Technical Support Action Not Applicable
Severity Not Applicable
Description The address bus integrity test failed due to an error in resetting the DSP.
Impact Not Applicable
Recovery Action Not Applicable
Technical Support Action Not Applicable
Severity Not Applicable
Description The data bus integrity test for the DRAM fails due to a memory verification error.
Impact Not Applicable
Recovery Action Not Applicable
Technical Support Action Not Applicable
Severity Not Applicable
Description The data bus integrity test for the SRAM fails due to a memory verification error.
Impact Not Applicable
Recovery Action Not Applicable
Technical Support Action Not Applicable
Severity Not Applicable
Description The diagnostic performed on the DRAM address bus failed due to a memory verification error.
Impact Not Applicable
Recovery Action Not Applicable
Technical Support Action Not Applicable
Severity Not Applicable
Description The diagnostic performed on the SRAM address bus failed due to a memory verification error.
Impact Not Applicable
Recovery Action Not Applicable
Technical Support Action Not Applicable
Severity Not Applicable
Description The memory lock test failed due to a problem in resetting the DSP.
Impact Not Applicable
Recovery Action Not Applicable
Technical Support Action Not Applicable
Severity Not Applicable
Description The memory lock test failed due to a problem in running the DSP.
Impact Not Applicable
Recovery Action Not Applicable
Technical Support Action Not Applicable
Severity Not Applicable
Description The memory lock test failed due to an unknown error.
Impact Not Applicable
Recovery Action Not Applicable
Technical Support Action Not Applicable
Severity Not Applicable
Description The memory lock test failed due to a write access failure in the XF locking mechanism.
Impact Not Applicable
Recovery Action Not Applicable
Technical Support Action Not Applicable
Severity Not Applicable
Description The memory lock test failed due to a read access failure in the XF locking mechanism.
Impact Not Applicable
Recovery Action Not Applicable
Technical Support Action Not Applicable
Severity Not Applicable
Description The short DRAM test failed due to an error in resetting the DSP.
Impact Not Applicable
Recovery Action Not Applicable
Technical Support Action Not Applicable
Severity Not Applicable
Description The short DRAM test failed due to a memory corruption.
Impact Not Applicable
Recovery Action Not Applicable
Technical Support Action Not Applicable
Severity Not Applicable
Description The short SRAM test failed due to an error in resetting the DSP.
Impact Not Applicable
Recovery Action Not Applicable
Technical Support Action Not Applicable
Severity Not Applicable
Description The short SRAM test failed due to a memory corruption.
Impact Not Applicable
Recovery Action Not Applicable
Technical Support Action Not Applicable
Severity Not Applicable
Description The executive task could not be mapped in.
Impact Not Applicable
Recovery Action Not Applicable
Technical Support Action Not Applicable
Severity Not Applicable
Description The executive task was not initialized properly.
Impact Not Applicable
Recovery Action Not Applicable
Technical Support Action Not Applicable
Severity Not Applicable
Description The message queue could not be read.
Impact Not Applicable
Recovery Action Not Applicable
Technical Support Action Not Applicable
Severity Not Applicable
Description The interrupt was not sent.
Impact Not Applicable
Recovery Action Not Applicable
Technical Support Action Not Applicable
Severity Not Applicable
Description The exec task could not be unmapped.
Impact Not Applicable
Recovery Action Not Applicable
Technical Support Action Not Applicable
Severity Not Applicable
Description Diagnostic will not run due to failure in allocation of memory for DSP Device structure.
Impact Not Applicable
Recovery Action Not Applicable
Technical Support Action Not Applicable
Severity Not Applicable
Description No C52 DSPs present.
Impact Not Applicable
Recovery Action Not Applicable
Technical Support Action Not Applicable
Severity Not Applicable
Description Unable to get DSP information.
Impact Not Applicable
Recovery Action Not Applicable
Technical Support Action Not Applicable
Severity Not Applicable
Description The DSP detected is not a C52 DSP.
Impact Not Applicable
Recovery Action Not Applicable
Technical Support Action Not Applicable
Severity Not Applicable
Description The selected DSP is not present.
Impact Not Applicable
Recovery Action Not Applicable
Technical Support Action Not Applicable
Severity Not Applicable
Description The selected DSP is not ON.
Impact Not Applicable
Recovery Action Not Applicable
Technical Support Action Not Applicable
Severity Not Applicable
Description Unable to map DSP.
Impact Not Applicable
Recovery Action Not Applicable
Technical Support Action Not Applicable
Severity Not Applicable
Description Unable to unmap DSP.
Impact Not Applicable
Recovery Action Not Applicable
Technical Support Action Not Applicable
Severity Not Applicable
Description Error code used for test only.
Impact Not Applicable
Recovery Action Not Applicable
Technical Support Action Not Applicable
Severity Not Applicable
Description TAPI error: Line error - Allocated - The line cannot be opened due to a persistent condition, such as that of a serial port being exclusively opened by another process.
Impact Not Applicable
Recovery Action Not Applicable
Technical Support Action Not Applicable
Severity Not Applicable
Description TAPI error: Line error - Bad Device ID - The specified device identifier or line device identifier (such as in a dwDeviceID parameter) is invalid or out of range.
Impact Not Applicable
Recovery Action Not Applicable
Technical Support Action Not Applicable
Severity Not Applicable
Description TAPI error: Line error - Bearer Mode Unavailable- The call bearer's mode cannot be changed to the specified bearer mode.
Impact Not Applicable
Recovery Action Not Applicable
Technical Support Action Not Applicable
Severity Not Applicable
Description TAPI error: Line error - Call unavailable- All call appearances on the specified address are currently in use.
Impact Not Applicable
Recovery Action Not Applicable
Technical Support Action Not Applicable
Severity Not Applicable
Description TAPI error: Line error - Completion overrun- The maximum number of outstanding call completions has been exceeded.
Impact Not Applicable
Recovery Action Not Applicable
Technical Support Action Not Applicable
Severity Not Applicable
Description TAPI error: Line error - Conference full- The maximum number of parties for a conference has been reached or the requested number of parties cannot be satisfied.
Impact Not Applicable
Recovery Action Not Applicable
Technical Support Action Not Applicable
Severity Not Applicable
Description TAPI error: Line error - Dial billing - The dialable address parameter contains dialing control characters that are not processed by the service provider.
Impact Not Applicable
Recovery Action Not Applicable
Technical Support Action Not Applicable
Severity Not Applicable
Description TAPI error: Line error - Dial dialtone - The dialable address parameter contains dialing control characters that are not processed by the service provider.
Impact Not Applicable
Recovery Action Not Applicable
Technical Support Action Not Applicable
Severity Not Applicable
Description TAPI error: Line error - Dial prompt - The dialable address parameter contains dialing control characters that are not processed by the service provider.
Impact Not Applicable
Recovery Action Not Applicable
Technical Support Action Not Applicable
Severity Not Applicable
Description TAPI error: Line error - Dial quiet -. The dialable address parameter contains dialing control characters that are not processed by the service provider
Impact Not Applicable
Recovery Action Not Applicable
Technical Support Action Not Applicable
Severity Not Applicable
Description TAPI error: Line error - Incompatible API version -. The application requested an API version or version range that is either incompatible or cannot be supported by the Telephony API implementation and/or corresponding service provider.
Impact Not Applicable
Recovery Action Not Applicable
Technical Support Action Not Applicable
Severity Not Applicable
Description TAPI error: Line error - Incompatible Ext version - The application requested an extension version range that is either invalid or cannot be supported by the corresponding service provider.
Impact Not Applicable
Recovery Action Not Applicable
Technical Support Action Not Applicable
Severity Not Applicable
Description TAPI error: Line error - INI file corrupt - The telephone.ini file cannot be read or understood properly by TAPI because of internal inconsistencies or formatting problems. For example, the (Locations), (Cards), or (Countries) section of the telephone.ini file may be corrupted or inconsistent.
Impact Not Applicable
Recovery Action Not Applicable
Technical Support Action Not Applicable
Severity Not Applicable
Description TAPI error: Line error - In Use - The line device is in use and cannot currently be configured, allow a party to be added, allow a call to be answered, allow a call to be placed, or allow a call to be transferred.
Impact Not Applicable
Recovery Action Not Applicable
Technical Support Action Not Applicable
Severity Not Applicable
Description TAPI error: Line error - Invalid address - A specified address is either invalid or not allowed. If invalid, the address contains invalid characters or digits, or the destination address contains dialing control characters (W, @, $) that are not supported by the service provider. If not allowed, the specified address is either not assigned to the specified line or is not valid for address redirection.
Impact Not Applicable
Recovery Action Not Applicable
Technical Support Action Not Applicable
Severity Not Applicable
Description TAPI error: Line error - Invalid address ID - The specified address identifier is either invalid or out of range.
Impact Not Applicable
Recovery Action Not Applicable
Technical Support Action Not Applicable
Severity Not Applicable
Description TAPI error: Line error Invalid address mode - The specified address mode is invalid.
Impact Not Applicable
Recovery Action Not Applicable
Technical Support Action Not Applicable
Severity Not Applicable
Description TAPI error: Line error - Invalid address state - dwAddressStates contains one or more bits that are not LINEADDRESSSTATE_constants.
Impact Not Applicable
Recovery Action Not Applicable
Technical Support Action Not Applicable
Severity Not Applicable
Description TAPI error: Line error - Invalid app handle - The application handle (such as specified by a hLineApp parameter) or the application registration handle is invalid.
Impact Not Applicable
Recovery Action Not Applicable
Technical Support Action Not Applicable
Severity Not Applicable
Description TAPI error: Line error - Invalid App Name - The specified application name is invalid. If an application name is specified by the application, it is assumed that the string does not contain any non-displayable characters and is zero-terminated.
Impact Not Applicable
Recovery Action Not Applicable
Technical Support Action Not Applicable
Severity Not Applicable
Description TAPI error: Line error - Invalid Bearer Mode - The specified bearer mode is invalid.
Impact Not Applicable
Recovery Action Not Applicable
Technical Support Action Not Applicable
Severity Not Applicable
Description TAPI error: Line error - Invalid call completion mode - The specified completion is invalid.
Impact Not Applicable
Recovery Action Not Applicable
Technical Support Action Not Applicable
Severity Not Applicable
Description TAPI error: Line error - Invalid call handle - The specified call handle is not valid. For example, the handle is not NULL but does not belong to the given line. In some cases, the specified call device handle is invalid.
Impact Not Applicable
Recovery Action Not Applicable
Technical Support Action Not Applicable
Severity Not Applicable
Description TAPI error: Line error - Invalid call parameters - The specified call parameters are invalid.
Impact Not Applicable
Recovery Action Not Applicable
Technical Support Action Not Applicable
Severity Not Applicable
Description TAPI error: Line error - Invalid call privilege - The specified call privilege parameter is invalid.
Impact Not Applicable
Recovery Action Not Applicable
Technical Support Action Not Applicable
Severity Not Applicable
Description TAPI error: Line error - Invalid call select - The specified select parameter is invalid.
Impact Not Applicable
Recovery Action Not Applicable
Technical Support Action Not Applicable
Severity Not Applicable
Description TAPI error: Line error - Invalid call state - The current state of a call is not in a valid state for the requested operation.
Impact Not Applicable
Recovery Action Not Applicable
Technical Support Action Not Applicable
Severity Not Applicable
Description TAPI error: Line error - Invalid call state list - The specified call state list is invalid.
Impact Not Applicable
Recovery Action Not Applicable
Technical Support Action Not Applicable
Severity Not Applicable
Description TAPI error: Line error - Invalid card - The permanent card identifier specified in dwCard could not be found in any entry in the (Cards) section in the registry.
Impact Not Applicable
Recovery Action Not Applicable
Technical Support Action Not Applicable
Severity Not Applicable
Description TAPI error: Line error - Invalid completion ID - The completion identifier is invalid.
Impact Not Applicable
Recovery Action Not Applicable
Technical Support Action Not Applicable
Severity Not Applicable
Description TAPI error: Line error - Invalid conference call handle - The specified call handle for the conference call is invalid or is not a handle for a conference call.
Impact Not Applicable
Recovery Action Not Applicable
Technical Support Action Not Applicable
Severity Not Applicable
Description TAPI error: Line error - Invalid consultation call handle - The specified call handle for the consultation call is invalid.
Impact Not Applicable
Recovery Action Not Applicable
Technical Support Action Not Applicable
Severity Not Applicable
Description TAPI error: Line error - Invalid country code - The specified country code is invalid.
Impact Not Applicable
Recovery Action Not Applicable
Technical Support Action Not Applicable
Severity Not Applicable
Description TAPI error: Line error - Invalid device class - The line device has no associated device for the given device class, or the specified line does not support the indicated device class.
Impact Not Applicable
Recovery Action Not Applicable
Technical Support Action Not Applicable
Severity Not Applicable
Description TAPI error: Line error - Invalid device handle.
Impact Not Applicable
Recovery Action Not Applicable
Technical Support Action Not Applicable
Severity Not Applicable
Description TAPI error: Line error - Invalid dial parameters.
Impact Not Applicable
Recovery Action Not Applicable
Technical Support Action Not Applicable
Severity Not Applicable
Description TAPI error: Line error - Invalid digit list - The specified digit list is invalid.
Impact Not Applicable
Recovery Action Not Applicable
Technical Support Action Not Applicable
Severity Not Applicable
Description TAPI error: Line error - Invalid digit mode - The specified digit mode is invalid.
Impact Not Applicable
Recovery Action Not Applicable
Technical Support Action Not Applicable
Severity Not Applicable
Description TAPI error: Line error - Invalid digits - The specified digit termination digits are invalid.
Impact Not Applicable
Recovery Action Not Applicable
Technical Support Action Not Applicable
Severity Not Applicable
Description TAPI error: Line error - Invalid extension version.
Impact Not Applicable
Recovery Action Not Applicable
Technical Support Action Not Applicable
Severity Not Applicable
Description TAPI error: Line error - Invalid group ID - The specified group identifier is invalid.
Impact Not Applicable
Recovery Action Not Applicable
Technical Support Action Not Applicable
Severity Not Applicable
Description TAPI error: Line error - Invalid line handle - The specified call, device, line device, or line handle is invalid.
Impact Not Applicable
Recovery Action Not Applicable
Technical Support Action Not Applicable
Severity Not Applicable
Description TAPI error: Line error - Invalid line state - The device configuration may not be changed in the current line state. The line may be in use by another application or a dwLineStates parameter contains one or more bits that are not LINEDEVSTATE_constants. The LINEERR_INVALLINESTATE value can also indicate that the device is DISCONNECTED or OUTOFSERVICE. These states are indicated by setting the bits corresponding to the LINDEVSTATUSFLAGS_CONNECTED and LINEDEVSTATUSFLAGS_INSERVICE values to 0 in the dwDevStatusFlags member of the LINEDEVSTATUS structure returned by the lineGetLineDevStatus function.
Impact Not Applicable
Recovery Action Not Applicable
Technical Support Action Not Applicable
Severity Not Applicable
Description TAPI error: Line error - Invalid location - The permanent location identifier specified in dwLocation could not be found in any entry in the (Locations) section in the registry.
Impact Not Applicable
Recovery Action Not Applicable
Technical Support Action Not Applicable
Severity Not Applicable
Description TAPI error: Line error - Invalid media list - The specified media list is invalid.
Impact Not Applicable
Recovery Action Not Applicable
Technical Support Action Not Applicable
Severity Not Applicable
Description TAPI error: Line error - Invalid media mode - The list of media types to be monitored contains invalid information. The specified media mode parameter is invalid or the service provider does not support the specified media mode. The media modes supported on the line are listed in the dwMediaModes member in the LINEDEVCAPS structure.
Impact Not Applicable
Recovery Action Not Applicable
Technical Support Action Not Applicable
Severity Not Applicable
Description TAPI error: Line error - Invalid message ID - The number given in dwMessageID is outside the range specified by the dwNumCompletionMessages member in the LINEADDRESSCAPS structure.
Impact Not Applicable
Recovery Action Not Applicable
Technical Support Action Not Applicable
Severity Not Applicable
Description TAPI error: Line error - parameter - A parameter (such as dwTollListOption, dwTranslateOptions, dwNumDigits, or a structure pointed to by lpDeviceConfig) contains invalid values, a country code is invalid, a window handle is invalid, or the specified forward list parameter contains invalid information.
Impact Not Applicable
Recovery Action Not Applicable
Technical Support Action Not Applicable
Severity Not Applicable
Description TAPI error: Line error - Invalid park ID.
Impact Not Applicable
Recovery Action Not Applicable
Technical Support Action Not Applicable
Severity Not Applicable
Description TAPI error: Line error - Invalid park mode - The specified park mode is invalid.
Impact Not Applicable
Recovery Action Not Applicable
Technical Support Action Not Applicable
Severity Not Applicable
Description TAPI error: Line error - Invalid pointer - One or more of the specified pointer parameters (such as lpCallList, lpdwAPIVersion, lpExtensionID, lpdwExtVersion, Iphlcon, IpLineDevCaps and IptoneList) are invalid or a required pointer to an output parameter is NULL.
Impact Not Applicable
Recovery Action Not Applicable
Technical Support Action Not Applicable
Severity Not Applicable
Description TAPI error: Line error - Invalid privilege select - An invalid flag or combination of flags was set for the dwPrivileges parameter.
Impact Not Applicable
Recovery Action Not Applicable
Technical Support Action Not Applicable
Severity Not Applicable
Description TAPI error: Line error - Invalid rate - The specified bearer mode is invalid.
Impact Not Applicable
Recovery Action Not Applicable
Technical Support Action Not Applicable
Severity Not Applicable
Description TAPI error: Line error - Invalid request mode - The specified request mode is invalid.
Impact Not Applicable
Recovery Action Not Applicable
Technical Support Action Not Applicable
Severity Not Applicable
Description TAPI error: Line error - Invalid terminal ID - The specified terminal mode parameter is invalid.
Impact Not Applicable
Recovery Action Not Applicable
Technical Support Action Not Applicable
Severity Not Applicable
Description TAPI error: Line error - Invalid terminal mode - The specified terminal mode parameter is invalid.
Impact Not Applicable
Recovery Action Not Applicable
Technical Support Action Not Applicable
Severity Not Applicable
Description TAPI error: Line error - Invalid timeout - Timeouts are not supported or the values of either or both of the parameters dwFirstDigitTimeout or dwinterDigitTimemout fall outside the valid range specified by the call's line-device capabilities.
Impact Not Applicable
Recovery Action Not Applicable
Technical Support Action Not Applicable
Severity Not Applicable
Description TAPI error: Line error - Invalid tone - The specified custom tone does not represent a valid tone or is composed of too many frequencies or the specified tone structure does not describe a valid tone.
Impact Not Applicable
Recovery Action Not Applicable
Technical Support Action Not Applicable
Severity Not Applicable
Description TAPI error: Line error - Invalid Tone List - The specified tone list is invalid.
Impact Not Applicable
Recovery Action Not Applicable
Technical Support Action Not Applicable
Severity Not Applicable
Description TAPI error: Line error - Invalid tone mode - The specified tone mode parameter is invalid.
Impact Not Applicable
Recovery Action Not Applicable
Technical Support Action Not Applicable
Severity Not Applicable
Description TAPI error: Line error - Invalid transfer mode - The specified transfer mode parameter is invalid.
Impact Not Applicable
Recovery Action Not Applicable
Technical Support Action Not Applicable
Severity Not Applicable
Description TAPI error: Line error - Line mapper failed - LINEMAPPER was the value passed in the dwDeviceID parameter but no lines were found that match the requirements specified in thelpCallParams parameter.
Impact Not Applicable
Recovery Action Not Applicable
Technical Support Action Not Applicable
Severity Not Applicable
Description TAPI error: Line error - No conference - The specified call is not a conference call handle or a participant call.
Impact Not Applicable
Recovery Action Not Applicable
Technical Support Action Not Applicable
Severity Not Applicable
Description TAPI error: Line error - No device - The specified device identifier, which was previously valid, is no longer accepted because the associated device has been removed from the system since TAPI was last initialized. Alternately, the line device has no associated device for the given device class.
Impact Not Applicable
Recovery Action Not Applicable
Technical Support Action Not Applicable
Severity Not Applicable
Description TAPI error: Line error - No driver - Either tapiaddr.dll could not be located or the telephone service provider for the specified device found that one of its components is missing or corrupt in a way that was not detected at initialization time. The user should be advised to use the Telephony Control Panel to correct the problem.
Impact Not Applicable
Recovery Action Not Applicable
Technical Support Action Not Applicable
Severity Not Applicable
Description TAPI error: Line error- No memory - Insufficient memory to perform the operation or unable to lock memory.
Impact Not Applicable
Recovery Action Not Applicable
Technical Support Action Not Applicable
Severity Not Applicable
Description TAPI error: Line error - No request - There currently is no request pending of the indicated mode or the application is no longer the highest-priority application for the specified request mode.
Impact Not Applicable
Recovery Action Not Applicable
Technical Support Action Not Applicable
Severity Not Applicable
Description TAPI error: Line error - Not owner - The application does not have owner privilege to the specified call.
Impact Not Applicable
Recovery Action Not Applicable
Technical Support Action Not Applicable
Severity Not Applicable
Description TAPI error: Line error - Not registered - The application is not registered as a request recipient for the indicated request mode.
Impact Not Applicable
Recovery Action Not Applicable
Technical Support Action Not Applicable
Severity Not Applicable
Description TAPI error: Line error - Operation failed - The operation failed for an unspecified or unknown reason. If an application gets an error return that it does not specifically handle (such as an error defined by a device-specific-extension), it should treat the error as a LINERR_OPERATIONFAILED (for an unspecified reason).
Impact Not Applicable
Recovery Action Not Applicable
Technical Support Action Not Applicable
Severity Not Applicable
Description TAPI error: Line error - Operation unavailable - The operation is not available such as for the given device or specified line.
Impact Not Applicable
Recovery Action Not Applicable
Technical Support Action Not Applicable
Severity Not Applicable
Description TAPI error: Line error - Rate unavailable - The service provider currently does not have enough bandwidth available for the specified rate.
Impact Not Applicable
Recovery Action Not Applicable
Technical Support Action Not Applicable
Severity Not Applicable
Description TAPI error: Line error - Resource unavailable - Insufficient resources to complete the operation. For example, a line cannot be opened due to a dynamic resource overcommitment.
Impact Not Applicable
Recovery Action Not Applicable
Technical Support Action Not Applicable
Severity Not Applicable
Description TAPI error: Line error - Request overrun.
Impact Not Applicable
Recovery Action Not Applicable
Technical Support Action Not Applicable
Severity Not Applicable
Description TAPI error: Line error - Structure too small - The dwTotalSize member indicates insufficient space to contain the fixed portion of the specified structure.
Impact Not Applicable
Recovery Action Not Applicable
Technical Support Action Not Applicable
Severity Not Applicable
Description TAPI error: Line error - Target not found - A target for the call handoff was not found. This can occur if the named application did not open the same line with the LINECALLPRIVILEGE_OWNER bit in the dwPrivileges parameter of lineOpen. Or, in the case of media-mode handoff, no application has opened the same line with the LINCALLPRIVILEGE_OWNER bit in the dwPrivileges parameter of lineOpen and with the media mode specified in the dwMediaMode parameter.
Impact Not Applicable
Recovery Action Not Applicable
Technical Support Action Not Applicable
Severity Not Applicable
Description TAPI error: Line error - Target Self- The application invoking this operation is the target of the indirect handoff. That is, TAPI has determined that the calling application is also the highest priority application for the given media mode.
Impact Not Applicable
Recovery Action Not Applicable
Technical Support Action Not Applicable
Severity Not Applicable
Description TAPI error: Line error - Uninitialized - The operation was invoked before any application called lineInitialize, lineInitializeEx.
Impact Not Applicable
Recovery Action Not Applicable
Technical Support Action Not Applicable
Severity Not Applicable
Description TAPI error: Line error - User Info Too big - The string containing user information exceeds the maximum number of bytes specified in the dwUUIAcceptSize, dwUUIAnswerSize, dwUUIDropSize, dwUUIMakeCallSize, or dwUUISendUserUserINforSize member of LINEDEVCAPS, or the string containing user information is too long.
Impact Not Applicable
Recovery Action Not Applicable
Technical Support Action Not Applicable
Severity Not Applicable
Description TAPI error: Line error - Reinit - The application attempted to initialize TAPI twice.
Impact Not Applicable
Recovery Action Not Applicable
Technical Support Action Not Applicable
Severity Not Applicable
Description TAPI error: Line error - Address blocked - The target call address has call blocking enabled.
Impact Not Applicable
Recovery Action Not Applicable
Technical Support Action Not Applicable
Severity Not Applicable
Description TAPI error: Line error - Billing rejected - The billing mode of the call was rejected.
Impact Not Applicable
Recovery Action Not Applicable
Technical Support Action Not Applicable
Severity Not Applicable
Description TAPI error: Line error - Invalid feature - The application invoked a feature which is not available on this line.
Impact Not Applicable
Recovery Action Not Applicable
Technical Support Action Not Applicable
Severity Not Applicable
Description TAPI error: Line error - No multiple instance- Multiple instances of this service provider are not allowed.
Impact Not Applicable
Recovery Action Not Applicable
Technical Support Action Not Applicable
Severity Not Applicable
Description TAPI error: Line error - Invalid agent ID - An invalid agent identifier was used. This value is exposed only to application which negotiate a TAPI version of 2.0 or higher.
Impact Not Applicable
Recovery Action Not Applicable
Technical Support Action Not Applicable
Severity Not Applicable
Description TAPI error: Line error - Invalid agent group- The application referenced an agent group that is invalid. This value is exposed only to applications which negotiate a TAPI version of 2.0 or higher.
Impact Not Applicable
Recovery Action Not Applicable
Technical Support Action Not Applicable
Severity Not Applicable
Description TAPI error: Line error - Invalid password - The application used an invalid password. This value is exposed only to applications which negotiate a TAPI version of 2.0 or higher.
Impact Not Applicable
Recovery Action Not Applicable
Technical Support Action Not Applicable
Severity Not Applicable
Description TAPI error: Line error - Invalid Agent State - The application referenced an agent state that is invalid. This value is exposed only to applications which negotiate a TAPI version of 2.0 or higher.
Impact Not Applicable
Recovery Action Not Applicable
Technical Support Action Not Applicable
Severity Not Applicable
Description TAPI error: Line error - Invalid Agent Activity - The application invoking this operation is the target of the indirect handoff. That is, TAPI has determined that the calling application is also the highest priority application for the given media mode. This value is exposed only to applications which negotiate a TAPI version of 2.0 or higher.
Impact Not Applicable
Recovery Action Not Applicable
Technical Support Action Not Applicable
Severity Not Applicable
Description TAPI error: Line error - Dial tone detect - Use of the ":" dial modifier is not supported. This value is exposed only to applications which negotiate a TAPI version of 2.0 or higher.
Impact Not Applicable
Recovery Action Not Applicable
Technical Support Action Not Applicable