Severity Critical
Description The MAS Blue Call Router (BCR) could not log in to the MAS Security service. As a result the BCR could not be started.
Impact The BCR will not start. This means that the MAS Server will not process any calls.
Recovery Action Check and restart the MAS Security service from the NT Control Panel , then stop and restart the MAS EMCI service. If problem persists, contact your technical support organization.
Technical Support Action Perform the following steps:
1. Check the rc in online help.
2. Use the Security Manager support tool to log in to the Security service.
3. If that fails, check and restart the MAS Security Manager service, then MCI.
Severity Critical
Description The MAS Blue Call Router (BCR) could not establish a connection to the MAS Configuration Manager service. As a result the BCR could not be started.
Impact The BCR will not start. This means that the MAS Server will not process any calls.
Recovery Action Check and restart the MAS Configuration Manager & Security services from the NT Control Panel , then stop and restart the MAS EMCI service. If problem persists, contact technical support organization.
Technical Support Action Perform the following steps:
1. Check the rc in online help.
2. Use the Configuration Manager support tool to log in to the Config service.
3. If that fails, check and restart the MAS Security and Config services, then restart MAS EMCI.
Severity Major
Description The MAS Blue Call Router (BCR) could not read a record in the Service DN (SDN) table (aka NBAccessDN table in the database) for a call. This may signal an internal error in the MAS Configuration Manager service or a general database problem.
Impact Calls to this DN will be given Fast Busy tone and disconnected.
Recovery Action Delete and re-enter the DN in the SDN table from the Client PC
Technical Support Action Perform the following steps:
1. Check and restart the MAS Configuration Manager service from NT Control Panel.
2. Try to read the DN using the Configuration Manager support tool.
3. If problem persists, check and restart the MAS EMCI service from NT Control Panel.
Severity Debug
Description An internal error occurred in the MAS Blue Call Router (BCR). This error indicates that the BCR Could not decrement call counts in MINMAX table. This event provides information which may be useful in debugging this fault. This information should be
Impact The Minimum and Maximum port calculations may not be correct for other calls.
Recovery Action If the problem persists, contact your technical support organization.
Technical Support Action Perform the following steps:
1. Check any event codes either preceding or following this event.
2. Check and restart the MAS EMCI service from NT Control Panel.
3. If problem persists, reboot the MAS Server.
Severity Debug
Description An internal error occurred in the MAS Blue Call Router (BCR). This error indicates that the BCR could not remove the call from the PCRQ. The information reported in this event may be valuable in debugging this fault.
Impact If problem persists, memory corruption may occur leading to lower availability of memory bytes.
Recovery Action If the problem persists, contact your technical support organization.
Technical Support Action Perform the following steps:
1. Check any event codes either preceding or following this event.
2. Check and restart the MAS EMCI service from NT Control Panel.
3. If problem persists, reboot the MAS Server.
Severity Debug
Description An internal error occurred in the MAS Blue Call Router (BCR). This error indicates that the BCR could not get the TAPI device ID of an Agent while a call was being idled. The information reported in this event may be valuable in debugging this fault
Impact The agent may remain in a LOGGEDOUT/NOTREADY state and may not take any more calls.
Recovery Action Verify if the AML link is enabled and active on the PBX. Check and restart the ACDPROXY application on the server. Disable, run diagnostics and re-enable the corresponding DS-0 channel. Disable and re-enable the corresponding MMA agent on the PBX.
Technical Support Action Check any event codes either preceding or following this event. Check and restart the ACDPROXY. Check and restart the MAS EMCI service from NT Control Panel. If problem persists, reboot the MAS Server.
Severity Debug
Description An internal error occurred in the MAS Blue Call Router (BCR). This error indicates that the BCR could not get the TAPI device ID of an Agent while a call was being presented to an application.
Impact The agent may remain in a READY state and call glare may occur.
Recovery Action Disable and re-enable the DS-0 channel. If the problem persists, contact your technical support organization.
Technical Support Action Check any event codes either preceding or following this event. Disable run diagnostics and re-enable the DS-0 channel. Shutdown and re-start all TAPI applications (MAS EMCI and MPCX SLEE). Disable and re-enable the corresponding MMA agent on the PBX.
Severity Debug
Description An internal error occurred in the MAS Blue Call Router (BCR). This error indicates that the BCR could not get the TAPI device ID of an Agent while a call was being returned to queue.
Impact The agent may remain in a READY state and call glare may occur.
Recovery Action Disable and re-enable the DS-0 channel. If the problem persists, contact your technical support organization.
Technical Support Action Check any event codes either preceding or following this event. Disable, run diagnostics and re-enable the DS-0 channel. Shutdown and re-start all TAPI applications (MAS EMCI and MPCX SLEE). Disable and re-enable the corresponding MMA agent on the PBX.
Severity Debug
Description An internal error occurred in the MAS Blue Call Router (BCR). This error indicates that the BCR could not get the ACD position ID of an Agent while a call was being routed to a channel.
Impact The call will be dropped.
Recovery Action Disable and re-enable the DS-0 channel. Check the TAPI Service Provider configuration, TN, DN, etc. If the problem persists, contact your technical support organization.
Technical Support Action Check any event codes either preceding or following this event. Disable, run diagnostics and re-enable the DS-0 channel. Shutdown and re-start all TAPI applications (MAS EMCI and MPCX SLEE). Disable and re-enable the corresponding MMA agent on the PBX.
Severity Debug
Description An internal error occurred in the MAS Blue Call Router (BCR). This error indicates that the BCR could not remove the client request from the PSRQ while idling a client request. The information reported in this event may be valuable in debugging this
Impact If problem persists, memory corruption may occur. A large number of these events may need a server reboot.
Recovery Action If the problem persists, contact your technical support organization.
Technical Support Action Check any event codes either preceding or following this event. Restart the MAS EMCI service from the NT Control Panel.
Severity Debug
Description An internal error occurred in the MAS Blue Call Router (BCR). This error indicates that the BCR could not return a Port to the idle resource queue while idling a call. The information reported in this event may be valuable in debugging this fault.
Impact The port will no longer accept any new call.
Recovery Action Disable and re-enable the DS-0 channel. If the problem persists, contact your technical support organization.
Technical Support Action Check any event codes either preceding or following this event. Restart the MAS EMCI service from the NT Control Panel.
Severity Debug
Description An internal error occurred in the MAS Blue Call Router (BCR). This error indicates that the BCR Could not return a Port to the idle resource queue while returning a call to the queue. The information reported in this event may be valuable in debugging.
Impact The port will no longer accept any new call.
Recovery Action Disable and re-enable the DS-0 channel. If the problem persists, contact your technical support organization.
Technical Support Action Check any event codes either preceding or following this event. Restart the MAS EMCI service from the NT Control Panel.
Severity Debug
Description An internal error occurred in the MAS Blue Call Router (BCR). This error indicates that the BCR could not get a port from the idle resource queue while presenting a port to an application. The information reported in this event may be valuable in de
Impact The call will remain unanswered in queue until the caller disconnects.
Recovery Action Disable and re-enable the DS-0 channel. If the problem persists, contact your technical support organization.
Technical Support Action Check any event codes either preceding or following this event. Restart the MAS EMCI service from the NT Control Panel.
Severity Debug
Description An internal error occurred in the MAS Blue Call Router (BCR). This error indicates that the BCR could not link the port to a call while presenting a call to an application. The information reported in this event may be valuable in debugging this fault.
Impact The call will be dropped.
Recovery Action Disable and re-enable the DS-0 channel. If the problem persists, contact your technical support organization.
Technical Support Action Check any event codes either preceding or following this event. Restart the MAS EMCI service from the NT Control Panel.
Severity Information
Description An ACD overflow call cannot be presented to an application because there are already maximum number of AppBuilder calls active in the system.
Impact The call will not be answered.
Recovery Action The keycode limits the number of AppBuilder call sessions. Verify your keycode and if necessary obtain a new keycode with a larger limit. Reporter will confirm if calls are being queued because of this limit.
Technical Support Action Run the Config Manager support tool to verify the Nbresourceparameter #3
Severity Debug
Description An internal error occurred in the MAS Blue Call Router (BCR). This error indicates that the BCR Could not return a Port to the idle resource queue while returning a call to the queue. The information reported in this event may be valuable in debugging.
Impact The port will no longer accept any new call.
Recovery Action Disable, run diagnostics and re-enable the DS-0 channel. If the problem persists, contact your technical support organization.
Technical Support Action Check any event codes either preceding or following this event. Restart the MAS EMCI service from the NT Control Panel.
Severity Major
Description A flag to indicated the completion of a TAPI asynchronous line operation affecting an agent on the switch could not be raised. As a result the line operation may have failed. Win32_rc is returned by API SetEvent().
Impact The call will be dropped.
Recovery Action Follow these steps:
1. Disable and re-enable the port.
2. If the problem persists, contact your technical support organization.
Technical Support Action Follow these steps:
1. Disable and re-enable the port.
2. If the problem persists, shut down and restart the BCR.
Severity Critical
Description The MAS Blue Call Router could not create a Semaphore object that is used to synchronize access to its internal data tables. Win32_rc is returned by API CreateSemaphore().
Impact The BCR will not start. This means that the MAS Server will not process any calls.
Recovery Action Reboot MAS Server. If the problem persists, contact your technical support organization.
Technical Support Action Check if there are multiple copies of executable nbbcrs.exe running using the NT task manager. If so, kill both processes, then restart the EMCI service from the NT Control Panel. If problem persists, reboot the MAS server.
Severity Critical
Description The MAS Blue Call Router could not create an Event object that is used to signal a completion of a TAPI asynchronous line operation affecting an agent on the switch Win32_rc is returned by API CreateEvent().
Impact The BCR will not start. This means that the MAS Server will not process any calls.
Recovery Action Reboot MAS Server. If the problem persists, contact your technical support organization.
Technical Support Action Check if there are multiple copies of executable nbbcrs.exe running using the NT task manager. If so, kill both processes, then restart the EMCI service from the NT Control Panel. If problem persists, reboot the MAS server.
Severity Critical
Description The MAS Blue Call Router could not allocate sufficient memory for its internal data tables.
Impact The BCR will not start. This means that the MAS Server will not process any calls.
Recovery Action Shutdown any non-essential applications and restart the EMCI service from the NT Control Panel. If the problem persists, contact your technical support organization.
Technical Support Action Make a note of the memory usage from the NT Task Manager or the NT Performance monitor. Shutdown any non-essential applications, shutdown any non-essential services (e.g. backup, maintenance, etc.) and restart the EMCI service. If problem persists, reboot
Severity Major
Description An internal error occurred in the MAS Blue Call Router (BCR) where the BCR could not get access to the CCr table for the purpose of adding a CCr entry. The Win32_rc is returned by API WaitForSingleObject().
Impact BCR will not be able to process calls on the corresponding agent on the Switch.
Recovery Action Disable, run diagnostics and re-enable the DS-0 channel. If the problem persists, contact your technical support organization.
Technical Support Action Restart the EMCI service from the NT Control Panel.
Severity Major
Description An internal error occurred in the MAS Blue Call Router (BCR) where the BCR Could not get access to the CCr table for the purpose of linking a CCr to a call. The Win32_rc is returned by API WaitForSingleObject().
Impact The call on this agent may behave unexpectedly, I.e. not answered, or cleared properly
Recovery Action Disable, run diagnostics and re-enable the DS-0 channel. If the problem persists, contact your technical support organization.
Technical Support Action Restart the EMCI service from the NT Control Panel.
Severity Major
Description An internal error occurred in the MAS Blue Call Router (BCR) where the BCR could not get access to CCr table for the purpose of decoupling a CCr from a call. This generally occurs when a port is being deallocated from a call when the call is idled
Impact The agent may stop taking any more calls.
Recovery Action Disable, run diagnostics and re-enable the DS-0 channel. If the problem persists, contact your technical support organization.
Technical Support Action Restart the EMCI service from the NT Control Panel.
Severity Major
Description An internal error occurred in the MAS Blue Call Router (BCR) where the BCR could not get access to CCr table for the purpose of retrieving the call that was previously linked to this CCr. This occurs when a call is being given IVR treatment. Win32_r
Impact The call on this agent may behave unexpectedly, I.e. not answered, or cleared properly
Recovery Action Disable, run diagnostics and re-enable the DS-0 channel. If the problem persists, contact your technical support organization.
Technical Support Action Restart the EMCI service from the NT Control Panel.
Severity Critical
Description The MAS Blue Call Router could not allocate sufficient memory for its internal data tables for a Control DN (CDN).
Impact Calls to the CDN will be routed to the DFDN (Default DN) defined for this CDN.
Recovery Action Shutdown any non-essential applications and restart the EMCI service from the NT Control Panel. If the problem persists, contact your technical support organization.
Technical Support Action Make a note of the memory usage from the NT Task Manager or the NT Performance monitor. Shutdown any non-essential applications, shutdown any non-essential services (e.g. backup, maintenance, etc.) and restart the EMCI service. If problem persists, reboot
Severity Major
Description The MAS Blue Call Router could locate the CDN in its internal data tables while attempting to put it in a Control (CNTL=yes/acquired) mode. This problem may occur when the BCR is starting up.
Impact Calls to the CDN will be routed to the Default DN (DFDN) defined for this CDN.
Recovery Action Verify that the AML link status is enabled and active on the PBX (overlay 48). Verify that the CDN is programmed on the PBX using overlay 23. Reboot server. If the problem persists, contact your support organization.
Technical Support Action Shutdown all TAPI applications (EMCI, SLEE), then start TAPI Browser and try to open the CDN line. If operation fails, check the TSP configuration for the CDN and verify that the DN and mode settings are correct. In ISQL verify if CDN is in NBCDN table
Severity Minor
Description The MAS Blue Call Router could locate the CDN in its internal data tables while attempting to put it in the Default (de-acquired) mode. This fault occurs when the BCR is being shutdown.
Impact Calls to the CDN will not be routed to the Default DN (DFDN) immediately after system is shutdown.
Recovery Action Follow these steps:
1. Put the CDN in a Default mode (CNTL=no) on the switch using overlay 23.
2. If the problem persists each time the BCR is shutdown, contact your support organization.
Technical Support Action Shutdown BCR and then use telephony support tool to open and close the CDN line. Use the AML link trace (overlay 48) to monitor AML messages. Verify that the CDN is programmed on the PBX using overlay 23.
Severity Minor
Description The MAS Blue Call Router could not stop a previously started internal timer that could have been used to time a call, agent or audit event. This event indicates that there was an error between the MAS Blue Call Router (BCR) and CTM.
Impact Problem happens during shutdown. Fault will be cleared when the BCR is restarted.
Recovery Action Not Applicable
Technical Support Action Not Applicable
Severity Major
Description The MAS Blue Call Router could not start an internal timer that is used to time a call, agent or audit event. This event indicates that there was an error between the MAS BCR and CTM.
Impact Calls may be dropped.
Recovery Action If the problem persists, contact your technical support organization.
Technical Support Action Ctsydown system and restart the MAS EMCI service from the Services applet. If problem persists, stop all CT applications, restart CTM and restart applications in that order.
Severity Minor
Description The MAS Blue Call Router could not respond to an outstanding call to API NBbcr_AcquireService(). This event indicates that there was an error between the MAS BCR and CTM. This error occurs when an outgoing call is in progress.
Impact Some outgoing calls are affected.
Recovery Action If the problem persists, CrtsyDown system and restart the EMCI service from the Services applet.
Technical Support Action Run chkdsk to verify files, restart CTM and CT apps, reinstall software if problem persists.
Severity Debug
Description An internal error occurred in the MAS Blue Call Router (BCR). This event indicates that there was an error between the MAS BCR and CTM. This error occurs when the BCR is being shutdown.
Impact Not Applicable
Recovery Action Not Applicable
Technical Support Action Check the return code. Shutdown and restart the CTM and all CT apps.
Severity Debug
Description An internal error occurred in the MAS Blue Call Router (BCR). This event indicates that there was an error between the MAS Blue Call Router (BCR) and MAS CT Media Server (CTMS). This error occurs when the BCR is being shutdown. CT_rc is
Impact Not Applicable
Recovery Action Not Applicable
Technical Support Action Check the return code. Shutdown and restart the CTM and all CT apps.
Severity Critical
Description This event indicates that there was an error between the MAS Blue Call Router (BCR) and CTM. This error occurs when the BCR is being started and the CTM SIA cannot be initialize. The return code from CTMS will indicate the reason for the failure.
Impact BCR will not start. This means that the MAS Server will not process any calls.
Recovery Action Reboot the server
Technical Support Action Check return code. Stop EMCI, restart CTM, restart EMCI. If problem persists, check if other services are having similar problem. Reinstall software and reboot server.
Severity Critical
Description This event indicates that there was an error between the MAS Blue Call Router (BCR) and MAS CTM. This error occurs when the BCR is being started and the MAS_BCR Service Provider cannot be created.
Impact BCR will not start. This means that the MAS Server will not process any calls.
Recovery Action Reboot the server
Technical Support Action Check return code. Stop EMCI, restart CTM, restart EMCI. If problem persists, check if other services are having similar problem. Reinstall software and reboot server.
Severity Critical
Description This event indicates that there was an error between the MAS Blue Call Router (BCR) and MAS CTM. This error occurs when the BCR is being started and the necessary event handler functions to shutdown the BCR cannot be attached to CTM.
Impact BCR will not start. This means that the MAS Server will not process any calls.
Recovery Action Reboot the server
Technical Support Action Check return code. Stop EMCI, restart CTM, restart EMCI. If problem persists, check if other services are having similar problem. Reinstall software and reboot server.
Severity Critical
Description This event indicates that there was an error between the MAS Blue Call Router (BCR) and MAS CTM. This error occurs when the BCR is being started and the callback function required to respond to a ping from CTMS cannot be attached to CTM.
Impact BCR will not start. This means that the MAS Server will not process any calls.
Recovery Action Reboot the server
Technical Support Action Check return code. Stop EMCI, restart CTM, restart EMCI. If problem persists, check if other services are having similar problem. Reinstall software and reboot server.
Severity Critical
Description This event indicates that there was an error between the MAS Blue Call Router (BCR) and MAS CTM. This error occurs when the BCR is being started and the callback functions required to handle API requests cannot be attached to CTM.
Impact BCR will not start. This means that the MAS Server will not process any calls.
Recovery Action Reboot the server
Technical Support Action Check return code. Stop EMCI, restart CTM, restart EMCI. If problem persists, check if other services are having similar problem. Reinstall software and reboot server.
Severity Critical
Description This event indicates that there was an error between the MAS Blue Call Router (BCR) and MAS CTM. This error occurs when the BCR is being started and a service maintenance facade cannot be created for the SP.
Impact BCR will not start. This means that the MAS Server will not process any calls.
Recovery Action Reboot the server
Technical Support Action Check return code. Stop EMCI, restart CTM, restart EMCI. If problem persists, check if other services are having similar problem. Reinstall software and reboot server.
Severity Critical
Description This event indicates that there was an error between the MAS Blue Call Router (BCR) and MAS CTM. This error occurs when the BCR is being started and the MAS_BCR SP cannot be created.
Impact BCR will not start. This means that the MAS Server will not process any calls.
Recovery Action Reboot the server
Technical Support Action Check return code. Stop EMCI, restart CTM, restart EMCI. If problem persists, check if other services are having similar problem. Reinstall software and reboot server.
Severity Debug
Description This event indicates that there was an error between the MAS Blue Call Router (BCR) and MAS CTM. This error occurs when the BCR is being shutdown and the MAS_BCR SP cannot be destroyed.
Impact Not Applicable
Recovery Action Not Applicable
Technical Support Action Check if the MAS_BCR service is still running from the CTM Admin GUI. Use TaskManager to kill the 'nbbcrs' process. Shutdown and restart CTM and all CT apps.
Severity Debug
Description This event indicates that there was an error between the MAS Blue Call Router (BCR) and MAS CTM. This error occurs when the BCR is being shutdown and the CTMS SIA cannot be de-initialized.
Impact Not Applicable
Recovery Action Not Applicable
Technical Support Action Check if the MAS_BCR service is still running from the CTM Admin GUI. Use TaskManager to kill the 'nbbcrs' process. Shutdown and restart CTM and all CT apps.
Severity Debug
Description This event indicates that there was an error between the MAS Blue Call Router (BCR) and MAS CTM. This error occurs when the BCR is being shutdown and the MAS_BCR SP cannot be destroyed.
Impact Not Applicable
Recovery Action Not Applicable
Technical Support Action Check if the MAS_BCR service is still running from the CTM Admin GUI. Use TaskManager to kill the 'nbbcrs' process. Shutdown and restart CTM and all CT apps.
Severity Debug
Description This event indicates that there was an error between the MAS Blue Call Router (BCR) and MAS CTM. This error occurs when the BCR is being shutdown (Normal shutdown) and it cannot set the service state of SP MAS_BCR from 'running' to 'idle'.
Impact BCR may show incorrect service state in the CTMS GUI.
Recovery Action Not Applicable
Technical Support Action Check if the MAS_BCR service is still running from the CTM Admin GUI. Use TaskManager to kill the 'nbbcrs' process. Shutdown and restart CTM and all CT apps.
Severity Debug
Description This event indicates that there was an error between the MAS Blue Call Router (BCR) and MAS CTM. This error occurs when the BCR is being shutdown (Normal shutdown) and the MAS_BCR SP cannot be destroyed.
Impact Not Applicable
Recovery Action Not Applicable
Technical Support Action Check if the MAS_BCR service is still running from the CTM Admin GUI. Use TaskManager to kill the 'nbbcrs' process. Shutdown and restart CTM and all CT apps.
Severity Debug
Description This event indicates that there was an error between the MAS Blue Call Router (BCR) and MAS CTM. This error occurs when the BCR is being shutdown (Emergency shutdown) and it cannot set the service state of SP MAS_BCR from 'running' to 'idle'.
Impact BCR may show incorrect service state in the CTMS GUI.
Recovery Action Not Applicable
Technical Support Action Check if the MAS_BCR service is still running from the CTM Admin GUI. Use TaskManager to kill the 'nbbcrs' process. Shutdown and restart CTM and all CT apps.
Severity Debug
Description This event indicates that there was an error between the MAS Blue Call Router (BCR) and MAS CTM. This error occurs when the BCR is being shutdown (Emergency shutdown) and the MAS_BCR SP cannot be destroyed.
Impact Not Applicable
Recovery Action Not Applicable
Technical Support Action Check if the MAS_BCR service is still running from the CTM Admin GUI. Use TaskManager to kill the 'nbbcrs' process. Shutdown and restart CTM and all CT apps.
Severity Debug
Description This event indicates that there was an error between the MAS Blue Call Router (BCR) and MAS CTM. This error occurs when the NBbcr_GiveService() API is invoked by an application.
Impact Not Applicable
Recovery Action Not Applicable
Technical Support Action Not Applicable
Severity Minor
Description This event indicates that there was an error between the MAS Blue Call Router (BCR) and CTM. This error occurs when the NBbcr_AcquireService() API is invoked by an application and the BCR attempted to read the function parameter.
Impact A failure code will be returned to the calling application. This usually occurs when there is a programming error in the application. Outgoing calls are affected.
Recovery Action If the problem persists, CrtsyDown system and restart the EMCI service from the Services applet.
Technical Support Action Run chkdsk to verify files, restart CTM and CT apps, reinstall software if problem persists.
Severity Minor
Description This event indicates that there was an error between the MAS Blue Call Router (BCR) and CTM. This error occurs when the NBbcr_AcquireService() API is invoked by an application and the BCR attempted to read the function parameter.
Impact A failure code will be returned to the calling application. This usually occurs when there is a programming error in the application. Outgoing calls are affected.
Recovery Action If the problem persists, CrtsyDown system and restart the EMCI service from the Services applet.
Technical Support Action Run chkdsk to verify files, restart CTM and CT apps, reinstall software if problem persists.
Severity Minor
Description This event indicates that there was an error between the MAS Blue Call Router (BCR) and CTM. This error occurs when the NBbcr_AcquireService() API is invoked by an application and the BCR failed to queue the API request.
Impact A failure code will be returned to the calling application. Outgoing calls will be affected.
Recovery Action If the problem persists, CrtsyDown system and restart the EMCI service from the Services applet.
Technical Support Action Run chkdsk to verify files, restart CTM and CT apps, reinstall software if problem persists.
Severity Minor
Description This event indicates that there was an error between the MAS Blue Call Router (BCR) and CTM. This error occurs when the NBbcr_AcquireService() API is invoked by an application and the BCR fails to process the request.
Impact The calling application will receive a failure return code. Affects outgoing calls only.
Recovery Action If the problem persists, CrtsyDown system and restart the EMCI service from the Services applet.
Technical Support Action Run chkdsk to verify files, restart CTM and CT apps, reinstall software if problem persists.
Severity Minor
Description This event indicates that there was an error between the MAS Blue Call Router (BCR) and CTM. This error occurs when the NBbcr_AcquireService() API is invoked by an application and BCR is unable to respond with a completion event to the app.
Impact Not Applicable
Recovery Action If the problem persists, CrtsyDown system and restart the EMCI service from the Services applet.
Technical Support Action Run chkdsk to verify files, restart CTM and CT apps, reinstall software if problem persists.
Severity Debug
Description This event indicates that there was an error between the MAS Blue Call Router (BCR) and CTM. This error occurs when the NBbcr_ConfigService() API is invoked by an application.
Impact
Recovery Action Not Applicable
Technical Support Action Not Applicable
Severity Critical
Description This event indicates that there was an error between the MAS Blue Call Router (BCR) and CTM. This error occurs when the BCR is being started and the MAS_BCR SP cannot be enabled.
Impact BCR will not start. This means that the MAS Server will not process any calls.
Recovery Action Reboot the server
Technical Support Action Check return code. Stop EMCI, restart CTM, restart EMCI. If problem persists, check if other services are having similar problem. Reinstall software and reboot server.
Severity Critical
Description This event indicates that there was an error between the MAS Blue Call Router (BCR) and CTM. This error occurs when the BCR is being started and it cannot set the service state of SP MAS_BCR from idle to running.
Impact BCR will not start. This means that the MAS Server will not process any calls.
Recovery Action Reboot the server
Technical Support Action Check return code. Stop EMCI, restart CTM, restart EMCI. If problem persists, check if other services are having similar problem. Reinstall software and reboot server.
Severity Critical
Description This event indicates that there was an error between the MAS Blue Call Router (BCR) and CTM. CT_rc is returned by API SCsp_AssignTransactionID().
Impact BCR will not start. This means that the MAS Server will not process any calls.
Recovery Action Reboot the server
Technical Support Action Check return code. Stop EMCI, restart CTM, restart EMCI. If problem persists, check if other services are having similar problem. Reinstall software and reboot server.
Severity Minor
Description The MAS Blue Call Router (BCR) experienced an unexpected and unhandled exception during program execution. The information in this event may be valuable in debugging this problem.
Impact May affect outgoing calls.
Recovery Action If the problem persists, CrtsyDown system and reboot server.
Technical Support Action If reboot fails to clear problem, reinstall software.
Severity Critical
Description The MAS Blue Call Router could not create an Event object that is used to co-ordinate the creation and execution of one of its thread. This error may occur when the BCR is being started. Win32_rc is returned by API CreateEvent().
Impact BCR will not start. This means that the MAS Server will not process any calls.
Recovery Action Reboot MAS Server. If the problem persists, contact your technical support organization.
Technical Support Action Check if there are multiple copies of executable nbbcrs.exe running using the NT task manager. If so, kill both processes, then restart the EMCI service from the NT Control Panel. If problem persists, reboot the MAS server.
Severity Critical
Description The MAS Blue Call Router could not create an I/O Completion port that is used to send messages to one of the BCR thread. This error may occur when the BCR is being started. Win32_rc is returned by API CreateIoCompletionPort().
Impact BCR will not start. This means that the MAS Server will not process any calls.
Recovery Action Reboot MAS Server. If the problem persists, contact your technical support organization.
Technical Support Action Check if there are multiple copies of executable nbbcrs.exe running using the NT task manager. If so, kill both processes, then restart the EMCI service from the NT Control Panel. If problem persists, reboot the MAS server.
Severity Critical
Description The MAS Blue Call Router could not create a Semaphore object that is used to synchronize access to one of its thread's message queue. This error may occur when the BCR is being started. Win32_rc is returned by API CreateSemaphore().
Impact BCR will not start. This means that the MAS Server will not process any calls.
Recovery Action Reboot MAS Server. If the problem persists, contact your technical support organization.
Technical Support Action Check if there are multiple copies of executable nbbcrs.exe running using the NT task manager. If so, kill both processes, then restart the EMCI service from the NT Control Panel. If problem persists, reboot the MAS server.
Severity Critical
Description The MAS Blue Call Router could not create and execute the CRM thread. The CRM thread is a critical component of the BCR and without it no call processing can take place. This error may occur when the BCR is being started. Win32_rc is returned by API
Impact BCR will not start. This means that the MAS Server will not process any calls.
Recovery Action Reboot MAS Server. If the problem persists, contact your technical support organization.
Technical Support Action Check if there are multiple copies of executable nbbcrs.exe running using the NT task manager. If so, kill both processes, then restart the EMCI service from the NT Control Panel. If problem persists, reboot the MAS server.
Severity Critical
Description The MAS Blue Call Router's CRM thread did not execute. The CRM thread is a critical component of the BCR and without it no call processing can take place. This error may occur when the BCR is being started. Win32_rc is returned by API WaitForSingleO
Impact BCR will not start. This means that the MAS Server will not process any calls.
Recovery Action Reboot MAS Server. If the problem persists, contact your technical support organization.
Technical Support Action Check if there are multiple copies of executable nbbcrs.exe running using the NT task manager. If so, kill both processes, then restart the EMCI service from the NT Control Panel. If problem persists, reboot the MAS server.
Severity Debug
Description The MAS Blue Call Router could not create an Event object that is used to co-ordinate the stopping of the CRM thread. This error may occur when the BCR is being shutdown. Win32_rc is returned by API CreateEvent().
Impact Not Applicable
Recovery Action Not Applicable
Technical Support Action Check the return code.
Severity Minor
Description The MAS Blue Call Router's CRM thread was instructed to halt but the thread did not respond to the command. This error may occur when the BCR is being shutdown. Win32_rc is returned by API WaitForSingleObject().
Impact Not Applicable
Recovery Action Not Applicable
Technical Support Action Check the return code.
Severity Minor
Description One of MAS Blue Call Router's thread's was unable to send a message to the CRM thread. This event signals either a memory corruption problem or that the CRM thread is dead.
Impact Some OM pegs will not be reported to the OM server.
Recovery Action Not Applicable
Technical Support Action Restart the EMCI service from the Services applet.
Severity Minor
Description One of MAS Blue Call Router's threads was unable to send a message to the CRM thread because the CRM message queue was being blocked by another thread. This event signals either a memory corruption problem or that the CRM thread is dead.
Impact Not Applicable
Recovery Action Not Applicable
Technical Support Action Restart the EMCI service from the Services applet.
Severity Critical
Description The MAS Blue Call Router's CRM thread could not signal to the main thread that it has started. The error returned is from WIN32 API SetEvent().
Impact The BCR will not start properly. This means that the MAS Server will not process any calls.
Recovery Action Reboot MAS Server. If the problem persists, contact your technical support organization.
Technical Support Action Check if there are multiple copies of executable nbbcrs.exe running using the NT task manager. If so, kill both processes, then restart the EMCI service from the NT Control Panel. If problem persists, reboot the MAS server.
Severity Minor
Description The MAS Blue Call Router (BCR)' CRM thread received an unexpected error when communicating with other threads with the process. The error returned is from WIN32 API GetQueuedCompletionStatus().
Impact The BCR will stop pegging OM data.
Recovery Action Not Applicable
Technical Support Action Shutdown and restart the EMCI service from the Services applet.
Severity Debug
Description The MAS Blue Call Router's CRM thread could not signal to the main thread that the thread has terminated. The error returned is from WIN32 API SetEvent(). This event may occur when the BCR is being shutdown.
Impact Not Applicable
Recovery Action Not Applicable
Technical Support Action Check return code.
Severity Debug
Description The Blue Call Router (BCR)' CRM thread received an unexpected error during call processing when it tried to get a outgoing call request from a client application. The client request could not be located in the PSRQ.
Impact An outgoing call request may be lost.
Recovery Action If the problem persists, contact your technical support organization.
Technical Support Action Shutdown and restart the BCR.
Severity Debug
Description The Blue Call Router (BCR)' CRM thread received an unexpected error during call processing when it tried to get an incoming call for an application. The call could not be located in the PCRQ.
Impact An outgoing call request may be lost.
Recovery Action If the problem persists, contact your technical support organization.
Technical Support Action Shutdown and restart the BCR.
Severity Minor
Description The MAS Blue Call Router (BCR) received an unexpected error during call processing when it tried to get a unique identifier for a call from the MAS OM server. As a result the OM data may be incorrect or lost for the call.
Impact OM data may be incorrect or lost. May impact OM Reporter and applications
Recovery Action If the problem persists, restart the MAS OM server from the Services applet.
Technical Support Action Check the return code. Run the OM support tool to investigate the problem.
Severity Minor
Description The MAS Blue Call Router (BCR) received an unexpected channel configuration parameter from the MAS Configuration Server. As a result the port will be configured with voice capability only for the call.
Impact DSP channel capability may be insufficient for the application. The application may terminate the call.
Recovery Action Remove the SDN entry and re-enter it. If the problem persists, contact your support organization.
Technical Support Action Select the SDN table entry using ISQL from the NBASDN table and verify that the MediaType field is defined in the range of 1..4. Restart the MAS Config, Fault and Security services from the Service applet. Use the Config Support tool to read the SDN.
Severity Minor
Description The MAS Blue Call Router (BCR) received an unexpected Application Service ID (ASI) parameter from the MAS Configuration Server. As a result the call will not be forwarded to its target application and will remain ringing at the CDN.
Impact The call will not be answered.
Recovery Action Remove the SDN entry and re-enter it. If the problem persists, contact your support organization.
Technical Support Action Select the SDN table entry using ISQL from the NBASDN table and verify that the ASI is defined. Restart the MAS Config, Fault and Security services from the Service applet. Use the Config Support tool to read the SDN.
Severity Minor
Description The MAS Blue Call Router (BCR) CRM thread experienced an unexpected and unhandled exception during program execution. The information in this event may be valuable in debugging this problem.
Impact OM data will be lost.
Recovery Action If the problem persists, Courtesy Down the system and reboot the server.
Technical Support Action If reboot fails to clear problem, reinstall software.
Severity Critical
Description The MAS Blue Call Router (BCR) could not create a Semaphore object that is used to synchronize access to the Call Register Pool, an internal data structure used to hold call information. As a result the BCR will not start.
Impact BCR will not start. This means that the MAS server will not process any calls.
Recovery Action Reboot MAS Server. If the problem persists, contact your technical support organization.
Technical Support Action Check if there are multiple copies of executable nbbcrs.exe running using the NT task manager. If so, kill both processes, then restart the EMCI service from the NT Control Panel. If problem persists, reboot the MAS server.
Severity Debug
Description The MAS Blue Call Router (BCR) could not destroy a Semaphore object that is used to synchronize access to the Call Register Pool, an internal data structure used to hold call information. This is event may occur when the BCR is being shutdown.
Impact Not Applicable
Recovery Action Not Applicable
Technical Support Action Check return code.
Severity Major
Description Blue Call Router (BCR) is running out on call registers, an internal data structure to hold call information for each call. New call will not be processed until the call volume is reduced.
Impact BCR will not process any calls until volume of calls reduce. Existing calls are unaffected.
Recovery Action If there are any disabled DS-0 or DSP channels, re-enable them. Re-engineer system to add more channels if necessary. Reboot system.
Technical Support Action Restart CTM and all CT apps.
Severity Debug
Description The Blue Call Router (BCR) is running dangerously low on call registers. Call registers are an internal data structure that are used to hold call information. Call registers are allocated dynamically to each call and deallocated when the call dropped.
Impact Not Applicable
Recovery Action If the problem persists, contact your technical support organization.
Technical Support Action Shutdown and restart the BCR.
Severity Debug
Description The MAS Blue Call Router (BCR) could not create an internal synchronization object that is used for each call. The returned error is from Win32 API CreateEvent().
Impact Not Applicable
Recovery Action Not Applicable
Technical Support Action Not Applicable
Severity Major
Description The MAS Blue Call Router (BCR) could not allocate memory for a call. As a result the call will remain unanswered in queue until caller disconnects or get diverted to the Default DN defined for the CDN.
Impact Calls to the CDN will be routed to the DFDN (Default DN) defined for this CDN.
Recovery Action Shutdown any non-essential applications and restart the EMCI service from the NT Control Panel. If the problem persists, contact your technical support organization.
Technical Support Action Make a note of the memory usage from the NT Task Manager or the NT Performance monitor. Shutdown any non-essential applications, shutdown any non-essential services (e.g. backup, maintenance, etc.) and restart the EMCI service. If problem persists, reboot
Severity Major
Description The MAS Blue Call Router (BCR) could not get access to the Call Register pool to allocate memory for a call. As a result the call will remain unanswered in queue until caller disconnects or get diverted to the Default DN defined for the CDN.
Impact Call will remain unanswered in queue until caller disconnects or get diverted to the Default DN defined for the CDN.
Recovery Action Shutdown any non-essential applications and restart the EMCI service from the NT Control Panel. If the problem persists, contact your technical support organization.
Technical Support Action Make a note of the memory usage from the NT Task Manager or the NT Performance monitor. Shutdown any non-essential applications, shutdown any non-essential services (e.g. backup, maintenance, etc.) and restart the EMCI service. If problem persists, reboot
Severity Minor
Description The MAS Blue Call Router (BCR) could not get access to the Call Register pool to deallocate memory for a call that has disconnected. As a result this memory block will not be reused for subsequent calls.
Impact If problem persists, memory leaks may occur.
Recovery Action If the problem persists, contact your technical support organization.
Technical Support Action Shutdown and restart the EMCI service.
Severity Critical
Description The MAS Blue Call Router (BCR) could not allocate memory for one of its internal data structure, i.e. Customer Table. As a result other data structures could not be created.
Impact BCR will not start. This means that the MAS Server will not process any calls.
Recovery Action Shutdown any non-essential applications and restart the EMCI service from the NT Control Panel. If the problem persists, contact your technical support organization.
Technical Support Action Make a note of the memory usage from the NT Task Manager or the NT Performance monitor. Shutdown any non-essential applications, shutdown any non-essential services (e.g. backup, maintenance, etc.) and restart the EMCI service. If problem persists, reboot
Severity Critical
Description The MAS Blue Call Router (BCR) failed to execute a SQL statement (SQLAllocEnv). As a result itcould not allocate memory for an SQL envrironment handle that is required to connect to the MAS database. As a result the BCR will not start.
Impact BCR will not start. This means that the MAS Server will not process any calls.
Recovery Action Check and restart the MAS Database service. If the problem persists, contact your technical support organization.
Technical Support Action Check if the SQL database service is running. Shutdown and restart the EMCI service.
Severity Critical
Description The MAS Blue Call Router (BCR) failed to execute a SQL statement (SQLAllocConnect). As a result itcould not allocate memory for an SQL envrironment handle that is required to connect to the MAS database. As a result the BCR will not start.
Impact BCR will not start. This means that the MAS Server will not process any calls.
Recovery Action Check and restart the MAS Database service. If the problem persists, contact your technical support organization.
Technical Support Action Check if the SQL database service is running. Shutdown and restart the EMCI service.
Severity Critical
Description The MAS Blue Call Router (BCR) could not retrieve the database user name and password for the MAS database. As a result the BCR will not be able to login to the database.
Impact BCR will not start. This means that the MAS Server will not process any calls.
Recovery Action Check and restart the MAS Database service. If the problem persists, contact your technical support organization.
Technical Support Action Check if the SQL database service is running. Shutdown and restart the EMCI service. Use the nbdb support tool to read the login ID and password.
Severity Critical
Description The MAS Blue Call Router (BCR) failed to execute a SQL statement (SQLConnect). As a result itcould not connect to the MAS database. As a result the BCR will not start.
Impact BCR will not start. This means that the MAS Server will not process any calls.
Recovery Action Check and restart the MAS Database service. If the problem persists, contact your technical support organization.
Technical Support Action Check if the SQL database service is running. Shutdown and restart the EMCI service.
Severity Critical
Description The MAS Blue Call Router (BCR) failed to execute a SQL statement (SQLAllocStmt). As a result it could not allocate memory for a Statement handle that is required to connect to the MAS database. As a result the BCR will not start.
Impact BCR will not start. This means that the MAS Server will not process any calls.
Recovery Action Check and restart the MAS Database service. If the problem persists, contact yourtechnical support organization.
Technical Support Action Check if the SQL database service is running. Shutdown and restart the EMCI service.
Severity Minor
Description The MAS Blue Call Router (BCR) failed to execute a SQL statement (SQLFreeStmt). As a result it could not de-allocate memory for a Statement handle that was used to read data from the MAS database.
Impact If problem persists, memory leaks may occur.
Recovery Action If the problem persists, contact yourtechnical support organization.
Technical Support Action Shutdown and restart the EMCI service.
Severity Major
Description The MAS Blue Call Router (BCR) failed to execute an SQL statement (SQLExecDirect). As a result it could not read a table or field in from the MAS database.
Impact A DS-30 call channel may stay in loading state.
Recovery Action Disable and re-enable the loading DS-30 channel.
Technical Support Action Check and restart the MAS Database service. Using ISQL verify that the NBCCR table exists and the rows of the table are valid. If problem persists recreate the table by running a hardware configuration program.
Severity Major
Description The MAS Blue Call Router (BCR) failed to execute an SQL statement (SQLBindCol). As a result it could not assigns the storage and data type for a column in a result set that was read from the MAS database.
Impact A DS-30 call channel may stay in loading state.
Recovery Action Disable and re-enable the loading DS-30 channel.
Technical Support Action Check and restart the MAS Database service. Using ISQL verify that the NBCCR table exists and the rows of the table are valid. If problem persists recreate the table by running a hardware configuration program.
Severity Major
Description The MAS Blue Call Router (BCR) failed to execute an SQL statement (SQLBindCol). As a result it could not read data from the MAS database.
Impact A DS-30 call channel may stay in loading state.
Recovery Action Disable and re-enable the loading DS-30 channel.
Technical Support Action Check and restart the MAS Database service. Using ISQL verify that the NBCCR table exists and the rows of the table are valid. If problem persists recreate the table by running a hardware configuration program.
Severity Minor
Description The MAS Blue Call Router (BCR) failed to execute an SQL statement (SQLFreeStmt). As a result it could not de-allocate memory for a Statement handle that was used to read data from the MAS database.
Impact If problem persists, memory leaks may occur.
Recovery Action If the problem persists, contact your technical support organization.
Technical Support Action Shutdown and restart the EMCI service.
Severity Critical
Description The MAS Blue Call Router (BCR) failed to execute an SQL statement (SQLExecDirect). As a result it could not read a table or field in from the MAS database. As a result the BCR will not start.
Impact BCR will not start. As a result the MAS server will not process any calls.
Recovery Action Not Applicable
Technical Support Action Check and restart the MAS Database service. Using ISQL verify that the NBCCR table exists and the rows of the table are valid. If problem persists recreate the table by running a hardware configuration program.
Severity Critical
Description The MAS Blue Call Router (BCR) failed to execute an SQL statement (SQLBindCol). As a result it could not assigns the storage and data type for a column in a result set that was read from the MAS database.
Impact BCR will not start. As a result the MAS server will not process any calls.
Recovery Action Not Applicable
Technical Support Action Check and restart the MAS Database service. Using ISQL verify that the NBCCR table exists and the rows of the table are valid. If problem persists recreate the table by running a hardware configuration program.
Severity Minor
Description The MAS Blue Call Router (BCR) failed to execute an SQL statement (SQLFreeStmt). As a result it could not de-allocate memory for a Statement handle that was used to read data from the MAS database.
Impact If problem persists, memory leaks may occur.
Recovery Action If the problem persists, contact your technical support organization.
Technical Support Action Shutdown and restart the EMCI service.
Severity Major
Description The MAS Blue Call Router (BCR) failed to execute an SQL statement (SQLExecDirect). As a result it could not read a table or field in from the MAS database.
Impact BCR will not process any calls.
Recovery Action Not Applicable
Technical Support Action Check and restart the MAS Database service. Using ISQL verify that the NBCDN table exists and the rows of the table are valid. If problem persists recreate the table by running a hardware configuration program.
Severity Critical
Description The MAS Blue Call Router (BCR) failed to execute an SQL statement (SQLBindCol). As a result it could not assigns the storage and data type for a column in a result set that was read from the MAS database.
Impact BCR will not process any calls.
Recovery Action Not Applicable
Technical Support Action Check and restart the MAS Database service. Using ISQL verify that the NBCDN table exists and the rows of the table are valid. If problem persists recreate the table by running a hardware configuration program.
Severity Critical
Description The MAS Blue Call Router (BCR) failed to execute an SQL statement (SQLFetch). As a result it could not read from the MAS database.
Impact BCR will not process any calls.
Recovery Action Not Applicable
Technical Support Action Check and restart the MAS Database service. Using ISQL verify that the NBCDN table exists and the rows of the table are valid. If problem persists recreate the table by running a hardware configuration program.
Severity Minor
Description The MAS Blue Call Router (BCR) failed to execute an SQL statement (SQLFreeStmt). As a result it could not de-allocate memory for a Statement handle that was used to read data from the MAS database.
Impact If problem persists, memory leaks may occur.
Recovery Action If the problem persists, contact your technical support organization.
Technical Support Action Shutdown and restart the EMCI service.
Severity Major
Description The MAS Blue Call Router (BCR) failed to execute an SQL statement (SQLExecDirect). As a result it could not read a table or field in from the MAS database.
Impact BCR will not process any calls.
Recovery Action Not Applicable
Technical Support Action Check and restart the MAS Database service. Using ISQL verify that the NBCDN table exists and the rows of the table are valid. If problem persists recreate the table by running a hardware configuration program.
Severity Major
Description The MAS Blue Call Router (BCR) failed to execute an SQL statement (SQLFetch). As a result it could not read data from the MAS database.
Impact BCR will not process any calls.
Recovery Action Not Applicable
Technical Support Action Check and restart the MAS Database service. Using ISQL verify that the NBCDN table exists and the rows of the table are valid. If problem persists recreate the table by running a hardware configuration program.
Severity Minor
Description The MAS Blue Call Router (BCR) failed to execute an SQL statement (SQLFreeStmt). As a result it could not de-allocate memory for a Statement handle that was used to read data from the MAS database.
Impact If problem persists, memory leaks may occur.
Recovery Action If the problem persists, contact your technical support organization.
Technical Support Action Shutdown and restart the EMCI service.
Severity Critical
Description The MAS Blue Call Router (BCR) failed to execute an SQL statement (SQLExecDirect). As a result it could not read a table or field in from the MAS database.
Impact BCR will not start. As a result the MAS server will not process any calls.
Recovery Action Not Applicable
Technical Support Action Check and restart the MAS Database service. Using ISQL verify that the NBSPC table exists and the rows of the table are valid. If problem persists recreate the table by running a hardware configuration program.
Severity Critical
Description The MAS Blue Call Router (BCR) failed to execute an SQL statement (SQLBindCol). As a result it could not assigns the storage and data type for a column in a result set that was read data from the MAS database.
Impact BCR will not start. As a result the MAS server will not process any calls.
Recovery Action Not Applicable
Technical Support Action Check and restart the MAS Database service. Using ISQL verify that the NBSPC table exists and the rows of the table are valid. If problem persists recreate the table by running a hardware configuration program.
Severity Critical
Description The MAS Blue Call Router could not create an Event object that is used to co-ordinate the creation and execution of the EXEC thread. This error may occur when the BCR is being started. Win32_rc is returned by API CreateEvent().
Impact The BCR will not start. This means that the MAS Server will not process any calls.
Recovery Action Reboot MAS Server. If the problem persists, contact your technical support organization.
Technical Support Action Check if there are multiple copies of executable nbbcrs.exe running using the NT task manager. If so, kill both processes, then restart the EMCI service from the NT Control Panel. If problem persists, reboot the MAS server.
Severity Critical
Description The MAS Blue Call Router could not create an I/O Completion port that is used to send messages to the EXEC thread. This error may occur when the BCR is being started. Win32_rc is returned by API CreateIoCompletionPort().
Impact The BCR will not start. This means that the MAS Server will not process any calls.
Recovery Action Reboot MAS Server. If the problem persists, contact your technical support organization.
Technical Support Action Check if there are multiple copies of executable nbbcrs.exe running using the NT task manager. If so, kill both processes, then restart the EMCI service from the NT Control Panel. If problem persists, reboot the MAS server.
Severity Critical
Description The MAS Blue Call Router could not create a Semaphore object that is used to synchronize access to the EXEC thread's message queue. This error may occur when the BCR is being started. Win32_rc is returned by API CreateSemaphore().
Impact The BCR will not start. This means that the MAS Server will not process any calls.
Recovery Action Reboot MAS Server. If the problem persists, contact your technical support organization.
Technical Support Action Check if there are multiple copies of executable nbbcrs.exe running using the NT task manager. If so, kill both processes, then restart the EMCI service from the NT Control Panel. If problem persists, reboot the MAS server.
Severity Critical
Description The MAS Blue Call Router could not create and execute the EXEC thread. The EXEC thread is a critical component of the BCR and without it no call processing can take place. This error may occur when the BCR is being started. Win32_rc is returned by A
Impact The BCR will not start. This means that the MAS Server will not process any calls.
Recovery Action Reboot MAS Server. If the problem persists, contact your technical support organization.
Technical Support Action Check if there are multiple copies of executable nbbcrs.exe running using the NT task manager. If so, kill both processes, then restart the EMCI service from the NT Control Panel. If problem persists, reboot the MAS server.
Severity Critical
Description The MAS Blue Call Router's EXEC thread did not start. The EXEC thread is a critical component of the BCR and without it no call processing can take place. This error may occur when the BCR is being started. Win32_rc is returned by API WaitForSingleObject.
Impact The BCR will not start. This means that the MAS Server will not process any calls.
Recovery Action Reboot MAS Server. If the problem persists, contact your technical support organization.
Technical Support Action Check if there are multiple copies of executable nbbcrs.exe running using the NT task manager. If so, kill both processes, then restart the EMCI service from the NT Control Panel. If problem persists, reboot the MAS server.
Severity Debug
Description The MAS Blue Call Router could not create an Event object that is used to co-ordinate the stopping of the EXEC thread. This error may occur when the BCR is being shutdown. Win32_rc is returned by API CreateEvent().
Impact Not Applicable
Recovery Action Not Applicable
Technical Support Action Check any return codes
Severity Debug
Description The MAS Blue Call Router's EXEC thread was instructed to halt but the thread did not respond to the command. This error may occur when the BCR is being shutdown. Win32_rc is returned by API WaitForSingleObject().
Impact Not Applicable
Recovery Action Not Applicable
Technical Support Action Check any return codes
Severity Major
Description One of MAS Blue Call Router's thread's was unable to send a message to the EXEC thread. This event signals either a memory corruption problem or that the EXEC thread is dead. In either case the BCR should be restarted. This error may occur when the
Impact May affect callprocessing. Incoming calls may not get answered.
Recovery Action Reboot MAS Server. If the problem persists, contact your technical support organization.
Technical Support Action Check return codes. Check if there are multiple copies of executable nbbcrs.exe running using the NT task manager. If so, kill both processes, then restart the EMCI service from the NT Control Panel. If problem persists, reboot the MAS server. Perform dummy upgrade if problem persists.
Severity Major
Description One of MAS Blue Call Router's threads was unable to send a message to the EXEC thread because the EXEC message queue was being blocked by another thread. This event signals either a memory corruption problem or that the EXEC thread is dead. In eithe
Impact May affect callprocessing. Incoming calls may not get answered.
Recovery Action Reboot MAS Server. If the problem persists, contact your technical support organization.
Technical Support Action Check return codes. Check if there are multiple copies of executable nbbcrs.exe running using the NT task manager. If so, kill both processes, then restart the EMCI service from the NT Control Panel. If problem persists, reboot the MAS server. Perform dummy upgrade if problem persists.
Severity Critical
Description The MAS Blue Call Router (BCR) EXEC thread could not signal to the main thread that it has started. The error returned is from WIN32 API SetEvent().
Impact The BCR will not start. This means that the MAS Server will not process any calls.
Recovery Action Reboot MAS Server. If the problem persists, contact your technical support organization.
Technical Support Action Check if there are multiple copies of executable nbbcrs.exe running using the NT task manager. If so, kill both processes, then restart the EMCI service from the NT Control Panel. If problem persists, reboot the MAS server.
Severity Critical
Description The MAS Blue Call Router (BCR) EXEC thread received an unexpected error when communicating with other threads with the process. The error returned is from WIN32 API GetQueuedCompletionStatus(). The EXEC thread will terminate itself and the BCR will restart
Impact The BCR will not start. This means that the MAS Server will not process any calls.
Recovery Action Reboot MAS Server. If the problem persists, contact your technical support organization.
Technical Support Action Check if there are multiple copies of executable nbbcrs.exe running using the NT task manager. If so, kill both processes, then restart the EMCI service from the NT Control Panel. If problem persists, reboot the MAS server.
Severity Debug
Description The MAS Blue Call Router (BCR) EXEC thread could not signal to the main thread that the thread has terminated. The error returned is from WIN32 API SetEvent(). This event may occur when the BCR is being shutdown.
Impact Not Applicable
Recovery Action Not Applicable
Technical Support Action Check for any return codes.
Severity Debug
Description The MAS Blue Call Router's EXEC thread was instructed to halt but the thread did not respond to the command. This error may occur when the BCR is being shutdown. Win32_rc is returned by API SetEvent().
Impact Not Applicable
Recovery Action Not Applicable
Technical Support Action Not Applicable
Severity Debug
Description The MAS Blue Call Router (BCR) EXEC thread received an unexpected error during call processing when it tried to idle a call, but could not locate it in its internal PCRQ structure. The call could not be located in the PCRQ.
Impact Not Applicable
Recovery Action Not Applicable
Technical Support Action Not Applicable
Severity Debug
Description The MAS Blue Call Router (BCR) EXEC thread received an unexpected error during call processing when it tried to answer a call, but could not locate it in its internal PCRQ structure. The call could not be located in the PCRQ.
Impact Not Applicable
Recovery Action Not Applicable
Technical Support Action Not Applicable
Severity Minor
Description The MAS Blue Call Router (BCR) EXEC thread received an unexpected error during call processing when it tried to process an incoming call, but could not locate it in its internal PCRQ structure. The call could not be located in the PCRQ.
Impact Incoming call may remain unanswered in queue.
Recovery Action Reboot MAS Server. If the problem persists, contact your technical support organization.
Technical Support Action Look at AML trace info for a call. Check if there are multiple copies of executable nbbcrs.exe running using the NT task manager. If so, kill both processes, then restart the EMCI service from the NT Control Panel. If problem persists, reboot the MAS server.
Severity Minor
Description The MAS Blue Call Router (BCR) EXEC thread received an unexpected error during call processing when it tried to allocate resources for a call.
Impact Incoming call may remain unanswered in queue.
Recovery Action Reboot MAS Server. If the problem persists, contact your technical support organization.
Technical Support Action Look at AML trace info for a call. Check if there are multiple copies of executable nbbcrs.exe running using the NT task manager. If so, kill both processes, then restart the EMCI service from the NT Control Panel. If problem persists, reboot the MAS server.
Severity Minor
Description The MAS Blue Call Router (BCR) EXEC thread received an unexpected error during call processing when it tried to process an incoming call, but could not locate it in its internal PCRQ structure. The call could not be located in the PCRQ.
Impact Incoming call may remain unanswered in queue.
Recovery Action Reboot MAS Server. If the problem persists, contact your technical support organization.
Technical Support Action Look at AML trace info for a call. Check if there are multiple copies of executable nbbcrs.exe running using the NT task manager. If so, kill both processes, then restart the EMCI service from the NT Control Panel. If problem persists, reboot the MAS server.
Severity Debug
Description The MAS Blue Call Router (BCR) EXEC thread received an unexpected error during call processing when it tried to process an client request, but could not locate it in its internal PSRQ structure. The call could not be located in the PSRQ.
Impact Outgoing call request will return failure to application.
Recovery Action Reboot MAS Server. If the problem persists, contact your technical support organization.
Technical Support Action Look at AML trace info for a call. Check if there are multiple copies of executable nbbcrs.exe running using the NT task manager. If so, kill both processes, then restart the EMCI service from the NT Control Panel. If problem persists, reboot the MAS server.
Severity Major
Description The MAS Blue Call Router (BCR) EXEC thread experienced an unexpected and unhandled exception during program execution. The information in this event may be valuable in debugging this problem. This information should be forwared to your MAS repres
Impact Incoming calls will not be answered.
Recovery Action Reboot MAS Server. If the problem persists, contact your technical support organization.
Technical Support Action Look at AML trace info for a call. Check if there are multiple copies of executable nbbcrs.exe running using the NT task manager. If so, kill both processes, then restart the EMCI service from the NT Control Panel. If problem persists, reboot the MAS server.
Severity Debug
Description A mismatch was found between the TAPI and BCR call states. The information in this event may be valuable in debugging this problem. This information should be forwared to your MAS .
Impact Unpredictable behaviour of the BCR.
Recovery Action Not Applicable
Technical Support Action Not Applicable
Severity Critical
Description The MAS Blue Call Router could not create a Semaphore object that is used to synchronize access to its internal data tables. Win32_rc is returned by API CreateSemaphore().
Impact The BCR will not start. This means that the MAS Server will not process any calls.
Recovery Action Reboot MAS Server. If the problem persists, contact your technical support organization.
Technical Support Action Check if there are multiple copies of executable nbbcrs.exe running using the NT task manager. If so, kill both processes, then restart the EMCI service from the NT Control Panel. If problem persists, reboot the MAS server.
Severity Major
Description An internal error occurred in the MAS Blue Call Router (BCR) where the BCR could not get access to the IdleCCr queue for the purpose of getting the first available Call Channel (DS-0) from the idle queue. The Win32_rc is returned by API WaitForSingleObject.
Impact BCR will not be able to process calls on the corresponding agent on the Switch.
Recovery Action Disable, run diags and re-enable the port. If the problem persists, contact your technical support organization.
Technical Support Action Disable on switch, disable on server, run diags and re-enable the port. If the problem persists, shutdown and re-start the BCR.
Severity Debug
Description The MAS Blue Call Router (BCR) could not read the MAX_PORT record in the NBResourceParameter table. This may signal an internal error in the MAS Configuration Manager or a general database problem.
Impact Not Applicable
Recovery Action Not Applicable
Technical Support
Action (1) Check if the MAS Configuration Manager service
is running.
(2) Check if the MAX_PORT field is datafilled in the NBResourceParameter
table.
Severity Critical
Description The MAS Blue Call Router could not allocate sufficient memory for its internal data tables.
Impact The BCR will not start. This means that the MAS Server will not process any calls.
Recovery Action Reboot MAS Server. If the problem persists, contact your technical support organization.
Technical Support Action Check if there are multiple copies of executable nbbcrs.exe running using the NT task manager. If so, kill both processes, then restart the EMCI service from the NT Control Panel. If problem persists, reboot the MAS server.
Severity Minor
Description The MAS Blue Call Router could clean up its internal data table when a call idled.
Impact Minimum and Maximum port checking may be incorrect, as a result incoming calls may not get answered.
Recovery Action Remove and re-add the SDN entry. Reboot MAS Server. If problem persists contact your technical support organization.
Technical Support Action Shutdown and restart the BCR.
Severity Minor
Description The MAS Blue Call Router could clean up its internal data table when a call idled.
Impact Minimum and Maximum port checking may be incorrect, as a result incoming calls may not get answered.
Recovery Action Remove and re-add the SDN entry. Reboot MAS Server. If problem persists contact your technical support organization.
Technical Support Action Shutdown and restart the BCR.
Severity Critical
Description The MAS Blue Call Router (BCR) could not login to the MAS Server. As a result the BCR could not be started.
Impact The BCR will not start. This means that the MAS Server will not process any calls.
Recovery Action Reboot MAS Server. If the problem persists, contact your technical support organization.
Technical Support Action Restart the Security Server. Use Security Server support tool to login to server. Check if there are multiple copies of executable nbbcrs.exe running using the NT task manager. If so, kill both processes, then restart the EMCI service from the NT Control Panel. If problem persists, reboot the MAS server.
Severity Critical
Description The MAS Blue Call Router (BCR) could not establish a connection to the MAS Operational Measurement (OM) Server. As a result the BCR could not be started.
Impact The BCR will not start. This means that the MAS Server will not process any calls.
Recovery Action Reboot MAS Server. If the problem persists, contact your technical support organization.
Technical Support Action Restart the OM Server. Use OM Server support tool to login to server. Check if there are multiple copies of executable nbbcrs.exe running using the NT task manager. If so, kill both processes, then restart the EMCI service from the NT Control Panel. If problem persists, reboot the MAS server.
Severity Minor
Description The MAS Blue Call Router (BCR) could not peg a call event to the MAS Operational Measurement (OM) Server. As a result OM data will be lost.
Impact Call data used to generate OM reports will be lost.
Recovery Action Reboot MAS Server. If the problem persists, contact your technical support organization.
Technical Support Action Restart the OM Server. Use OM Server support tool to login to server. Check if there are multiple copies of executable nbbcrs.exe running using the NT task manager. If so, kill both processes, then restart the EMCI service from the NT Control Panel. If problem persists, reboot the MAS server.
Severity Minor
Description The MAS Blue Call Router (BCR) could not peg a call event to the MAS Operational Measurement (OM) Server. As a result OM data will be lost.
Impact Call data used to generate OM reports will be lost.
Recovery Action Reboot MAS Server. If the problem persists, contact your technical support organization.
Technical Support Action Restart the OM Server. Use OM Server support tool to login to server. Check if there are multiple copies of executable nbbcrs.exe running using the NT task manager. If so, kill both processes, then restart the EMCI service from the NT Control Panel. If problem persists, reboot the MAS server.
Severity Minor
Description The MAS Blue Call Router (BCR) could not peg a call event to the MAS Operational Measurement (OM) Server. As a result OM data will be lost.
Impact Call data used to generate OM reports will be lost.
Recovery Action Reboot MAS Server. If the problem persists, contact your technical support organization.
Technical Support Action Restart the OM Server. Use OM Server support tool to login to server. Check if there are multiple copies of executable nbbcrs.exe running using the NT task manager. If so, kill both processes, then restart the EMCI service from the NT Control Panel. If problem persists, reboot the MAS server.
Severity Minor
Description The MAS Blue Call Router (BCR) could not peg a call event to the MAS Operational Measurement (OM) Server. As a result OM data will be lost.
Impact Call data used to generate OM reports will be lost.
Recovery Action Reboot MAS Server. If the problem persists, contact your technical support organization.
Technical Support Action Restart the OM Server. Use OM Server support tool to login to server. Check if there are multiple copies of executable nbbcrs.exe running using the NT task manager. If so, kill both processes, then restart the EMCI service from the NT Control Panel. If problem persists, reboot the MAS server.
Severity Critical
Description The MAS Blue Call Router could not create a Semaphore object that is used to synchronize access to its internal data tables. Win32_rc is returned by API CreateSemaphore().
Impact The BCR will not start. This means that the MAS Server will not process any calls.
Recovery Action Reboot MAS Server. If the problem persists, contact your technical support organization.
Technical Support Action Check if there are multiple copies of executable nbbcrs.exe running using the NT task manager. If so, kill both processes, then restart the EMCI service from the NT Control Panel. If problem persists, reboot the MAS server.
Severity Minor
Description The MAS Blue Call Router could not get access to its internal data tables that stores call objects. Win32_rc is returned by API WaitSingleObject().
Impact Incoming call may remain unanswered in queue or an existing call may get dropped.
Recovery Action Reboot MAS Server. If the problem persists, contact your technical support organization.
Technical Support Action Look at AML trace info for a call. Check if there are multiple copies of executable nbbcrs.exe running using the NT task manager. If so, kill both processes, then restart the EMCI service from the NT Control Panel. If problem persists, reboot the MAS server.
Severity Major
Description The MAS Blue Call Router could not get access to its internal data tables that stores call objects. Win32_rc is returned by API WaitSingleObject().
Impact Incoming call may remain unanswered in queue or an existing call may get dropped.
Recovery Action Reboot MAS Server. If the problem persists, contact your technical support organization.
Technical Support Action Look at AML trace info for a call. Check if there are multiple copies of executable nbbcrs.exe running using the NT task manager. If so, kill both processes, then restart the EMCI service from the NT Control Panel. If problem persists, reboot the MAS server.
Severity Debug
Description The MAS Blue Call Router could not get access to its internal data tables that stores call objects. Win32_rc is returned by API WaitSingleObject().
Impact Not Applicable
Recovery Action Not Applicable
Technical Support Action Not Applicable
Severity Minor
Description The MAS Blue Call Router could not get access to its internal data tables that stores call objects. Win32_rc is returned by API WaitSingleObject().
Impact Incoming call may remain unanswered in queue or an existing call may get dropped.
Recovery Action Reboot MAS Server. If the problem persists, contact your technical support organization.
Technical Support Action Look at AML trace info for a call. Check if there are multiple copies of executable nbbcrs.exe running using the NT task manager. If so, kill both processes, then restart the EMCI service from the NT Control Panel. If problem persists, reboot the MAS server.
Severity Minor
Description The MAS Blue Call Router could not get access to its internal data tables that stores call objects. Win32_rc is returned by API WaitSingleObject().
Impact Incoming call may remain unanswered in queue or an existing call may get dropped.
Recovery Action Reboot MAS Server. If the problem persists, contact your technical support organization.
Technical Support Action Look at AML trace info for a call. Check if there are multiple copies of executable nbbcrs.exe running using the NT task manager. If so, kill both processes, then restart the EMCI service from the NT Control Panel. If problem persists, reboot the MAS server.
Severity Debug
Description The MAS Blue Call Router could not clean up some internal data structures while shutting down. Win32_rc is returned by API CloseSemaphore().
Impact Not Applicable
Recovery Action Not Applicable
Technical Support Action Check return codes.
Severity Minor
Description The MAS Blue Call Router could not get access to its internal data tables that stores call objects. Win32_rc is returned by API WaitSingleObject().
Impact The call will be dropped.
Recovery Action Reboot MAS Server. If the problem persists, contact your technical support organization.
Technical Support Action Look at AML trace info for a call. Check if there are multiple copies of executable nbbcrs.exe running using the NT task manager. If so, kill both processes, then restart the EMCI service from the NT Control Panel. If problem persists, reboot the MAS server.
Severity Debug
Description The MAS Blue Call Router could not get access to its internal data tables that stores call objects. Win32_rc is returned by API WaitSingleObject().
Impact Not Applicable
Recovery Action Not Applicable
Technical Support Action Not Applicable
Severity Minor
Description The MAS Blue Call Router could not get access to its internal data tables that stores call objects. Win32_rc is returned by API WaitSingleObject().
Impact Incoming call may remain unanswered in queue or an existing call may get dropped.
Recovery Action Reboot MAS Server. If the problem persists, contact your technical support organization.
Technical Support Action Look at AML trace info for a call. Check if there are multiple copies of executable nbbcrs.exe running using the NT task manager. If so, kill both processes, then restart the EMCI service from the NT Control Panel. If problem persists, reboot the MAS server.
Severity Critical
Description The MAS Blue Call Router could not create a Semaphore object that is used to synchronize access to its internal data tables. Win32_rc is returned by API CreateSemaphore().
Impact The BCR will not start. This means that the MAS Server will not process any calls.
Recovery Action Reboot MAS Server. If the problem persists, contact your technical support organization.
Technical Support Action Check if there are multiple copies of executable nbbcrs.exe running using the NT task manager. If so, kill both processes, then restart the EMCI service from the NT Control Panel. If problem persists, reboot the MAS server.
Severity Major
Description The MAS Blue Call Router could not get access to its internal data tables that stores call objects. Win32_rc is returned by API WaitSingleObject().
Impact The outgoing call will not be made.
Recovery Action Reboot MAS Server. If the problem persists, contact your technical support organization.
Technical Support Action Check if there are multiple copies of executable nbbcrs.exe running using the NT task manager. If so, kill both processes, then restart the EMCI service from the NT Control Panel. If problem persists, reboot the MAS server.
Severity Major
Description The MAS Blue Call Router could not get access to its internal data tables that stores call objects. Win32_rc is returned by API WaitSingleObject().
Impact The outgoing call will not be made.
Recovery Action Reboot MAS Server. If the problem persists, contact your technical support organization.
Technical Support Action Check if there are multiple copies of executable nbbcrs.exe running using the NT task manager. If so, kill both processes, then restart the EMCI service from the NT Control Panel. If problem persists, reboot the MAS server.
Severity Major
Description The MAS Blue Call Router could not get access to its internal data tables that stores call objects. Win32_rc is returned by API WaitSingleObject().
Impact The outgoing call will be dropped.
Recovery Action Reboot MAS Server. If the problem persists, contact your technical support organization.
Technical Support Action Look at AML trace info for a call. Check if there are multiple copies of executable nbbcrs.exe running using the NT task manager. If so, kill both processes, then restart the EMCI service from the NT Control Panel. If problem persists, reboot the MAS server.
Severity Debug
Description The MAS Blue Call Router could not clean up some internal data structures while shutting down. Win32_rc is returned by API CloseSemaphore().
Impact Not Applicable
Recovery Action Not Applicable
Technical Support Action Check for return codes.
Severity Minor
Description The MAS Blue Call Router could not get access to its internal data tables that stores call objects. Win32_rc is returned by API WaitSingleObject().
Impact The outgoing call will not be made.
Recovery Action Reboot MAS Server. If the problem persists, contact your technical support organization.
Technical Support Action Look at AML trace info for a call. Check if there are multiple copies of executable nbbcrs.exe running using the NT task manager. If so, kill both processes, then restart the EMCI service from the NT Control Panel. If problem persists, reboot the MAS server.
Severity Debug
Description The MAS Blue Call Router could not get access to its internal data tables that stores call objects. Win32_rc is returned by API WaitSingleObject().
Impact Not Applicable
Recovery Action Not Applicable
Technical Support Action Not Applicable
Severity Minor
Description The MAS Blue Call Router could not get access to its internal data tables that stores call objects. Win32_rc is returned by API WaitSingleObject().
Impact The outgoing call will not be made.
Recovery Action Reboot MAS Server. If the problem persists, contact your technical support organization.
Technical Support Action Perform the following steps:
1. Look at AML trace info for a call.
2. Check if there are multiple copies of executable nbbcrs.exe running using the NT task manager.
3. If so, kill both processes, then restart the EMCI service from the NT Control Panel.
4. If problem persists, reboot the MAS server.
Severity Minor
Description The MAS Blue Call Router could not create a CTMS Group because an internal memory allocation failure occurred when it tried to create or operate on a KVset. This error may occur when a DS-30channel is being enabled.
Impact The DS-30 channel will not go into service.
Recovery Action Disable, run diags and re-enable channel. If the problem persists, contact your technical support organization.
Technical Support Action Perform the following steps:
1. Shutdown and restart the BCR.
2. Shutdown and restart the CTMS server.
Severity Minor
Description The MAS Blue Call Router could not create a CTMS Group because an error occurred in the CTMS server. This error may occur when a DS-30 channel is being enabled.The return code will give details on the specific error.
Impact The DS-30 channel will not go into service.
Recovery Action If the problem persists, contact your technical support organization.
Technical Support Action Perform the following steps:
1. Shutdown and restart the BCR.
2. Shutdown and restart the CTMS server.
Severity Minor
Description The MAS Blue Call Router could not destroy a CTMS Group because an internal memory allocation failure occurred when it tried to create or operate on a KVset. This error may occur when a DS-30 channel is being disabled.
Impact The DS-30 channel will not go out of service.
Recovery Action If the problem persists, contact your technical support organization.
Technical Support Action Perform the following steps:
1. Shutdown and restart the BCR.
2. Shutdown and restart the CTMS server.
Severity Minor
Description The MAS Blue Call Router could not destroy a CTMS Group because an error occurred in the CTMS server. This error may occur when a DS-30 channel is being disabled. The return code will give details on the specific error.
Impact The DS-30 channel will not go out of service.
Recovery Action If the problem persists, contact your technical support organization.
Technical Support Action Perform the following steps:
1. Shutdown and restart the BCR.
2. Shutdown and restart the CTMS server.
Severity Minor
Description The MAS Blue Call Router could not retrieve a CTMS Group from an application because an internal memory allocation failure occurred when it tried to create or operate on a KVset. This error may occur when a port is being disabled.
Impact The DS-30 channel will not go out of service.
Recovery Action If the problem persists, contact your technical support organization.
Technical Support Action Perform the following steps:
1. Shutdown and restart the BCR.
2. Shutdown and restart the CTMS server.
Severity Minor
Description The MAS Blue Call Router could not retrieve a CTMS Group from an application because an error occurred in the CTMS server. This error may occur when a port is being disabled. The return code will give details on the specific error.
Impact The DS-30 channel will not go out of service.
Recovery Action If the problem persists, contact your technical support organization.
Technical Support Action Perform the following steps:
1. Shutdown and restart the BCR.
2. Shutdown and restart the CTMS server.
Severity Minor
Description The MAS Blue Call Router could not handoff a CTMS Group to an application because an internal memory allocation failure occurred when it tried to create or operate on a KVset. This error may occur when a call is being presented to an application.
Impact The call will be dropped.
Recovery Action Disable, run diags and reenable the DS-30 channel.
Technical Support Action Perform the following steps:
1. Shutdown and restart the BCR.
2. Shutdown and restart the CTMS server.
Severity Minor
Description The MAS Blue Call Router could not handoff a CTMS Group to an application because an error occurred in the CTMS server. This error may occur when a call is being presented to an application. The return code will give details on the specific error.
Impact The call will be dropped.
Recovery Action Disable, run diags and reenable the DS-30 channel.
Technical Support Action Perform the following steps:
1. Shutdown and restart the BCR.
2. Shutdown and restart the CTMS server.
Severity Minor
Description The MAS Blue Call Router could not handoff a CTMS Group to an application because an error occurred in the CTMS server. This error may occur when a call is being presented to an application. The return code will give details on the specific error.
Impact The call will be dropped.
Recovery Action Disable, run diags and reenable the DS-30 channel.
Technical Support Action Perform the following steps:
1. Shutdown and restart the BCR.
2. Shutdown and restart the CTMS server.
Severity Debug
Description The MAS Blue Call Router could not shutdown the connection to the CTMS server because memory allocation failure occurred when it tried to create or operate on a KVset. This error may occur when the BCR is being shutdown.
Impact Not Applicable
Recovery Action Not Applicable
Technical Support Action Perform the following steps:
1. Check return codes.
2. Restart CTMS server.
Severity Debug
Description The MAS Blue Call Router could not shutdown the connection to the CTMS server because an error occurred in the CTMS server. This error may occur when the BCR is being shutdown. The return code will give details on the specific error.
Impact Not Applicable
Recovery Action Not Applicable
Technical Support Action Perform the following steps:
1. Check return codes.
2. Restart CTMS server.
Severity Debug
Description The MAS Blue Call Router could not shutdown the connection to the CTMS server because an error occurred in the CTMS server. This error may occur when the BCR is being shutdown. The return code will give details on the specific error.
Impact Not Applicable
Recovery Action Not Applicable
Technical Support Action Perform the following steps:
1. Check return codes.
2. Restart CTMS server.
Severity Critical
Description The MAS Blue Call Router could not create an Event object that is used to co-ordinate the creation and execution of the SCSA thread. This error may occur when the BCR is being started. Win32_rc is returned by API CreateEvent().
Impact The BCR will not start. This means that the MAS Server will not process any calls.
Recovery Action Reboot MAS Server. If the problem persists, contact your technical support organization.
Technical Support Action Perform the following steps:
1. Check if there are multiple copies of executable nbbcrs.exe running using the NT task manager.
2. If so, kill both processes, then restart the EMCI service from the NT Control Panel.
3. If problem persists, reboot the MAS server.
Severity Critical
Description The MAS Blue Call Router could not initiate a connection to the CTMS server because an error occurred in the CTMS server. This error may occur when the BCR is being started. The return code will give details on the specific error.
Impact The BCR will not start. This means that the MAS Server will not process any calls.
Recovery Action Reboot MAS Server. If the problem persists, contact your technical support organization.
Technical Support Action Perform the following steps:
1. Check if there are multiple copies of executable nbbcrs.exe running using the NT task manager.
2. If so, kill both processes, then restart the EMCI service from the NT Control Panel.
3. If problem persists, reboot the MAS server.
Severity Critical
Description The MAS Blue Call Router could not initiate a connection to the CTMS server because memory allocation failure occurred when it tried to create or operate on a KVset. This error may occur when the BCR is being started.
Impact The BCR will not start. This means that the MAS Server will not process any calls.
Recovery Action Reboot MAS Server. If the problem persists, contact your technical support organization.
Technical Support Action Perform the following steps:
1. Check if there are multiple copies of executable nbbcrs.exe running using the NT task manager.
2. If so, kill both processes, then restart the EMCI service from the NT Control Panel.
3. If problem persists, reboot the MAS server.
Severity Critical
Description The MAS Blue Call Router could not initiate a connection to the CTMS server because an error occured in the CTMS server. This error may occur when the BCR is being started.
Impact The BCR will not start. This means that the MAS Server will not process any calls.
Recovery Action Reboot MAS Server. If the problem persists, contact your technical support organization.
Technical Support Action Perform the following steps:
1. Check if there are multiple copies of executable nbbcrs.exe running using the NT task manager.
2. If so, kill both processes, then restart the EMCI service from the NT Control Panel.
3. If problem persists, reboot the MAS server.
Severity Critical
Description The MAS Blue Call Router could not create a Semaphore object that is used to synchronize access to the SCSA thread's message queue. This error may occur when the BCR is being started. Win32_rc is returned by API CreateSemaphore().
Impact The BCR will not start. This means that the MAS Server will not process any calls.
Recovery Action Reboot MAS Server. If the problem persists, contact your technical support organization.
Technical Support Action Perform the following steps:
1. Check if there are multiple copies of executable nbbcrs.exe running using the NT task manager.
2. If so, kill both processes, then restart the EMCI service from the NT Control Panel.
3. If problem persists, reboot the MAS server.
Severity Critical
Description The MAS Blue Call Router could not create and execute the SCSA thread. The SCSA thread is a critical component of the BCR and without it no call processing can take place. This error may occur when the BCR is being started. Win32_rc is returned by A
Impact The BCR will not start. This means that the MAS Server will not process any calls.
Recovery Action Reboot MAS Server. If the problem persists, contact your technical support organization.
Technical Support Action Perform the following steps:
1. Check if there are multiple copies of executable nbbcrs.exe running using the NT task manager.
2. If so, kill both processes, then restart the EMCI service from the NT Control Panel.
3. If problem persists, reboot the MAS server.
Severity Critical
Description The MAS Blue Call Router's SCSA thread did not execute. The SCSA thread is a critical component of the BCR and without it no call processing can take place. This error may occur when the BCR is being started. Win32_rc is returned by API WaitForSingl
Impact The BCR will not start. This means that the MAS Server will not process any calls.
Recovery Action Reboot MAS Server. If the problem persists, contact your technical support organization.
Technical Support Action Perform the following steps:
1. Check if there are multiple copies of executable nbbcrs.exe running using the NT task manager.
2. If so, kill both processes, then restart the EMCI service from the NT Control Panel.
3. If problem persists, reboot the MAS server.
Severity Debug
Description The MAS Blue Call Router could not create an Event object that is used to co-ordinate the stopping of the SCSA thread. This error may occur when the BCR is being shutdown. Win32_rc is returned by API CreateEvent().
Impact Not Applicable
Recovery Action Not Applicable
Technical Support Action Check return codes
Severity Debug
Description An internal thread withing the MAS Blue Call Router could not send a message to another thread because memory allocation failure occurred when it tried to create or operate on a KVset.
Impact Not Applicable
Recovery Action Not Applicable
Technical Support Action Check return codes
Severity Debug
Description An internal thread withing the MAS Blue Call Router could not send a message to another thread because an error occurred in the CTMS server.
Impact Not Applicable
Recovery Action Not Applicable
Technical Support Action Check return codes
Severity Debug
Description One of MAS Blue Call Router's threads was unable to send a message to the SCSA thread because the SCSA message queue was being blocked by another thread. This event signals either a memory corruption problem or that the SCSA thread is dead. In either case the BCR should be restarted if the problem persists.
Impact Not Applicable
Recovery Action Not Applicable
Technical Support Action Not Applicable
Severity Critical
Description An internal thread withing the MAS Blue Call Router could not start the SCSA thread because memory allocation failure occurred when it tried to create or operate on a KVset.
Impact The BCR will not start. This means that the MAS Server will not process any calls.
Recovery Action Reboot MAS Server. If the problem persists, contact your technical support organization.
Technical Support Action Perform the following steps:
1. Check if there are multiple copies of executable nbbcrs.exe running using the NT task manager.
2. If so, kill both processes, then restart the EMCI service from the NT Control Panel.
3. If problem persists, reboot the MAS server.
Severity Critical
Description The MAS Blue Call Router's SCSA thread could not signal to the main thread that it has started. The error returned is from WIN32 API SetEvent().
Impact The BCR will not start. This means that the MAS Server will not process any calls.
Recovery Action Reboot MAS Server. If the problem persists, contact your technical support organization.
Technical Support Action Perform the following steps:
1. Check if there are multiple copies of executable nbbcrs.exe running using the NT task manager.
2. If so, kill both processes, then restart the EMCI service from the NT Control Panel.
3. If problem persists, reboot the MAS server.
Severity Debug
Description The MAS Blue Call Router's SCSA thread could not signal to the main thread that the thread has terminated. The error returned is from WIN32 API SetEvent(). This event may occur when the BCR is being shutdown.
Impact Not Applicable
Recovery Action Not Applicable
Technical Support Action Not Applicable
Severity Debug
Description The MAS Blue Call Router's SCSA thread could not signal to the main thread that the thread has terminated. The error returned is from WIN32 API SetEvent(). This event may occur when the BCR is being shutdown.
Impact Not Applicable
Recovery Action Not Applicable
Technical Support Action Not Applicable
Severity Minor
Description The MAS Blue Call Router's SCSA thread received a unexpected or invalid event from the CTMS server during Group operations. As a result the call will be cleared. This event may happen during maintenace operation on a DS-30 channel.
Impact If a call was active on the channel it will be dropped.
Recovery Action Disable, run diags and re-enable the DS-30 channel
Technical Support Action Perform the following steps:
1. Restart BCR.
2. Restart CTMS.
3. Check return codes.
Severity Minor
Description The MAS Blue Call Router's SCSA thread could not allocate memory for a KVset during Group operations. As a result the call will be cleared.
Impact If a call was active on the channel it will be dropped.
Recovery Action Disable, run diags and re-enable the DS-30 channel
Technical Support Action Perform the following steps:
1. Restart BCR.
2. Restart CTMS.
3. Check return codes.
Severity Debug
Description This fault could occur due to Group 'caching'.
Impact No system impact.
Recovery Action None.
Technical Support Action None.
Severity Debug
Description The MAS Blue Call Router's SCSA thread received an unexpected or invalid event from the CTMS server during Group handoff.
Impact If the error is no resource or no application, BCR will retry. Otherwise, the call will be cleared.
Recovery Action Disable, run diagnostics and re-enable the DS-30 channel. Check if all DSP resources and applications are running.
Technical Support Action Perform the following steps:
211. Restart BCR.
2. Restart CTMS.
3. Check return codes.
Severity Minor
Description The MAS Blue Call Router's SCSA thread could not allocate memory for a KVset during Group operations. As a result the call will be cleared.
Impact If a call was active on the channel it will be dropped.
Recovery Action Disable, run diags and re-enable the DS-30 channel
Technical Support Action Perform the following steps:
1. Restart BCR.
2. Restart CTMS.
3. Check return codes.
Severity Major
Description The MAS Blue Call Router SCSA thread experienced an unexpected and unhandled exception during program execution.
Impact Incoming calls will not be answered or maintenace operations on a DS-30 channel may fail.
Recovery Action Reboot MAS Server. If the problem persists, contact your technical support organization.
Technical Support Action Perform the following steps:
1. Look at AML trace info for a call.
2. CCheck if there are multiple copies of executable nbbcrs.exe running using the NT task manager.
3. If so, kill both processes, then restart the EMCI service from the NT Control Panel.
4. If problem persists, reboot the MAS server.
Severity Debug
Description The MAS Blue Call Router SCSA thread received an unexpected event from the CTMS server. The information in this event may be valuable in debugging this problem. This information should be forwared to your MAS .
Impact Not Applicable
Recovery Action Not Applicable
Technical Support Action Not Applicable
Severity Debug
Description The MAS Blue Call Router was trying to get the current state of one of the MAS port agents but TAPI replied with an error.
Impact Not Applicable
Recovery Action Not Applicable
Technical Support Action Not Applicable
Severity Minor
Description The MAS Blue Call Router was trying to get the current state of one of the MAS port agents but TAPI replied with an error.
Impact DS-30 channel will not go into service
Recovery Action Disable, run diags and re-enable the DS-30 channel. If problem persists contact your technical support organization.
Technical Support Action Perform the following steps:
1. Verify if TAPI server is running and the TSP data is correct.
2. Check if ACDPROXY is running.
3. Check if the AML link is connected.
Severity Debug
Description The MAS Blue Call Router was trying to set the state of one of the MAS port agents but TAPI replied with an error.
Impact Not Applicable
Recovery Action Not Applicable
Technical Support Action Not Applicable
Severity Minor
Description The MAS Blue Call Router was trying to set the state of one of the MAS port agents but TAPI replied with an error.
Impact DS-30 channel will not go into service
Recovery Action Disable, run diags and re-enable the DS-30 channel. If problem persists contact your technical support organization.
Technical Support Action Perform the following steps:
1. Verify if TAPI server is running and the TSP data is correct.
2. Check if ACDPROXY is running.
3. Check if the AML link is connected.
Severity Minor
Description The MAS Blue Call Router failed to get the current status of a call..
Impact DS-30 channel will not go into service. If a call was active on the channel it will be dropped.
Recovery Action Disable, run diags and re-enable the DS-30 channel. If problem persists contact your technical support organization.
Technical Support Action Perform the following steps:
1. Verify if TAPI server is running and the TSP data is correct.
2. Check if ACDPROXY is running.
3. Check if the AML link is connected.
Severity Major
Description The MAS Blue Call Router failed to add a call to its internal data structure.
Impact OutCall request will fail.
Recovery Action If the problem persists, contact your technical support organization.
Technical Support Action Shutdown and Restart the BCR.
Severity Debug
Description The MAS Blue Call Router failed to answer a call.
Impact Not Applicable
Recovery Action Not Applicable
Technical Support Action Not Applicable
Severity Debug
Description The MAS Blue Call Router failed to disconnect a call.
Impact Not Applicable
Recovery Action Not Applicable
Technical Support Action Not Applicable