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
Severity Debug
Description The MAS Blue Call Router failed to idle 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
Severity Debug
Description The MAS Blue Call Router failed to deallocate memory for an idle call.
Impact Not Applicable
Recovery Action Not Applicable
Technical Support Action Not Applicable
Severity Debug
Description The MAS Blue Call Router failed to give treatment to a call in the CDN.
Impact Not Applicable
Recovery Action Not Applicable
Technical Support Action Not Applicable
Severity Minor
Description The MAS Blue Call Router failed to give treatment to a call in the CDN.
Impact Call will get ring no answer treatment.
Recovery Action Disable, run diags and re-enable the DS-30 channel. If problem persists contact your 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 give IVR treatment to a call in the CDN.
Impact Call will get ring no answer treatment.
Recovery Action Disable, run diags and re-enable the DS-30 channel. If problem persists contact your 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 open a TAPI line device. The BCR opens line devices corresponding to ports and CDN to monitor for incoming calls. If these devices cannot be opened, calls will not be processed.
Impact If device is CDN, it will remain in default mode. If device is agent, it will will not load.
Recovery Action Check if the Telephony data is correct for CDN and MMA agents. If the problem persists, contact your support organization.
Technical Support Action Perform the following steps:
1. Check NGen tables for CDN and CCr.
2. Check TSP tables.
3. Check switch config.
4. Shutdown and restart TAPI server.
Severity Debug
Description The MAS Blue Call Router failed to close a TAPI line device. The BCR closes line devices corresponding to ports and CDN to stop monitor for incoming calls. If these devices cannot be closed, calls will be presented to these devices on the switch.
Impact If device is CDN, it will remain in control mode. If device is agent, it will will remain in log-in state.
Recovery Action If CDN remains in Control mode, force it to Default mode using overlay 23.
Technical Support Action Not Applicable
Severity Major
Description The MAS Blue Call Router failed to allocate memory for a TAPI structure that is used to get information about a TAPI line device. Without this information, BCR will not be able to open the TAPI line device.
Impact If device is CDN, it will remain in default mode. If device is agent, it will will not load.
Recovery Action Check if the Telephony data is correct for CDN and MMA agents. If the problem persists, contact your support organization.
Technical Support Action Perform the following steps:
1. Check NGen tables for CDN and CCr.
2. Check TSP tables.
3. Check switch config.
4. Shutdown and restart TAPI server.
Severity Major
Description The MAS Blue Call Router failed to allocate memory for a TAPI structure that is used to get information about a TAPI line device. Without this information, BCR will not be able to open the TAPI line device.
Impact If device is CDN, it will remain in default mode. If device is agent, it will will not load.
Recovery Action Check if the Telephony data is correct for CDN and MMA agents. If the problem persists, contact your support organization.
Technical Support Action Perform the following steps:
1. Check NGen tables for CDN and CCr.
2. Check TSP tables.
3. Check switch config.
4. Shutdown and restart TAPI server.
Severity Major
Description The MAS Blue Call Router failed to get address information about a TAPI line device. Without this information, BCR will not be able to open the TAPI line device.
Impact If device is CDN, it will remain in default mode. If device is agent, it will will not load.
Recovery Action Check if the Telephony data is correct for CDN and MMA agents. If the problem persists, contact your support organization.
Technical Support Action Perform the following steps:
1. Check NGen tables for CDN and CCr.
2. Check TSP tables.
3. Check switch config.
4. Shutdown and restart TAPI server.
Severity Major
Description The MAS Blue Call Router failed to allocate memory for a TAPI structure that is used to get information about a TAPI line device. Without this information, BCR will not be able to open the TAPI line device.
Impact If device is CDN, it will remain in default mode. If device is agent, it will will not load.
Recovery Action Check if the Telephony data is correct for CDN and MMA agents. If the problem persists, contact your support organization.
Technical Support Action Perform the following steps:
1. Check NGen tables for CDN and CCr.
2. Check TSP tables.
3. Check switch config.
4. Shutdown and restart TAPI server.
Severity Major
Description The MAS Blue Call Router failed to allocate memory for a TAPI structure that is used to get information about a TAPI line device. Without this information, BCR will not be able to open the TAPI line device.
Impact If device is CDN, it will remain in default mode. If device is agent, it will will not load.
Recovery Action Check if the Telephony data is correct for CDN and MMA agents. If the problem persists, contact your support organization.
Technical Support Action Perform the following steps:
1. Check NGen tables for CDN and CCr.
2. Check TSP tables.
3. Check switch config.
4. Shutdown and restart TAPI server.
Severity Major
Description The MAS Blue Call Router failed to get device information about a TAPI line device. Without this information, BCR will not be able to open the TAPI line device.
Impact If device is CDN, it will remain in default mode. If device is agent, it will will not load.
Recovery Action Check if the Telephony data is correct for CDN and MMA agents. If the problem persists, contact your support organization.
Technical Support Action Perform the following steps:
1. Check NGen tables for CDN and CCr.
2. Check TSP tables.
3. Check switch config.
4. Shutdown and restart TAPI 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 TELE 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 customer 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 an I/O Completion port that is used to receives callprocessing messages from TAPI. 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 customer 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 failed to allocate memory for a TAPI structure that is used to get information about TAPI. Without this information, BCR will not be able to start.
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 customer 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 failed to allocate memory for a TAPI structure that is used to get information about TAPI. Without this information, BCR will not be able to start.
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 customer 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 failed to get applicaton information from TAPI. Without this information, BCR will not be able to start.
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 customer 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 will not run with the installed version of TAPI. BCR needs at least version 2.0 to run.
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 customer 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.
4. Run a Dummy upgrade to update files.
Severity Critical
Description The MAS Blue Call Router failed to detect any line devices in TAPI. Without this information, BCR will not be able to start.
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 customer 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 TELE 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 customer 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 TELE thread. The TELE 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 CreateThread.
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 customer 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 TELE thread did not start. The TELE 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 customer 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 TELE 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 The MAS Blue Call Router's TELE 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 return codes.
Severity Debug
Description One of MAS Blue Call Router's thread's was unable to send a message to the TELE thread. This event signals either a memory corruption problem or that the TELE thread is dead. In either case the BCR should be restarted.
Impact Not Applicable
Recovery Action Not Applicable
Technical Support Action Restart the BCR if problem persists.
Severity Debug
Description One of MAS Blue Call Router's threads was unable to send a message to the TELE thread because the TELE message queue was being blocked by another thread. This event signals either a memory corruption problem or that the TELE 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 Restart the BCR if problem persists.
Severity Debug
Description The MAS Blue Call Router's TELE 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 Minor
Description The MAS Blue Call Router's TELE thread was not able to locate a call in the Pending Call Request queue for the purpose of storing information for a new incoming call.
Impact Call will not be offered to application.
Recovery Action Not Applicable
Technical Support Action Not Applicable
Severity Minor
Description The MAS Blue Call Router's TELE thread was not able to allocate memory for an internal structure that is used to accept an incoming call..
Impact Call will not be offered to application.
Recovery Action Check if the Telephony data is correct for CDN and MMA agents. If the problem persists, contact your support organization.
Technical Support Action Perform the following steps:
1. Check NGen tables for CDN and CCr.
2. Check TSP tables.
3. Check switch config.
4. Shutdown and restart TAPI server.
Severity Minor
Description The MAS Blue Call Router's TELE thread was not able to allocate memory for an internal structure that is used to accept an incoming call.
Impact Call will not be offered to application.
Recovery Action Check if the Telephony data is correct for CDN and MMA agents. If the problem persists, contact your support organization.
Technical Support Action Perform the following steps:
1. Check NGen tables for CDN and CCr.
2. Check TSP tables.
3. Check switch config.
4. Shutdown and restart TAPI server.
Severity Minor
Description The MAS Blue Call Router's TELE thread was not able to query call information from TAPI.
Impact Call will not be offered to application.
Recovery Action Check if the Telephony data is correct for CDN and MMA agents. If the problem persists, contact your support organization.
Technical Support Action Perform the following steps:
1. Check NGen tables for CDN and CCr.
2. Check TSP tables.
3. Check switch config.
4. Shutdown and restart TAPI server.
Severity Minor
Description The MAS Blue Call Router's TELE thread was not able to deallocate a call.
Impact Memory will not be released.
Recovery Action Use Winnt Performance monitor to track memory usage. Check Telephony configuration, reboot server to clear problem
Technical Support Action Restart the BCR
Severity Debug
Description The MAS Blue Call Router's TELE thread was not able to delete a call from its queue.
Impact Not Applicable
Recovery Action Not Applicable
Technical Support Action Not Applicable
Severity Debug
Description The MAS Blue Call Router's TELE thread was not able to add a new call to its queue.
Impact Not Applicable
Recovery Action Not Applicable
Technical Support Action Not Applicable
Severity Debug
Description The MAS Blue Call Router's TELE thread was not able to locate a call in its queue for the purpose of matching a TAPI LINE_REPLY Id to the call.
Impact Not Applicable
Recovery Action Not Applicable
Technical Support Action Not Applicable
Severity Debug
Description The MAS Blue Call Router's TELE thread was not able to signal that line reply was received for a call from TAPI.
Impact Not Applicable
Recovery Action Not Applicable
Technical Support Action Not Applicable
Severity Debug
Description The MAS Blue Call Router's TELE thread was not able to signal that line reply was received for a call from TAPI.
Impact Not Applicable
Recovery Action Not Applicable
Technical Support Action Not Applicable
Severity Critical
Description The MAS Blue Call Router (BCR)' TELE thread received an unexpected error when communicating with other threads with the process. The error returned is from WIN32 API GetQueuedCompletionStatus(). The TELE thread will terminate itself and the BCR will restart by itself.
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 customer 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.
4. Run a Dummy upgrade to update files.
Severity Debug
Description The MAS Blue Call Router's TELE thread was not able to shutdown the the TAPI line during process shutdown.
Impact Not Applicable
Recovery Action Not Applicable
Technical Support Action Check return codes.
Severity Debug
Description The MAS Blue Call Router's TELE 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 codes.
Severity Minor
Description The MAS Blue Call Router (BCR) TELE thread experienced an unexpected and unhandled exception during program execution. The information in this event may be valuable in debugging this problem.
Impact Incoming calls will not be answered.
Recovery Action Reboot MAS Server. If the problem persists, contact your customer 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 A MAS Blue Call Router (BCR) thread was not able to start a call timer.
Impact Incoming calls will not be answered.
Recovery Action Reboot MAS Server. If the problem persists, contact your customer 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.
5. Restart CTMS if necessary.
Severity Minor
Description A MAS Blue Call Router (BCR) thread was not able to stop a call timer.
Impact Incoming calls will not be dropped
Recovery Action Reboot MAS Server. If the problem persists, contact your customer 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.
4. Restart the EMCI service from the NT Control Panel.
5. If problem persists, reboot the MAS server.
6. Restart CTMS if necessary.
Severity Minor
Description A MAS Blue Call Router (BCR) thread was not able to signal that a call timer has expired.
Impact Incoming calls will not be answered.
Recovery Action Reboot MAS Server. If the problem persists, contact your customer 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.
4. Restart the EMCI service from the NT Control Panel.
5. If problem persists, reboot the MAS server.
6. Restart CTMS if necessary.
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 customer 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.
3. Restart the EMCI service from the NT Control Panel.
4. If problem persists, reboot the MAS server.
Severity Major
Description A MAS Blue Call Router (BCR) thread was not able to start a call timer because no memory is available.
Impact Incoming calls will not be answered.
Recovery Action Reboot MAS Server. If the problem persists, contact your customer 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.
4. Restart the EMCI service from the NT Control Panel.
5. If problem persists, reboot the MAS server.
6. Restart CTMS if necessary.
Severity Debug
Description The MAS Blue Call Router (BCR) could not destroy a Semaphore object that is used to synchronize access to the Timer queue, 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 Not Applicable
Severity Minor
Description A MAS Blue Call Router (BCR) thread attempted to start a timer that already exists.
Impact Incoming calls will not be answered.
Recovery Action Reboot MAS Server. If the problem persists, contact your customer 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.
4. Restart the EMCI service from the NT Control Panel.
5. If problem persists, reboot the MAS server.
6. Restart CTMS if necessary.
Severity Minor
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 enabling a DS-30 channel. The information reported in this event may be valuable in debugging this fault.
Impact The DS-30 channel will no longer accept any new call.
Recovery Action Disable and re-enable the DS-30 channel.
Technical Support Action Perform the following steps:
1. Disable and re-enable the DS-30 channel
2. If the problem persists, shutdown and re-start the BCR.
3. Check Database tables.
Severity Minor
Description An internal error occurred in the MAS Blue Call Router (BCR). This error indicates that the BCR could not delete a DS-30 channel from the idle resource queue while enabling a DS-30 channel. The information reported in this event may be valuable in debugging this fault.
Impact The DS-30 channel will no longer accept any new call.
Recovery Action Disable and re-enable the DS-30 channel.
Technical Support Action Perform the following steps:
1. Disable and re-enable the DS-30 channel
2. If the problem persists, shutdown and re-start the BCR.
3. Check Database tables.
Severity Minor
Description An internal error occurred in the MAS Blue Call Router (BCR). This error indicates that the BCR could not open a TAPI line while enabling a DS-30 channel. The information reported in this event may be valuable in debugging this fault.
Impact The DS-30 channel will will not load.
Recovery Action Check if the Telephony data is correct for CDN and MMA agents. If the problem persists, contact your support organization.
Technical Support Action Perform the following tasks:
1. Check NGen tables for CDN and CCr.
2. Check TSP tables.
3. Check switch config.
4. Shutdown and restart TAPI server.
Severity Minor
Description An internal error occurred in the MAS Blue Call Router (BCR). This error indicates that the BCR could not return a DS-30 channel to the idle resource queue while enabling a DS-30channel. The information reported in this event may be valuable in debugging this fault.
Impact The DS-30 channel will will not load.
Recovery Action Check if the Telephony data is correct for CDN and MMA agents. If the problem persists, contact your support organization.
Technical Support Action Perform the following tasks:
1. Check NGen tables for CDN and CCr.
2. Check TSP tables.
3. Check switch config.
4. Shutdown and restart TAPI server.
Severity Minor
Description An internal error occurred in the MAS Blue Call Router (BCR). This error indicates that the BCR could not close a TAPI line while disabling a DS-30 channel
Impact The DS-30 channel will will not load.
Recovery Action Check if the Telephony data is correct for CDN and MMA agents. If the problem persists, contact your support organization.
Technical Support Action Perform the following tasks:
1. Check NGen tables for CDN and CCr.
2. Check TSP tables.
3. Check switch config.
4. Shutdown and restart TAPI server.
Severity Information
Description This is an informational event indicating that the MAS Blue Call Router has started.
Impact Not Applicable
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 MAS CT Media Server (CTMS). This error occurs when the BCR is being started and the necessary event handler functions to shutdown the BCR cannot be attached.
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 customer support organization.
Technical Support Action Perform the following tasks:
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 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 started and the necessary event handler functions to shutdown the BCR cannot be attached.
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 customer support organization.
Technical Support Action Perform the following tasks:
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 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 and the necessary event handler functions to shutdown the BCR cannot be detached.
Impact Not Applicable
Recovery Action Not Applicable
Technical Support Action Not Applicable
Severity Minor
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.
Impact The DS-30 channel will no longer accept any new call.
Recovery Action Disable and re-enable the DS-30 channel.
Technical Support Action Perform the following steps:
1. Disable and re-enable the DS-30 channel.
2. If the problem persists, shutdown and re-start the BCR.
3. Check Database tables.
Severity Major
Description An internal error occurred in the MAS Blue Call Router (BCR). This error indicates that the BCR could not add a new call to the PCR queue. The information reported in this event may be valuable in debugging this fault. This information should be passed to your Nortel Networks representative.
Impact The call will not be answered.
Recovery Action If the problem persists, contact your Nortel Networks representative.
Technical Support Action Restart the BCR.
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 If the problem persists, contact your Nortel Networks representative.
Technical Support Action Check if the MAS Configuration Manager service is running.
Severity Minor
Description The MAS Blue Call Router (BCR) could not get the current line state of an agent on the switch.
Impact The DS-30 channel will no longer accept any new call.
Recovery Action If the problem persists, contact your Nortel Networks representative.
Technical Support Action Check if the TAPI service is running and that the AML link is connected.
Severity Minor
Description The MAS Blue Call Router (BCR) could not handoff a call to Application. BCR will retry the handoff in 6 seconds.
Impact The Incoming call will be answered with some delay on this port.
Recovery Action If the problem persists, contact your Nortel Networks representative.
Technical Support Action Check if the TAPI service and Application is running.
Severity Minor
Description The MAS Blue Call Router (BCR) could not configure a CTMS Group to perform Dtmf tone detection because an internal memory allocation failure occurred when it tried to create or operate on a Kvset. This error may occur when a call with inband Dtmf tone CallInfo arrived.
Impact The call will be dropped.
Recovery Action Disable, run diags and re-enable the DS-30 channel.
Technical Support Action Perform the following steps:
1. Disable and restart the BCR.
2. Shutdown and restart the CTMS server.
Severity Minor
Description The MAS Blue Call Router could not configure a CTMS Group to perform Dtmf tone detection because an error occurred in the CTMS server. This error may occur when a call with inband Dtmf tone CallInfo arrived. The return code will give details on the specific error.
Impact The call will be dropped.
Recovery Action Disable, run diags and re-enable the DS-30 channel.
Technical Support Action Perform the following steps:
1. Disable and restart the BCR.
2. Shutdown and restart the CTMS server.
Severity INFO
Description This is an informational event indicating that no more CCr is available to handle call until All_Port_Busy flag has been cleared.
Impact Not applicable
Recovery Action Not applicable
Technical Support Action Not applicable
Severity MINOR
Description An internal error occurred in the Blue Call Router (BCR). This error indicates that the BCR receives an unknown CCr state while enabling a DS-30 channel. The information reported in this event may be valuable in debugging this fault.
Impact The DS-0 channel will no longer accept any new call.
Recovery Action Disable and re-enable the DS-0 channel.
Technical Support Action Perform the following steps:
1. Disable and re-enable the DS-0 channel
2. If the problem persists, shutdown and re-start the BCR.
3. Check Database tables.
Severity MINOR
Description An internal error occurred in the Blue Call Router (BCR). This error indicates that the BCR receives an unknown CCr state while disabling or courtesy disabling a DS-30 channel. The information reported in this event may be valuable in debugging this fault.
Impact The DS-0 channel will remain in invalid state and will not be able to use it to accept call in future.
Recovery Action Disable and re-enable the DS-0 channel.
Technical Support Action Perform the following steps:
1. Disable and re-enable the DS-0 channel
2. If the problem persists, shutdown and re-start the BCR.
Severity MINOR
Description An internal error occurred in the Blue Call Router (BCR). This error indicates that the BCR receives an unknown CCr state while reloading a DS-30 channel. The information reported in this event may be valuable in debugging this fault.
Impact The DS-0 channel is never destroy or create. This channel is locked in out of service state.
Recovery Action Disable and re-enable the DS-0 channel.
Technical Support Action Perform the following steps:
1. Disable and re-enable the DS-0 channel
2. If the problem persists, shutdown and re-start the BCR.
Severity MINOR
Description An internal error occurred in the Blue Call Router (BCR). This error indicates that the BCR receives an unknown CCr state while disconnecting a call by retrieving the group back from the application. The information reported in this event may be valuable in debugging this fault.
Impact The call will still be active if the call is in connected state
Recovery Action Disable and re-enable the DS-0 channel.
Technical Support Action Perform the following steps:
1. Disable and re-enable the DS-0 channel
2. If the problem persists, shutdown and re-start the BCR.
Severity DEBUG
Description An internal error occurred in the Blue Call Router (BCR). This error indicates that the BCR receives an unknown CCr state when MaintState timer has expired. The information reported in this event may be valuable in debugging this fault.
Impact DS-0 will remain in current state and timeout event is ignored.
Recovery Action Disable and re-enable the DS-0 channel.
Technical Support Action Perform the following steps:
1. Disable and re-enable the DS-0 channel
2. If the problem persists, shutdown and re-start the BCR.
Severity MINOR
Description An internal error occurred in the Blue Call Router (BCR). This error indicates that the BCR receives an unknown CCr state after finished creating a group. The information reported in this event may be valuable in debugging this fault.
Impact No action was done upon completing group creation. If problem persists, group resources will be wasted
Recovery Action Disable and re-enable the DS-0 channel.
Technical Support Action Perform the following steps:
1. Disable and re-enable the DS-0 channel
2. If the problem persists, shutdown and re-start the BCR.
Severity MINOR
Description An internal error occurred in the Blue Call Router (BCR). This error indicates that the BCR receives an unknown CCr state after finished destroying a group. The information reported in this event may be valuable in debugging this fault.
Impact No action was done upon completing group destruction. DS-0 will remain in current state.
Recovery Action Disable and re-enable the DS-0 channel.
Technical Support Action (1)Disable and re-enable the DS-0 channel (2)If the problem persists, shutdown and re-start the BCR.
Severity MINOR
Description An internal error occurred in the Blue Call Router (BCR). This error indicates that the BCR receives an unknown CCr state after finished retrieving a group. The information reported in this event may be valuable in debugging this fault.
Impact Failed to handle retrieved group. DS-0 will remain in current state.
Recovery Action Disable and re-enable the DS-0 channel.
Technical Support Action (1)Disable and re-enable the DS-0 channel (2)If the problem persists, shutdown and re-start the BCR.
Severity DEBUG
Description SQL Error occurred in BCR when BCR tries to log internal errors.
Impact No error logs generate for all database errors.
Recovery Action Check and restart the Database service. If the problem persists, contact your support organization.
Technical Support Action Check if the SQL database service is running. Shutdown and restart the BCR.
Severity CRITICAL
Description The Symposium Blue Call Router (BCR) could not fetch the storage and data type for a column in a result set that was read from the Symposium database.
Impact BCR will not start.
Recovery Action If the problem persists, contact your Nortel representative.
Technical Support Action (1) Check if the SQL database is running (2) Shutdown and restart the BCR. (3) Check if the NBCCR table is defined and contains correct data.
Severity DEBUG
Description The Symposium Blue Call Router (BCR) could not handle a LINE_AGENTSTATUS message on behalf of an agent due to invalid agent type. It's neither a CDN nor ACD call. The information reported in this event may be valuable in debugging this fault.
Impact Not applicable
Recovery Action Restart BCR. If the problem persists, contact your customer support organization.
Technical Support Action Restart BCR. If the problem persists, contact your customer support organization.
Severity DEBUG
Description An internal error occurred in Blue Call Router. Failed to return group due to Null CR pointer.
Impact Group never returns.
Recovery Action Re-enable the DS-0. If problem persist, restart BCR or contact Nortel Representatives.
Technical Support Action Re-enable the DS-0. If problem persist, restart BCR or contact Nortel Representatives.
Severity DEBUG
Description The Blue Call Router's SCSA 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 INFO
Description The Blue Call Router's SCSA thread was instructed to check if a DS-0 has any pending calls. This indicates that this DS-0 has no pending calls.
Impact Not necessary to configure or unconfigure group.
Recovery Action Not applicable
Technical Support Action Not applicable
Severity DEBUG
Description The Blue Call Router's SCSA thread has received invalid events from CT Media, either SCR or session event. This event will not handle by BCR.
Impact This CT event will not be ignored
Recovery Action Not applicable
Technical Support Action Not applicable
Severity MINOR
Description BCR fails to issue a CTgrp_x() command to the CT server (where x = retrieve, destroy, handoff and configure) when trying to destroy a group due to invalid handle.
Impact CTgrp command will never be executed.
Recovery Action Check any other previous event logs. Check CT server.
Technical Support Action Check any other previous event logs. Check CT server.
Severity MAJOR
Description The Blue Call Router (BCR) could not find a matching record in the Service DN (SDN) table (aka NBAccessDN table in the database) for a call.
Impact Calls to this DN will be given Fast Busy tone and disconnected or Ring no answer
Recovery Action Re-enter the DN in the ASDN table from the Client PC
Technical Support Action Re-enter the DN in the ASDN table from the Client PC
Severity MAJOR
Description Read table failed when searching the ASDN table to find a matching record for a client request or incoming call
Impact Unable to make call or receive call for this DN
Recovery Action Check any other previous event logs. Check the DN in the ASDN table
Technical Support Action Check any other previous event logs. Check the DN in the ASDN table
Severity DEBUG
Description An internal error occurred in the Blue Call Router (BCR). This error indicates that the BCR receives an unexpected timeout event while the call is pending for TSP to collect info. The infomration reported in this event may be valuable in debugging this fault.
Impact The call will revert back to pending state, doing ASDN lookup again on the call.
Recovery Action Not applicable
Technical Support Action Not applicable
Severity DEBUG
Description An internal error occurred in the Blue Call Router (BCR). This error indicates that the BCR receives an unexpected call state while call's PM timer expires. The infomration reported in this event may be valuable in debugging this fault.
Impact The call will remain in the queue while timer still expires.
Recovery Action Not applicable
Technical Support Action Not applicable
Severity DEBUG
Description An internal error occurred in the Blue Call Router (BCR). This error indicates that the BCR generates a null pointer while doing call processing implementations to the call. The call may be in faulty state or memory corruptions occur.
Impact Unable to restart expired timer, the call will result in faulty state.
Recovery Action Re-enable the DS-0. If problem persist, restart BCR or contact Nortel Representatives.
Technical Support Action Re-enable the DS-0. If problem persist, restart BCR or contact Nortel Representatives.
Severity DEBUG
Description An internal error occurred in the Blue Call Router (BCR). This error indicates that the call is not in either pcrq or psrq when timer expires.
Impact Timeout unhandle.
Recovery Action If problem persist, contact Nortel Representatives.
Technical Support Action If problem persist, contact Nortel Representatives.
Severity MINOR
Description An internal error occurred in the Blue Call Router (BCR). Group cannot be configured after user has abandoned and reconfiguring is done.
Impact DS-0 will remain in CallInfoPending state and it will not received any call.
Recovery Action Check previous event log gererated by SCSA thread. Check the CTMS server.
Technical Support Action Check previous event log gererated by SCSA thread. Check the CTMS server.
Severity DEBUG
Description This error occurs when a group configuration operation fails. Timer will expires eventually and BCR will retry group configuration again
Impact BCR will retry group configuration after timer expires.
Recovery Action Not applicable
Technical Support Action Not applicable
Severity DEBUG
Description This error occurs when BCR fails to get all relevant information from a call after the group has been configured.
Impact The DS-0 will remain in CallInfoPending state and the group is set to unconfigured. Call will not be offered to application.
Recovery Action If problem persists, contact Nortel representatives.
Technical Support Action If problem persists, contact Nortel representatives.
Severity DEBUG
Description This error occurs when BCR fails to unconfigure the group for a CCr.
Impact The DS-0 will remain in current status of resource group. Call will not be offered to application.
Recovery Action Check previous event log. If problem persists, contact Nortel representatives.
Technical Support Action Check previous event log. If problem persists, contact Nortel representatives.
Severity DEBUG
Description Failed to redirect a call while a call is in PCRQ or PSRQ when call timer has expired or has exceed max number of redirect limit.
Impact The call will either remain in the queue or will become idle.
Recovery Action Disable and re-enable the DS-0 channel. If the problem persists, contact your customer support organization.
Technical Support Action Check any event codes either preceding or following this event. restart the BCR from Service Manager.
Severity DEBUG
Description This error occcurs when BCR encounters insufficient resources (DSP) to do any call processing after handoff completion. Either due to no resources or no applications.
Impact If CDN, call is returned to the queue; if ACD, the call is idled until resources is available.
Recovery Action Not applicable
Technical Support Action Not applicable
Severity MINOR
Description This event indicates that there was an error occurred when the NBbcr_AcquireService() API is invoked by an application and CLIENT thread has trouble posting this information back to EXEC thread.
Impact No resources will be available for outgoing calls.
Recovery Action Restart BCR. If the problem persists, contact your customer support organization.
Technical Support Action Restart BCR. If the problem persists, contact your customer support organization.
Severity MINOR
Description This event indicates that there was an error between the Blue Call Router (BCR) and CTM. This error occurs when the maintenance commands is invoked by Maintenance SP 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. Maintenance operations will be affected such as enable and disable boards.
Recovery Action If the problem persists, CrtsyDown system and restart BCR.
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 Blue Call Router (BCR) and CTM. This error occurs when the maintenance commands is invoked by Maintenance SP and the BCR attempted to read the function parameter. The return code CT_rc will give details on the specific error.
Impact A failure code will be returned to the calling application. This usually occurs when there is a programming error in the application. Maintenance operations will be affected such as enable and disable boards.
Recovery Action If the problem persists, CrtsyDown system and restart BCR.
Technical Support Action Perform the following steps:
1. Run chkdsk to verify files.
2. Restart CTM and CT apps.
3. Reinstall software if problem persists.
Severity MINOR
Description An error occurred in the Blue Call Router (BCR). This error indicates that the BCR receives an unexpected response from a client request. The infomration reported in this event may be valuable in debugging this fault.
Impact Some outgoing calls are affected.
Recovery Action If the problem persists, restart the BCR from Service Manager.
Technical Support Action Perform the following steps:
1. Restart CTM and CT apps.
2. If problem persists, reinstall software.