NN44400-713 01.03 FAULT Event Codes

Nortel Contact Center 7.0 Event Codes Version 01.
03
17 July 2009
Copyright © 2009 Nortel Networks. All Rights Reserved.
LEGAL NOTICE
While the information in this document is believed to be accurate and reliable, except as otherwise
expressly agreed to in writing NORTEL PROVIDES THIS DOCUMENT "AS IS" WITHOUT
WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED. The information and/or products
described in this document are subject to change without notice.
Trademarks
Nortel, the Nortel logo, the Globemark, Meridian 1, and Succession are trademarks of Nortel
Networks.
All other trademarks are the property of their respective owners.
Nortel, the Nortel logo, the Globemark, Meridian 1, and Succession are trademarks of Nortel
Networks.
All other trademarks are the property of their respective owners.
Standard
except as otherwise
" WITHOUT
on and/or products
marks of Nortel
Contact Center Manager Se
Event
Number Source Severity Label
40877 NGEN Security Critical NBDBU Error
Management
41002 NGEN Performance Critical OM Server Startup Failed. RC=

Management (OM) %np0
41065 NGEN Performance Critical Failed to start RPC Server. rc=

Management (OM) %np0
41526 NGEN System Critical Could not start the SM, rc=
Manager %np0.
41550 NGEN System Critical The SM could not start service
Manager %nvs, rc=%np0.
41552 NGEN System Critical The SM could not query

Manager service %nvs, rc=%np0.
41559 NGEN System Critical Too many services.

Manager
41560 NGEN System Critical Service %nvs has died too
Manager many times.
42510 TSM Major %nvs: Link state changed to

%ads. PID = %np1. Cause:
%np0.
42605 TSM Minor Server logon to switch attempt

failed - switch rejected the
logon attempt.

failed - switch did not respond
to logon request.

failed - a parameter is invalid.

failed - resource limitation.
failed - invalid LinkSet name
42612 TSM Minor Switch rejected the logon

attempt - IP Address is wrong.

failed - reason = %np0.
42614 TSM Critical Server is unable to log onto the

switch.
42615 TSM Information ELAN connection with switch

established.
42616 TSM Major ELAN connection with switch

has been broken.
42617 TSM Information Logon to the switch was

successful.
42618 TSM Major Switch is not responding.
42619 TSM Minor Unexpected CONNECTION

UP while ELAN connection
was active.
42620 TSM Critical Dongle check failed.
42621 TSM Minor Insufficient amount of disk

space (AML) for the value
configured.
42622 TSM Critical ACCESS LINK is DOWN
42652 TSM Major IVR initialization failure.
42654 TSM Major Server has refused connection

request from IVR system.
42670 TSM Information Communication has been
established with the IVR
system.
42671 TSM Information Communication with the IVR
system has been interrupted.
42672 TSM Major IVR port not monitored.

Port/DN %np0 is active.
42673 TSM Major Too much data received from

IVR system.
42674 TSM Major Calls queued in system have

exceeded maximum
engineering limit.
42675 TSM Information Calls queued in system have

fallen below engineering
maximum.
42676 TSM Critical Voice processing Meridian Mail

Mailbox password has expired.
42677 TSM Critical AML link failure owing to

Network/Switch problem.
42678 TSM Major Communication error between

switch and CCMS.
42679 TSM Information Switch link up.
42680 TSM Critical Switch link down.

42682 TSM Major Switch has initialized.
42683 TSM Major Switch has initialized after

sysload.
42684 TSM Minor Switch overload (flow control

level 1).
42685 TSM Minor Switch overload (flow control

level 2).
42686 TSM Major Switch overload (flow control

level 3).
42687 TSM Information Overflow condition has been

cleared.
space (TSM Server) for the
value configured.

space (TSM API) for the value
configured.

space (TSM Exec) for the
value configured.

space (ELH) for the value
configured.
44900 RSM Minor RSM failed to load
NIOAMISAPI.DLL. rc = %np0
44903 RSM Major System failed to launch RSM

service.
44906 RSM Minor RSM is not enabled in

keycode.
45018 OAM Information Service has stopped.
45019 OAM Information Service has started.

45022 OAM Information Service is starting.
45023 OAM Information Service is stopping.
45145 Network Information NCC is in Configuration mode.
45300 TOOLKIT Critical Failed to start service due to

unsuccessful registration. [RC
%np0]
45301 TOOLKIT Critical Failed to start service. The
service handler failed to
dispatch service. [RC %np0]
45304 TOOLKIT Critical "%ads"
45305 TOOLKIT Major %nvs, WaitForMultipleObject()

failed with error %np0.
45320 TOOLKIT Information A Toolkit service has started,

Service: "%ads"

Service: "%ads"

Service: "%ads"

Service: "%ads"

Service: "%ads"

Service: "%ads"

Service: "%ads"

Service: "%ads"
Service: "%ads"

Service: "%ads"

Service: "%ads"

Service: "%ads"

Service: "%ads"

Service: "%ads"

Service: "%ads"

Service: "%ads"

Service: "%ads"

Service: "%ads"

Service: "%ads"

Service: "%ads"

Service: "%ads"

Service: "%ads"

Service: "%ads"

Service: "%ads"

Service: "%ads"

Service: "%ads"
Service: "%ads"

Service: "%ads"

Service: "%ads"
45360 TOOLKIT Critical A Toolkit service has stopped,

Service: "%ads"

Service: "%ads"

Service: "%ads"

Service: "%ads"

Service: "%ads"

Service: "%ads"
Service: "%ads"

Service: "%ads"

Service: "%ads"

Service: "%ads"

Service: "%ads"

Service: "%ads"

Service: "%ads"

Service: "%ads"
Service: "%ads"

Service: "%ads"

Service: "%ads"

Service: "%ads"

Service: "%ads"

Service: "%ads"

Service: "%ads"

Service: "%ads"
Service: "%ads"

Service: "%ads"

Service: "%ads"

Service: "%ads"

Service: "%ads"

Service: "%ads"

Service: "%ads"
45390 TOOLKIT Minor Insufficient amount of disk

space for the value configured.
45903 OAM Critical
45905 OAM Critical Database error (code=%np0
description of error: %ads).
45908 OAM Critical Existing database connection

lost during a database access
by the OAM (rc=%np0).
46000 OAM Information %id1 added Activity Code

%nvs.
46001 OAM Information %id1 modified Activity Code
%nvs.
46002 OAM Information %id1 deleted Activity Code
%nvs.
46005 OAM Information %id1 added Application %nvs.
46006 OAM Information %id1 modified Application

%nvs.
46007 OAM Information %id1 deleted Application
%nvs.
46010 OAM Information %id1 added Skillset %nvs.
46011 OAM Information %id1 deleted Skillset %nvs.
46012 OAM Information %id1 modified Skillset %nvs.
46020 OAM Information %id1 added Phoneset Display

Field %nvs.
46021 OAM Information %id1 modified Phoneset
Display Field %nvs.
46022 OAM Information %id1 deleted Phoneset Display
Field %nvs.
46023 OAM Information %id1 modified Phoneset
Display Field list %np1.
46025 OAM Information %id1 added TN with Switch ID
%np1 and Port Address %nvs.
46026 OAM Information %id1 deleted TN with Switch

ID %np1 and Port Address
%nvs.
46027 OAM Information %id1 modified TN with Switch
ID %np1 and Port Address
%nvs.
46030 OAM Information %id1 added User %nvs.
46031 OAM Information %id1 modified User %nvs.
46032 OAM Information %id1 deleted User %nvs.
46033 OAM Information %id1 modified User Entry List

%nvs.
46034 OAM Information %id1 deleted User Entry List
%nvs.
46045 OAM Information %id1 added User Skillset
Assignment %nvs.
46046 OAM Information %id1 modified User Skillset
Assignment %nvs.
46047 OAM Information %id1 deleted User Skillset

Assignment %nvs.
46050 OAM Information %id1 added Call Presentation

Class %nvs.
46051 OAM Information %id1 modified Call

Presentation Class %nvs.
46052 OAM Information %id1 deleted Call Presentation

Class %nvs.
46055 OAM Information %id1 added Route %np1.
46056 OAM Information %id1 modified Route %np1.
46057 OAM Information %id1 deleted Route %np1.
46060 OAM Information %id1 added Call-by-Call

Application %nvs.
46061 OAM Information %id1 deleted Call-by-Call
Application %nvs.
46062 OAM Information %id1 modified Historical
Statistics configuration.
46063 OAM Information %id1 modified Historical
Statistics Duration
configuration.
46064 OAM Information %id1 modified Real-Time
Statistics configuration.
46065 OAM Information %id1 modified Statistical Data
Propagator configuration.
46066 OAM Information %id1 added CDN %nvs.

46067 OAM Information %id1 modified CDN %nvs.
46068 OAM Information %id1 deleted CDN %nvs.
46070 OAM Information %id1 added DNIS %nvs.

46071 OAM Information %id1 modified DNIS %nvs.
46072 OAM Information %id1 deleted DNIS %nvs.
46075 OAM Information %id1 added Script %nvs.
46076 OAM Information %id1 modified Script %nvs.
46077 OAM Information %id1 deleted Script %nvs.
46080 OAM Information %id1 added Script Item with

Script ID: %nvs Item ID: %np1
Item Type: %np2.
46081 OAM Information %id1 deleted Script Item with
Script ID: %nvs Item ID:
%np1 Item Type: %np2.
46085 OAM Information %id1 added Script reference

%ads to agent %nvs.
46086 OAM Information %id1 deleted Script reference

%ads to agent %nvs.
46091 OAM Information %id1 modified Voice Port with

Addr: %nvs Port Chnl: %ads
SW ID: %np1.
46095 OAM Information %id1 added IVR ACDDN

%nvs.
46096 OAM Information %id1 modified IVR ACDDN
%nvs.
46097 OAM Information %id1 deleted IVR ACDDN
%nvs.
46100 OAM Information %id1 added Agent to

Supervisor assignment %nvs.
46101 OAM Information %id1 modified Agent to

46102 OAM Information %id1 deleted Agent to

46105 OAM Information %id1added Threshold Class

%nvs with SrvLvl %np1, MSCD
%np2, TType %ads.
46106 OAM Information %id1 deleted Threshold Class

%np2,TType %ads.
46107 OAM Information %id1 modified Threshold Class

%np2, TType %ads.
46110 OAM Information %id1 added Script Variable

%nvs.
46111 OAM Information %id1 deleted Script Variable
%nvs.
46112 OAM Information %id1 modified Script Variable
%nvs.
46115 OAM Information %id1 modified Global
Parameter %nvs.
46120 OAM Information %id1 added Formula %nvs.
46121 OAM Information %id1 modified Formula %nvs.
46122 OAM Information %id1 deleted Formula %nvs.

Display %nvs.
Display Column List %nvs.
46125 OAM Information %id1 removed agent attribute

for user %nvs.
46126 OAM Information %id1 removed supervisor
attribute for user %nvs.
46206 OAM Major %nvs returned communication

error (assignID=%np0) when
running Sched User Assign
46211 OAM Major Cannot get num of agent

positions purchased (Ngen API
rc = %np1 & DB rc = %np2).
46212 OAM Major Security failure due to invalid

SessionID passed to the OAM
(%nvs, %np1).
46213 OAM Major %nvs returned Clnt/Srv

communication error (%np0)
when running Sched Reports.
46300 OAM Information %id1 added Contact Type:

%nvs (%np1) with skillset:
%ads (%np2).
46301 OAM Information %id1 deleted Contact Type:

%nvs (%np1).
46302 OAM Information %id1 modified Contact Type:
%nvs (%np1) with skillset:
%ads (%np2).
46311 OAM Information %id1 added Media Server:

%nvs.
46312 OAM Information %id1 modified Media Server:
%nvs.
46313 OAM Information %id1 deleted Media Server:
%nvs.
46314 OAM Information %id1 added Media Service:
%nvs.
46315 OAM Information %id1 modified Media Service:
%nvs.
46316 OAM Information %id1 deleted Media Service:
%nvs.
46317 OAM Information %id1 added
MediaServiceRoute, Server =
%nvs, Service = %ads,
OrdPref = %np1.
46318 OAM Information %id1 deleted

MediaServiceRoute, Server =
%nvs, Service = %ads,
OrdPref = %np1.
46753 HDC Critical Unable to write statistical data

to file: (%ads)
46872 HDC Minor Insufficient disk space for the

value configured.
46873 HDC Information Parameters exceeded

Database limit: %ads.
46907 RDC Critical RDC failed to initialize with
SDMCA (rc = %np0).
46908 RDC Critical RDC failed to initialize with

SDMCA (rc = %np0).
46909 RDC Critical Unable to register with Event

Broker for Call Processing
messages (rc = %np0).
46910 RDC Critical Unable to connect with Data

Propagator.
46912 RDC Critical Unable to send data to Data

Propagator (rc = %np0).
46963 RDC Minor Insufficient amount of disk
46964 RDC Information Interval-To-Date Definition is

set wrongly to zero.
47112 EB Information Time change detected. %ads
47116 EB Information Dump memory requested by

PScan. %ads
47117 EB Information Call cleared by PScan. %ads
47118 EB Information Call cleared by Audit. %ads
47120 EB Minor Insufficient amount of disk

47500 DP Critical DP cannot allocate memory for

the SDP listener/master; DP
failed to start.
47501 DP Critical DP cannot allocate memory for

the new scheduler; DP failed to
start.
47502 DP Critical DP unable to create new

propagator; DP failed to start.
47505 DP Critical DP failed to start. Unable to

register request query. [Client=
%nvs]
47506 DP Critical DP failed to start. Unable to

locate RDC service (Channel=
%nvs, RC=%np0).
47525 DP Critical Failed to set the service state

of DP. [RC=%np0]
47533 DP Minor Insufficient amount of disk
47700 HDM Critical HDM cannot connect to the

database server.
47701 HDM Critical HDM lost connection to the

database.
47702 HDM Critical DBPROCESS handle is

invalid.
47703 HDM Critical Critical Database error. (error

code=%np0)
47704 HDM Critical Major Database error. (error
code=%np0)
47705 HDM Critical Minor Database error. (error

code=%np0)
47707 HDM Major HDM was unable to create

Call-by-Call table.
47712 HDM Major Cannot find the bulk copy

format file (%ads).
47755 HDM Major HDM was unable to create Net

Call-by-Call table.
47756 HDM Major Net Call-by-Call file has been
deleted.
47757 HDM Major Remote BCP for Net Call-by-

Call file exceeded 15 minutes.
47785 HDM Information HDM service started.

47787 HDM Information Online upgrade process
started.
47788 HDM Information Online upgrade process

canceled.
47789 HDM Information Error during online upgrade

process.
47907 SDMCA Critical Unable to connect to OAM
(%nvs %np0 %id1 %ads).
47908 SDMCA Critical SDMA cannot connect to one

of: EB, RDC, HDC (%nvs
%np0 %id1 %ads).
47909 SDMCA Critical Event Broker connection failed

(%nvs %np0 %id1).
47929 SDMCA Critical SDM Configuration Admin

startup failed (%nvs %np0
%id1).
48100 ASM Critical Out of Memory. (%nvs, %ads)
48103 ASM Critical Shared Memory Failed. (%np0,

%nvs)
48106 ASM Minor TN Acquire Failure. (TN: %ads,

Cause: %np0, Reason: %np1,
File/Function: %nvs)
48107 ASM Minor TN Release Failure. TN: %ads,

Cause: %np0, Reason: %np1,
File/Function: %nvs.
48111 ASM Major Agent Login Err. LoginID:

%ads, TN: %ads, Cause:
%np0, Resp: %np1, File/Func:
%nvs.
48113 ASM Information Login Warning. (%ads, %np0,

%nvs)
48114 ASM Information Invalid Login Attempt.

(LoginID: %ads, TN: %ads,
Cause: %np0, File/Func:
%nvs)
48115 ASM Information Call Forward Enable Error.

(%np0, %ads, %ads, %nvs)
48116 ASM Information Call Forward Disable Error.

(%np0, %ads, %ads, %nvs)
48117 ASM Critical Communication failed with

another CCMS component.
(%np0, %np1, %np2, %nvs)
48134 ASM Critical ASM startup error: (%np0,

%nvs)
48139 ASM Minor Insufficient amount of disk
48143 ASM Minor DN acquire failed. (%np0,

%np1, %ads, %nvs)
48158 ASM Major TSM Registration Error -

ME_NO_ACCESS
48189 ASM Information ASM operational. %nvs.

48190 ASM Information ASM shutting down. %nvs.
48197 ASM Major Set Display Messages Error.

(%ads, %np0, %nvs)
48198 ASM Information Link status change. (%ads,

%np1, %np2, %nvs)
48199 ASM Minor Unable to read the Skillset

config type for SS: %np1. Call
ID: %np0.
48200 ASM Minor Unable to get Avg Answer

Delay value for SS: %np0.
Setting default value.
48201 ASM Minor Default Queue Management

failure. (%ads, %np0, %nvs)
48202 ASM Minor Acquisition Event on Landing

Pad: %nvs Failed.
48203 ASM Information TSM Registration Successful.

48204 ASM Critical TSM connection lost -
AS_REGISTER_RELEASED
48401 TFE Critical TFE service halted. (Evt:

%np1.Call id:%np2.Comp:
%ads. File/Function: %nvs)
48402 TFE Information Unused event code.
48403 TFE Critical Server out of memory. (Cause:

%np0. File/Func: %nvs)
48404 TFE Major TSM request has timed out.

(Call id: %np2. Cause: %ads.
File/Func: %nvs)
48405 TFE Major ASM request has timed out.

File/Func: %nvs)
48406 TFE Major VSM request has timed out.

File/Func: %nvs)
48407 TFE Major HDX request has timed out.

File/Func: %nvs)
48408 TFE Major Internal data structures

overflow. (Cause: %np0.
File/Func: %nvs)
48409 TFE Critical Incorrect installation
configuration data. (File/Func:
%nvs)
48410 TFE Major TSM request failed. (Cause:
%np0.Req: %np1.Call/Dev id:
%np2.File/Function: %nvs)
48411 TFE Major VSM request failed. (Result:

%np0.Req: %np1.Call ID:
%np2.File/Func: %nvs)
48412 TFE Major TSM request to switch failed.

(Cause: %np0. Cmd: %np1.
Call id: %np2. TF: %ads. File:
%nvs)
48413 TFE Critical TFE service terminated due to

an internal error. (%ads.
File/Func: %nvs)
48414 TFE Major CDN acquire failed.

(Cause/RC: %np0. CDN:
%ads. File/Func: %nvs)
48415 TFE Major CDN deacquire failed. Cause:
%np0. CDN: %ads. File/Func:
%nvs
48416 TFE Minor Cannot create error log file.
(File/Function: %nvs)
48417 TFE Critical Cannot open configuration file.

(%ads. File/Func: %nvs)
48418 TFE Major Invalid message received.

(Cause: %np0. Evt: %np1.
Info: %ads. File/Func: %nvs)
48421 TFE Critical CMF link down.
48423 TFE Major Script execution error. (Cause:

%np0. PC: %np1. TF: %ads.
File/Func: %nvs)
48424 TFE Major Call not processed. (Cause:

%np0. Call ID: %np1. CDN:
48427 TFE Major Invalid CDN. (Cause: %np0.

Device: %np1. CDN: %ads.
File/Func: %nvs)
48428 TFE Major CDN is deacquired by the

switch. (Cause: %np0. CDN:
%np1.File/Func: %nvs)
48429 TFE Major CDN acquire request failed.

(Cause: %np0. CDN: %ads.
48431 TFE Major CDN state change request

failed. (CDN: %ads. Cause:
%np0. Evt: %np2. File/Func:
%nvs)
48432 TFE Information Request and response

mismatch. (Comp: %np0.
Resp: %np1. Call id: %np2.
File/Func: %nvs)
48433 TFE Information Invalid reason received by
TFE. (Event: %np0. Reason:
48434 TFE Major CDN %ads is in a wrong state.

(State: %np1. File/Func: %nvs)
48436 TFE Minor Call treatment failed. (Cause:

%np0. Cmd: %np1. Call ID:
%np2. TF: %ads. File/Func:
%nvs)
48437 TFE Information Data out of legal range.

(Queue count: %np1.
File/Func: %nvs)
48438 TFE Major Call defaulted. (Call ID: %np1.
Req Func: %nvs)
48439 TFE Major Default skillset not configured.

(File/Func: %ads)
48440 TFE Minor Default RAN not configured.

(File/Func: %nvs)
48442 TFE Major Memory allocation error.

(Cause %np0. File/Func:
%nvs)
48443 TFE Major Requested call treatment not
completed. (Req: %np1. Call
id: %np2. File/Func: %nvs)
48445 TFE Major CDN request timed out. (Req:

%nvs)
48447 TFE Minor Call ID mismatch. (Call ID:
%nvs)
48448 TFE Information CMF link up.
48452 TFE Information IVR request canceled. (Call ID:

48453 TFE Minor Invalid message type received.

(Msg type: %np1. Call id:
48454 TFE Minor Invalid ACD priority request.

(Priority: %np1. Call id: %np2.
File/Func: %nvs)
48455 TFE Information ACD %np1 cannot be inserted

into the ACD list. (Call id:
48456 TFE Information ACD %np1 cannot be removed
from the ACD list. (Call id:
48457 TFE Minor Delay time value out of range.

(Delay time: %np1. Call id:
48458 TFE Minor Unexpected event received.

(%np0. State: %np1. Call id:
%np2. Info: %ads. File: %nvs)
48459 TFE Minor Invalid call state. (Call state:

%np1. Call id: %np2.
48460 TFE Minor Invalid Call ID. (Event: %np1.

Call id: %np2. File/Function:
%nvs)
48461 TFE Major Invalid ASM data sent. (#
items: %np0. Event: %np1.
Call id: %np2. File/Func:%nvs)
48463 TFE Minor Missing data. (Var id: %np1.

Info: %ads. File/Func: %nvs)
48464 TFE Major TFE encountered internal

exception. (File/Function:
%nvs)
48466 TFE Major Unknown: %ads, variable data
type. (File/Function: %nvs)
48467 TFE Information Script log message: %ads.

(Call id: %np2)
48469 TFE Major Execute command failed.
(Script id: %np1. Call id: %np2.
File/Func: %nvs)
48470 TFE Major Request to OAM failed: %ads.

(Return Code: %np0.
48474 TFE Minor Unknown ASM command:

(%np0. Call id: %np2.
File/Func: %nvs)
48475 TFE Minor Unknown third-party

command: (%np0. Call id:
48477 TFE Major Unknown response event:

(np0. Call id: %np2. File/Func:
%nvs)
48478 TFE Minor Cannot change CDN type.
(Cause: %np0. CDN: %np1.
File/Func: %nvs)
48479 TFE Major Invalid resource name: (%ads.
File/Func: %nvs)
48480 TFE Major Script validation error.

(File/Func: %nvs)
48483 TFE Major Invalid %ads type. (Type value:
%np0. Call id: %np2.
48484 TFE Minor Invalid %ads state. (State:

48487 TFE Major Invalid event received (Event:

%np0).
48488 TFE Major Failed to get master script from
the database. (Return Code:
48489 TFE Major Failed to get master script.

(Return Code: %np0.
File/Func: %nvs)
48490 TFE Major Failed to set master script
status. (Return Code: %np0.
File/Func: %nvs)
48491 TFE Major Failed to activate master script.

(Return Code: %np0. File
Func: %nvs)
48492 TFE Major Failed to get network script
from the database. (Return
Code: %np0. File/Func: %nvs)
48493 TFE Major Failed to get network script.

(Return Code: %np0.
File/Func: %nvs)
48494 TFE Major Failed to set network script
status. (Return code: %np0.
File/Func: %nvs)
48495 TFE Major Failed to activate network

script. (Return Code: %np0.
File Func: %nvs)
48497 TFE Minor Total number of skillsets

exceeds the limit. (%ads. Call
48498 TFE Minor Invalid %ads item. (Call id:

%np2. File/Function: %nvs)
48499 TFE Major Error in loading script. (Script

name: %ads. Cause: np0.
File/Func: %nvs)
48500 TFE Minor Voice segment not played.
Voice segment is corrupted
(File/Func: %nvs)
48501 TFE Major VSM request failed. (Result:

%np0. Event: %np1. Call ID:
%np2. File/Funct: %nvs)
48503 TFE Major Error in reading script file.

(Script name: %ads.
48504 TFE Major Invalid script file. (Script name:

%ads)
48505 TFE Major Error in validating script file.
(Script:%ads.Num errs:
%np0.File/Func:%nvs)
48508 TFE Information CDN is not in acquired state.

(CDN number: %np0. CDN
Type: %np1. File/Function:
%nvs)
48509 TFE Information CDN type remained the same.

(CDN number: %np0, CDN
type: %np1. File/Func: %nvs)
48510 TFE Major Call already exists. (Try list:

%np0. Call id: %np2. Req func:
%ads. File/Func:%nvs)
48511 TFE Minor Call not in system. (%np0. Call

id: %np2. In list: %np1.
File/Func: %nvs)
48512 TFE Minor Skillset/agent script command

failed. (%np0. SS/Agt: %np1.
Call id: %np2. File: %nvs)
48513 TFE Major Invalid Call ID. (%np0. Dev id:

%np1. Evt: %np2. Msg: %ads.
File/Func: %nvs)
48514 TFE Major ASM request failed. (Cause:

%np0. SS/Agt: %np1. Call ID:
%np2. Resp: %ads. File/Func:
%nvs)
48515 TFE Major Call not presented to agent.

(State: %np1. Call id: %np2.
File/Func: %nvs)
48516 TFE Major TFE encountered some

internal error. (%ads fails.
Cause/RC: %np0. File/Func:
%nvs)
48517 TFE Major Failed to reserve agent. (Call
48518 TFE Critical TFE failed in retrieving switch

info. (Cause: %np0. API:
48519 TFE Information No active agents. (Cause:

%np0. Skillset: %np1. Call ID:
%np2. Intrin: %ads. File: %nvs)
48520 TFE Information Zero substituted for script

expression. (PC: %np1. CallId:
%np2. Info: %ads. File: %nvs)
48521 TFE Major Memory Allocation Failure.

(Object : %ads. File/Func:
%nvs.)
48522 TFE Major Resource request timed out
(File/Function: %nvs).
48523 TFE Minor HDX variable length too long.

(Var Type:%np1.Call id:
%np2.File/Func:%nvs)
48524 TFE Minor HDX response timed out.

(Cause: %np0. Call ID: %np2.
File/Func: %nvs)
48525 TFE Major Send Request statement to

HDX failed. (Cmd: %np1. Call
ID: %np2. File/Func: %nvs)
48526 TFE Major Send Info statement to HDX

failed. (Cause: %np0. Call ID:
48527 TFE Major HDX does not exist. (Cause:

%np0. Call ID: %np2.
File/Func: %nvs)
48528 TFE Major HDX application ID mismatch:
(PC: %np1. Call ID: %np2. TF:
48529 TFE Minor Number of call variables

exceeded the limit. (Cause:
%np0. # of Vars: %np1. File:
%nvs)
48530 TFE Major Script command not executed.

(Cause: %np0. Cmd: %np1.
Call id: %np2. TF: %ads. File:
%nvs)
48531 TFE Minor Call may not be disconnected.
(Event: %np1. Call id: %np2.
File/Func: %nvs)
48532 TFE Minor Invalid voice segment file

name. (%ads. Cause: %np0.
Call ID: %np2. File/Func:
%nvs)
48533 TFE Minor Event Handler command

failed. (Cause: %ads. Evt:
%np1. Call ID: %np2.
File/Func: %nvs)
48534 TFE Major HDX Register ID mismatch.

(%ads. Cause: %np0. Call ID:
48535 TFE Information Skillset List Error: (%ads.

Skillset: %np0. Call ID: %np1.
File/Func: %nvs)
48536 TFE Minor Caller-entered data %np0 has

wrong size. (File/Func: %nvs.
Call ID: %np1 f)
48537 TFE Minor Caller-entered data contains

more than 10 fields. (File/Func:
%nvs. Call ID: %np1)
48538 TFE Minor Field %np0 contains non-digit.

(File/Func: %nvs. Call ID:
%np1 )
48539 TFE Critical TSM connection lost -
(File/Func: %nvs)
48540 TFE Minor Disallowed script commands.
(Cause: %ads. Call ID: %np1.
Script: %nvs )
48541 TFE Information Thread %ads. (Thread no:

%np1. Timeout: %np0.
File/Func: %nvs. )
48542 TFE Information Switch event: %ads. (Reason:

%np0. Line: %np1. File/Func:
%nvs)
48543 TFE Information Message: %ads. (Thread id:

%np1. Time Lapse: %np0.
File/Func: %nvs)
48544 TFE Major TSM Registration Error -

ME_NO_ACCESS
48545 TFE Information TSM Registration Successful.
48546 TFE Minor Unable to create Windows

event to monitor registry key
changes.
48547 TFE Information Failed to start Generic Logger.

(File/Func: %nvs)
48580 TFE Information TSM link congestion detection
48581 TFE Information Link Health Monitoring: TFE

taking too long to process
calls.
48800 VSM Major Memory allocation failure.
(%nvs, %ads)
48815 VSM Major Resource

monitoring/acquisition failure.
Error code : %xp0, %nvs,
(%ads)
48836 VSM Major VSM failed to initialize. (%nvs,

%ads)
48837 VSM Major TSM Registration Error -

ME_NO_ACCESS
48842 VSM Major Resource status updated

incorrectly - OAM request
failure (%nvs, %ads)
48848 VSM Major Service Request Failure. Error

code: %xp0. %nvs.
File/Line/Func: %ads.
48850 VSM Major Failed to retrieve switch
information. (%xp0, %nvs,
%ads)
48852 VSM Major VSM Communication failure.

(Thread name: %nvs, Thread
Id: %xp0, %ads)
48854 VSM Minor Non-CCMS call placed to IVR

ACD-DN / Voice Port (Device
Id: %np0.,%nvs.,%ads.)
48856 VSM Information Number of voice segments to

play is more than 50: (Call Id:
%xp0. %nvs. %ads.)
48857 VSM Information Play Prompt failed due to

invalid file segment: (Call Id:
%xp0. %nvs., %ads.)
48858 VSM Information Play Prompt file open failure.

(%xp0. %nvs., %ads.)
48860 VSM Major Exceeded MAX number retry

for MailBoxLogon. (%xp0.
%nvs., %ads.)
48861 VSM Information Voice Play Complete (Session
End Without Answer) for
device (Id: %xp0. %nvs.,
%ads.)
48862 VSM Information TSM Registration Successful.

48863 VSM Critical TSM connection lost -
48864 VSM Minor Unable to create Registry

Change Notification Event.
48865 VSM Minor Insufficient amount of disk

49013 Network Major The Dialable DN has not been

configured for site %nvs.
49014 Network Information %nvs is being filtered for the

configured filter timer.
49015 Network Major Reached the maximum

configured retry count for
%nvs. Site has been filtered.
49016 Network Major NACD package on the switch

has not been enabled at site
%nvs.
49017 Network Major Dialable DN for %nvs has been

configured incorrectly.
49018 Network Major The dialable DN for site %nvs

is invalid.
49019 Network Major Failure sending agent

reservation message to target
%nvs.
49020 Network Minor Network_Script at %nvs has
not been activated.
49021 Network Major D-channel to %nvs is down.
49022 Network Major NACD resend timer has

expired for %nvs.
49023 Network Minor All trunks busy on local switch.
49024 Network Minor All trunks busy at %nvs.
49025 Network Minor Network skillset %np2 at %nvs

is out of service.
49026 Network Minor Exceeded call request queue

size for network skillset %np2
at %nvs.
49028 Network Information %nvs is being filtered for %np2

seconds.
49029 Network Major %nvs is being filtered until

manual intervention.
49030 Network Major Unable to read the Skillset

config type for SS: %np0. Call
ID: %np2.
49031 Network Information Cannot queue to Multiple

Skillsets with different Config
Types. Call ID: %np2
49033 Network Information All Landing Pads busy at

%nvs.
49034 Network Minor DNIS Network CDN at %nvs is

not valid.
49035 Network Minor Communication error
attempting to contact
UNE/CMF at %nvs.
49231 TFA Information Invalid application id used in

%ads in: %nvs.
49400 MLINK Major TSM Registration Error -

ME_NO_ACCESS
49415 MLINK Major Socket Send Failure.

Association: %np2, Error code
(socket layer): %np0
49416 MLINK Major Message Receive Error.

Association ID: %np2, Error
code (socket layer): %np0
49430 MLINK Information Connection to 3rd party

application RESET,
Association ID: %np2, Socket
Error: %np0
49438 MLINK Information Number of 3rd party

applications connected =
%np0.
49442 MLINK Information TSM Registration Successful.
49443 MLINK Critical TSM connection lost -

49444 MLINK Information CCMS MLSM DN License

Denied.
49445 MLINK Information CCMS MLSM ROD License
Denied.
50502 Network Information The Applications list was
modified by %id1.
50503 Network Information Network Skillset (%nvs) was
added by %id1.
deleted by %id1.
50505 Network Information The Network Skillset (%nvs)

was modified by %id1.
50506 Network Information Site (%nvs) was added by

%id1.
50507 Network Information Site (%nvs) was deleted by
%id1.
50508 Network Information Information for site (%nvs) was
modified by %id1.
50509 Network Information A routing table was modified by

%id1.
50510 Network Information Routing table assignment
(%nvs) was added by %id1.
50511 Network Information Routing table assignment

(%nvs) was deleted by %id1.
50512 Network Information Information for routing table

assignment (%nvs) was
modified by %id1.
50513 Network Information Information for routing table

assignment (%nvs) was
modified by %id1.
50606 Network Minor Insufficient disk space (NCC)

for the value configured.
50722 Network Minor Insufficient amount of disk

space (NOAM) for the value
configured.
50740 Network Information Site: (%nvs) Site Id: (%nv1)

has Flow Control: OFF.
50902 Network Information The Applications list was

modified by %id1.
added by %id1.
deleted by %id1.
50905 Network Information Information for Network Skillset

(%nvs) was modified by %id1.
50906 Network Information Site (%nvs) was added by

%id1.
50907 Network Information Site (%nv3) was deleted by
%id1
50908 Network Information Information for site (%nvs) was
modified by %id1.
50909 Network Information A routing table was modified by

%id1.
50910 Network Information Network communication
parameters were modified by
%id1.
50911 Network Information The NCC site name was
changed to (%nvs) by %id1.
50912 Network Information Network skillset (%nvs) status

has been modified to (%ads)
by %id1.
50913 Network Information The communication status to

site (%nvs) has changed to
(%ads).
50914 Network Major Failed to send sanity

messages from CCMS to NCC.
50940 Network Information Synchronization between the

NCC and CCMS has started.
50941 Network Information Completed synchronization

between this site and NCC.
51174 DB Major Unable to back up database to

a network drive. Access to the
directory is denied.
51306 ES Minor niebprxy.dll not found
51308 ES Minor Client registration problem with

the Event Server, rc=%np0.
51345 ES Minor Communication problem, rc=

%np0.
51503 HAI Major HAI failed to initialize CORBA
infrastructure: %np0
51504 HAI Major HAI failed to initialize ODBC

51505 HAI Major HAI failed to initialize TAPI

51506 HAI Major HAI failed to allocate memory

for %ads.
51507 HAI Minor HAI shut down abnormally:
%np0
51701 TFEBRDG Minor Could not initialize event
server. rc = %np0
51704 TFEBRDG Major Call dequeue.
51707 TFEBRDG Minor Call interflowed.
51708 TFEBRDG Minor Call removed from NACD.
51709 TFEBRDG Minor Give NACD.
51710 TFEBRDG Minor Bridge handler.
51711 TFEBRDG Minor NACD ping.
51712 TFEBRDG Minor Post route.
61400 CCMSCS Information Service has started.

61401 CCMSCS Information Service has stopped.
61402 CCMSCS Information Service is starting.
61403 CCMSCS Information Service is stopping.
61404 CCMSCS Information Starting CCMS services.

61405 CCMSCS Information Requesting license %ads.
61406 CCMSCS Information License for %ads is %ads.
61407 CCMSCS Information Communication between

License Manager and CCMS
has been re-established.
61408 CCMSCS Information License for %ads is %ads. Will

wait for license to be released
up to 7 minutes.
61409 CCMSCS Critical CCMS package is not in the

database.
61410 CCMSCS Critical Unable to read CCMS

configuration data from the
database. Error code: %np0.
61411 CCMSCS Critical Unable to get switch type from

registry.
61412 CCMSCS Critical Unable to get the

SetupComplete registry value.
61413 CCMSCS Critical CCMS server was not

configured.
61414 CCMSCS Critical Unable to determine the status

of the server.
61416 CCMSCS Critical Cannot start CCMS Control

Service because CCMS
services being shutdown.
61417 CCMSCS Critical Could not start LM refresh

thread. Error Code: %np0.
LMIF Client ID: %np1.
61418 CCMSCS Critical Could not start LM refresh

thread. Error Code: %np0.
LMIF Client ID: %np1.
61419 CCMSCS Critical Failed to confirm license for

package %ads. LM Error
Code: %np1.
Code: %np1.
Code: %np1.
Code: %np1.
61423 CCMSCS Information Received
SERVICE_CONTROL_STOP.
61424 CCMSCS Information Received

SERVICE_CONTROL_SHUTD
OWN.
61425 CCMSCS Major Communication error occurred
between License Manager and
CCM Server.
61426 CCMSCS Major Warm Standby license was not

granted for CCMS server.
61500 OAMB Critical OAMBridge Start Up failure,

transferring data from OAM to
CMF failed.
61501 OAMB Critical General exception caught.

OAMBridge shutting down
immediately.
61502 OAMB Critical Exception caught. OAMBridge

failed to complete restart.
61503 OAMB Minor Failed to add CCMS Status

Thread during OAMBridge
Start Up.
61504 OAMB Critical Could not open connection to

registry: %ads.
61505 OAMB Major Could not close connection to

registry: %ads.
61506 OAMB Critical Exception occurred while

getting server type.
61507 OAMB Critical Could not set the properties for
OAMBridge.
61508 OAMB Major Error getting Host Address.
61509 OAMB Critical OamListener message

registration failed. %ads
61510 OAMB Critical Could not instantiate the

ServiceProviderStatusListener.

TerminalStateChangeListener
on %ads.
61512 OAMB Major OAMListener heartbeat not

found. OAMListener restarting.
61513 OAMB Critical Could not start the OAM

Listener Monitor Thread.
61514 OAMB Critical Could not complete

ServiceProviderStatusListener
process. %ads
61515 OAMB Critical Could not complete

TerminalStateChangeListener
process.
61516 OAMB Critical Could not start the Pooling

Thread.

OAMListener.
61518 OAMB Critical Exception caught while created
providers during %ads.
61519 OAMB Critical Unable to set Contact Manager

master status. %ads
61520 OAMB Critical Passive provider not created

on %ads. OAMBridge exiting.
61521 OAMB Critical CCMM provider not created on

%ads. OAMBridge exiting.
61522 OAMB Critical Network provider not created

on %ads. OAMBridge exiting.
61523 OAMB Critical Failed to get Contact Manager.
61524 OAMB Critical Failed to clean up CCMM

Provider.
61525 OAMB Critical Failed to clean up Passive

Provider.
61526 OAMB Critical Failed to clean up Network

Provider.
61527 OAMB Critical Failed to add contact type to

CCMM Provider.

Passive Provider.

Network Provider.
61530 OAMB Major Unable to read Agent data

from OAM database on %ads.
61531 OAMB Major Unable to add Agent data to

CMF from database on %ads.
61532 OAMB Major Unable to read CDN data from
database on %ads.
61533 OAMB Major Unable to add CDN data to

CMF from database on %ads.
61534 OAMB Major Unable to read Route data

from database on %ads.
61535 OAMB Major Unable to add Route data to

CMF from database %ads.
61536 OAMB Major Unable to read DNIS data from

database on %ads.
61537 OAMB Major Unable to add DNIS data to

CMF from database %ads.
61538 OAMB Major Unable to read Media Server

data from the database on
%ads.
61539 OAMB Major Unable to add Media Server

data to CMF from database
%ads.
61540 OAMB Major Unable to read Media Service

data from the database %ads.
61541 OAMB Major Unable to add Media Service

data to CMF from database
%ads.
61542 OAMB Major Unable to read Media Service

Route data from the database
%ads.
61543 OAMB Major Unable to add Media Service
Route data to CMF from
database % ads.
61544 OAMB Critical Failed to clean entire CMF

space on start up.
61545 OAMB Major OAM Request Fault: Adding

Agent %ads to CMF failure.

Supervisor %ads to CMF
failure.

Agent Supervisor %ads to
CMF failure.

Agent %ads during update
failure.
61549 OAMB Major OAM Request Fault: Deleting

Agent %ads during agent
upgrade/downgrade failure.
Agent %ads during agent
upgrade/downgrade failure.

contact types to Agent
supervisor %ads failed.

agent template for Supervisor
%ads failure.

agent template for Agent
Supervisor %ads error.

agent template for Agent %ads
failure.
61555 OAMB Major OAM Request Fault: Modifying

Agent %ads data failure.

Agent %ads data failure.

Agent Template %ads data
failure.
failure.

failure.

Treatment Terminal %ads
failure.

Treatment Address %ads
failure.
61562 OAMB Major OAM Request Fault: Treatment

Terminal %ads not found.
61563 OAMB Major OAM Request Fault: Treatment

Address %ads not found.

CDN %ads data failure.


Route %ads data failure.



DNIS %ads data failure.



Agent Contact Type failure
%ads.
Agent Contact Type failure
%ads.

Media Service %ads data
failure.

failure.

failure.

Media Server %ads data
failure.

failure.

failure.

Media Service Route data
failure %ads.
Media Service Route data
failure %ads.
61583 OAMB Critical Error setting Passive Provider

in service on %ads.
61584 OAMB Critical Error setting CCMM provider in

service on %ads.
61585 OAMB Critical Error setting Network provider

in service on %ads.
61586 OAMB Critical Exception caught forcing

passive provider in service.
61587 OAMB Minor Failed to stop CCMS Status

Thread after OAMBridge Start
Up.
61588 OAMB Major CMF Data Fault for OAM

Request: User %ads info notify
failure.
61589 OAMB Information OAMBridge started.
61590 OAMB Information OAMBridge stopped.

61591 OAMB Major CTI Replication Link Fault:
%ads
61592 OAMB Information CTI Replication Link

established.
62601 Niprotam Minor %ads

62603 Niprotam Information %ads
63800 ALA Major %ads
63801 ALA Critical %ads

63805 ALA Minor %ads
63806 ALA Information %ads
63900 SCMU Information %ads

63901 SCMU Information %ads
63902 SCMU Minor %ads

63904 SCMU Major %ads

64000 SERVMON Information %nvs: A new instance is
started.
64001 SERVMON Information %nvs: The CCMS Service
Monitor is turned Off.
64002 SERVMON Information %nvs: Started monitoring

services.
64003 SERVMON Information %nvs: Stopped by CCMS
Control Service request.
64004 SERVMON Information %nvs: Resetting to continue

monitoring until switchover is
started by Cache.
64005 SERVMON Information %nvs: Running iccmSU to
restart stopped services.
64006 SERVMON Information %nvs: Waiting for ICCMSU to

finish starting up the CCMS
services.
64007 SERVMON Information %nvs: Retrieved the updated

configuration data from DB.
64016 SERVMON Major %nvs: Updated the alternative

Switch IP = %ads in the
registry.
64017 SERVMON Major %nvs: Updated the alternative

Switch Customer Number =
%np0 in the registry.
64018 SERVMON Major %nvs: Initiated switchover to

standby CCMS Server.
64019 SERVMON Critical %nvs: %ads.
64020 SERVMON Major %nvs: %ads.
64021 SERVMON Minor %nvs: %ads.
64022 SERVMON Minor %nvs: is stopped by CCMS

Service Monitor.
64023 SERVMON Minor %nvs: %ads.

64024 SERVMON Minor %nvs: is being restarted by the
CCMS Service Monitor.
64025 SERVMON Minor %nvs: cannot be restarted.

%ads.
64026 SERVMON Minor %nvs: is terminated by the

CCMS Service Monitor.
Process ID %np0.
64027 SERVMON Major %nvs: Service with processID=

%np) could not be terminated.
64031 SERVMON Critical %nvs: Exception found in

%ads. Return code: %np0.
64032 SERVMON Critical %nvs: Could not read the

configuration data from the DB.
64033 SERVMON Critical %nvs: Worker thread error:

%ads.
64034 SERVMON Critical %nvs: Failed to connect to the

database. %ads.
64035 SERVMON Critical %nvs: Failed to update the

database. %ads.
64036 SERVMON Critical %nvs: Registry error: %ads.
64037 SERVMON Critical %nvs: Error initiating

switchover to standby CCMS
Server.
64038 SERVMON Critical %nvs: %ads.
64039 SERVMON Critical %nvs: Error stopping the

service. %ads. Return code:
%np0,.
64041 SERVMON Critical %nvs: Error starting the
service.
49446 MLINK Information Cannot create or open MLSM
Log file.
Contact Center Manager Server event codes
Detailed Description Impact

An error occurred due to a faulty Bedbug API call. A
desktop user could not be added, could not be
deleted, could not be modified, or could not be
granted appropriate rights. The error occurred in the
system part of the database.
The OM Service could not be started.
Unable to set the RPC server.
The software could not start the SM to get it running.
The SM could not start the specified service.
The SM could not query the specified service to

determine its status.
The number of services has exceeded the capacity of

the SM.
The specified service has died too many times and
will not be restarted.
CCMS is not responding to the switch. The link is down between CCMS and the switch. Calls
during this time are defaulted and the statistics will reflect
this. The link will attempt to automatically reset.
At startup, one attempt to log on to the switch was The logon attempt will be retried. If five attempts fail, a
rejected. This could be due to a message being critical event is created.
corrupted while communication with the switch was
being established.
At startup, this attempt to log on to the switch did not The logon attempt will be retried. If five attempts fail, a
receive a reply. critical event is created.
This attempt to log on to the switch failed because the The logon attempt will be retried. If five attempts fail, a
logon request sent to the switch was not complete. critical event is created.
switch does not have the resources to permit the critical event is created.
logon.
LinkSet name contained in the logon request is invalid critical event is created.
switch will not permit logon from the ELAN of the critical event is created.
server.
This attempt to log on to the switch failed but the The logon attempt will be retried. If five attempts fail, a
switch has returned an unknown error. critical event is created.
The ELAN connection with the switch has been The server will attempt the logon again, but will probably
established, but a number of attempts to log on to the continue to fail. Contact Center Manager Server is unable
switch have failed. The causes of these failures have to control or receive information from the switch until it can
been previously reported as "Minor" level events. log on successfully. Call center activity will be conducted
These events should be viewed to obtain the cause of by ACD software on the switch.
the failure.
The link to the switch has been established. The No impact. This is a normal operating condition.
server will attempt to log onto the switch.
The link to the switch has been broken. Now the Until the connection can be reestablished, the switch will
server will attempt to re-establish the connection. perform the call center functions.
The switch is now ready to accept requests from the The server is ready to begin operation.
server and to send call activity to the server.
The switch has failed to respond to several Until the connection can be re-established, calls are
"continuity" messages sent to it. The server will processed by the default ACD-DN on the switch.
attempt to reconnect to the switch.
After the server connected to the switch, the server Receiving a CONNECTION UP indication is normally
was notified of a new ELAN connection. The server caused by the restarting of a failed server component.
will break the current connection and reconnect to the
switch.
The server is unable to connect to the switch because The server cannot function.
the dongle check failed.
A change in any of the following registry key values The registry keys that control the maximum number of
led to a situation where the available disk space for files or maximum file size revert back to their previous
logging is less. Logging cannot continue with the value settings to ensure there is sufficient disk space for
current configured values for these keys. all the logs of the service.
1. LogPath key
2. MaxNumLogFiles key
3. MaxLogFilesInMeg
The access link is down. The communication between CCMS and CallPilot is
disconnected.
The attempt to create the IVR connections listening Communication is not possible with the IVR system. The
socket failed, probably due to a conflict with another call is handled by the server, but no caller-entered data
application using the same socket port. information is available for the call.
This event suggests an internal error in the server. Communication is not possible with the IVR system. The
Rebooting the server is recommended. call is handled by the server, but no caller-entered data
information is available for the call.
The system successfully established a connection Calls are processed by the IVR system and the caller-
with an IVR system. entered data is made available to the server.
The IVR system disconnected from the server. Communication is not possible with the IVR system. The
call is handled by the server, but no caller-entered data
information is available for the call.
Data was received from a port/DN not currently Data collected on this device was discarded. No caller-
configured for IVR. As a result, collected data was entered data is available for this call.
discarded. This is probably due to a Voice Port
configuration problem.
The data received exceeds the maximum supported Data collected on this device was discarded. No caller-
limit of 128 bytes. To avoid causing data corruption, entered data is available for this call.
the whole message was discarded.
The number of calls waiting in the system exceeds the Incoming calls that are to be queued to a CDN will be
system limit of 15,000. defaulted.
The number of calls waiting in the system has No impact.

returned within engineered system limits (less than
15,000). All calls are being processed by the server.
The Advanced Voice Processing script commands Provided the "Maximum Invalid Logon Attempts permitted
(Open Voice Session and Give Controlled Broadcast) per mailbox" field has been configured on Meridian Mail to
require a Meridian Mail Mailbox. The password for be greater than the number of voice ports, voice
this mailbox has expired. processing should continue to operate until the following
day at 2 a.m. All voice processing commands, except for
Give IVR, will stop working if the password is not changed
by 2:00 AM the following day.
AML did not receive switch heartbeats (polls). There No communication occurs between TSM (CCMS) and the
is a problem with either the switch or the LAN. switch.
Ten consecutive application response time-outs All call-processing components, such as ASM, TFE, VSM,
registered while trying to hand off call control for calls and MLSM, will either restart and/or reacquire all
entering CDNs. resources. All existing calls are defaulted. Until the
connection can be re-established, the switch performs the
call center functions.
The link between the switch and TSM has been None. Information purposes only.
established.
The link between the switch and TSM is down. All existing calls will be defaulted. All call-processing
components, such as ASM, TFE, VSM, and MLSM, wait
for a Switch link up event, and then start to reacquire all
resources. Until the connection can be re-established, the
switch performs the call center functions.
The switch has initialized. All existing calls will be defaulted. All call-processing
The switch has initialized after sysload. All existing calls will be defaulted. All call-processing
Level 1 flow control is being imposed on the link None. Information purposes only.
(warning, but the switch takes no action).
Level 2 flow control is being imposed on the link Calls may be defaulted during this time. The statistics will
(certain incoming messages will be discarded by the reflect this.
switch).
Level 3 flow control is being imposed on the link (all The switch reached the critical overflow threshold level.
incoming messages will be discarded by the switch). Calls may be defaulted during this time. The statistics will
reflect this.
Flow control ends (back to normal operation). None. Information purposes only.
1. LogPath key
3. MaxLogFilesInMeg
1. LogPath key
3. MaxLogFilesInMeg
1. LogPath key
3. MaxLogFilesInMeg
1. LogPath key
3. MaxLogFilesInMeg
RSM cannot find nioamisapi.dll. The most likely cause Multicast Real-Time Display and Translation to Names or
is that mioamisapi.dll is not in the server directory IDs are not available.
path.
RSM cannot find nioamisapi.dll. The most likely cause Multicast Real-Time Display and Translation to Names or
is that nioamisapi.dll is not in the server directory IDs are not available.
path.
RSM is not enabled in the keycode. Multicast Real-Time Display and Translation to Names or
IDs are not available.
This is information to log a service shutdown.
This is information to log a service startup.

This is information to log a service is in its starting
sequence.
This is information to log a service is in its stopping
sequence.
The NCC is in configuration mode. Synchronization between the NCC and each Contact
Center Manager Server does not occur when the NCC is
in configuration mode.
A service could not complete the registration process A service component could not be started properly.
with the WinNT service control manager.
A service could not complete the registration process A service component could not be started properly.
with the WinNT service control manager.
A notification message send to a client failed due to That particular client may not receive any more messages
that send timing out. on the specified channel.
Wait for Multiple Objects returned an error. If the error A service may terminate if the error code is not 6 or 183.
code returned is 6 or 183, the problem has been
handled and the service is not terminated. If not, then
the service will terminate.
An internal service in the contact center has started This event is logged on all Toolkit service start conditions
The service name is given in the event text. for any service that is not covered by any of the other
startup event codes in the range 45321-28.
The SDP service in the contact center has started. This event is logged on all Toolkit service start conditions
for this service.
The RDC service in the contact center has started. This event is logged on all Toolkit service start conditions
for this service.
The HDC service in the contact center has started. This event is logged on all Toolkit service start conditions
for this service.
The HDM service in the contact center has started. This event is logged on all Toolkit service start conditions
for this service.
The SDMCA service in the contact center has started. This event is logged on all Toolkit service start conditions
for this service.
The EB service in the contact center has started. This event is logged on all Toolkit service start conditions
for this service.
The IS service in the contact center has started. This event is logged on all Toolkit service start conditions
for this service.
The TFE service in the contact center has started. This event is logged on all Toolkit service start conditions
for this service.
The ASM service in the contact center has started. This event is logged on all Toolkit service start conditions
for this service.
The VSM service in the contact center has started. This event is logged on all Toolkit service start conditions
for this service.
The NCP service in the contact center has started. This event is logged on all Toolkit service start conditions
for this service.
The OAM service in the contact center has started. This event is logged on all Toolkit service start conditions
for this service.
The AUDIT service in the contact center has started. This event is logged on all Toolkit service start conditions
for this service.
The MLSM service in the contact center has started. This event is logged on all Toolkit service start conditions
for this service.
The TFA service in the contact center has started. This event is logged on all Toolkit service start conditions
for this service.
The NDLOAM service in the contact center has This event is logged on all Toolkit service start conditions
started. for this service.
The NCCOAM service in the contact center has This event is logged on all Toolkit service start conditions
The NITSM service in the contact center has started. This event is logged on all Toolkit service start conditions
for this service.
The NBTSM service in the contact center has started. This event is logged on all Toolkit service start conditions
for this service.
The DDC service in the contact center has started. This event is logged on all Toolkit service start conditions
for this service.
The ES service in the contact center has started. This event is logged on all Toolkit service start conditions
for this service.
The RSM service in the contact center has started. This event is logged on all Toolkit service start conditions
for this service.
The TFABRIDGE service in the contact center has This event is logged on all Toolkit service start conditions
The HAI service in the contact center has started. This event is logged on all Toolkit service start conditions
for this service.
The TFEBRIDGE service in the contact center has This event is logged on all Toolkit service start conditions
The TC service in the contact center has started. This event is logged on all Toolkit service start conditions
for this service.
The CCMS_NIMSM service in the contact center has This event is logged on all Toolkit service start conditions
The CCMS_NBMSM service in the contact center has This event is logged on all Toolkit service start conditions
An internal service in the contact center has stopped. The contact center is not fully functional if any of its
The service name is given in the event text. services have stopped. This event is logged on all Toolkit
service stop conditions for any service that is not covered
by any of the other stopped event codes in the range
45361-68, including when a stop or shutdown command is
sent to the service through the Windows Service Control
Manager.
The SDP service in the contact center has stopped. The contact center is not fully functional if any of its
services have stopped. This event is logged on all Toolkit
service stop conditions for this service, including when a
stop or shutdown command is sent to the service through
the Windows Service Control Manager.
The RDC service in the contact center has stopped. The contact center is not fully functional if any of its
The HDC service in the contact center has stopped. The contact center is not fully functional if any of its
The HDM service in the contact center has stopped. The contact center is not fully functional if any of its
The SDMCA service in the contact center has The contact center is not fully functional if any of its
stopped. services have stopped. This event is logged on all Toolkit
The EB service in the contact center has stopped. The contact center is not fully functional if any of its
The IS service in the contact center has stopped. The contact center is not fully functional if any of its
The TFE service in the contact center has stopped. The contact center is not fully functional if any of its
The ASM service in the contact center has stopped. The contact center is not fully functional if any of its
The VSM service in the contact center has stopped. The contact center is not fully functional if any of its
The NCP service in the contact center has stopped. The contact center is not fully functional if any of its
The OAM service in the contact center has stopped. The contact center is not fully functional if any of its
The AUDIT service in the contact center has stopped. The contact center is not fully functional if any of its
The MLSM service in the contact center has stopped. The contact center is not fully functional if any of its
The TFA service in the contact center has stopped. The contact center is not fully functional if any of its
The NDLOAM service in the contact center has The contact center is not fully functional if any of its
The NCCOAM service in the contact center has The contact center is not fully functional if any of its
The NITSM service in the contact center has stopped. The contact center is not fully functional if any of its
The NBTSM service in the contact center has The contact center is not fully functional if any of its
The DDC service in the contact center has stopped. The contact center is not fully functional if any of its
The ES service in the contact center has stopped. The contact center is not fully functional if any of its
The RSM service in the contact center has stopped. The contact center is not fully functional if any of its
The TFABRIDGE service in the contact center has The contact center is not fully functional if any of its
The HAI service in the contact center has stopped. The contact center is not fully functional if any of its
The TFEBRIDGE service in the contact center has The contact center is not fully functional if any of its
The TC service in the contact center has stopped. The contact center is not fully functional if any of its
The CCMS_NIMSM service in the contact center has The contact center is not fully functional if any of its
The CCMS_NBMSM service in the contact center has The contact center is not fully functional if any of its
1. LogPath key
3. MaxLogFilesInMeg
The OAM Service detected a critical error during an The OAM Service is significantly impaired.
access to the database.
The database connection was lost during a database No server call processing occurs. Incoming calls are
access by the OAM Service. treated by the default ACD-DN. OAM Service is restarted.
An activity code was added to the database.
An activity code was modified in the database.
An activity code was deleted from the database.
An application was added to the database.
An application was modified in the database.
An application was deleted from the database.
A skillset was added to the database.
A skillset was deleted from the database.
A skillset was modified in the database.
A telset field display was added to the database.
A telset field display was modified in the database.
A telset field display was deleted from the database.
A telset field display list was modified in the database.
A TN with switch ID and port address was added to

the database.
A TN with switch ID and port address was deleted

from the database.
A TN with switch ID and port address was modified in

the database.
A user was added to the database.

A user was modified in the database.
A user was deleted from the database.
A user entry list from the database was modified.
A user entry list was deleted from the database.
A user skillset assignment was added to the

database.
A user skillset assignment was modified in the
database.
A user skillset assignment was deleted from the

database
A call presentation class was added to the database.
A call presentation class was modified in the

database.
A call presentation class was deleted from the

database.
A route was added to the database.
A route was modified in the database.
A route was deleted from the database.
The Call-by-Call statistics collection status was turned

on for the given application.
The Call-by-Call statistics collection status was turned
off for the given application.
Historical Statistics configuration was modified in the
database.
Historical Statistics Duration configuration was
modified in the database.
Real-Time Statistics configuration was modified in the

database.
Statistical Data Propagator configuration was
modified in the database.
A CDN was added to the database.

A CDN was modified in the database.
A CDN was deleted from the database.
A DNIS was added to the database.

A DNIS was modified in the database.
A DNIS was deleted from the database.
A script was added to the database.
A script was modified in the database.
A Script was deleted from the database.
A script Item was added to the database.

A script reference to an Item was deleted from the
database.
A script reference to an agent was added to the

database.
A script reference to an agent was deleted from the

database.
A voice port was modified in the database.
An IVR ACD-DN was added to the database.
An IVR ACD-DN was modified in the database.
An IVR ACD-DN was deleted from the database.
An agent to supervisor assignment was added to the

database.
An agent to supervisor assignment was modified in

the database.
An agent to supervisor assignment was deleted from

the database.
A threshold class was added to the database.
A threshold class was deleted from the database.
A threshold class was modified in the database.
A script variable was added to the database.
A script variable was modified in the database.
A script variable was deleted from the database.
A global parameter was modified in the database.

A formula was added to the database.
A formula was modified in the database.
A formula was deleted from the database.
A Real-Time Display was modified.
A Real-Time Display column list was modified in the

database.
The agent attribute was removed from the database.
The supervisor attribute was removed from the user

record.
Communication failure returned by API call. Unable to complete the requested API call. May not be
able to run a scheduled user assignment or a user to
skillset assignment.
Failed to update the maximum number of agents in Cannot update/configure the database at startup with the
the database during startup. maximum number of agents purchased.
Invalid session ID passed into OAM Server when Cannot complete OAM request due to security failure.
OAM client application calling OAM API.
Communication failure with client while running Unable to communicate with client. Cannot generate the
scheduled reports, due to socket communication scheduled report.
failure.
Added contact type with skillset.
Deleted contact type.
Modified contact type with different skillset.
A Media Server was added to the database
Media Server information was updated in the

database.
A Media Server was deleted from the database.
A Media Service was added to the database.
Media Service information was updated in the

database.
A Media Service was deleted from the database.
A Media Service route was added to the database.
A Media Service was deleted from the database.
HDC failed to write statistical data to the temporary Pegged data is not written to the database.
data file.
A change in any of the following registry keys led to a The registry keys that control the maximum number of
situation where the available disk space for logging is files or maximum file size revert back to their previous
less and logging cannot continue with the current value settings to ensure that sufficient disk space exists
configured values for these keys: for all the logs of the service.
1. LogPath key
3. MaxLogFilesInMegs key
RDC failed to send Initialization Request message to Client real-time display cannot get data from Data
SDMCA. Propagator.
RDC failed to send Initialization Done message to Client real-time display cannot get data from Data
SDMCA. Propagator.
RDC was unable to register for call processing RDC cannot provide the Real-Time Data Streams data.
messages with the Event Broker, using the toolkit API.
RDC is unable to connect with Data Propagator. Client real-time display cannot get data from Data
Propagator.
RDC is unable to send data to Data Propagator. Client real-time display cannot get data from Data
Propagator.
logging is less. Logging cannot continue with the value settings to ensure that sufficient disk space exists
current configured values for these keys. for all the logs of the service.
1. LogPath key
A change in any of the following registry key values

led to a situation where the available disk space for
logging is less. Logging cannot continue with the
current configured values for these keys.
1. LogPath key
Time was changed on either the switch or CCMS.

Data pegging during the time change may not be
accurate.
PScan requested dump memory. Obsolete call objects are removed.
PScan cleared a call. Obsolete call objects are removed.
The Audit process cleared a call. Obsolete call objects are removed.
logging is less and logging cannot continue with the value settings to ensure there is sufficient disk space for
current configured values for those keys: all the logs of the service.
1. LogPath key
DP cannot allocate memory for its processing. No real-time data is sent to the client or third-party
interface.
interface.
interface.
interface.
DP cannot allocate memory for its processing or No real-time data is sent to the client or third-party
cannot locate the RDC service. interface.
Failed to set the state of DP service. DP does not run. No real-time data is sent to the client or
third-party interface.
logging is less and logging cannot continue with the value settings to ensure there is sufficient disk space for
current configured values for those keys: all the logs of the service.
1. LogPath key
HDM failed to connect to the database server. HDM cannot write historical statistics to the database.
HDM lost its connection to the database. HDM cannot write historical statistics to the database.
The DB client thread is dead. HDM cannot write historical statistics to the database.
HDM received a critical error message from the HDM cannot write historical statistics to the database.
database.
HDM received a major error message from the HDM cannot write historical statistics to the database.
database.
HDM received a minor error message from the HDM cannot write historical statistics to the database.
database.
HDM was unable to create a call-by-call table. HDM cannot store call-by-call statistics in the database.
HDM was unable to find the specified bulk copy HDM cannot write historical statistics to the database.
format file.
HDM was unable to create the network call-by-call HDM cannot store network call-by-call statistics in the
table. database.
HDM detected insufficient disk space. The oldest Network call-by-call statistics are deleted. The
network call-by-call file was deleted. corresponding information is lost permanently.
A remote BCP for a network call-by-call file exceeded NetCBC data takes more than 15 minutes to be delivered
15 minutes. to the NCC. No data is lost; however, data for the current
interval may not be available for reporting within the
expected time frame.
The HDM service has started.

The online upgrade process is starting. Administration
operations are no longer permitted.
The online upgrade process will be canceled.
An error occurred during the online upgrade process.
SDM Configuration Admin cannot register with the All SDM components failed to start (SDMCA, EB, RDC,
entity described in the error log string. HDC, IS). No data collection occurs.
SDMCA cannot connect to one of the following The following SDM components failed to start: EB, RDC,
services: EB, RDC, or HDC. HDC, IS. No data collection occurs.
SDMCA cannot sent a "data collector(s) ready" No data collection occurs.

message to EB. EB is not responding to SDMCA
messages.
SDM Configuration Admin fails to start up, due to All SDM components failed to start (SDMCA, EB, RDC,
either a memory allocation problem or a toolkit HDC, IS). No data collection occurs.
problem.
Process could not allocate memory. ASM and its components fail.
A shared memory failure occurred. Shared memory used for queuing and intrinsic support
may not work properly. Agents may not receive CCMS
calls.
TN could not be acquired from the switch. CCMS agents cannot log on from this phone set.
The switch could not release the TN. This phoneset does not revert back to a regular ACD
phoneset.
An error occurred while an agent attempted to log on. Agent information may be corrupted and the agent cannot
log on.
An agent is logging on with incomplete or erratic Depending on the cause, some CCMS features are not
information. enabled.
An agent attempted to log on with an invalid ID. The agent cannot log on.
Call forwarding error. The agent who has the DN specified in the error does not
have their phone calls forwarded.
Call forwarding cancel error. The agent who has the DN specified in the error still has
their calls forwarded.
A communication failure occurred between ASM and ASM components cannot communicate with other CCMS
another CCMS component. components.
ASM startup error - the service cannot start due to an No call processing can occur.
internal ASM error.
This event occurred because of an increase in either Logging continues in the current directory location. The
the number of trace files or the trace file size, leading number of files and trace file size will be set to the last
to shortage in disk space. configured, running settings.
A DN acquire failed. Agent personal DN calls are not call-forwarded to the

phoneset at which the agent is logged on.
TSM Registration Return code: ME_NO_ACCESS ASM cannot communicate with the switch. Calls will be
TSM can be temporarily busy with a previous register defaulted.
or deregister. ASM will continue to attempt to register
with TSM.
ASM is up and operational. None

ASM is shutting down. None
A problem was detected relating to the Set Display for See event for cause ID code.
agents - language file corrupted. If the cause ID code is 112 or 113, some or all of the
messages displayed on the phoneset for the set of agents
configured for the language indicated, are corrupted and
are in English.
If the cause ID code is 114, none of the messages
displayed on the phoneset for the agent indicated are in
the language configured. Messages appear in the default
system language.
A link status change. None
ASM cannot read the skillset type for this call. The The new networking enhancements for this release are
result is that the skillset type is set to default mode not available. The Skillset configuration type defaults to
(First Back) for this call. This means that new First Back.
networking enhancements will not work. Possible If you are not using the new networking enhancements,
causes for this problem are: there is no impact.
1. There is an internal communication problem
between ASM and BNS.
2. The BNS structure was not updated with the SS
config type from the DB.
3. The Skillset entry does not exist in the database.
ASM is unable to communicate with the Intrinsic The source node receives a default value from this target
server to get the Average Answer Delay intrinsic. A node, which may result in this node receiving no calls for
default value is returned to the source node. the skillset in question.
The agent logged on but could not be moved to the The agent cannot serve the desired ACD queue.
desired ACD queue.
Acquisition Event failure on Pad. This pad is not available for Universal Networking calls.
TSM registration was successful. None

The communication interface between TSM and ASM ASM cannot communicate with the switch. Calls will be
was lost. defaulted.
The TFE service terminated due to an unrecoverable No call processing is handled by the server while the TFE
error. This was caused by a Windows NT exception. service is down. Calls are defaulted to ACD-DN.
None
Unable to allocate memory during script process. No call processing can be handled by the server. Calls are
defaulted to ACD-DN.
A request to an outstanding call treatment timed out. Request for call treatment is not handled properly. The call
is still being processed.
A skillset or agent request timed out. Request for call treatment is not handled properly. The call
is still being processed.
A request to an outstanding voice treatment timed out. Request for voice treatment is not handled properly. The
call is still being processed.
A request to an external application timed out. If the call was suspended to wait for the HDX response,
the next command in the script will be executed.
Internal data structures in call processing are Calls are processed by default ACD-DN.
overflowing.
The system profile file contains invalid data. TFE service may not be in operational mode. Calls may
not be handled properly.
A request to an outstanding call treatment failed. Call processing may not be handled properly. Calls may
be defaulted.
A request to an outstanding voice treatment failed. Voice processing may not be handled properly. Calls may
be defaulted.
TSM is unable to perform requests to the switch. Call processing may not be handled properly. Calls may
be defaulted.
TFE service terminated due to an internal error. The TFE service terminates. Calls are defaulted to ACD-
DN.
CDN acquire request by TFE failed. A CDN was not acquired. The server cannot process calls
on this CDN.
CDN deacquire request by TFE failed. A CDN was not deacquired as requested.
TFE cannot create the error log file used by the script Script compiler messages are not available. If validation is
activation request. successful, the script is activated.
TFE cannot locate the system profile. It may have TFE may not be in proper operational state. Calls may not
been moved or deleted from the system. be handled properly.
Another component in the system sent TFE an invalid Call or voice processing may not be handled properly.
type of message. Calls may be defaulted.
The link between Contact Management Framework All existing multimedia contacts in CMF will be defaulted.
(CMF) and TFE is down. All multimedia agents will be logged off. All blended
agents will become voice-only agents. All existing voice
contacts will not be affected. When the CMF link is
recovered, CCMS can start processing incoming
multimedia contacts. A blended agent who was changed
to voice only must log off and log back on again to regain
full capacity.
The script contains incomplete or undefined variables. Call processing may not be handled properly. Depending
on the nature of the error, calls may be defaulted to ACD-
DN.
A call was not processed by the server, due to a The call is rejected by TFE.
configuration error.
TFE received an invalid CDN. The call may not be handled properly.
A CDN is deacquired by the switch. Calls on this CDN are defaulted to ACD-DN.
A CDN acquire request failed. Calls on this CDN are not processed by the server.
A CDN change request failed. A CDN is in an unexpected state. Calls on that CDN will
not be handled properly.
The received response does not match the An incoming response event from another component
outstanding request. cannot be treated.
An invalid reason was found in a response message None.
received by TFE.
A CDN is in a wrong state. Calls on this CDN are not handled properly.
Call treatment was not executed successfully. Calls may not receive treatment as requested.
Data is out of the legal range. None.
TFE defaulted the call. The requested call treatment is not given. The call is
processed by the default ACD-DN.
The default skillset is not configured. Calls queued to the default skillset are defaulted to the
ACD-DN.
The default RAN is not configured. Calls are not given default RAN request as expected.
A memory allocation error occurred during call Calls are processed by default ACD-DN.
processing.
The requested call treatment failed to complete. The requested call treatment did not occur.
A CDN request timed out. Calls not presented are defaulted if the deacquire times
out. There is no impact on calls if acquire CDN times out.
A call ID mismatch resulted in a service request time The call is processed by the default ACD-DN.
out.
The link between Contact Management Framework None

(CMF) and TFE is up.
An IVR request was canceled by Voice Services. The IVR session is canceled by Voice Services.
TFE received an invalid message type. Calls may be processed by the default ACD-DN.
TFE received an invalid ACD priority. The requested ACD priority does not execute as
expected.
ACD cannot be inserted into the ACD list. None.

ACD cannot be removed from the ACD list. None.
The delay time value is out of range. The time specified for the wait command may not be
correct.
TFE received an unexpected event. Calls may be processed by the default ACD-DN.
A call is not in a valid state. Requested call treatment may not occur.
TFE received an invalid call ID. The call may not be treated as expected.
TFE received invalid data inside response messages Call processing may not be handled properly.
from ASM.
An internal table contains wrong data or is missing The call processing script may not execute as expected.
data.
TFE encountered an internal exception. There is a possible loss of global or call variable data.
An unknown variable data type error or variable TFE service is not in proper operational state.
conversion error occurred.
Script log message. None.
A script execution command failed. The requested Call processing skips the Execute Script command and
script is not currently active. continues script execution until the end of the current
script. Otherwise, the call is defaulted to ACD.
Request to the Operation, Administration, and TFE service and other components may not be in proper
Maintenance service failed. operational state.
TFE received an unknown ASM command. The call may not be treated as expected.
TFE received an unknown third-party command. The call may not be treated as expected.
TFE received an unknown response event. The call may be processed by the default ACD-DN.
A change CDN type request failed. TFE cannot change the CDN type as requested.
TFE failed to validate and lock resources during script TFE service may not be in proper operational state.
execution.
A script validation error occurred. TFE service may not be in proper operational state.
A general type mismatch occurred when processing The call may be defaulted.
call requests.
TFE detected an invalid CDN or call state. The CDN state cannot be updated, or the call state is
invalid.
Another component in the system sent TFE an invalid Call or voice processing may not be handled properly. The
event. call may be defaulted.
TFE failed to get the master script binary file from the TFE service is not in proper operational state. Calls are
database. processed by the default ACD-DN.
TFE failed to get the master script. TFE service is not in proper operational state. Calls are
TFE failed to set the master script status. TFE service is not in proper operational state. Calls are
TFE failed to activate the master script. TFE service is not in proper operational state. Calls are
TFE failed to get the network script binary file from the Networking call processing may not be handled properly.
database.
TFE failed to get the network script. Networking call processing may not be handled properly.
TFE failed to set the network script status. Networking call processing may not be handled properly.
TFE failed to activate the network script. Networking call processing may not be handled properly.
The total number of skillsets exceeds maximum No significant impact.

skillsets.
TFE encountered invalid internal data. Call processing may not be handled properly.
An error occurred during loading of a script. TFE service is not in proper operational state. Calls are
TFE was unable to process a voice segment. The requested voice segment was not played.
A VSM request failed during a VSM task execution. Voice services may not be given to calls. Calls may be
defaulted.
An error occurred while TFE was reading a script file. TFE may not be in proper operational state.
The compiled script output file is not compatible with Calls are processed by the default ACD-DN.
TFE.
TFE encountered an error when validating and TFE may not be in proper operational state.
activating the script file.
The CDN is not in acquired state. CDN state change may not execute as expected.
The CDN type remained the same. The CDN type remained the same.
TFE is presented a call with a call ID already used by The call is processed by the default ACD-DN.
another call.
An application presented a call unknown to TFE. No impact.
Script commands relating to a skillset or agent failed The skillset/agent/script command did not execute.
due to a possible error in the script.
The server was presented with an invalid call ID. The call will not be processed by the server.
Script commands relating to a skillset or agent failed The requested skillset or agent command failed.
to process.
Failed to present call to agent. The call is processed by the default ACD-DN.
A TFE internal error occurred. Call processing may not be handled properly. Calls may
be defaulted.
Failed to reserve agent ID. The call may not be queued to the specified agent. The
call may be defaulted.
A switch configuration error was detected. TFE service is not in proper operational state.
There are no active agents for the skillset. Expected Wait Time is not calculated for this skillset.
The denominator of an expression was calculated to Substitution with zero may lead to unexpected call flow.
be zero in the script. The expression was replaced
with the value of zero. This may lead to unexpected
call flow behavior.
TFE request failed because memory could not be The system is running low in memory. Normal operation is
allocated. likely to be affected.
TFE cannot install requested resources. Some resources failed to install. The call may be
defaulted.
HDX variable length is too long. Value of a call variable from HDX is not assigned properly.
Depending on the variable, call commands may not work
as expected.
The Host Data Exchange application did not respond Host Data Exchange statements did not execute as
within the system-defined time limit. expected.
A Send Request statement to the Host Data Host Data Exchange statements are not executed as
Exchange component failed. expected.
A Send Info statement to the Host Data Exchange Host Data Exchange statements are not executed as
component failed. expected.
HDX (third-party application) does not exist. Host Data Exchange statements are not executed as
expected.
Application IDs for the Send Request and Get Unable to execute Send Request/Get Response.
Response statements must match.
The number of call variables exceeded the maximum Unable to execute Send Request/Get Response.
limit.
A script command failed to execute during call The call may be processed by the default ACD-DN.
processing.
The switch may not disconnect a call. The specified call may not be disconnected.
The script tried to play a voice segment file that does The caller does not hear the intended voice segment in
not exist. the call flow during script execution.
A command in Event Handler failed. This failure is not No impact.

treated further by Event Handler.
The Host Data Exchange Provider Register ID must Host Data Exchange statements are not executed.
match the script application ID.
Call could not be queued or removed from the queue, The script command had no impact on call processing.
or the priority could not be changed in the specified
skillset.
A caller-entered data field contains more than 32 The caller-entered data field is discarded. Call processing
digits. may not proceed as expected.
Caller-entered data contains more than 10 fields. There should be no impact on script processing. The
script should not allow reference to the 11th field in caller-
entered data.
Caller-entered data field contains non-digits. The caller-entered data field is discarded. This may
impact the script processing that is based on caller-
entered data.
The communication interface between TSM and TFE Calls are defaulted for the switch to handle. TFE cannot
was lost. communicate with the switch as it has lost connection with
TSM.
Disallowed script commands were encountered in the Disallowed script commands are not executed. Processing
Network_Script or subscript for an incoming network continues with the next command in the script.
call.
The thread may be hung. TFE service may not be functioning properly.
The TFE thread received event messages from the TFE may stop handling call processing until receiving a
switch. recovery message from the switch.
Message location reveals the last activity of a relating Subsequent to thread polling timeout.
thread.
TSM Registration Return code: ME_NO_ACCESS TFE cannot communicate with the switch. All calls are
TSM can be temporarily busy with a previous register defaulted.
or deregister. TFE continues to attempt a registration
with TSM.
TSM registration was successful. None.
Unable to create Windows event to monitor registry Any changes made to the TFE registry key will not take
key changes. effect until TFE restarts.
Failed to start Generic Logger. TFE logging failed to start.
TSM link congestion detection Calls are defaulted.
Link Health Monitoring: TFE taking too long to Calls are defaulted.
process calls.
A voice processing script failed due to a memory The system is running low on memory. Normal voice
allocation failure. processing script operations such as Open Voice Session,
Give Controlled Broadcast, or Give IVR are affected.
A resource such as a CDN, IVR ACD-DN, or Voice Voice processing script commands such as Open Voice
Port/Channel could not be acquired or monitored by Session, Give Controlled Broadcast, and Give IVR may
VSM. not be operational. Calls will be defaulted.
A problem occurred in the VSM start phase. VSM There will be a 5 to 10 minute outage in script voice
start has failed. The server will attempt to start VSM processing commands (Open Voice Session, Give
again in 5-10 minutes. Controlled Broadcast, and Give IVR). The calls will be
defaulted during this time. VSM will automatically restart.
TSM Registration Return code: ME_NO_ACCESS VSM cannot communicate with TSM. All voice processing
TSM can be temporarily busy with a previous register script commands do not work (Open Voice Session, Give
or deregister. VSM will continue to attempt to register Controlled Broadcast, and Give IVR).
with TSM.
OAM failed to correctly process a VSM request to Depending on the state mismatch, voice processing script
update the status of a resource (IVR ACD-DNs and commands may fail.
Voice Ports). The server status for the resource may
not reflect the actual switch status for the resources
(for example, AcquirePending instead of
AcquireLogin).
A failure occurred in the setup or execution of the

internal VSM object that handles execution of an
operation. This operation will be cancelled. This is an
internal failure in VSM.
Could not retrieve switch information (for example, All voice processing script commands (Open Voice
switch ID, customer number, switch type, switch Session, Give Controlled Broadcast, and Give IVR) cannot
name). Without the correct switch type and customer function.
number, switch resources (IVR ACD-DNs, Voice
Ports, etc) cannot be controlled or monitored by VSM.
Communication with another system service has A 5 to 10 minute outage in script voice processing
unexpectedly terminated. VSM will automatically commands (Open Voice Session, Give Controlled
restart. Broadcast, and Give IVR) occurs. The calls will be
defaulted by the script processor during this time. VSM will
be automatically restarted.
A call was routed to an IVR ACD-DN that is dedicated If this happens infrequently, it will have very little impact
for voice processing commands (Open Voice Session, and can be ignored. If this occurs frequently, voice
Give Controlled Broadcast, or Give IVR). processing may intermittently fail.
The number of voice segments to be played is more The playing of voice segments is truncated to the limit of
than the system limit of 50. VSM truncates the voice 50 for the play prompt command being executed.
segment list to the first 50.
A voice prompt variable, used in an active script, is Voice script commands (Open Voice Session and Give
referring to a voice segment that does not exist. Controlled Broadcast), which use the voice prompt
variable that has the value defined with an invalid file
segment, do not work. Instead the calls are defaulted.
A voice prompt variable, being used in a script, is Voice script commands (Open Voice Session and Give
referring to a voice file that does not exist. Controlled Broadcast) that use this voice prompt variable
do not work. Instead, the calls are defaulted.
Exceeded the maximum number of retries for Voice Services are not available in the contact center.
MailBoxLogon. Either the username or password is
invalid.
A call was presented to an Access Voice Port for a The call that was using the port is defaulted.
Play Prompt request. However, VSM never answered
the call on the Voice Port. This can be due to many
reasons like network congestion or a slow serial link
to MMAIL. The Voice Services engine has sent a
Voice Play End for the specified device, with reason
Session End Without Answer, and has released the
voice port. VSM has deacquired and reacquired the
voice port to make it available for subsequent calls.
VSM has recovered the situation.
TSM Registration Successful. None. Information purposes only.

The communication interface between TSM and VSM VSM cannot communicate with TSM. All voice processing
has been lost. script commands do not work (Open Voice Session, Give
Controlled Broadcast, Give IVR).
Unable to create a Registry Change Notification A problem occurred creating the event that is triggered
event. when a change in the registry occurs. Dynamic changes to
logging parameters in the registry may not be detected
correctly by the application.
A change in any one of the registry key values led to a The registry keys that control the maximum number of
less. Logging cannot continue with the current value settings to ensure there is sufficient disk space for
configured values for these keys. all the logs of the service.
1. LogPath key
The dialable DN has not been configured for a target Without a dialable DN for a target site, calls cannot be
site. networked out to this site.
The target site is being filtered from all routing tables No new calls are networked to the target site. New calls
at this site. are networked to the other sites configured in the routing
tables.
The configured retry count for the target site was No new calls are networked to the target site. New calls
reached. As a result, the target site is filtered from all are networked to the other sites configured in the routing
routing tables at this site. tables.
The NACD package on the target switch is not No new calls are networked to the target site. New calls
enabled. This feature must be enabled on all switches are networked to the other sites configured in the routing
in the contact center network for calls to be tables.
successfully networked.
The dialable DN for the target site is configured Without a valid dialable DN for a target site, no network
incorrectly. Without the correct dialable DN, calls calls can be completed.
cannot be networked to the target site.
The dialable DN for the target site is configured Without a valid dialable DN for a target site, no network
incorrectly. Without the correct dialable DN, calls calls can be completed.
cannot be networked to the target site.
An agent reservation message to the target site was When an agent reservation message fails, calls cannot be
not sent. networked to the target site.
The Network_Script at the target site was not If the Network_Script is not active, network calls that are
activated. not answered correctly at the target site do not receive the
treatment specified in the Network_Script.
D-channel between this site and the target site is Calls are not queued to sites when the D-channel is down.
down.
An NACD resend timer on the D-channel has expired No calls are networked to the target site.
for the target site, which indicates an NACD failure.
All trunks are busy on the local switch. No calls are networked to the target site.
All trunks are busy at the target site. No calls are networked to the target site.
The network skillset at the target site is out of service. Calls are not queued to the network skillset at the target
site until the network skillset is back in service.
The configured maximum calls that can be queued to Calls are not queued to the network skillset at the target
a network skillset has been reached at the target site. site until the number of calls in queue decreases by the
New network agent requests will not be accepted at configured flow control threshold at the target site.
the target site.
tables.
tables.
Unable to read the skillset type for this call. The The new networking features are not available for this call.
skillset type is set to default mode (First Back) for this The skillset configuration type is defaulted to First Back.
call. The new networking features are not available. If you are not using the new networking features, there is
Possible causes for this problem are: no impact.
• An internal communication problem exists between
ASM and BNS.
• The BNS structure was not updated with the SS
config type from the DB.
• The skillset entry does not exist in the database.
In the Master Script, the call is being queued to Attempts to use Longest Idle Agent or Average Answer
multiple network skillsets. All of the skillsets queued to Speed for this call do not work. The skillset type has
a multiple skillset command must be of the same type. defaulted to First Back.
In this case, they are not so the skillset type is set to
operate in default mode for this call. The default mode
is First Back.
All Landing Pads are busy on the target node. No calls are networked to the target node until a Landing
Pad becomes free.
The DNIS Network CDN at the target node is not No calls are networked to the target node until the DNIS
configured correctly or is not acquired. Network CDN at the target node is correctly configured
and acquired.
When requesting a Landing Pad from the target node, No calls are networked to the target node until reason for
the response either timed out or returned an error the communication error is resolved.
response, due to a problem on the target CMF.
An invalid application ID was used. Request will be rejected.
TSM Registration Return code: ME_NO_ACCESS. MLSM cannot communicate with the switch. Calls may
TSM can be temporarily busy with a previous register default.
or deregister. MLSM will continue to attempt to
register with TSM.
MLSM failed to send data to a third-party application. The third-party application cannot communicate with the
MLSM service.
MLSM failed to receive a message from a third-party The third-party application cannot communicate with the
application. MLSM service.
The connection to the MLSM client application has The session between the client application and the MLSM
shut down gracefully. service finished.
The maximum number of simultaneously third-party There is no impact on operational third-party applications.
applications (16) has been reached. Any attempt to launch a new third-party application will be
rejected.
TSM registration was successful. None
The communication interface between TSM and MLSM cannot communicate with the switch. Calls may
MLSM has been lost. default.
CCMS MLSM DN license was denied. MLSM cannot acquire the DNs.
CCMS MLSM ROD license was denied. The ROD feature will not be available.
The Applications list was modified. Each Contact Center Manager Server is updated with the
new list of applications.
A Network skillset was added at the Network Control Each Contact Center Manager Server is updated with the
Center. new Network skillset.
A Network skillset was deleted at the Network Control The Network skillset is deleted at each Contact Center
Center. Manager Server in the network. If calls are still being
queued to this Network skillset with the QUEUE TO
NETWORK SKILLSET command, the execution of the
command will fail.
A Network skillset was modified at the Network Each Contact Center Manager Server is updated with the
Control Center. modified Network skillset information.
A site was added to the Network Control Center. Following this event, a number of messages should
appear in the Event Browser at the added site, indicating
that a synchronization event has started and stopped.
A network site was deleted from the Network Control The site is deleted from all Contact Center Manager
Center. Servers in the network.
Site information was modified at the Network Control Each Contact Center Manager Server is updated with the
Center. modified site information.
A routing table was modified at the Network Control The site to which the routing table applies is updated.
Center.
A routing table assignment was added to the Network None
Control Center.
A routing table assignment was deleted from the None

Network Control Center.
A routing table assignment was modified at the If this routing table assignment is scheduled, the new
Network Control Center. routing table will take effect when the assignment is run.
A routing table assignment was modified at the If this routing table assignment is scheduled, the new
Network Control Center. routing table will take effect when the assignment is run.
less. Logging cannot continue with the current value settings to ensure that sufficient disk space exists
1. LogPath key
less. Logging cannot continue with the current value settings to ensure that sufficient disk space exists
1. LogPath key
The target nodal site has been unfiltered and network None
calls can now be queued to the site.
The Applications list was modified. None
A Network skillset was added. The Network skillset can be assigned to agents and used
in scripts.
A Network skillset was deleted. If calls are still being queued to this Network skillset, with
the QUEUE TO NETWORK SKILLSET command, the
execution of the command will fail.
Information for a Network skillset was modified. The modified information immediately comes into effect.
A new site was added to the network of Contact With appropriate script modifications, you can now start
Center Manager Servers. routing calls to this site.
A site in the network was removed. None
Site information was modified. None
A routing table was modified. The calls are routed using the new routing table.
Network communication parameters were modified. The modified information immediately comes into effect.
The NCC site name was changed. The NCC site name must be correct in order for the data
to synchronize between the Contact Center Manager
Server and the NCC. Loss of synchronization causes
significant network call routing problems. This should not
be changed unless the site name at the NCC has
changed.
Network skillset status was modified.
If the status is changed from OFF, the site that has the
network skillset status changed is filtered from the routing
tables. When the condition that caused the filtering to start
is changed, the site is no longer filtered from routing table.
A "keep alive" message should be received from each Calls are not queued to sites when the communication
site on a regular basis. If the "keep alive" message is status is closed.
not received, the communication status is set to
Closed and the site is filtered from all routing tables.
When communication is re-established, the status
changes to Open.
Failed to send a sanity (Nodeup) message to the Calls may not be networked in or out of this site.
NCC.
Synchronization between the NCC and Contact The server will be synchronized with the NCC data.
Center Manager Server has started.
Synchronization between the NCC and Contact The server has been synchronized with the NCC data.
Center Manager Server is complete. The data takes effect immediately.
Unable to back up the database to a network drive. DB cannot back up the database
Access to the directory is denied.
The Event Server cannot find niebprxy.dll. The most The Event Server cannot start. Clients cannot connect to
likely cause is that niebprxy.dll is not in the server the Event Server.
directory path.
The Event Server failed to request initialization from The client fails to register with the Event Server.
other components. This error may be a result of an
Event Broker service failure.
A communication problem occurred due to an event The client attempting to register with the Event Server
registration request, which may be caused by an does not receive any events.
Event Broker service issue.
HAI failed to initialize the CORBA infrastructure. There will be no connection to the TFA Service.
HAI failed to initialize the ODBC infrastructure. There will be no connection to the ODBC databases.
HAI failed to initialize the TAPI infrastructure. There will be no connection to the TAPI server.
HAI failed to allocate memory. The HAI Service cannot start.
HAI shutdown was abnormal. HAI is down.
Could not initialize the event server due to the

following reasons:
• Error in receiving the object error
• Object reference is incorrect
• Registration unsuccessful for SEI event/SEI
initialization
• Failed to create Orb handling thread
A call dequeue occurred due to

• translation of agent ID was not
successful (CORBA exception)
• RSM returned incorrect number of agent
• Hash table returned incorrect result
• Sending dequeued message using HDX was not
successful
• Has table should contain dequeue information
Sending call interflowed message using HDX was not

successful
Sending call removed from NACD message using
HDX was not successful.
Sending give NACD message using HDX was not
successful.
Unable to bind to HDX/RSM interface
or
Unable to create SEI handling thread
or
Unable to create NACD ping handling thread
or
Unable to create post route handling thread.
Sending NACD ping message using HDX was not

successful.
Exception in getting message from HDX
or
Received time-out message from HDX
or
Sending post route response message using HDX
was not successful.
The CCMS Control Service has started. CCMS services have started.
The CCMS Control Service has stopped. CCMS services have stopped.
The CCMS Control Service is in starting state. CCMS services will be started.
The CCMS Control Service is in stopping state. CCMS services will be stopped.
CCMS services are starting.

CCMS Control Service requested a license.
CCMS license status
CCMS license status Grace period has been canceled.
CCMS license status
A critical error was detected by the CCMS Control CCMS services cannot be started.
Service while accessing the database.
Service during an access to the database.
Service during access to the registries.
A critical error was detected by the CCMS Service. CCMS services cannot be started.
Service.
Service.
CCMS is configured with a Nodal package but the IP CCMS services cannot be started.
address of the License Manager does not match the
IP address(es) of CCMS.
This is information to log that a service is entering into Started CCM Server shutdown.
stopping state.
CCMS Control Service is entering into stopping state. Started CCM Server shutdown.
A communication error occurred between the License The CCM Server will continue to run for a grace period of
Manager and CCM Server. 5 days.
Warm Standby license was not granted for CCMS The Warm Standby feature is not available on this server.
server.
An error was encountered during the transfer of data The OAMBridge application will shut down. Data was not
from the OAM database to the CMF application upon transferred from OAM to CMF. SIP, UNE, and Multimedia
startup of OAMBridge. Check the event logs for a full cannot process calls.
description of the error.
OAMBridge encountered an error and will shut down OAMBridge will shut down. SIP, UNE, and Multimedia
immediately. Check the event logs for a full cannot process calls.
description.
An error was encountered during the transfer of data Data was not transferred from OAM to CMF. SIP, UNE,
from the OAM database to the CMF application during and Multimedia cannot process calls.
a restart of the OAMBridge. Check the event logs for
a full description of the error.
OAMBridge Application Fault encountered when The CCMS Status Thread does not inform Windows
trying to stop the CCMS Status Thread. This thread is services that the OAMBridge is about to start, which may
used to inform Windows services that the OAMBridge have a knock on effect on dependent services.
is about to start. Check the event logs for a full
description.
OAMBridge could not open a connection with the OAMBridge cannot communicate with the registry and
registry. Check the event logs for a full description. cannot retrieve or set application data in the registry. The
OAMBridge application cannot operate correctly, which
results in SIP, UNE, and Multimedia being unable to
handle calls.
OAMBridge encountered a fault closing a connection OAMBridge cannot close a connection to the registry.
with the registry. Check the event logs for a full
description.
OAMBridge could not retrieve the server type from the OAMBridge cannot set the server type that it must use. If
registry. Check the event logs for a full description. the server type is SIP, the SIP provider will not be created
and SIP will be unable to process calls.
OAMBridge encountered a fault and was unable to OAMBridge cannot set its properties. OAMBridge cannot
set the application properties. Check the event logs operate correctly, which results in SIP, UNE, and
for a full description. Multimedia being unable to handle calls.
OAMBridge encountered a fault getting the host The host address is required for remote host registration
address from the database. Check the event logs for in client mode.
a full description.
There has been an OAMBridge Listener fault. A OAMBridge cannot receive and process events of this
registration was not added to the listener. Check the type from OAM, resulting in data not being added to,
event logs for a full description. deleted from, or modified in CMF. This in turn, impacts the
handling of calls for SIP, UNE, and Multimedia.
OAMBridge could not set up the If providers go out of service, OAMBridge must act
ServiceProviderStatusListener, which is used to notify accordingly. Without this listener, OAMBridge cannot react
OAMBridge of the status of its providers. Check the and SIP, UNE, and Multimedia cannot process calls
event logs for a full description. properly.
OAMBridge could not set up the OAMBridge is not notified of changes in the state of
TerminalStateChangeListener, which is used to notify terminals, which results in SIP, UNE, and Multimedia
OAMBridge of the status of terminals where calls are using the wrong terminals for calls.
placed. Check the event logs for a full description.
OAMBridgeListener must be active so that Without the heartbeat, OAMBridge cannot be sure that the
OAMBridge can be notified of any changes to data in OAMListener is active. Therefore, the OAMListener must
OAM and replicate those changes to CMF. The be restarted.
heartbeat is used to check that the OAMListener is
active. Check the event logs for a full description.
OAMBridge uses this thread to retrieve notifications OAMBridge cannot pick up any events from the
from the OAMListener. Check the event logs for a full OAMListener, resulting in any changes to OAM going
description. unnoticed. This results in SIP, UNE, and Multimedia calls
not being processed correctly.
ServiceProviderStatusListener, which is used to notify If providers go out of service, OAMBridge must act
OAMBridge of the status of its providers, is not accordingly. Without this listener, OAMBridge cannot react
functioning properly. Check the event logs for a full and SIP, UNE, and Multimedia cannot process calls
description. properly.
TerminalStateChangeListener, which is used to notify OAMBridge is not notified of changes in the state of
OAMBridge of the status of terminals where calls are terminals, which results in SIP, UNE, and Multimedia
placed, is not functioning correctly. Check the event using the wrong terminals for calls.
logs for a full description.
The Pooling Thread failed to start. OAMBridge uses OAMBridge does not set the master status for the contact
the Pooling Thread to keep the CMF contact manager manager and is not notified of events for the
in an active state and notify OAMBridge of events for TerminalStateChange and ServiceProviderStatus
the TerminalStateChange and ServiceProviderStatus listeners. As a result, SIP, UNE, and Multimedia calls are
listeners. Check the event logs for a full description. not processed correctly.
The OAMBridge OAMListener was not set up. The OAMBridge cannot receive and process events from
listener is required to receive events from OAM. OAM, which results in data not being added to, deleted
Check the event logs for a full description. from, or modified in CMF. This impacts the handling of
calls for SIP, UNE, and Multimedia.
OAMBridge could not create all the providers Without the providers, SIP, UNE, and Multimedia cannot
required. Check the event logs for a full description. handle calls. OAMBridge shuts down.
OAMBridge cannot set the contact manager master Without the contact manager in an active state, SIP, UNE,
status. Contact manager must be kept in an active and Multimedia cannot handle calls.
state to handle calls. Check the event logs for a full
description.
The SIP passive provider was not created. Check the Without the passive provider, SIP cannot handle calls. The
event logs for a full description. OAMBridge application shuts down.
The CCMM provider was not created. Check the Without the CCMM provider, Multimedia cannot handle
event logs for a full description. calls. The OAMBridge application shuts down.
The Network provider was not created. Check the Without the Network provider, UNE cannot handle calls.
event logs for a full description. The OAMBridge shuts down.
OAMBridge cannot retrieve the contact manager from Without the contact manager, SIP, UNE, and Multimedia
CMF. Check the event logs for a full description. cannot handle calls.
OAMBridge encountered a fault cleaning the CMF OAMBridge cannot clean CCMM provider objects from the
space of an object associated with the CCMM space, which can result in duplicate entries, redundant
provider. Check the event logs for a full description. data, and memory leak, impacting the ability of Multimedia
to handle calls.
OAMBridge encountered a fault cleaning the CMF OAMBridge cannot clean Passive provider objects from
space of an object associated with the Passive the space, which can result in duplicate entries, redundant
provider. Check the event logs for a full description. data, and memory leak, impacting the ability of SIP to
handle calls.
OAMBridge encountered a fault cleaning the CMF OAMBridge cannot clean Network provider objects from
space of an object associated with the Network the space, which can result in duplicate entries, redundant
provider. Check the event logs for a full description. data, and memory leak, impacting the ability of UNE to
handle calls.
OAMBridge encountered an error in adding a contact Without this contact type being added to the CCMM
type to the CCMM provider. Check the event logs for provider, Multimedia cannot handle all the different call
a full description. types that it should be able to handle.
OAMBridge encountered an error in adding a contact Without this contact type being added to the Passive
type to the Passive provider. Check the event logs for provider, SIP cannot handle all the different call types that
a full description. it should be able to handle.
OAMBridge encountered an error in adding a contact Without this contact type being added to the Network
type to the Network provider. Check the event logs for provider, UNE cannot handle all the different call types
a full description. that it should be able to handle.
OAMBridge encountered a fault retrieving agent data OAMBridge cannot populate agent data from the OAM
from the OAM database. Agent data is needed for database to CMF, which impacts the ability of SIP, UNE,
assigning calls. Check the event logs for a full and Multimedia to handle calls.
description.
OAMBridge encountered a fault placing agent data OAMBridge cannot populate agent data from the OAM
into the CMF application. Agent data is needed for database to CMF, which impacts the ability of SIP, UNE,
assigning calls. Check the event logs for a full and Multimedia to handle calls.
description.
OAMBridge encountered a fault retrieving CDN data OAMBridge cannot populate CDN data from the OAM
from the OAM database. CDN data is needed for database to CMF, which impacts the ability of SIP, UNE,
transferring calls. Check the event logs for a full and Multimedia to handle calls.
description.
OAMBridge encountered a fault placing CDN data OAMBridge cannot populate CDN data from the OAM
into the CMF application. CDN data is needed for database to CMF, which impacts the ability of SIP, UNE,
description.
OAMBridge encountered a fault retrieving route data OAMBridge cannot populate route data from the OAM
from the OAM database. Route data is needed for database to CMF, which impacts the ability of SIP, UNE,
handling calls. Check the event logs for a full and Multimedia to handle calls.
description.
OAMBridge encountered a fault placing route data OAMBridge cannot populate route data from the OAM
into the CMF application. Route data is needed for database to CMF, which impacts the ability of SIP, UNE,
handling calls. Check the event logs for a full and Multimedia to handle calls.
description.
OAMBridge encountered a fault retrieving DNIS data OAMBridge cannot populate DNIS data from the OAM
from the OAM database. DNIS data is needed for database to CMF, which impacts the ability of SIP, UNE,
description.
OAMBridge encountered a fault placing DNIS data OAMBridge cannot populate DNIS data from the OAM
into the CMF application. DNIS data is needed for database to CMF, which impacts the ability of SIP, UNE,
description.
OAMBridge encountered a fault retrieving Media OAMBridge cannot populate Media Server data from the
Server data from the OAM database. Media Server OAM database to CMF, which impacts the ability of SIP,
data is needed for handling calls (for example, IVR, UNE, and Multimedia to handle calls.
music). Check the event logs for a full description.
OAMBridge encountered a fault placing Media Server OAMBridge cannot populate Media Server data from the
data into the CMF application. Media Server data is OAM database to CMF, which impacts the ability of SIP,
needed for handling calls (for example, IVR, music). UNE, and Multimedia to handle calls.
Check the event logs for a full description.
OAMBridge encountered a fault retrieving Media OAMBridge cannot populate Media Service data from the
Service data from the OAM database. Media Server OAM database to CMF, which impacts the ability of SIP,
OAMBridge encountered a fault placing Media OAMBridge cannot populate Media Service data from the
Service data into the CMF application. Media Server OAM database to CMF, which impacts the ability of SIP,
OAMBridge encountered a fault retrieving Media OAMBridge cannot populate Media Service Route data
Service Route data from the OAM database. Media from the OAM database to CMF, which impacts the ability
Service Route data is needed for delivering a Media of SIP, UNE, and Multimedia to handle calls.
Server through a Media Service for calls (for example,
IVR, music). Check the event logs for a full
description.
OAMBridge encountered a fault placing Media OAMBridge cannot populate Media Service Route data
Service Route data into the CMF application. Media from the OAM database to CMF, which impacts the ability
Service Route data is needed for delivering a Media of SIP, UNE, and Multimedia to handle calls.
Server through a Media Service for calls (for example,
IVR, music). Check the event logs for a full
description.
OAMBridge encountered an error in removing all OAMBridge may be adding data from the OAM database
objects from the CMF space. Check the event logs for to an already populated CMF space, resulting in duplicate
a full description. entry exceptions, redundant entries, and memory leak.
This affects the ability of SIP, UNE, and Multimedia to
handle calls.
OAMBridge encountered a fault adding new agent OAMBridge cannot update CMF with the new agent data
data to CMF during an OAM request. Check the event from OAM, which can result in a synchronization issue
logs for a full description. between CCT, Multimedia, Network, and SIP components.
This agent will not be able to log on or perform any other
actions. This affects the ability of SIP, UNE, and
Multimedia to handle calls.
OAMBridge encountered a fault adding new OAMBridge cannot update CMF with the new supervisor
supervisor data to CMF during an OAM request. data from OAM, which can result in a synchronization
Check the event logs for a full description. issue between CCT, Multimedia, Network, and SIP
components. This supervisor will not be able to log on or
perform any other actions. This affects the ability of SIP,
UNE, and Multimedia to handle calls.
OAMBridge encountered a fault adding new agent OAMBridge cannot update CMF with the new agent
supervisor data to CMF during an OAM request. supervisor data from OAM, which can result in
Check the event logs for a full description. synchronization issues between CCT, Multimedia,
Network, and SIP components. This agent supervisor will
not be able to log on or perform any other actions. This
affects the ability of SIP, UNE, and Multimedia to handle
calls.
OAMBridge encountered a fault updating agent data OAMBridge cannot update CMF with the new agent data
during an OAM request. Check the event logs for a from OAM, which can result in synchronization issues
full description. between CCT, Multimedia, Network, and SIP components.
This agent will not be able to log on or perform any other
OAMBridge encountered a fault updating agent data OAMBridge cannot update CMF with the agent data from
during an OAM request. Check the event logs for a OAM, which can result in a synchronization issue between
full description. CCT, Multimedia, Network, and SIP components. This
agent will not be able to log on or perform any other
OAMBridge encountered a fault updating agent data OAMBridge cannot update CMF with the agent data from
during an OAM request. Check the event logs for a OAM, which can result in a synchronization issue between
agent will not be able to log on or perform any other
actions, affecting the ability of SIP, UNE, and Multimedia
to handle calls.
OAMBridge encountered a fault updating agent OAMBridge cannot update CMF with the agent supervisor
supervisor data during an OAM request. Check the contact type data according to OAM requests, which can
event logs for a full description. result in synchronization issues between CCT,
Multimedia, Network, and SIP components. This agent
supervisor will not be available for all contact types,
affecting the ability of SIP, UNE, and Multimedia to handle
calls.
OAMBridge encountered a fault updating CMF with OAMBridge cannot update CMF data according to OAM
new supervisor template data during an OAM request. requests, which can result in synchronization issues
Check the event logs for a full description. between CCT, Multimedia, Network, and SIP components.
The supervisor cannot perform without the template,
calls.
the new agent supervisor template data during an requests, which can result in synchronization issues
OAM request. Check the event logs for a full between CCT, Multimedia, Network, and SIP components.
description. The agent supervisor cannot perform without the template,
calls.
the new agent template data during an OAM request. requests, which can result in synchronization issues
Check the event logs for a full description. between CCT, Multimedia, Network, and SIP components.
The agent supervisor cannot perform without the template,
calls.
OAMBridge encountered a fault updating agent data OAMBridge cannot update CMF with the new agent data
during an OAM request. Check the event logs for a from OAM, which can result in synchronization issues
Because the agent does not have the updated data, its
actions will not be correct, affecting the ability of SIP,
OAMBridge encountered a fault removing agent data OAMBridge cannot remove from CMF the agent data from
during an OAM request. Check the event logs for a OAM, which can result in synchronization issues between
agent will still be available in the system, affecting the
ability of SIP, UNE, and Multimedia to handle calls.
OAMBridge encountered a fault updating CMF data OAMBridge cannot update CMF data according to OAM
during an OAM request. Check the event logs for a requests, which can result in synchronization issues
OAMBridge encountered a fault updating CMF with OAMBridge cannot add to CMF the new treatment
the new treatment terminal data during an OAM terminal data according to OAM requests, which can result
request. Treatment terminals are used for handling in synchronization issues between CCT, Multimedia,
calls (for example, IVR, music). Check the event logs Network, and SIP components. The media server related
for a full description. to this treatment terminal will not be available to SIP, UNE,
and Multimedia for handling calls.
OAMBridge encountered a fault updating CMF with OAMBridge cannot add to CMF the new treatment
the new treatment address data during an OAM address data according to OAM requests, which can result
request. Treatment addresses are used to deliver in synchronization issues between CCT, Multimedia,
treatment terminals (for example, IVR, music) during Network, and SIP components. This treatment address
call handling. Check the event logs for a full will not be available to deliver a media server so that SIP,
description. UNE, and Multimedia can handle calls effectively.
OAMBridge cannot find the treatment terminal data in Without this treatment terminal, SIP, UNE, and Multimedia
CMF. Treatment terminals are used for handling calls cannot use the related media server during the handling of
(for example, IVR, music). Check the event logs for a calls.
full description.
OAMBridge cannot find the treatment address data in Without this treatment address, SIP, UNE, and Multimedia
CMF. Treatment addresses are used to deliver call cannot use all possible media servers during the handling
handling methods (for example, IVR, music). Check of calls.
the event logs for a full description.
OAMBridge encountered a fault updating CMF with OAMBridge cannot update CMF with new CDN data
new CDN data during an OAM request. CDNs are according to OAM requests, which can result in
used to transfer calls. Check the event logs for a full synchronization issues between CCT, Multimedia,
description. Network, and SIP components. This CDN will not be
available for transferring calls, affecting the ability of SIP,
OAMBridge encountered a fault removing CDN data OAMBridge cannot update CMF data according to OAM
from CMF during an OAM request. CDNs are used to requests, which can result in synchronization issues
transfer calls. Check the event logs for a full between CCT, Multimedia, Network, and SIP components.
description. This CDN will still be available, affecting how SIP, UNE,
and Multimedia handle calls (they may still use a CDN that
should not be available).
OAMBridge encountered a fault updating CDN data to OAMBridge cannot update CMF data according to OAM
CMF during an OAM request. CDNs are used to requests, which can result in synchronization issues
transfer calls. Check the event logs for a full between CCT, Multimedia, Network, and SIP components.
description. This CDN will not be updated, affecting how SIP, UNE,
and Multimedia handle calls (the CDN does not perform
as the updated data intended).
new route data during an OAM request. Routes are requests, which can result in synchronization issues
used for handling calls. Check the event logs for a full between CCT, Multimedia, Network, and SIP components.
description. This route will not be available, affecting how SIP, UNE,
and Multimedia handle calls.
OAMBridge encountered a fault updating route data in OAMBridge cannot update CMF data according to OAM
CMF during an OAM request. Routes are used for requests, which can result in synchronization issues
handling calls. Check the event logs for a full between CCT, Multimedia, Network, and SIP components.
description. Using old route data affects how SIP, UNE, and
Multimedia handle calls.
OAMBridge encountered a fault removing route data OAMBridge cannot update CMF data according to OAM
from CMF during an OAM request. Routes are used requests, which can result in synchronization issues
for handling calls. Check the event logs for a full between CCT, Multimedia, Network, and SIP components.
description. Not removing the old route data can allow SIP, UNE, and
Multimedia to handle calls in ways they should no longer
be handled.
new DNIS data during an OAM request. DNIS data is requests, which can result in synchronization issues
used for transferring calls. Check the event logs for a between CCT, Multimedia, Network, and SIP components.
full description. This DNIS will not be available for SIP, UNE, and
Multimedia to use to transfer calls.
OAMBridge encountered a fault removing DNIS data OAMBridge cannot update CMF data according to OAM
from CMF during an OAM request. DNISs are used requests, which can result in synchronization issues
for transferring calls. Check the event logs for a full between CCT, Multimedia, Network, and SIP components.
description. This DNIS will still be available, affecting how SIP, UNE,
and Multimedia handle calls (they may use a DNIS that
should no longer be available).
OAMBridge encountered a fault updating the DNIS OAMBridge cannot update CMF data according to OAM
data in CMF during an OAM request. DNIS data is requests, which can result in synchronization issues
used for transferring calls. Check the event logs for a between CCT, Multimedia, Network, and SIP components.
full description. This DNIS will not be updated, affecting how SIP, UNE,
and Multimedia handle calls, as the DNIS will not perform
as the updated data would intend.
OAMBridge encountered a fault adding agent contact OAMBridge cannot update CMF data according to OAM
type data to CMF during an OAM request. Contact requests, which can result in synchronization issues
types depict the types of calls an agent can handle. between CCT, Multimedia, Network, and SIP components.
Check the event logs for a full description. This affects how SIP, UNE, and Multimedia process calls,
as agents are not available for all the call types that they
should be able to handle.
OAMBridge encountered a fault removing agent OAMBridge cannot update CMF data according to OAM
contact type data from CMF during an OAM request. requests, which can result in synchronization issues
Contact types depict the types of calls the agent can between CCT, Multimedia, Network, and SIP components.
handle. Check the event logs for a full description. This affects how SIP, UNE, and Multimedia process calls,
as agents are available for call types they should not be
handling.
OAMBridge encountered a fault adding media service OAMBridge cannot update CMF data according to OAM
data to CMF during an OAM request. Media service is requests, which can result in synchronization issues
used to deliver media servers (for example, IVR, between CCT, Multimedia, Network, and SIP components.
music) during the handling of calls. Check the event SIP, UNE, and Multimedia cannot use this media service
logs for a full description. to deliver treatments such as IVR or music to calls during
call handling.
OAMBridge encountered a fault removing media OAMBridge cannot update CMF data according to OAM
service data from CMF during an OAM request. Media requests, which can result in synchronization issues
service is used to deliver media servers (for example, between CCT, Multimedia, Network, and SIP components.
IVR, music) during the handling of calls. Check the SIP, UNE, and Multimedia can still use this media service
event logs for a full description. to deliver treatments (such as IVR or music) to calls when
it should not be available.
new media service data during an OAM request. requests, which can result in synchronization issues
Media service is used to deliver media servers (for between CCT, Multimedia, Network, and SIP components.
example, IVR, music) during the handling of calls. SIP, UNE, and Multimedia will use an out-of-date media
Check the event logs for a full description. service to deliver treatments (such as IVR or music) to
calls resulting in incorrect handling.
new media server data during an OAM request. requests, which can result in synchronization issues
Media servers are treatments (such as IVR or music) between CCT, Multimedia, Network, and SIP components.
used during call handling. Check the event logs for a SIP, UNE, and Multimedia cannot use this media server
full description. treatment during call handling.
server data from CMF during an OAM request. Media requests, which can result in synchronization issues
servers are treatments (such as IVR or music) used between CCT, Multimedia, Network, and SIP components.
during call handling. Check the event logs for a full SIP, UNE, and Multimedia can still use this media server
description. treatment (such as IVR or music) during call handling.
OAMBridge encountered a fault updating media OAMBridge cannot update CMF data according to OAM
server data in CMF during an OAM request. Media requests, which can result in synchronization issues
servers are treatments (such as IVR or music) used between CCT, Multimedia, Network, and SIP components.
during call handling. Check the event logs for a full SIP, UNE, and Multimedia still use an old media server
description. treatment during call handling.
new media service route data during an OAM request. requests, which can result in synchronization issues
Media service routes associate media server between CCT, Multimedia, Network, and SIP components.
treatments (such as IVR or music) for calls with media SIP, UNE, and Multimedia cannot use the treatment (such
services, which makes the treatments available for as IVR or music) associated with this media service route
calls. Check the event logs for a full description. for calls.
service route data from CMF during an OAM request. requests, which can result in synchronization issues
Media service routes associate media server between CCT, Multimedia, Network, and SIP components.
treatments (such as IVR or music) for calls with media SIP, UNE, and Multimedia can still use the treatment
services, which makes the treatments available for (such as IVR or music) associated with this media service
calls. Check the event logs for a full description. route for calls.
OAMBridge encountered a fault putting the SIP OAMBridge does not have access to providers in CMF. If
passive provider in service. Check the event logs for a the passive provider is not in service, SIP cannot handle
full description. calls.
OAMBridge encountered a fault putting the CCMM OAMBridge does not have access to providers in CMF. If
provider in service. Check the event logs for a full the CCMM provider is not in service, Multimedia cannot
description. handle calls.
OAMBridge encountered a fault putting the Network OAMBridge does not have access to providers in CMF. If
provider in service. Check the event logs for a full the Network provider is not in service, UNE cannot handle
description. calls.
OAMBridge encountered a fault putting the SIP OAMBridge does not have access to providers in CMF. If
passive provider in service. Check the event logs for a the passive provider is not in service, SIP cannot handle
full description. calls.
OAMBridge Application Fault encountered when CCMS thread continues to inform Windows services that
trying to stop the CCMS Status Thread. This thread is OAMBridge is about to start, which may have a knock on
used to inform Windows services that the OAMBridge effect on dependant services.
is about to start. Check the event logs for a full
description.
OAMBridge encountered a fault processing a user OAMBridge cannot update CMF with the new agent data
info notify to CMF during an OAM request. An info from OAM, which can result in synchronization issues
notify is used to update agent details (for example, if between CCT, Multimedia, Network, and SIP components.
an agent is being updated to a supervisor). Check the Because the agent does not have the updated data, its
event logs for a full description. actions will not be correct, affecting the ability of SIP,
The OAMBridge application has started up. The OAMBridge application started.
The OAMBridge application has stopped. The OAMBridge application stopped.

The replication channel from the CCMS OAM space CCMS cannot replicate data to CCT. This may be due to
to the CCT CTI space is not available. an incorrect configuration setup.
The replication link from OAM to CTI space has been The OAMBridge application stopped.
established.
The Niprotam service could not retrieve information Process monitoring cannot take place until this problem is
about services from the operating system. resolved.
The Niprotam service could not access its Process monitoring cannot take place until this problem is
configuration file, processTasks.xml. This file must be resolved.
located in the same folder as CCMonitorService.exe
(normally, \Nortel\iccm\bin\).
The Niprotam service could not find its configuration The Niprotam service relies on default values for
file, CCMonitorService.exe.config. This file must be MonitorInterval and StartupDelay. The impact is minimal.
located in the same folder as CCMonitorService.exe
(normally, \Nortel\iccm\bin\). If this file cannot be
found or if the correct values are missing from the file,
the Niprotam service relies on default values.
The Niprotam service could not retrieve information Process monitoring continues; however, information
about services from the operating system. displayed by the UI tool may be incorrect.
The Niprotam service detected a change to the list of The list of services that Niprotam monitors and controls
monitored services. will be reread from disk.
The Niprotam service acted to lower the priority of a This is expected behavior. The priority of the process
process whose CPU usage exceeded a should be restored shortly.
predetermined limit.
The Niprotam service acted to restore the priority of a This is expected behavior.
process that was previously lowered.
The CC Process Monitor detected that a monitored This process will be monitored when it starts.
process is not running or has exited.
The CC Process Monitor detected that one of its This process will now be monitored.
monitored processes has started.
The Niprotam service could not be contacted. Process monitoring cannot take place.
The CC Process Monitor service component started Process monitoring will now take place.
successfully.
The CC Process Monitor service component has Process monitoring has been suspended.
been paused.
The CC Process Monitor service component has Process monitoring resumes.
resumed.
The CC Process Monitor service component has Process monitoring ceases.
been shut down.
The CC Process Monitor could not successfully The affected process may become starved of CPU if the
detach from a monitored process. The process may system is overloaded.
be running with an incorrect priority.
The CC Process Monitor could not successfully If the system becomes overloaded, this process may
monitor the process. More details can be found in the starve another process of CPU time.
Niprotam log file.
The file is not archived.

Could not access a file to add it to a log archive. The
file will be missing in this archive.
Failed to create an archive file. The zipping operation The archive has failed and will be missing from the archive
did not succeed. location.
The Log Archiver could not access the archive Archiving cannot take place until the Log Archiver can
location. access the archive location.
An attempt to delete older archive files to maintain Archiving cannot continue until sufficient disk space is
disk space failed. made available.
The archiver service could not move this archive file This archive will be missing from the archive location.
from a temp location to the archive location.
There is no longer sufficient disk space at the archive Archiving ceases until sufficient disk space is freed at the
location to create new archives. archive location.
The Log Archiver failed to delete a temporary file from This file exists in the Log Archiver directory, consuming
its directory after an archive failure. space.
The Log Archiver could not read or understand its The Log Archiver service shuts down and archiving
configuration file. ceases.
One of the rules in the configuration is malformed and This rule is ignored by the service.
will be skipped.
To maintain disk usage within limits, the Log Archiver Older archive files are deleted.
is deleting older archive files from the archive
location.
The Log Archiver service failed to respond to a Archiving ceases. The service needs to be restarted.
service command.
The Log Archiver has received too many requests. Archive events will be lost.
Requests will time out.
The Log Archiver service started successfully. Archive events will be detected.
The Log Archiver service has been stopped. Archive events are no longer detected.
All services were started successfully. None

All services were shut down successfully. None
Some services failed to start. The system may not be operational.

Some services failed to shut down. The system may not be completely stopped.
Failed to open the XML configuration file. Could not read the service list fro the XML file. Unable to
start or shut down any services. The system state is
unchanged.
Failed to save the XML configuration file. Could not save the service list XML file. The custom list
will not be persisted.
Failed to create a thread. Threaded operation may not take place.
The CCMS Control service started the new instance Service Monitor starts monitoring the call processing
of Service Monitor.dll. services.
The Service Monitoring is turned off (default) or is not Call processing services are not monitored.
set to monitor the call processing services by the
customer action.
Service Monitor started monitoring the call processing The call processing services are monitored.
services.
The CCMS Control Service stopped the service The system is shut down.
monitoring (upon shutdown of the CCMS Control
service).
After the Service Monitor initiated the switchover to Service monitoring will continue.
standby, due to a fault on Cache or a configuration
issue, the switchover did not occur. In the next
monitoring cycle, the Service Monitor reset itself and
started monitoring the services again.
After stopping an affected call processing service, the The stopped services start.
Service Monitor is now running ICCMSU to restart all
stopped services.
Upon startup of the CCMS 7.0, the ICCMSU is run Service Monitor will continue after ICCMU finishes.
and can take some time to finish starting up all the
services. The Service Monitor waits until ICCMSU
finishes to start monitoring the call processing
services.
The CCMS administrator updated the service The Service Monitor reads the updated configuration data
monitoring configuration data (for example, changed and restarts the monitoring of the call processing services
the service restart wait time, service restart limit for from the beginning, using the updated configuration data.
one or more call processing services, or turned on or
off the service monitoring).
The Service Monitor.DLL swapped the switch IP All call processing services are restarted after this event.
address in the registry with the alternative switch IP
address because the NBTSM service LINK_STATUS
was not UP (connected) for the configured amount of
time.
The Service Monitor.DLL swapped the switch All call processing services are restarted after this event.
customer number in the registry with the alternative
switch customer number because the NBTSM service
LINK_STATUS was not UP (connected) for the
configured amount of time.
The Service Monitor initiated the switchover to the The CCMS switches over to the standby CCMS.
standby server.
The restart limit of the call processing service was The switchover occurs to the standby CCMS.
exceeded. The Service Monitor initiates the
switchover to the standby CCMS server.
The restart limit of the call processing service was The Service Monitor continues monitoring the services.
exceeded. The Service Monitor resets itself and starts
monitoring the call processing services again. (In this
case, Redundancy and Resiliency is not configured
on CCMS.)
The Service Monitor is sending the messages that it The call processing service will be restarted in the given
will restart the service in %d seconds or initiate the time or the switchover to the standby server will be
switchover in %d seconds. (Restart of the service initiated in the given time.
occurs when the restart limit is not exceeded and after
that, the initiate message will appear in the event.)
The affected call processing service is stopped by the The call processing service is stopped and will be
Service Monitor because the toolkit state was not up restarted with ICCMSU after this event.
for the allowed service restart wait time.
The call processing service is stopped, which could The call processing service is down. Service Monitor
be due to maintenance activity on the server continues to monitor this service but does not take any
(SU/SUS) or is stopped by the Service Monitor in an action.
attempt to restart this affected service.
The Service Monitor is attempting to restart the The call processing service will be restarted.
affected call processing service.
The affected call processing service cannot be Service Monitor waits for the next cycle (10 seconds) to
restarted because either ICCMSU or ICCMSD is take any further actions on this service.
already running.
The affected call processing service could not be The call processing service is stopped.
stopped. Service Monitor terminated the service
process.
The Service Monitor encountered an error while The call processing service may end up in a suspended
terminating the affected call processing service state.
process.
The CCMS Service Monitor detected a critical error. Service monitoring may stop. Generally, the CCMS
There is a general exception in the code of the Control service is designed to restart service monitoring.
Service Monitor.dll.
The Service Monitor could not get the configuration Service monitoring will not start.
data from the database. There may be a database
issue or the ODBC DSN CCMS_CACHE_DSN cannot
connect to the CCMS_STAT namespace.
The Service Monitor thread encountered an error Service monitoring stops.

(generally, a memory or coding issue).
The Service Monitor could not connect to the Service monitoring may not start.
database. There may be a database issue or the
ODBC DSN CCMS_CACHE_DSN cannot connect to
the CCMS_STAT namespace.
The Service Monitor could not connect to the Service monitoring may not start.
database for status updates or initiating the
switchover. There may be a database issue or the
ODBC DSN CCMS_CACHE_DSN cannot connect to
the CCMS_STAT namespace.
An error occurred while reading or updating the The alternative switch IP, Service Monitor registry updates
registry values. cannot occur. Service monitoring continues.
An issue occurred writing the initiating flag to the The switchover to the standby CCMS does not occur.
CCMS database. Service monitoring continues to operate.
There are ODBC driver errors. An ODBC or database issue exists. Service Monitor may
not run and cannot function correctly.
An error occurred stopping the service. The service cannot be stopped. Service Monitor attempts
to stop the service process.
An error occurred starting up the call processing Services may not start. The system may become unstable.
service.
Cannot create or open MLSM Log file. MLSM cannot save log messages.
Probable
Probable Cause Cause
This problem can be caused when the Niprotam service does not have
sufficient security permissions to access process information.
This problem may be caused if the processTasks.xml is missing, in the

wrong folder, or corrupt. It may also be caused if the Niprotam service
does not have sufficient security permissions to access the file.
The CCMonitorService.exe configuration file is missing, in the wrong
folder, missing key values, or corrupt.
This problem can be caused when the Niprotam service does not have
sufficient security permissions to access service information.
The processTasks.xml file changed, triggering a rebuild of the list of

monitored items.
A monitored process exceeded its predetermined CPU usage limit. These
limits can be changed using the CCMonitorUI application.
A process that had its priority lowered by the Niprotam service, has now
had its priority restored.
Recovery Action
Verify that the Contact Center software was installed correctly. If the problem persists, contact your Customer Support
Representative.
Try restarting the OM Service. If the problem persists, note any error codes and messages and contact your Customer Support
Representative.
1. Verify that the RPC service is up and running.

2. Try restarting the service.
If the problem persists, note any error codes and messages and contact your Customer Support Representative.
Note the event report with the return code and contact your Customer Support Representative.
Try manually restarting the specified service. If the problem persists, check for other events associated with this service and
contact your Customer Support Representative.
Check whether the specified service is up and running. If not, try restarting the service. If the problem persists, contact your
Customer Support Representative.
Note any error codes and messages and contact your Customer Service Representative.
Note the problematic service mentioned in the error message. Check for other event logs associated with this service around
the time this event was logged and contact your Customer Support Representative.
If calls continue to be defaulted, note any error codes and messages and contact your Customer Support Representative.
No action required if logon succeeds in a subsequent attempt.
There are 2 possible causes of this problem:

1. The logon parameters are incorrect. Check the Switch Information in the Feature Reports of the
Sysops Utilities.
2. The switch was not configured to allow logon from the IP address of the server, or the logon
parameters defined on the switch do not match the ones defined on the server.

There are 2 possible causes of this problem:
1. The logon parameters are incorrect. Check the Switch Information in the Feature Reports of the
Sysops Utilities.
2. The switch was not configured to allow logon from the IP address of the server or the logon
parameters defined on the switch do not match the ones defined on the server.
The switch may not be configured to accept a connection from the IP address of the server or the IP Address of the ELAN is not
correct in the Registry.
1. The logon parameters may be incorrect. Check the Switch Information in the Feature Reports of the Sysops Utilities.
2. The switch may not be configured to allow logon from the ELAN IP address of the server, or the logon parameters defined on
the switch do not match the ones defined on the server.
3. The switch may have a software load that is incompatible with Contact Center Manager Server.
4. The switch may have a problem.
No action required. This is a normal operating condition.
No action required. The server will attempt to re-establish the connection.
Check the LAN connections (one may be broken). A network segment may have lost power.
No action required. The server should be able to re-establish the connection quickly.
Verify the dongle is properly installed and is the correct dongle.
Make sure there is sufficient disk space for logging of trace files.
1. Take the necessary action to bring the connection up.

2. Check the physical connection of the ELAN.
A listening port conflict may have occurred. Ensure that no other program is using the same port.
Reboot the server.

Check the operational status of the IVR system. It may be down.
1. Ensure this port/DN has been properly configured on the Voice Ports administration window.
2. Ensure the TAPI communication module configuration file for the IVR system is correct.
3. Ensure the order of the DNs matches the reported Voice Ports and Position IDs .
Ensure the voice session script for the IVR system does not allow more than 128 bytes to be collected.
To prevent calls from defaulting, the number of calls queued against the CDNs
must be reduced. This can be achieved by increasing the number of logged on
agents or by treating calls differently in the call scripts. This may also point to a
call center overload situation or some other service anomaly; service should return
to normal after the event.
This is for informational purposes only and requires no action.
Change the password by either logging on to the mailbox through the Meridian Mail VM voice service or through the Meridian
Mail administration screen. After making the change on Meridian Mail, make the change in the IVR ACD-DN client application
under the File > Global Settings window.
Ensure that the CCMS and switch link is up and that CSLPOLL is turned ON.
The server will attempt to re-establish the connection. Monitor SMONW to ensure that the system recovers. Perform a PING to
confirm connectivity between the switch and CCMS. If the PING fails, check cable connections. Check if TSM, ASM, and TFE
are UP. If applicable, check if VSM and MLSM are UP.
None required.
None required.
If calls continue to be defaulted, note any error codes or messages and contact your Customer Support Representative and
your switch administrator.
Contact your Customer Support Representative and your switch administrator.
None required.
Make sure that sufficient disk space exists for logging of trace files.
Modify the server directory path to include nioamisapi.dll. The correct location for nioamisapi.dll is D:\Nortel\iccm\bin.
1. Modify the server directory path to include nioamisapi.dll. The correct location for nioamisapi.dll is
D:\Nortel\iccm\bin.
2. Restart the RSM service.
Make sure you have the valid keycode for RSM or contact your Customer Support Representative to obtain a valid keycode.

While the NCC is in configuration mode, data is not synchronized between the NCC and the Contact Center Manager Servers.
Taking the NCC out of configuration mode synchronizes the NCC with the Contact Center Manager Servers. This can only be
done at the NCC server.
Manually restart the service. If the service cannot be restarted, try rebooting the server.
Manually restart the service. If the service cannot be restarted, try rebooting the server.
If known, manually restart the affected client component/service. Otherwise restart the client. Note any error codes and
messages and contact your Customer Support Representative.
Note any error codes and messages and contact your Customer Support Representative.
No action is required if the service startup was expected (for example, if the service was previously stopped for a known
reason). If the service started unexpectedly, note any related error codes and messages and contact your Customer Support
Representative.
reason). If a service started unexpectedly, note any related error codes and messages and contact your Customer Support
Representative.
reason). If a service started unexpectedly, note any related error codes and messages and contact your Customer Support
Representative.
Representative.
Representative.
Representative.
Representative.
Representative.
Representative.
Representative.
Representative.
Representative.
Representative.
Representative.
Representative.
Representative.
Representative.
Representative.
Representative.
Representative.
Representative.
Representative.
Representative.
Representative.
Representative.
Representative.
Representative.
Representative.
Representative.
No action is required if the service stop was expected (for example, if the service was deliberately stopped using the Windows
Service Control Manager). Otherwise, use the Windows Service Control Manager to attempt to restart the service named in the
event text. Note any related error codes and messages and contact your Customer Support Representative.
Check the OAM logs.
Check the OAM logs.
Audit message. No action required.






Use the PING utility to check that the server is connected to the LAN. Make sure that all system services are up and running.
Ensure that NGEN is up. Go to the Services Manager and check that MAS Configuration Manager and
MAS OM Server are up. If these are not up, activate them by selecting the Start button for the
particular service.
If this security failure occurs frequently, notify your Customer Support representative.
Ensure client and server are properly connected. Make sure that both the clients and the server are connected to the LAN by
using the PING utility.
Ensure that report listener (nicrlstn.exe) is running on the client.

This problem may be caused by insufficient hard disk space. If this is the case, delete unnecessary files, and then stop and
restart HDC from the Service Control Manager.
Information only. No action required.
This event indicates a start-up problem. Check the following:

1. In the Services control panel, verify that the SDMCA_Service is running.
2. If the service is not running, start SDMCA.
3. Check if the RDC component starts up.
4. If RDC does not start up, start the RDC service manually in the Services control panel.
5. If the problem persists, note any error codes and messages and contact your Customer Support
Representative.

1. In the Services control panel, verify that the SDMCA_Service is running.
2. If the service is not running, start SDMCA.
3. Check if the RDC component starts up.
4. If RDC does not start up, start the RDC service manually in the Services control panel.
Representative.

1. In the Services control panel, verify that the EB_Service is running.
2. If the service is not running, start EB.
3. Restart the RDC component and check that no further event errors are flagged.
Representative.

1. In the Services control panel, verify that the DP (SDP_Service) is running.
2. If the service is not running, start DP. If the service is running, restart DP.
3. If you still cannot connect with DP, restart RDC.
Representative.
This error indicates a start-up problem. Check the following:

1. In the Services control panel, verify that the DP (SDP_Service) is running.
2. If the service is not running, start DP. If the service is running, restart DP.
3. If still unable to send data to DP, restart RDC.
Representative.
Note any error codes and messages and contact your Customer Support representative.
To ensure that call processing has enough system resources, close any non-call processing services that are not essential to
the operation of the server.
Ensure that RDC is up and running. To ensure that call processing has enough system resources, close any non-call
processing services that are not essential to the operation of the server.
Try to restart DP. If the problem persists, reboot the server.

Make sure that sufficient disk space is made available for logging of trace files.
1. Gather the HDM logs. Collect the following HDM log files from the directory <InstallDir>:\Nortel\Logs\CCMS:
• CCMS_HDMCACHE*.log
• CCMS_HDM*.txt
2. If HDM is not running, start HDM.
3. If the problem persists, note any error codes and messages, gather the relevant logs, and contact
your Customer Support representative.
• CCMS_HDM*.txt
• CCMS_HDM*.txt
• CCMS_HDM*.txt
• CCMS_HDM*.txt
• CCMS_HDM*.txt
• CCMS_HDM*.txt
• CCMS_HDM*.txt
• CCMS_HDM*.txt
• CCMS_HDM*.txt
3. Remove unnecessary files on the server.
4. Disable the NetCBC option.
• CCMS_HDM*.txt
3. There is too much NetCBC data collected. Disable collection within your client application or select
fewer applications for NetCBC.


1. In the Services control panel, verify that OAM is running.
2. If OAM is not running, start it.
3. Check if the SDM components start up.
4. If the SDM components do not start up, start them manually.
1. In the Services control panel, verify that each of the following services is running: EB, RDC, HDC.
2. If they are not running, start them manually. Start EB first, then RDC, and then HDC.
1. Check that EB is up.

2. If EB is not running, start it manually.
3. Check that RDC and HDC are up.
4. If RDC and HDC are not running, start them.
1. In the Services control panel, manually restart the SDMCA_Service.

2. After the SDMCA_Service is running, manually restart the EB, RDC, and HDC services.
Perform one or all of the following actions:
1. Use the CapTool application to make sure system resources meet software requirements.
2. Shut down other applications to free up memory.
3. Use the Services control panel to restart ASM.
Note: Restarting ASM takes several minutes. During this down time, agents cannot receive CCMS calls.
1. Verify that the TN status on the switch matches that of CCMS.
2. Ping the switch to check the connection.
Perform one or all of the following actions. If the problem persists, note any error codes, messages, and system information and
contact your Customer Support Representative.
1. Check the connection between CCMS and the switch.
2. Attempt to deacquire the TN again.
3. Delete the TN on the switch and add it back into the switch configuration.
Perform one or all of the following actions:

1. Try to acquire and then deacquire the TN.
2. Delete and reconfigure the TN the agent is trying to log on to.
3. Delete and reconfigure the agent.
4. Restart ASM. TFE automatically stops when ASM stops. Manually restart TFE after ASM restarts.
1. Check in the User Application to make sure that the supervisor position ID of the agent logging on is
valid.
2. Check in the User Application to make sure that the supervisor AGT key of the agent logging on is
valid.
1. Make sure the agent has a valid Login ID.

2. Make sure the TN is valid.
3. Make sure the agent is not already logged on to another phoneset.
4. Make sure the agent position ID is not already in use.
Check the following:
1. The DN for this set has been acquired.
2. The agent has successfully logged on to a phoneset.
3. The Call Forward feature is enabled.
Perform one or all of the following:

1. Make sure the DN is valid.
2. Log the agent off, delete the DN, add it back, and try again.
Perform one or all of the following actions. If the problem persists, note any error codes, messages, and system information and
contact your Customer Support representative.
1. Make sure all CCMS components are up and running properly.
2. Restart ASM. TFE automatically stops when ASM stops. Manually restart TFE after ASM restarts.
Note: Restarting ASM or the CCMS server takes several minutes. During this down time, the agents cannot receive CCMS
calls.
ASM will restart itself. If not, restart ASM. If this does not resolve the problem, reboot the server.
Warning: If you reboot the server, no call processing can be performed by CCMS during the process. If the problem persists,
ensure that the CCMS is installed properly (try reinstalling the server). If the problem still persists, note any error codes and
messages and contact your Customer Support representative.
Ensure that sufficient disk space is available for the logging of trace files.
Verify the server and switch connections. Make sure the DN is valid on an AST set or a phantom DN and try again. Note any
error codes and messages and contact your Customer Support representative.
Check if TSM is up. ASM will attempt to register to TSM again. If the problem persists, contact your Customer Support
representative.

Try one or all of the following to recover.

For cause ID 112, 113:
1. Reinstall the language data files.
2. Restart ASM (and necessarily, TFE). Warning: If you perform this step, agents cannot take CDN calls during the process.
For cause ID 114:
1. Delete the agent's configuration from CCMS and re-enter it.
2. Try to log the agent on again.
Manually inspect the .txt files in the \Nortel\iccm\data directory for any apparent errors. Attempt to restore the files if they are
corrupted or incorrect.
Ensure that the skillset is configured correctly and is in service. If the problem persists, contact a member of the Customer
Support team.
Ensure that the Intrinsic server is running correctly from both the SMonW window and the Services window in the Control
Panel. If necessary, restart the service. If this does not resolve the problem, contact a member of the Customer Support team.
Ensure that the DQM ACD-DN is a valid ACD-DN. See the Agent Profile page in CCMA for reason of failure.
1. Ensure the following services are up and running:

• NIMSM
• NBMSM
• CMFOAM
2. Deacquire and reacquire the pad in CCMA.

Check that TSM is up. ASM will attempt to register to TSM and reacquire all resources. If the problem persists, contact your
distributor.
TFE should recover from this error. From the Service Monitor window, ensure that the TFE service is in TFE_UP state. If TFE
has not recovered, reboot the server and contact your distributor.
No action required.
If this problem persists over time, ensure that the capacity of the server has been engineered correctly. Note any error codes
and messages and contact your distributor before rebooting the server.
Check for associated TSM messages. These will indicate the source of the problem.
Check for associated ASM messages. These will indicate the source of the problem.
Check for associated VSM messages. These will indicate the source of the problem.
This error is logged when there is no response from HDX. Check the "Get Automatic Response" in the HDX provider on the
server. If the problem persists, try to stop and restart the TFA service on the server in the Service Monitor window, and then
start the HDX provider. This affects all active calls communicating with HDX.
Ensure that the TFE service is running. Manually restart TFE. A server reboot may also be required. If the problem persists,
note any error codes and messages and contact your distributor.
Check the installation configuration data, make any necessary changes, and reboot the server. If the problem persists, note any
error codes and messages and contact your distributor.
TFE should recover from this error. From the Service Monitor window, ensure that the TFE service is in TFE_UP state. If TFE
has not recovered, reboot the server and contact your distributor.
1. Check that the CDN is properly configured in the client CDN window.
2. Ensure that the CDN is not being used by another server.
Check the switch for the status of CDNs.
Make sure that the installation is performed correctly.
Note any error codes and messages and contact your distributor.
This event indicates that there is a mismatch between TFE and other components. Determine if there is a recent PEP update.
Confirm that the following services are started in the Service Control Panel:
• CCMS NBMSM_Service
• CCMS OAMCMF_Service
Check if ASM and TFE are UP.
Check if the script variables are correctly defined. This event can also indicate a mismatch of third-party application (HDX) data.
Make sure the TFE service is running. If the problem persists, manually restart the TFE service.
1. Check that CDNs are properly configured in the client CDN window and that the CDN is not being
used by another server.
2. Make sure that the script does not start with a QUIT or WAIT statement as the first executable script
statement.
3. Make sure the TFE service is up.
Check the event logs on the switch.
Check the event logs on the switch.
Check the CDN display to ensure the CDN is acquired. Ensure that the CDN is not acquired by another server and try again.
Check if the TFE service is running. If the problem persists, manually restart the TFE service.
If this event is logged with an earlier event with the number 48443, when a request to another component was not properly
recorded by TFE, it can indicate a problem finding the call with the specified call ID in TFE.
Check the CDN display to ensure the CDN is acquired/deacquired. Ensure that the CDN is not acquired by another server and
try again.
Ensure that all call processing services are in the UP state and communication between TFE and other services is normal.
Check the event log for other messages indicating the source of the problem.
A missing default skillset indicates that the server was not successfully restarted or installed. The server needs to be rebooted
to have proper default configuration information.
1. Check the RAN configuration.

2. Check if the RAN provider is running.
If the problem persists over time, ensure that the capacity of the server has been engineered correctly. Note any error codes
and messages and contact your distributor.
This event may indicate a transient error. If more of these errors occur, service will be impaired. You may need to reboot the
server.
1. Make sure the ELAN cable is connected.

2. Check if the TFE service is running.
3. If the problem persists, manually restart the TFE service.
This event may indicate a synchronization issue TFE and other components. If this error persists over time, TFE or one of the
other components may need to be restarted.
This event indicates that there is a mismatch between TFE and other components. Verify that any PEPs or upgrades were
performed correctly.
Ensure that the ACD priority in the script is valid. Refer to the Scripting Guide and use the appropriate priority range.

Ensure that the delay time in the script is valid. Refer to the Scripting Guide and use the appropriate delay time.
This event indicates that there is a mismatch of events between TFE and other components. Verify that any PEPs or upgrades
were performed correctly.
This event indicates synchronization issues with services provided by the switch. If the problem persists, check the switch logs
for a service problem.
This event may indicate a synchronization issue between TFE and other components. If this error persists over time, TFE or
one of the other components may need to be restarted.
This event may indicate that a call is out of sequence. See the Event Browser for all event logs. If the problem persists, contact
your distributor.
This event may indicate that a variable reference in the call processing script is missing or not defined. Make sure all script
variables are properly defined. There may be other event logs that indicate source of the problem.
1. Make sure TFE is running.

2. Manually restart TFE.
3. If the problem persists, note any error codes and messages and contact your distributor.
Ensure that the TFE service is running. The TFE service may need to be manually restarted.
Make sure that all requested scripts are active and that no script is referring to itself.
Check that TFE and other components are running. Manually restart TFE. If the problem persists, reboot the server.
This event may indicate a mismatch between components. Ensure that software updates are performed.
This event may indicate a mismatch between components. Ensure that software updates are performed.
Determine if there are any recent PEP updates. If the problem persists, contact your distributor.
Check the CDN display for CDN types. Make sure that the CDN state is acquired before changing the CDN type and try again.
1. Ensure that TFE is running.
2. Ensure that all referred scripts are validated.
Ensure that TFE is running. Check the script output file. TFE may need to be restarted.
Determine if there are any recent PEP updates. If the problem persists, contact your distributor.
Check the CDN display for CDN states. Ensure that the CDN is not acquired by another server and try again. If this is call state
related, ensure that the call is presented to an agent/skillset.
This event indicates a mismatch between TFE and other components. Determine if there is a recent PEP update.
Ensure that the OAM service is in UP state. Restart the OAM service, and then restart the TFE service.
Ensure that the OAM service is in UP state. Restart the OAM service, and then restart the TFE service.
1. Ensure that the OAM service is in UP state.

2. Ensure the script is validated and try to activate it again.
Ensure that the OAM service is in UP state. Try to restart the TFE service and reactivate the script.
Ensure that the OAM service is in UP state. You may need to restart the TFE service.
1. Ensure that the OAM service is in UP state.

2. Ensure the script is validated and try to activate it again.
Check your script for the total number of skillsets specified.
This event indicates that another service encountered a problem. Examine the event log.
Ensure that the VSM service is in UP state. You may need to restart VSM and TFE services.
No action required.
No action required.
This problem is typically encountered on higher caller rates. If the problem persists over time, contact Product Support.
No action required.
Check the semantics of the script. Note the use of queue to skillset/agent, remove from skillset/agent, and change priority of
skillset/agent.
Check the switch logs to make sure the switch is operating correctly.
1. Ensure that the ASM and TFE services are in UP state.

2. Check scripts and skillset configuration.
3. You may need to restart ASM and TFE services.
Ensure that the ASM and TFE services are in UP state. You may need to restart ASM and TFE services.
Ensure that all services are operational. If needed, reboot the server.
1. Ensure that the ASM service is in UP state.
2. Ensure that agents and skillsets are properly defined.
1. Ensure that the ELAN cable is connected and the switch link is up.
2. In the Service Monitor, ensure that the TFE service is in TFE_UP state.
3. If the problem persists, there is a network problem. Contact your distributor.
Check the script logic and determine why the denominator of the "divide by" expression was zero. Use the "IF" statement to
check the value of the denominator before using it in the expression.
Check the server to ensure that other non-call processing services are utilizing memory. Do any necessary clean up. If the
problem persists over time, ensure that the capacity of the server is engineered correctly.
Ensure that the OAM service is in UP state. You may need to restart the OAM and TFE services.
Note the length of data passing into the script from HDX.
Ensure that the HDX application is running.
Ensure that the HDX application is running. You may need to restart TFE, HDX, and Provider Application.
1. Ensure that the HDX application is running.

2. Check the script to ensure that data sent to HDX is valid.
Ensure that the HDX application (provider) is running and Service Registration is successful.
Make sure that the Application IDs for a Send Request/Get Response statement match.
Make sure that the number of call variables in the script command is valid. For more information, refer to the Scripting Guide.
The CDN where calls arrive may not be controlled by server. Ensure that CDNs are acquired and controlled by server.
Check trunk types.
Make sure that the voice segment file of the voice segment variable in the script variables is valid.
See the Scripting Guide for reference. This should not happen.
Make sure that the Provider Register ID matches the HDX provider ID.
Make sure that the call is not already queued to the skillset. A remove from/change priority in skillset cannot be executed if the
call is not queued in the skillset. For more information, refer to the Scripting Guide.
Make sure that the caller-entered data field contains no more than 32 digits.
Make sure that caller-entered data contains no more than 10 fields.
Make sure that the caller-entered data field does not contain non-digits.
Check if TFE is up. TFE will attempt to register to TSM and reacquire all resources. If the problem persists, contact your
distributor.
Make sure that the disallowed script commands are not included in the Network_Script or its subscripts for incoming network
calls.
The server may need to be rebooted.
The TFE thread may timeout and the service restarts.
Thread polling timeout message will follow.
Check if TSM is up. TFE will attempt to register to TSM again and will attempt to restart TSM to recover.
None required.
No immediate action required.
None required.
None required.
None required.
Manually test the changes by calling a script that uses voice processing and Queue To Skillset (to present the call to an agent).
Confirm that calls are being handled as expected by voice processing, as well as skillset queuing and call presentation. If the
problem persists over time, check the Engineering Guide for the site to ensure the server capacity has been engineered
correctly.
If all of the services appear to be up and running, check on CCMS and the switch that the IVR ACD-DNs and voice ports have
all been successfully acquired. If they have been, no further action is required. If the resources have not be successfully
acquired:
1. Review all voice processing configurations to confirm the correct information has been entered.
2. Run the Voice Prompt Editor to confirm that it is operational. If it fails, run the Meridian Mail Universal
Link Monitor to confirm that the Access Link is operational.
3. Confirm that the Access Class numbers in the Meridian Mail Channel Allocation Table match the
channel numbers supplied to CCMS.
4. Confirm that the Voice Port TN lists in CCMS match those in the MM Channel Allocation Table.
5. Confirm that the Voice Port TNs have been configured properly on the switch.
Check that VSM is up and running. If it is, manually test a voice processing script to confirm that calls are being handled as
expected. If this situation persists, a capacity problem may exist. Contact your distributor for an analysis of your specific
configuration.
Check if TSM is up. VSM will attempt to register with TSM and reacquire all resources. Check that TSM and VSM services are
up and running. If the services are running, manually test the system by calling a script that uses voice processing and Queue
to Skillset (to present the call to an agent). Confirm that calls are being handled as expected by voice processing, as well as
skillset queuing and call presentation. If calls are being handled as expected, the system has automatically resolved the
problem. If voice processing is not working, confirm that the switch configuration information on the server is correct (IP
addresses, ELAN connectivity, software release numbers). If the problem occurred during a system restart or if the problem
persists, reboot the server.
Review the status of the system resources using the Voice Ports and IVR ACD-DN windows. If elements are not in Pending
status, then deacquire and reacquire each entry. If an entry remains in AcquirePending or DeacquirePending, call your
distributor and indicate the situation. They have a utility called UNPEND, which can be used to resolve this situation.
Record the error numbers and any messages. If the problem persists, contact your product vendor.
This problem can only occur while VSM is being started. Check to see that the VSM service is up and running. If it is, manually
test the system by calling a script that uses voice processing and Queue To Skillset (to present the call to an agent). Confirm
that calls are being handled as expected by voice processing, as well as skillset queuing and call presentation. If the problem
persists, check the switch configuration information on the server (switch ID number, customer number, software release
numbers, IP addresses). Also check that the server can communicate with the switch over the ELAN by pinging the switch.
1. Check that VSM is up and running.

2. Restart any services that have stopped.
3. Manually test voice processing by calling a voice processing script.
4. If the situation persists, contact your distributor for an analysis of your specific CCMS configuration.
This event typically occurs when:

1. Someone has accidentally dialed the IVR ACD-DN.
2. Voice ports are being shared with non-CCMS calls.
3. A maintenance utility (such as Meridian Mail Call Path Diagnostics) is using the voice ports.
Ensure that all voice ports and ACD queues being used are dedicated to call processing. They should not be shared with non-
CCMS calls or maintenance utilities. The event label lists the IVR ACD-DN and Originating DN. This information can be used to
try to isolate the origin of the calls.
Review the scripts being executed to see which individual Play Prompt or Give Controlled Broadcast Announcement command
exceeds the limit of 50 voice segments. Separate Give Controlled Broadcast Announcement or Play Prompt commands can be
used.
Using the file name indicated in the event label, isolate the variable that is failing. Confirm each variable is referring to real
segments by using the Voice Prompt Editor to play back the prompts being used. (Note: If you are trying to play a number,
there are no prerecorded numbers when the product is shipped. Voice prompt segments for numbers must first be recorded.)
Ensure that the voice segment is saved to the server.
Using the file name indicated in event label, isolate the variable which is failing. Confirm each variable is referring to real files by
using the Voice Prompt Editor to play back the prompts being used. (If you are trying to play a number, there are no
prerecorded numbers when the product is shipped. Voice prompt segments for numbers must first be recorded.) Ensure that
the voice segment is saved to the server.
Ensure that the correct Mailbox Number and Password are entered in the Global Settings. If the problem persists, contact a
member of the Support team.
1. Monitor the event logs for a recurrence of this message.

2. If the problem persists, a check of all physical connections between CCMS and the Voice Services
platform (CallPilot or Meridian Mail) must be carried out.
3. If the problem cannot be resolved, contact a member of the Support team.
None required.
Check if TSM is up. VSM will attempt to register with TSM and reacquire all resources. Check that TSM and VSM services are
up and running. If the services are running, manually test the system by calling a script that uses voice processing and Queue
to Skillset (to present the call to an agent). Confirm that calls are being handled as expected by voice processing, as well as
skillset queuing and call presentation. If calls are being handled as expected, the system has automatically resolved the
problem. If voice processing is not working, confirm that the switch configuration information on the server is correct (IP
addresses, ELAN connectivity, software release numbers). If the problem occurred during a system restart or if the problem
persists, reboot the server.
Not applicable.
In the Contact Center Manager Administration client application, use the Network Communication Parameters function to define
a dialable DN for the target site.
A preceding event should describe the reason the site is being filtered. After the problem causing the site to be filtered is
cleared, use the Network Communication Parameters function in the Contact Center Manager Administration client application
to stop filtering the site or wait for the filter timer to expire.
Possible reasons for the target site being filtered are D-channel down, All Trunks Busy (ATB) at the source or destination, trunk
blocked, resend timer expired (NACD error), All Landing Pads Busy at the destination, or CMF out of service on the target
node. If the problem clears itself soon after the filtering starts, consider changing the retry timer and retry count. If the problem
is cleared before the filter timer expires, use the Network Communication Parameters function in Contact Center Manager
Administrator (CCMA) to stop filtering.
Ensure that the NACD software is installed and enabled at all network sites. In the Contact Center Manager Administration
client application, use the Network Communication Parameters function to stop filtering the site after the NACD package is
enabled at the target site.
In the Contact Center Manager Administration client application, use the Network Communication Parameters function to enter
the dialable DN for the target site. If the dialable DN is correct, check that the Network CDN is successfully acquired at the
target site. If the Network CDN is acquired, check that the Network_Script is activated. If the error still occurs, call your
distributor and report the incident.
In the Contact Center Manager Administration client application, use the Network Communication Parameters function to enter
the dialable DN for the target site. If the dialable DN is correct, check that the Network CDN is successfully acquired at the
target site. If the Network CDN is acquired, check that the Network_Script is activated. If the error still occurs, call your
distributor and report the incident.
1. Ensure that the target site server is running and all services are active.
2. If the server is running, try to ping the CLAN IP address of the server. If the ping fails, there is a
network problem and you need to contact your network administrator. If the ping succeeds, use the
Network Communication Parameters function in the CCMA client application to try to stop the filtering.
1. Check that the Network_Script at the target site is active.
2. If the script is active, check that the dialable DN for the target site is correct.
3. If the dialable DN is correct, check that the Network CDN is successfully acquired at the target site.
4. If the error still occurs, call your distributor and report the incident.
Resolve the D-channel problem on the switch.
Increase the resend timer on the switch. If this error still occurs, call your distributor and report the incident.
An all trunks busy condition may indicate that the current network engineering is insufficient for the call traffic. Review the All
Trunks Busy report on the M1 to determine the frequency and duration of these events. Depending on your service
requirements, consider increasing the number of trunks.
An all trunks busy condition may indicate that the current network engineering is insufficient for the call traffic. Review the All
Trunks Busy report on the M1 to determine the frequency and duration of these events. Depending on your service
requirements, consider increasing the number of trunks.
Consider scheduling changes to routing tables to remove this site when a network skillset is scheduled to be out of service. If
the out-of-service condition is not expected, contact a supervisor at the target site to determine why there is no staffing on this
skillset.
If this condition persists, it may indicate that the call request queue size needs to be increased at the target site.
to stop filtering this site or wait for the filter timer to expire.
to stop filtering this site.
Ensure that the skillset is configured correctly and is in service. If the problem persists, contact a member of the Customer
Support team.
Modify the script so that calls are only queued to skillsets that are configured with the same option.
An All Landing Pads busy condition may indicate that the current network engineering is insufficient for the call traffic. Assuming
that Landing Pads are freed correctly after use, enough Landing Pads may not be currently configured to cope with the current
call traffic. Depending on your service requirements, consider increasing the number of Landing Pads. Remember that Landing
Pads are only required for a short time relative to the duration of the call.
Check that the DNIS Network CDN has been configured and acquired at the target node.
Check that the following services are running on the source and target nodes:
• CCMS_UNE_Service
• CCMS_MSM_Service
• CCMS_OAMCMF_Service
1. Check that there is no network congestion.

2. Check that the third-party application has enough resources to process calls.
3. The script and the third-party application must use the same application ID. Stop and restart the
third-party application, using the matching application ID, or modify the application ID in the script
(script activation is then required).
Check if TSM is up. MLSM will attempt to register with TSM again.
1. Ping the third-party application server.

2. Check that the third-party application is running.
1. Ping the third-party application server.

2. Check that the third-party application is running.
1. Check if there are any MLINK test tools running anywhere on the network connected to this instance
of MLSM. If possible, shut down the test tool.
2. Close any unnecessary third-party applications.
Check if TSM is up. MLSM will attempt to register with TSM again.
Obtain the necessary CCMS MLSM DN license.
Obtain the necessary CCMS MLSM ROD license.
This is a configuration data audit trail. No action is required.

This is an audit trail of configuration data being changed. No action is required.
This is an audit trail of configuration data being changed. No action is required.

1. If the communication status is set to Closed, ensure that the remote server is running and all
services are active.
2. If the server is running, try to ping the CLAN IP address of the server. If the ping fails, there is a
network problem and you need to contact your network administrator. If the ping succeeds, use the
Network Communication Parameters client to try to stop filtering.
1. Make sure that the NCC site name is entered correctly in the Network Communication Parameters.
2. If the name is specified correctly, check if the NCC is up and running.
3. If the NCC is active, try to ping the NCC CLAN IP address. If the ping fails, there is a network problem
and you need to contact your network administrator. If the ping succeeds, check all network node
addresses using the Configuration utility available on the server.
This is a communication status message. No action is required.
This is a communication status message. No action is required.
Check if the backup account has write permission to the remote network. Restart the database backup.
Check that the location of niebprxy.dll is included in the server directory path.
Check the NT services to ensure that the Event Broker service is active. If it is not active, start the Event Broker service.
If the Event Broker service is active, stop and restart the service.
Check the NT services to ensure that the Event Broker service is active. If it is not active, start the Event Broker service.
If the Event Broker service is active, stop and restart the service.
Check that the TFE Service is started. Contact support.
Contact support.
Note the error code returned and contact support.
Check the amount of free memory on the machine. Memory may be running low.
Restart the HAI Service.
Note any error codes or messages and contact your Customer Support Representative.


Run CCMS Server Setup Configuration and configure the CCMS package.
Run CCMS Server Setup Configuration and complete CCMS configuration.
Run CCMS Server Setup Configuration and complete CCMS configuration.
Wait until the CCMS services have shut down and start the Control Service again.
Restart the License Manager server, and then restart CCMS.
Restart the License Manager server, and then restart CCMS.
1. Run the Server Setup Configuration utility and configure the server with a valid CCMS package.
2. Ensure that the License Manager contains a license for the %ads package.
Ensure that CCMS and the LM servers are connected and that the LM server service is running.
1. Run the Server Configuration utility and correct the License Manager IP address.
2. Restart CCMS.
1. Run the Server Setup Configuration utility and configure the server with a valid CCMS package.
2. Ensure that the License Manager contains a license for the %ads package.
The grace period is reset when communication is restored. Ensure that the License Manager service is running. Verify the
network connection between CCMS and the LM servers.
Configure the License Manager with a license file that contains the Warm Standby license.
1. Restart the CCMS OAMCMF_SERVICE.

2. If the problem persists, restart the server.
3. Contact your Customer Support representative with the cmfoam.log file.



1. Verify the Windows NT registry entries for the service are correctly entered by using the Windows
NT registry editor. For information about these entries, consult your CCMS documentation.
NT registry editor. For information about these entries, consult your CCMS documentation.
NT registry editor. For information about these entries, consult your CCMS documentation. Look under
HKEY_LOCAL_MACHINE\SOFTWARE\Nortel\Setup\Switch.















1. Check that OAM_SERVICE is running.

















































1. Check that the CCT services are running.
2. Check the configuration details entered for CCMS, CCT, and Open Queue are correct.
1. Check that the account the Niprotam service runs under has sufficient permissions.
2. Contact your Customer Support representative.
Ensure that the processTasks.xml file is in the \Nortel\iccm\bin\ folder and that the Niprotam service has sufficient security
permissions to access the file.
Ensure that the CCMonitorService.exe configuration file is present in the \Nortel\iccm\bin\ folder.
1. Check that the account the Niprotam service runs under has sufficient permissions.
2. Contact your Customer Support representative.
None required.
None required.
None required.
None required.
None required.
Restart the Niprotam service.
None required.
None required.
None required.
None required.
Use Task Manager to reset the priority of the affected process.
Check the log files to clarify the problem.
None.
Ensure that the archive location is accessible and that the Log Archiver has permission to write to it.
None.
Ensure the Log Archiver service has sufficient permissions to delete files at the archive location. Revise the disk usage limits
and consider manual deletion of files to free up space.
Ensure that the archive location is accessible and the Log Archiver service has permission to write to it. Review disk usage
limits and the amount of free space available at the archive location.
If circular archiving is not enabled, consider enabling it. Review archive location and disk usage settings. Consider manually
freeing disk space at the archive location.
Consider manual deletion of archive files that are left in the Log Archiver directory.
Ensure that the Log Archiver configuration file exists and has valid entries. Consider using the Log Archiver user interface to
regenerate the configuration file.
This event may indicate a deeper problem with the Log Archiver configuration. Review the configuration file to ensure it is
correct. Consider using the Log Archiver user interface to regenerate the configuration file.
If the disk usage limits are badly set or the archive location is on a small disk, this deletion may not be sufficient to ensure that
archiving continues. Consider reviewing the archive location and disk usage limits, or manually freeing space at the archive
location.
Restart the service. Examine the log files to trace the root cause of the error.
Examine the rate of logging on the system and the rule set that is being used with Log Archiver.
None.
None.
Not applicable.
Not applicable.
Use the CC SCMU and the Windows Services Control Manager to check the service states.
Use the CC SCMU and the Windows Services Control Manager to check the service states.
Ensure the XML file (SCMUConfig.xml) is present in D:\Nortel\iccm\bin. Ensure it is not corrupt.
Ensure the XML file (SCMUConfig.xml), in D:\Nortel\iccm\bin has sufficient access permissions.
This event indicates an operating system error. Try restarting the server.
This is for informational purposes and requires action to investigate why the switchover did not occur.
The CCMS administrator must ensure the switch connectivity is ok to avoid this event. If this event occurs, make sure the
alternative switch is accessible to CCMS. This event occurs only if an alternative switch IP address is configured on CCMS.
The CCMS administrator must ensure the switch connectivity is ok to avoid this event. If this event occurs, make sure the
alternative switch is accessible to CCMS. This event occurs only if an alternative switch IP address is configured on CCMS.
Verify the switchover occurs correctly, the standby CCMS becomes active, and the call processing services are up and running
on the standby server after the switchover.
Verify why the restart of the affected call processing service did not work in the previous monitoring cycles.
Verify why the restart of the affected call processing service did not work in the previous monitoring cycles.
Verify switch connectivity and if configuration issues exist with the call processing services.
Verify switch connectivity and if configuration issues exist with the call processing services. If this service cannot be stopped or
started manually, reboot the CCMS.
If service monitoring does not restart, contact Nortel Customer Support.
Check the ODBC DSN CCMS_CACHE_DSN exists and is set to connect to the CCMS_STAT namespace (perform a test
connection).
Contact Nortel Customer Support.
Restart the CCMS Control service (this will restart CCMS services).
connection).
connection).
Check that the switch IP registry and Service Monitor registry is accessible (regedit).
connection).
connection).
Check Control Panel, Services to see if the service is stopped.
Try running the affected service manually or run iccmSU.exe.
1. Check whether the MLSM log file is locked by another program.

2. Ensure sufficient disk space exists on the hard drive.
Recovery
Action
Contact Center Manager Administration event
Event
Number
Source Severity Description
101 CCMA Major Registry key \SOFTWARE\Nortel\RTD cannot be created
or opened!
102 CCMA Major Registry value

\SOFTWARE\Nortel\RTD\Transform Rate cannot be
read!
103 CCMA Major Registry value \SOFTWARE\Nortel\RTD\Output Rate

cannot be read!
104 CCMA Major Registry value \Software\Nortel\RTD\IP Receive cannot

be read!
105 CCMA Major Registry value \Software\Nortel\RTD\IP Receive cannot

be written!
106 CCMA Major Registry value \Software\Nortel\RTD\IP Send cannot be

written!
107 CCMA Major Registry value \Software\Nortel\RTD\Transform Rate

cannot be written!
108 CCMA Major Registry value \Software\Nortel\RTD\Output Rate cannot
be written!
109 CCMA Major Registry value \Software\Nortel\RTD\IP Send cannot be

read!
110 CCMA Major Registry value \Software\Nortel\RTD\OAM Timeout

cannot be written!
111 CCMA Major Registry value \Software\Nortel\RTD\OAM Timeout

cannot be read!
112 CCMA Major Registry value \Software\Nortel\RTD\Transmission Option

cannot be written!
113 CCMA Major Registry value \Software\Nortel\RTD\Transmission Option

cannot be read!
114 CCMA Warning Unicast realtime data transmission is not supported from
this server.
115 CCMA Information A unicast connection with this client already exists for
statistic type %1.
116 CCMA Minor The IP address %1 for stat %2 could not be stored.
Unicast connection cannot be established.
117 CCMA Major Error establishing unicast socket, could not bind to the
socket.
118 CCMA Major Error establishing unicast socket, the socket could not be
created.
119 CCMA Major Registry value \Software\Nortel\RTD\Max Unicast

Sessions cannot be written!
120 CCMA Major Registry value \Software\Nortel\RTD\Max Unicast

Sessions cannot be read!
121 CCMA Major Registry value \Software\Nortel\RTD\Compression cannot

be written!
122 CCMA Major Registry value \Software\Nortel\RTD\Compression cannot

be read!
123 CCMA Major %1 unicast sessions open, no further sessions available.

%nThis value may be increased through the RTR
settings.
124 CCMA Major The IP address %1!s! for stat %2 could not be stored in
the timestamp map. Unicast connection not established.
125 CCMA Major Registry value \Software\Nortel\RTD\Multicast Filter

cannot be written!
126 CCMA Major Registry value \Software\Nortel\RTD\Multicast Filter

cannot be read!
140 CCMA Major Socket "select" in receiver thread failed %1
141 CCMA Major HELLO Message Timeout. Haven't heard from IP %1!s!
stat %2!s! for more than 5 minutes. Closing connection.
142 CCMA Information RTI Login successful: IP = xxx.xxx.xxx.xxx
143 CCMA Major RTI Login failed: IP = xxx.xxx.xxx.xxx
150 CCMA Major Socket initialization failed.
151 CCMA Major Request failed! Host is down or nbnmsrvc.exe is not

running. Error code %1!s!.
152 CCMA Minor OAM Error! Error code %1!s!.

153 CCMA Major Host %1!s! not found! %nError resolving host name to IP
address.
154 CCMA Minor %1!s!: Socket error %2!s!.
155 CCMA Minor Registry value \\Software\\Nortel\\RTD\\NCC Server

cannot be read or written!
156 CCMA Minor Registry value \\Software\\Nortel\\Wclient_path cannot be

read or write!
157 CCMA Minor Registry key \\Software\\Nortel\\Wclient cannot be

opened!
159 CCMA Minor Host name parameter is missing or empty in call to

function.
160 CCMA Minor Registry key \\Software\\Nortel\\EmergencyHelp cannot

be opened!
161 CCMA Minor Invalid registry key name was passed!
162 CCMA Major %1!s! error: %2!s!.\nHost: %3!s!.\nIP Address: %4!

s!.\nNote: SCCS 4.0 servers do not support that function
200 CCMA Information System Error Detail = %1!s!

201 CCMA Information Generic Error Detail = %1!s!
500 CCMA Information %1!s!

1000 CCMA Minor ICESocket Exception: %1!s!
1000 ICEEmHlp Information lists successfully and unsuccessfully refreshed servers

Service
1100 CCMA Major Message registration Send failed with %1!s! %nMessage:
%2!s! %nChannel: %3!s! %nStatus=%4 %nchName=%5!
s! %naddress=%6!s!
1101 CCMA Information Message registration passed with %1!s! %nMessage:

%2!s! %nChannel: %3!s! %nchannelName = %4!s!
%address = %5!s! %n
1102 CCMA Major Message registration Connect failed with %1!s!

%nMessage: %2!s! %nChannel: %3!s! %nStatus=%4
%nchName=%5!s! %naddress=%6!s!
1103 CCMA Major Message Re-Registration Send failed with %1!s!

%nChannel %2!s! %nstatus = %3 %nchannel name =
%4!s! %naddress = %5!s!
1104 CCMA Information Message Re-Registration passed with %1!s! %nChannel:

%2!s! %nchannel Name = %3!s! %address = %4!s!
1105 CCMA Major Message Re-Registration Connect Failed with %1!s!
%nChannel: %2!s! %nstatus=%3 %nchannel name=%4!
s! %naddress=%5!s!
1106 CCMA Major Cannot find server name for the site %1!s!
1107 CCMA Major Cannot find host %1!s! address

1108 CCMA Minor ePerform NIOAM_dwUserGet error: %1
1109 CCMA Minor %1!s! %nError: %2. %nHost: %3!s!. %nIP Address: %4!s!
2000 CCMA Information Generic OAM Error: %1!s!
7031 Service Control Critical ISS Service failure.

Manager The World Wide Web Publishing Service service
terminated unexpectedly.
7031 Service Control Critical ISS Service failure.
Manager The ISS Admin Service service terminated unexpectedly.
7031 Service Control Critical ADAM Service failure.

Manager The Symposium WC Service terminated unexpectedly.
7031 Service Control Major Real Time Information Service failure.

Manager The IceRTDService service terminated unexpectedly.
7031 Service Control Major ICE Assignment Service failure.

Manager The ICE Assignment Service terminated unexpectedly.
7031 Service Control Major Emergency Help Service failure.

Manager The IceEmHlpService terminated unexpectedly.
7031 Service Control Major License Manager Service failure.

Manager The CCMA LMService service terminated unexpectedly.
8000 NTBackup Information The backup begins.

8001 NTBackup Information The backup ends.
8008 NTBackup Information The ntbackup begins verification.
8009 NTBackup Information The ntbackup ends verification.
8018 NTBackup Information The ntbackup begins operation.
8019 NTBackup Information The ntbackup ends operation.
61600 CCMA- Major License Manager Interface initialization failed: <Error
LMService code/description>
61601 CCMA- Informational License Manager Interface initialization successful.

LMService
61602 CCMA- Minor Request for license denied:
LMService Error: <ErrorDescription>, License Type: <LicenseType>
UserID: <UserID:ClientIP>
61603 CCMA- Informational Request for license granted:

LMService License Type: <LicenseType> UserID: <UserID:ClientIP>
61604 CCMA- Minor The license obtained by the user cannot be released
LMService because the license is tagged as invalid by the License
Manager interface: License Type: <LicenseType>
UserID: <UserID:ClientIP>
61605 CCMA- Informational Release of license successful: License

LMService Type: <LicenseType> UserID: <UserID:ClientIP>
61606 CCMA- Minor The license for License Type: <LicenseType> UserID:
LMService <UserID:ClientIP> could not be refreshed by the LM
interface.
61607 CCMA- Informational Communication re-established with License Manager
LMService server after a communication error.
61608 CCMA- Major Communication error with the License Manager server.
LMService Grace period value: 10 days
The cumulative duration of the grace periods cannot
exceed 10 days.
61609 CCMA- Major Grace period has expired. The CCMA LM Service is
LMService shutting down and no new licenses can be opened.
61610 CCMA- Minor There is an error writing the persistent license usage data
LMService to CCMA database (ADAM): License Type:
<LicenseType>
61611 CCMA- Informational License Manager interface has successfully logged the
LMService persistent RCW license usage data to CCMA database
(ADAM).
61612 CCMA- Minor There is an error reading the persistent license usage
LMService data from the CCMA database (ADAM) at the startup of
CCMA LM Service.
61613 CCMA- Informational License manager interface has successfully retrieved the
LMService persistent license usage data from CCMA database
(ADAM) at the startup of CCMA LMService:
<LicenseType> Max Usage: <number>
61614 CCMA- Minor There is an error parsing the XML object while reading
LMService the persistent license usage data from the CCMA
database (ADAM) at the startup of CCMA LMService:
<Error Description>
61615 CCMA- Minor Unable to write to the Audit Trail due to unregistered
LMService WCLIENTAUDITTRAIL.DLL:
Cannot log Audit Trail event ID: <Impacted Audit Event>
61616 CCMA- Major An error was encountered by CCMA LMService while

LMService logging to Windows event logs due to the following
reasons:
1. Unregistered Logger.dll
2. There is a Windows related issue with Windows event
log.
61617 CCMA- Major There is an error encountered reading the LMService

LMService registry entries by CCMA LMService at the startup:
<registry value> Return Code: <ErrorCode>
61618 CCMA- Informational CCMA LM Service startup - No registry update required

LMService for a Co-res server
61619 CCMA- Informational LM Service - Updated HKLM\Nortel\LM\Type registry
LMService value to <NODAL or CORP> Return Code: <return code>
at the CCMA LMService startup
61620 CCMA- Major An error was encountered updating the

LMService HKLM\Nortel\LM\Type registry value to <NODAL or
CORP> at the CCMA LMService startup
61621 CCMA- Informational CCMA LMService started.

LMService
61622 CCMA- Informational CCMA LM Service Stopped/Shutdown. All active CCMA
LMService LM Service active licenses will be released.
61623 CCMA- Major An error was encountered while adding or updating to the
LMService list of active licenses into the CCMA LMService cache.
61624 CCMA- Major An error was encountered while reading the list of active
LMService licenses from the CCMA LMService cache.
61625 CCMA- Major An error was encountered while deleting the granted
LMService license list in CCMA LMService cache upon shutdown or
normal license release.
61700 CCMA-HistRpt Info The RptAdmin.exe process has started.
61701 CCMA-HistRpt Major Error starting RptAdmin.exe process:

<Error Description>
61702 CCMA-HistRpt Major Cannot setup scheduled reports to use Domain Account:
<Domain Account>
because domain is either invalid or the CCMA server is
not configured for this domain.
The local iceAdmin account will be used.
61703 CCMA-HistRpt Warning Resetting scheduled report credentials in MS Task

Scheduler from:
<PrevAccount> to <NewAccount>
61704 CCMA-HistRpt Major There is an error resetting scheduled report credentials in

MS Task Scheduler from:
<PreviousAccount> to <NewAccount>.
<Error Description>.
61705 CCMA-HistRpt Info The scheduled report was run successfully.

Report Name: <ReportName>
Job ID: <JobID>
Owner: <User Name>
Server: <ServerName or IP>
Printer: <Printer Name>
Export Destination: <ExportFileName>
Status Email: <EmailAddress>
61706 CCMA-HistRpt Minor The scheduled report was run with errors:
Report Name: <Report Name>.
Job ID: <Job ID>.
Owner: <UserName>.
Server: <Server Name or IP>.
Printer Status: <Status> - <Printer Name>.
Export Destination: <Status> - <Export File Name>.
Status Email: <Status> - <Email Addresses>.
61707 CCMA-HistRpt Major The scheduled report failed to run:
Report Name: <Report Name>.
Job ID: <Job ID>.
Owner: <User Name>.
Server: <Server Name or IP>.
Error: <Error Description>.
61708 CCMA-HistRpt Major The RptAdmin.EXE process failed to execute the

scheduled report(s) in the report queue.
Error: <Error Description>

ger Administration event codes
Probable Recovery
Impact Cause Action
Real-time displays do not have data as no data is received from the
CCMS/SCCS servers.
Real-time display may not refresh at the rate expected. The default
value for Transform rate is used.
Real-time display may not refresh at the rate expected. The default
value for the Output rate is used.

CCMS/SCCS servers. If the default IP Receive data is used on
CCMS, the real-time displays will have data.

CCMS/SCCS servers (the IP Receive address must correspond to
the CCMS multicast send address).
Real-time displays do not have data as no data is sent out from the
CCMA server. If the default send address works, then the data will
be sent out.
The rate at which the CCMA server processes the data from the
server cannot be changed in the registry. This affects the expected
refresh rate for the displays.
The rate at which the CCMA server sends out the multicast data
cannot be changed in the registry. This affects the expected refresh
rate for the displays.
Real-time displays do not have data as no data is sent from the

CCMA server. The default IP Send address is used. If this matches
the CCMS configuration, there will be data in the real-time display.
It is possible that data can be lost if the OAM timeout needed to be

increased due to a slow CCMS server or network.
The CCMA icertdservice does not use the OAM timeout value
specified by the CCMA administrator on the CCMA server.
The CCMA administrator cannot disable multicast between the

CCMA server and the client and use unicast as an alternative or
vice versa. Also unable to use Multicast and Unicast option.
The icertdservice does not know whether to use multicast or

unicast or both for transporting the data between the CCMA app
server and the client. By default, the unicast and mulicast option is
used.
If the Transmission Option is set to Unicast, no data is sent from the

CCMA server. If the option is set to Multicast and Unicast,
multicast is used to send the data to the clients.
Another unicast session will not be opened. Existing unicast

session is used.
If the Tranmission Option is set to Unicast, no data is sent from the
CCMA server. If the option is set to Multicast and Unicast, multicast
is used to send the data to the clients.
is used to send out the data to the clients.

The limit of active unicast sessions cannot be changed.
Icertdservice does not know the upper limit of unicast sessions that
are allowed to be active. The default value of 30 unicast sessions is
used.
Unable to modify whether compression between the client and

CCMA is turned on or off.
The data transferring between the client and CCMA will not be
compressed as unable to read data from registry.
No more unicast sessions allowed. Some clients will not see any
real-time data.
There is no visible impact with the RTDs, but more data is being
sent on network than required. The ability to receive/not receive
data from only the servers configured on the CCMA does not exist.
Data is processed and sent from CCMA for all CCMS servers on
the network that have a multicast send address that is the same as
the CCMA receive address. Using multicast filtering, only the data
for the servers configured on CCMA is processed and sent out.
No data appears in the real-time displays as no data is received

from the CCMS server.
The unicast client session timed out and closed down. No further
unicast data is sent to the client.
RTI login for CCMS server xxx.xxx.xxx.xxx used for transmission on

unicast real-time data between CCMS and CCMA was successful.
RTI login for CCMS server xxx.xxx.xxx.xxx used for transmission on

unicast real-time data between CCMS and CCMA failed. Unicast
real-time data is not transmitted between CCMS and CCMA using
the RTI API.
No data appears in the real-time displays as no data is received

from the CCMS server.
OAM Error. No real-time data received from the CCMS server.
No real-time data received from the CCMS server. The RTD cache
is not updated.
No real-time data received from CCMS server.
No data received from the NCC.
No real-time data received.
No real-time data received.
No real-time data received from the CCMS server.
OAM Error. No real-time data received from CCMS server.

No real-time data received from the CCMS server. No real time

data is displayed on the client.
Connection cannot be re-established with the CCMS server to

receive multicast data. No data is received by CCMA and hence no
data is sent out for that particular CCMS server. As a result, the
real-time displays for that CCMS server do not work. RTD Cache
data is affected.
Real time display will work as expected.

data is affected.

data is affected.
Real time display will work as expected.

data is affected.


The backup started.
The backup is complete.
Verification of the backup has started.
Verification of the backup is complete.
The Backup operation is beginning.
The backup operation is complete.
1. The CCMA LM Service may not start or stop after restarting.
2. Licenses cannot be granted (for example, for RCW).
No impact.
A user was unable to get the license for the requested application
(for example, Report Creation Wizard [RCW]) as there are no
available licenses. This event can occur if there is a communication
error with the License Manager server, invalid license type stored in
the CCMA registry, not enough RCW licenses available, or the
CCMA LM Service is not starting.
The user is able to get the license to start the CCMA application
(for example, RCW). The user ID granted the license and the
license type are included in the description.
If the license is unable to be released, the maximum number of

licenses can no longer be granted.
No impact.
No impact on the existing CCMA browser session (for example,

RCW session).
No impact.
• If the CCMA LM service was running before this error, the License
Manager server will grant new licenses, up to the configured
licenses of the License Manager server at the time of the start up of
the CCMA LM Service, until the grace period expires.
• If the CCMA LM service is restarted during the grace period, any
new sessions requiring a license (for example, RCW) cannot be
started until communication is re-established with License Manager
Server.
• If the grace period expires before communication with the
License Manager server is re-established, new sessions requiring
a license cannot be started.
New sessions requiring a license (for example, RCW) cannot be
opened.
No impact.
No impact.
No impact on granting/releasing the licenses (for example, for

RCW sessions).
No impact.
No impact on granting/releasing the licenses (for example, for

RCW sessions).
No impact on grant/release of licenses e.g. for RCW sessions.

Audit Trail is not updated.
No impact on grant/release of licenses e.g. for RCW sessions.

Note: LM Service events are not logged to Windows event logs.
Therefore, this event will be written to the LMService.log. Check the
LMService.log under Nortel_Log directory.
CCMA LM Service may not grant licenses (for example, RCW

session can not be started and the CCMA LMService may fail to
start).
No impact.
No impact.
Note: This event will be raised only on a standalone CCMA server.
CCMA LM Service will not grant licenses (for example, RCW

session can not be started and the CCMA LMService may fail to
start).
No impact.
Upon shutdown of CCMA Server or stop of CCMA LM Service on

CCMA, the CCMA LM Service releases all the existing open
licenses. Example: The opened RCW sessions will continue to be
active and users can continue with their existing RCW session to
save/update the RCW reports. Also, when the existing RCW
browser session is closed, the event ID: 61603 will not be recorded
at the time of close of the RCW session, because the LM Service
has already released the license and recorded the event 61603
upon shutdown.
CCMA LMService may abruptly stop or may not grant any new
licenses (for example, new RCW session cannot be opened).
Informational message
The scheduled reports will not run.

The scheduled report export to the domain network PC may fail
due to permission issues on the domain PC.
The scheduled report export to the domain network PC may fail

due to permission issues on the domain PC.
The existing scheduled jobs may not run due to failure of changing
the account credentials for the existing job in the MS Task
Scheduler.
The scheduled report was run.

Note: This event will be generated for all scheduled reports that are
run successfully. It may potentially fill up the Windows application
event log on the CCMA server. Therefore, ensure that application
event log size is large enough to log such informational events.
The scheduled report run did not print, export, or send the e-mail
notification. There were errors when running this scheduled report:
1. Report printing to the assigned printer failed.
2. Report export to a destination file failed.
3. Cannot send e-mail to the assigned e-mail address.
The affected scheduled report failed to run. Error description
associated with this event provides more details about the root
cause (for example, error returned from a function or dependent
.dll).
The rptAdmin.exe process that runs all of the scheduled reports,

encountered problems processing the scheduled jobs. This is a
major error and shows that all or some of the scheduled reports
cannot be run.
License Manager event codes
Event
61100 LM Minor CC License Manager Startup
61101 LM Minor CC License Manager is

Standby Server
61102 LM Minor CC License Manager is Active

Server
61103 LM Major CC License Manager switching

to Active Server
61104 LM Major CC License Manager switching

to Standby Server
61105 LM Major CC License Manager shutting

down
61106 LM Critical CC License Manager failed
start-up due to invalid license
identifier
61107 LM Minor CC License Manager Standby

Server detected
61108 LM Critical CC License Manager failed

start-up. Check LM server log
file.
61109 LM Major CC License Manager
connection to database fails.
61110 LM Major License returned to pool

because it was not refreshed.
Check LM server log file.
61111 LM Major License refresh failed because

license has expired. Check LM
server log file.
61112 LM Major License not granted because

max exceeded. Check LM
server log file.

no license. Check LM server
log file.
license has expired. Check LM
server log file.
61150 LM Critical %nvs, In Grace Period, Time

Remaining = %np1 days,
%np2 hours of 10 days Code =
%ads
61151 LM Major %nvs, Error Condition

detected, Lock Code = %ads
61152 LM Minor Error condition resolved for

Client %nvs
61153 LM Minor %nvs, Not in Grace Period,
%ads
61154 LM Critical %nvs, Fatal Error in License

Refresh, Grace Period expired,
Lock Code = %ads
61155 LM Minor Client %nvs: Resetting the

Grace Period to 10 days
61156 LM Minor Client %nvs: Grace Period not

reset as invalid lock code
entered:
61157 LM Minor %nvs, Grace Period

%np2 hours
61158 LM Minor Insufficient amount of disk
space (LMConfig) for the value
configured.
61159 LM Minor Insufficient amount of disk

space (LMClient) for the value
configured.
61160 LM Critical CRITICAL: Threshold value
reached.
61161 LM Major MAJOR: License nearing

threshold.
License Manager event codes
Probable
Description Impact Cause
CC License Manager is starting up. CC License Manager is starting.
CC License Manager started as the Standby Server. CC License Manager is the Standby License Manager.
This License Manager remains as the Standby
License Manager until the Active License Manager
goes out of service.
CC License Manager started as the Active Server. CC License Manager is the Active License Manager.
This License Manager issues all licenses in the
network.
CC License Manager switched from Standby to the CC License Manager is the Active License Manager.
Active Server. This License Manager now issues all There is a problem with the previous Active License
licenses in the network. The previous Active License Manager.
Manager has gone out of service.
CC License Manager detected another Active License CC License Manager is the Active License Manager.
Manager and switches to standby mode. There is a problem with the previous Active License
Manager.
CC License Manager was signaled to stop. CC License Manager is shutting down.
CC License Manager cannot start as there is no valid CC License Manager cannot start.
license identifier to verify the license file against.
CC Standby License Manager detected. Active/Standby operation commences. If the Active

License Manager goes out of service, the Standby
License Manager becomes the new Active License
Manager.
CC License Manager cannot start. Check the LM CC License Manager cannot start.
server log file.
CC License Manager cannot connect to the database. No statistics are collected.

Statistics will not be written to the database.
License returned to pool because it was not License that was available to a server has been returned.
refreshed. For more information, check the LM server Calling application may not be running.
log file.
License refresh failed because the license has License that was available to a server has been returned.
expired. For more information, check the LM server Calling application may not be running.
log file.
License not granted because maximum exceeded. No more licenses are available.
For more information, check the LM server log file.
License not granted because there is no license. For No license of that type is available.
more information, check the LM server log file.
License not granted because license has expired. For No more licenses are available.
more information, check the LM server log file.
A communication error occurred. The error code is If the grace period reaches 10 days, the application shuts
needed if you want to reset the grace period. The down. This event is fired every six hours while licenses
current length of the grace period is displayed. A are held.
maximum of 10 days is allowed. View the
troubleshooting guide to resolve the communication
error.
A communication error occurred. The error code is The application is experiencing network problems. If the
needed if you want to reset the grace period. grace period reaches 10 days, the application shuts down.
The current length of the grace period is displayed.
There is a maximum of 10 days allowed. View the
troubleshooting guide to resolve the communication
error.
The error between the License Manager and client None

was resolved.
Communication is okay. The length of time remaining If the grace period reaches 10 days, the application shuts
in the grace period is displayed. down. This event is fired every six hours while licenses
are held.
The grace period has expired due to the inability to The client application will be shut down.
communicate with the License Manager.
Grace period has been reset to 10 days. Grace period reset to 20 days.
Invalid code entered. No change to grace period.
Communication is okay. The length of time remaining If the grace period reaches 10 days, the application shuts
in the grace period is displayed. down.
logging is less: value settings to ensure there is sufficient disk space for
1. LogPath key all the logs of the service.
Logging cannot continue with the current configured
values for those keys.
logging is less: value settings to ensure there is sufficient disk space for
1. LogPath key all the logs of the service.
Logging cannot continue with the current configured
values for those keys.
Displayed is the alarm generated if the current users If current users cross the value set, the Critical Alarm is
cross the critical value set by the user. generated.
Displayed is the alarm generated if the current users If current users cross the value set, the Major Alarm is
cross the major value set by the user. generated.
Recovery
Action
Contact Center Multimedia even
Event
2000 OAM
2001 OAM 1 (most severe)
2004 OAM 1 and 6

2006 OAM
2007 OAM
2010 OAM 5
2011 OAM
2012 OAM 5
2013 OAM 5
2014 OAM 4
2015 OAM 4
2016 OAM 4
2017 OAM 5
2018 OAM 5
2019 OAM 6
2020 OAM
2021 OAM 6
2022 OAM 6
2023 OAM 6
2024 OAM 5
2025 OAM 5
2026 OAM 4
2027 OAM 4
2028 OAM 4
2029 OAM 4
2030 OAM 5
2031 OAM 5
2032 OAM 5
2033 OAM 4
2034 OAM 5
2035 OAM 4
2036 OAM 4
2037 OAM
2038 OAM 1
2039 OAM 1
2040 OAM
2041 OAM
2042 OAM 6
2043 OAM 6
2044 OAM 6
2045 OAM 3
2046 OAM 3
2047 OAM 6
2048 OAM 6
2050 OAM 5
2051 OAM 1
2052 OAM
2053 OAM
2054 OAM
2055 OAM
2056 OAM
2057 OAM
2058 OAM
2059 OAM 6
2060 OAM 6
2061 OAM
2062 OAM
2063 OAM 2
2064 OAM 1
2065 OAM 6
2066 OAM 1
2067 OAM 6
2068 OAM 4
2069 OAM 4
2070 OAM 4
2071 OAM 4
2072 OAM 4
2073 OAM 4
2074 OAM 4
2075 OAM
2076 OAM
2077 OAM
2078 OAM
2079 OAM
2080 OAM
2081 OAM
2082 OAM
2083 OAM
2084 OAM
2085 OAM
2086 OAM
2087 OAM
2088 OAM
2089 OAM
2090 OAM
2091 OAM
2092 OAM
2093 OAM
2094 OAM
2095 OAM
2096 OAM
2097 OAM
2098 OAM
2099 OAM
2100 OAM
2101 OAM
2102 OAM
2103 OAM
2104 OAM
2105 OAM
2106 OAM
2107 OAM
2108 OAM
2109 OAM
2110 OAM
2111 OAM
2112 OAM
2113 OAM
2114 OAM
2115 OAM
2116 OAM
2117 OAM
2118 OAM
2119 OAM
2120 OAM
2121 OAM
2123 OAM
2124 OAM
2125 OAM
2126 OAM
2127 OAM
2128 OAM
2129 OAM
2130 OAM
2131 OAM
2132 OAM
2134 OAM
2134 OAM
2135 OAM
2136 OAM
2137 OAM
2138 OAM
2139 OAM
2140 OAM
2141 OAM
2142 OAM
2143 OAM
2144 OAM
2145 OAM
2146 OAM
2147 OAM
2148 OAM
2149 OAM
2150 OAM
2151 OAM
2152 OAM
2153 OAM
2154 OAM
2155 OAM
2156 OAM
2157 OAM
2158 OAM
2159 OAM
2160 OAM
2161 OAM
2162 OAM
2163 OAM
2164 OAM
2165 OAM
2166 OAM
2167 OAM
2168 OAM
2169 OAM
2170 OAM
2171 OAM
2172 OAM
2173 OAM
2174 OAM
2175 OAM
2176 OAM
2177 OAM
2178 OAM
2179 OAM
2180 OAM
2181 OAM
2182 OAM
2183 OAM
2184 OAM
2185 OAM
2186 OAM
2187 OAM
2188 OAM
2189 OAM
2190 OAM
2191 OAM
2192 OAM
2193 OAM
2194 OAM
2195 OAM
2196 OAM
2197 OAM
2198 OAM
2199 OAM
2200 OAM
2201 OAM
2202 OAM
2204 OAM
2205 OAM
2206 OAM
2207 OAM
2208 OAM
2209 OAM
2210 OAM
2211 OAM
2212 OAM
2213 OAM
2214 OAM
2215 OAM
2216 OAM
2217 OAM
2218 OAM
2219 OAM
2220 OAM
2221 OAM
2222 OAM
2223 OAM
2224 OAM
2225 OAM
2226 OAM
2227 OAM
2228 OAM
2229 OAM
2230 OAM
2231 OAM
2232 OAM
2233 OAM
2234 OAM
2235 OAM
2236 OAM
2237 OAM
2238 OAM
2239 OAM
2240 OAM
2241 OAM
2242 OAM
2243 OAM
2244 OAM
2245 OAM
2246 OAM
2247 OAM
2248 OAM
2249 OAM
2250 OAM
2251 OAM
2252 OAM
2253 OAM
2254 OAM
2255 OAM
2256 OAM
2257 OAM
2258 OAM
2259 OAM
2260 OAM
2261 OAM
2262 OAM
2263 OAM
2264 OAM
2265 OAM
2266 OAM
2267 OAM
2268 OAM
2269 OAM
2270 OAM
2271 OAM
2272 OAM
2273 OAM
2275 OAM
2276 OAM
2277 OAM
2278 OAM
2279 OAM
2280 OAM
2281 OAM
2282 OAM
2283 OAM
2284 OAM
2285 OAM
2286 OAM
2287 OAM
2288 OAM
2289 OAM
2290 OAM
2291 OAM
2292 OAM
2293 OAM
2294 OAM
2295 OAM
2296 OAM
2297 OAM
2298 OAM
2299 OAM
2300 OAM
2301 OAM
2302 OAM
2303 OAM
2304 OAM
2305 OAM
2306 OAM
2307 OAM
2308 OAM
2309 OAM
2310 OAM
2311 OAM
2312 OAM
2313 OAM
2314 OAM
2315 OAM
2316 OAM
2317 OAM
2318 OAM
2319 OAM
2320 OAM
2321 OAM
2322 OAM
2323 OAM
2324 OAM
2325 OAM
2326 OAM
2327 OAM
2328 OAM
2329 OAM
2330 OAM
2331 OAM
2332 OAM
2333 OAM
2334 OAM
2335 OAM
2336 OAM
2337 OAM
2338 OAM
2339 OAM
2340 OAM
2341 OAM
2342 OAM
2343 OAM
2344 OAM
2346 OAM
2347 OAM
2348 OAM
2349 OAM
2350 OAM
2351 OAM
2352 OAM
2353 OAM
2354 OAM
2355 OAM
2356 OAM
2357 OAM
2358 OAM
2359 OAM
2360 OAM
2361 OAM
2362 OAM
2363 OAM
2364 OAM
2365 OAM
2366 OAM
2367 OAM
4096 Log4j 1
4096 Log4j 1
4096 Log4j 1
4096 Log4j 1
4096 Log4j 1
4096 Log4j 1
4096 Log4j 1
7031 Service Critical IIS Service Failure

Control
Manager
7031 Service Critical IIS Service Failure
Control
Manager
7100 Email
Manager
7101 Email
Manager
7102 Email
Manager
7103 Email
Manager
7104 Email
Manager
7105 Email
Manager
7106 Email
Manager
7107 Email
Manager
7108 Email
Manager
7109 Email
Manager
7110 Email
Manager
7111 Email
Manager
7112 Email
Manager
7113 Email
Manager
7114 Email
Manager
7115 Email
Manager
7116 Email
Manager
7117 Email
Manager
7118 Email
Manager
7119 Email
Manager
7120 Email
Manager
7121 Email
Manager
7122 Email
Manager
7123 Email
Manager
7124 Email
Manager
7125 Email
Manager
7126 Email
Manager
7127 Email
Manager
7128 Email
Manager
7129 Email
Manager
7130 Email
Manager
7131 Email
Manager
7132 Email
Manager
7133 Email
Manager
7134 Email
Manager
7135 Email
Manager
7136 Email
Manager
7137 Email
Manager
7138 Email
Manager
7139 Email
Manager
7140 Email
Manager
7141 Email
Manager
7142 Email
Manager
7143 Email
Manager
7144 Email
Manager
7145 Email
Manager
7146 Email
Manager
7147 Email
Manager
7148 Email
Manager
7149 Email
Manager
7150 Email
Manager
7151 Email
Manager
7152 Email
Manager
7153 Email
Manager
7154 Email
Manager
7155 Email
Manager
7156 Email
Manager
7157 Email
Manager
7158 Email
Manager
7159 Email
Manager
7160 Email
Manager
7161 Email
Manager
7162 Email
Manager
7163 Email
Manager
7164 Email
Manager
7165 Email
Manager
7166 Email
Manager
7167 Email
Manager
7168 Email
Manager
7169 Email
Manager
7170 Email
Manager
7171 Email
Manager
7172 Email
Manager
7173 Email
Manager
7174 Email
Manager
7175 Email
Manager
7176 Email
Manager
7177 Email
Manager
7178 Email
Manager
7179 Email
Manager
7180 Email
Manager
7181 Email
Manager
7182 Email
Manager
7183 Email
Manager
7184 Email
Manager
7185 Email
Manager
7186 Email
Manager
7187 Email
Manager
7188 Email
Manager
7189 Email
Manager
7190 Email
Manager
7191 Email
Manager
7192 Email
Manager
7193 Email
Manager
7194 Email
Manager
7195 Email
Manager
7196 Email
Manager
7197 Email
Manager
7198 Email
Manager
7199 Email
Manager
7200 Email
Manager
7201 Email
Manager
7202 Email
Manager
7203 Email
Manager
7204 Email
Manager
7205 Email
Manager
7206 Email
Manager
7207 Email
Manager
7208 Email
Manager
7209 Email
Manager
7210 Email
Manager
7211 Email
Manager
7212 Email
Manager
7213 Email
Manager
7214 Email
Manager
7215 Email
Manager
7216 Email
Manager
7217 Email
Manager
7218 Email
Manager
7219 Email
Manager
7220 Email
Manager
7221 Email
Manager
7222 Email
Manager
7223 Email
Manager
7224 Email
Manager
7225 Email
Manager
7226 Email
Manager
7227 Email
Manager
7228 Email
Manager
7229 Email
Manager
7230 Email
Manager
7231 Email
Manager
7232 Email
Manager
7233 Email
Manager
7234 Email
Manager
7235 Email
Manager
7236 Email
Manager
7237 Email
Manager
7238 Email
Manager
7239 Email
Manager
7240 Email
Manager
7241 Email
Manager
7242 Email
Manager
7243 Email
Manager
7244 Email
Manager
7245 Email
Manager
7246 Email
Manager
7247 Email
Manager
7248 Email
Manager
7249 Email
Manager
7250 Email
Manager
7251 Email
Manager
7252 Email
Manager
7253 Email
Manager
7254 Email
Manager
7255 Email
Manager
7256 Email
Manager
7257 Email
Manager
7258 Email
Manager
7259 Email
Manager
7260 Email
Manager
7261 Email
Manager
8000 OAM
10000 Email
Manager
10001 Email
Manager
10002 Email
Manager
10003 Email
Manager
10004 Email
Manager
10005 Email
Manager
10006 Email
Manager
10007 Email
Manager
10008 Email
Manager
10009 Email
Manager
10010 Email
Manager
10011 Email
Manager
10012 Email
Manager
10013 Email
Manager
10014 Email
Manager
10015 Email
Manager
10016 Email
Manager
10017 Email
Manager
10018 Email
Manager
10019 Email
Manager
10020 Email
Manager
10021 Email
Manager
10022 Email
Manager
10023 Email
Manager
10024 Email
Manager
10025 Email
Manager
10026 Email
Manager
10027 Email
Manager
10028 Email
Manager
10029 Email
Manager
10030 Email
Manager
10031 Email
Manager
10032 Email
Manager
10033 Email
Manager
10034 Email
Manager
10035 Email
Manager
10036 Email
Manager
10037 Email
Manager
10038 Email
Manager
10039 Email
Manager
10040 Email
Manager
10041 Email
Manager
10042 Email
Manager
10043 Email
Manager
10044 Email
Manager
10045 Email
Manager
11000 Email
Manager
11001 Email
Manager
12001 Email
Manager
12002 Email
Manager
12003 Email
Manager
12004 Email
Manager
12005 Email
Manager
12006 Email
Manager
12007 Email
Manager
12008 Email
Manager
12009 Email
Manager
12010 Email
Manager
12011 Email
Manager
12012 Email
Manager
12013 Email
Manager
12014 Email
Manager
12015 Email
Manager
12016 Email
Manager
12017 Email
Manager
12018 Email
Manager
12019 Email
Manager
12020 Email
Manager
12021 Email
Manager
12022 Email
Manager
12023 Email
Manager
12024 Email
Manager
12025 Email
Manager
12026 Email
Manager
12027 Email
Manager
13000 Email
Manager
13001 Email
Manager
13002 Email
Manager
13003 Email
Manager
13004 Email
Manager
13005 Email
Manager
13006 Email
Manager
13007 Email
Manager
13008 Email
Manager
13009 Email
Manager
13010 Email
Manager
13011 Email
Manager
13012 Email
Manager
13013 Email
Manager
14000 Email
Manager
14001 Email
Manager
14002 Email
Manager
14003 Email
Manager
14004 Email
Manager
14005 Email
Manager
14006 Email
Manager
14007 Email
Manager
14008 Email
Manager
14009 Email
Manager
14010 Email
Manager
14011 Email
Manager
14012 Email
Manager
14013 Email
Manager
14014 Email
Manager
14015 Email
Manager
14016 Email
Manager
14017 Email
Manager
14018 Email
Manager
14019 Email
Manager
14020 Email
Manager
14021 Email
Manager
14022 Email
Manager
14023 Email
Manager
14024 Email
Manager
14025 Email
Manager
14026 Email
Manager
14027 Email
Manager
14028 Email
Manager
14029 Email
Manager
14030 Email
Manager
14031 Email
Manager
14032 Email
Manager
14033 Email
Manager
14034 Email
Manager
14035 Email
Manager
14036 Email
Manager
14037 Email
Manager
14038 Email
Manager
14039 Email
Manager
14040 Email
Manager
14041 Email
Manager
14042 Email
Manager
14043 Email
Manager
14044 Email
Manager
14045 Email
Manager
14046 Email
Manager
14047 Email
Manager
14048 Email
Manager
14049 Email
Manager
14050 Email
Manager
14051 Email
Manager
14052 Email
Manager
14053 Email
Manager
14054 Email
Manager
14055 Email
Manager
14056 Email
Manager
14057 Email
Manager
14058 Email
Manager
14059 Email
Manager
14060 Email
Manager
14061 Email
Manager
14062 Email
Manager
14063 Email
Manager
14064 Email
Manager
14065 Email
Manager
14066 Email
Manager
14067 Email
Manager
14068 Email
Manager
14069 Email
Manager
14070 Email
Manager
14071 Email
Manager
14072 Email
Manager
14073 Email
Manager
14074 Email
Manager
14075 Email
Manager
14076 Email
Manager
14077 Email
Manager
14078 Email
Manager
14079 Email
Manager
14080 Email
Manager
14081 Email
Manager
14082 Email
Manager
14083 Email
Manager
14084 Email
Manager
14085 Email
Manager
14086 Email
Manager
14087 Email
Manager
14088 Email
Manager
14089 Email
Manager
14090 Email
Manager
14091 Email
Manager
14092 Email
Manager
14093 Email
Manager
14094 Email
Manager
14095 Email
Manager
14096 Email
Manager
14097 Email
Manager
14098 Email
Manager
14099 Email
Manager
14100 Email
Manager
14101 Email
Manager
14102 Email
Manager
14103 Email
Manager
14104 Email
Manager
14105 Email
Manager
14106 Email
Manager
14107 Email
Manager
14108 Email
Manager
14109 Email
Manager
14110 Email
Manager
14111 Email
Manager
14112 Email
Manager
14113 Email
Manager
14114 Email
Manager
14115 Email
Manager
21000 Email
Manager
22000 Email
Manager
22001 Email
Manager
22002 Email
Manager
22003 Email
Manager
22004 Email
Manager
22005 Email
Manager
22006 Email
Manager
22007 Email
Manager
22008 Email
Manager
22009 Email
Manager
22010 Email
Manager
22011 Email
Manager
22012 Email
Manager
22013 Email
Manager
22014 Email
Manager
23000 Email
Manager
23001 Email
Manager
23002 Email
Manager
23003 Email
Manager
23004 Email
Manager
23005 Email
Manager
24000 Email
Manager
24001 Email
Manager
24002 Email
Manager
24003 Email
Manager
24004 Email
Manager
24005 Email
Manager
24006 Email
Manager
24007 Email
Manager
24008 Email
Manager
24009 Email
Manager
24010 Email
Manager
24011 Email
Manager
24012 Email
Manager
24013 Email
Manager
24014 Email
Manager
24015 Email
Manager
24016 Email
Manager
24017 Email
Manager
24018 Email
Manager
24019 Email
Manager
24020 Email
Manager
24021 Email
Manager
24022 Email
Manager
24023 Email
Manager
24024 Email
Manager
24025 Email
Manager
24026 Email
Manager
24027 Email
Manager
24028 Email
Manager
24029 Email
Manager
24030 Email
Manager
24031 Email
Manager
24032 Email
Manager
24033 Email
Manager
24034 Email
Manager
24035 Email
Manager
24036 Email
Manager
24037 Email
Manager
24038 Email
Manager
24039 Email
Manager
24040 Email
Manager
24041 Email
Manager
24042 Email
Manager
24043 Email
Manager
24044 Email
Manager
25000 Email
Manager
25001 Email
Manager
25002 Email
Manager
25003 Email
Manager
25004 Email
Manager
25100 Email
Manager
25101 Email
Manager
25102 Email
Manager
25103 Email
Manager
25200 Email
Manager
25201 Email
Manager
25202 Email
Manager
25203 Email
Manager
25204 Email
Manager
25205 Email
Manager
25206 Email
Manager
25207 Email
Manager
25208 Email
Manager
25209 Email
Manager
25210 Email
Manager
25211 Email
Manager
25212 Email
Manager
25213 Email
Manager
25214 Email
Manager
25215 Email
Manager
25216 Email
Manager
25217 Email
Manager
25218 Email
Manager
25219 Email
Manager
25220 Email
Manager
25221 Email
Manager
25222 Email
Manager
25223 Email
Manager
25224 Email
Manager
25225 Email
Manager
25226 Email
Manager
25227 Email
Manager
25228 Email
Manager
25229 Email
Manager
25230 Email
Manager
25231 Email
Manager
25232 Email
Manager
25233 Email
Manager
25234 Email
Manager
25300 Email
Manager
25301 Email
Manager
25302 Email
Manager
25303 Email
Manager
25304 Email
Manager
25305 Email
Manager
25306 Email
Manager
25307 Email
Manager
25308 Email
Manager
25309 Email
Manager
25310 Email
Manager
25311 Email
Manager
25312 Email
Manager
25313 Email
Manager
25314 Email
Manager
25315 Email
Manager
25316 Email
Manager
25317 Email
Manager
25318 Email
Manager
25319 Email
Manager
25320 Email
Manager
25321 Email
Manager
25322 Email
Manager
25323 Email
Manager
25324 Email
Manager
25400 Email
Manager
25401 Email
Manager
25402 Email
Manager
25403 Email
Manager
25500 Email
Manager
25501 Email
Manager
25502 Email
Manager
25503 Email
Manager
25504 Email
Manager
25505 Email
Manager
25506 Email
Manager
25507 Email
Manager
25509 Email
Manager
25510 Email
Manager
25511 Email
Manager
25512 Email
Manager
25513 Email
Manager
25600 Email
Manager
25601 Email
Manager
25602 Email
Manager
25603 Email
Manager
25604 Email
Manager
25605 Email
Manager
25606 Email
Manager
25607 Email
Manager
25608 Email
Manager
25609 Email
Manager
25610 Email
Manager
25612 Email
Manager
25613 Email
Manager
25614 Email
Manager
25615 Email
Manager
25616 Email
Manager
25700 Email
Manager
25701 Email
Manager
25702 Email
Manager
25703 Email
Manager
25704 Email
Manager
25705 Email
Manager
25706 Email
Manager
25707 Email
Manager
31004 Nortel CCMM High
License
Manager

License
Manager
License
Manager

License
Manager
31010 Nortel CCMM Low

License
Manager

License
Manager
32201 MCMC 2
32202 MCMC 2
32203 MCMC 2
32204 MCMC 4
32205 MCMC 5
32206 MCMC 5
32207 MCMC 3
32208 MCMC 6
32209 MCMC 6
32210 MCMC
32211 MCMC 2
32212 MCMC 5
32213 MCMC 2
32214 MCMC 2
32215 MCMC 2
32216 MCMC 3
32217 MCMC 3
32218 MCMC 6
32219 MCMC 6
32220 MCMC 3
32221 MCMC 4
32222 MCMC 4
32223 MCMC 3
32224 MCMC 6
32225 MCMC 6
32226 MCMC 3
32227 MCMC 3
32228 MCMC 3
32229 MCMC 2
32230 MCMC 2
32231 MCMC 6
32232 MCMC 2
32233 MCMC 2
32234 MCMC 2
32235 MCMC 6
32236 MCMC 3
32237 MCMC 3
32238 MCMC 2
32239 MCMC 4
32240 MCMC 3
32241 MCMC 6
32242 MCMC 3
32243 MCMC 2
32244 MCMC
32245 MCMC
32246 MCMC
32247 MCMC
32248 MCMC
32249 MCMC
32250 MCMC
32251 MCMC
32252 MCMC
32253 MCMC
32254 MCMC
32255 MCMC
32256 MCMC
32257 MCMC
32258 MCMC
32259 MCMC
32260 MCMC
32261 MCMC
32262 MCMC
32263 MCMC
32265 MCMC
32266 MCMC
32267 MCMC
32268 MCMC
32269 MCMC
32270 MCMC
32271 MCMC
32272 MCMC
32273 MCMC
32274 MCMC
32275 MCMC
32276 MCMC
32277 MCMC
32278 MCMC
32279 MCMC
32280 MCMC
32281 MCMC
32282 MCMC
32283 MCMC
32284 MCMC
32285 MCMC
32286 MCMC
32287 MCMC
32288 MCMC
32289 MCMC
32290 MCMC
32291 MCMC
32292 MCMC
32293 MCMC
32294 MCMC
32295 MCMC
32296 MCMC
32297 MCMC
32298 MCMC
32299 MCMC
32300 MCMC
32301 MCMC
32302 MCMC
32303 MCMC
32304 MCMC
32305 MCMC
32306 MCMC
32307 MCMC
32308 MCMC
32309 MCMC
32310 MCMC
32311 MCMC
32312 MCMC
32313 MCMC
54000 Predictive
Outbound
54001 Predictive
Outbound
54002 Predictive
Outbound
54003 Predictive
Outbound
54004 Predictive
Outbound
54005 Predictive
Outbound
54006 Predictive
Outbound
54007 Predictive
Outbound
54008 Predictive
Outbound
54009 Predictive
Outbound
54010 Predictive
Outbound
54011 Predictive
Outbound
54012 Predictive
Outbound
54013 Predictive
Outbound
54014 Predictive
Outbound
54015 Predictive
Outbound
54016 Predictive
Outbound
54017 Predictive
Outbound
54018 Predictive
Outbound
54019 Predictive
Outbound
54020 Predictive
Outbound
54021 Predictive
Outbound
54022 Predictive
Outbound
54023 Predictive
Outbound
54024 Predictive
Outbound
54025 Predictive
Outbound
54026 Predictive
Outbound
54027 Predictive
Outbound
54028 Predictive
Outbound
54029 Predictive
Outbound
54030 Predictive
Outbound
54031 Predictive
Outbound
54032 Predictive
Outbound
54033 Predictive
Outbound
54034 Predictive
Outbound
54035 Predictive
Outbound
54036 Predictive
Outbound
54037 Predictive
Outbound
54038 Predictive
Outbound
54039 Predictive
Outbound
54040 Predictive
Outbound
54041 Predictive
Outbound
54042 Predictive
Outbound
54043 Predictive
Outbound
54044 Predictive
Outbound
54045 Predictive
Outbound
54046 Predictive
Outbound
54047 Predictive
Outbound
54048 Predictive
Outbound
54049 Predictive
Outbound
54050 Predictive
Outbound
54051 Predictive
Outbound
54052 Predictive
Outbound
54053 Predictive
Outbound
54054 Predictive
Outbound
54055 Predictive
Outbound
54056 Predictive
Outbound
54057 Predictive
Outbound
54058 Predictive
Outbound
54059 Predictive
Outbound
54060 Predictive
Outbound
54061 Predictive
Outbound
54062 Predictive
Outbound
54063 Predictive
Outbound
54064 Predictive
Outbound
54065 Predictive
Outbound
54066 Predictive
Outbound
54067 Predictive
Outbound
54068 Predictive
Outbound
54069 Predictive
Outbound
54070 Predictive
Outbound
54071 Predictive
Outbound
54072 Predictive
Outbound
54073 Predictive
Outbound
54074 Predictive
Outbound
54075 Predictive
Outbound
54076 Predictive
Outbound
54077 Predictive
Outbound
54078 Predictive
Outbound
54079 Predictive
Outbound
54080 Predictive
Outbound
54081 Predictive
Outbound
54082 Predictive
Outbound
54083 Predictive
Outbound
54084 Predictive
Outbound
54085 Predictive
Outbound
54086 Predictive
Outbound
54087 Predictive
Outbound
54088 Predictive
Outbound
54089 Predictive
Outbound
54090 Predictive
Outbound
54091 Predictive
Outbound
54092 Predictive
Outbound
54093 Predictive
Outbound
54094 Predictive
Outbound
54095 Predictive
Outbound
54096 Predictive
Outbound
54097 Predictive
Outbound
54098 Predictive
Outbound
54099 Predictive
Outbound
54100 Predictive
Outbound
54101 Predictive
Outbound
54102 Predictive
Outbound
54103 Predictive
Outbound
54104 Predictive
Outbound
54105 Predictive
Outbound
54106 Predictive
Outbound
54107 Predictive
Outbound
54108 Predictive
Outbound
54109 Predictive
Outbound
54110 Predictive
Outbound
54111 Predictive
Outbound
54112 Predictive
Outbound
54113 Predictive
Outbound
54114 Predictive
Outbound
54115 Predictive
Outbound
54116 Predictive
Outbound
54117 Predictive
Outbound
54118 Predictive
Outbound
54119 Predictive
Outbound
54120 Predictive
Outbound
54121 Predictive
Outbound
54122 Predictive
Outbound
54123 Predictive
Outbound
54124 Predictive
Outbound
54125 Predictive
Outbound
54126 Predictive
Outbound
54127 Predictive
Outbound
54128 Predictive
Outbound
54129 Predictive
Outbound
54130 Predictive
Outbound
54131 Predictive
Outbound
54132 Predictive
Outbound
54133 Predictive
Outbound
54134 Predictive
Outbound
54135 Predictive
Outbound
54136 Predictive
Outbound
54137 Predictive
Outbound
54138 Predictive
Outbound
54139 Predictive
Outbound
54140 Predictive
Outbound
54141 Predictive
Outbound
54142 Predictive
Outbound
54143 Predictive
Outbound
54144 Predictive
Outbound
54145 Predictive
Outbound
54146 Predictive
Outbound
54147 Predictive
Outbound
54148 Predictive
Outbound
54149 Predictive
Outbound
54150 Predictive
Outbound
54151 Predictive
Outbound
54152 Predictive
Outbound
54153 Predictive
Outbound
54154 Predictive
Outbound
54155 Predictive
Outbound
54156 Predictive
Outbound
54157 Predictive
Outbound
54158 Predictive
Outbound
54159 Predictive
Outbound
54160 Predictive
Outbound
54161 Predictive
Outbound
54162 Predictive
Outbound
54163 Predictive
Outbound
54164 Predictive
Outbound
54165 Predictive
Outbound
54166 Predictive
Outbound
54167 Predictive
Outbound
54168 Predictive
Outbound
54169 Predictive
Outbound
54170 Predictive
Outbound
54171 Predictive
Outbound
54172 Predictive
Outbound
54173 Predictive
Outbound
54174 Predictive
Outbound
54175 Predictive
Outbound
54176 Predictive
Outbound
54177 Predictive
Outbound
54178 Predictive
Outbound
54179 Predictive
Outbound
54180 Predictive
Outbound
54181 Predictive
Outbound
54182 Predictive
Outbound
54183 Predictive
Outbound
54184 Predictive
Outbound
54185 Predictive
Outbound
54186 Predictive
Outbound
54187 Predictive
Outbound
54188 Predictive
Outbound
54189 Predictive
Outbound
54190 Predictive
Outbound
54191 Predictive
Outbound
54192 Predictive
Outbound
54193 Predictive
Outbound
54194 Predictive
Outbound
54195 Predictive
Outbound
54196 Predictive
Outbound
54197 Predictive
Outbound
54198 Predictive
Outbound
54199 Predictive
Outbound
54200 Predictive
Outbound
54201 Predictive
Outbound
54202 Predictive
Outbound
54203 Predictive
Outbound
54204 Predictive
Outbound
54205 Predictive
Outbound
54206 Predictive
Outbound
54207 Predictive
Outbound
54208 Predictive
Outbound
54209 Predictive
Outbound
54210 Predictive
Outbound
54211 Predictive
Outbound
54212 Predictive
Outbound
54213 Predictive
Outbound
54214 Predictive
Outbound
54215 Predictive
Outbound
54216 Predictive
Outbound
54217 Predictive
Outbound
54218 Predictive
Outbound
54219 Predictive
Outbound
54220 Predictive
Outbound
54221 Predictive
Outbound
54222 Predictive
Outbound
54223 Predictive
Outbound
54224 Predictive
Outbound
54225 Predictive
Outbound
54226 Predictive
Outbound
54227 Predictive
Outbound
54228 Predictive
Outbound
54229 Predictive
Outbound
54230 Predictive
Outbound
54231 Predictive
Outbound
54232 Predictive
Outbound
54233 Predictive
Outbound
54234 Predictive
Outbound
54235 Predictive
Outbound
54236 Predictive
Outbound
54237 Predictive
Outbound
54238 Predictive
Outbound
54239 Predictive
Outbound
54240 Predictive
Outbound
54241 Predictive
Outbound
54242 Predictive
Outbound
54243 Predictive
Outbound
54244 Predictive
Outbound
54245 Predictive
Outbound
54246 Predictive
Outbound
54247 Predictive
Outbound
54248 Predictive
Outbound
54249 Predictive
Outbound
54250 Predictive
Outbound
54251 Predictive
Outbound
54252 Predictive
Outbound
54253 Predictive
Outbound
54254 Predictive
Outbound
54255 Predictive
Outbound
54256 Predictive
Outbound
54257 Predictive
Outbound
54258 Predictive
Outbound
54259 Predictive
Outbound
54260 Predictive
Outbound
54261 Predictive
Outbound
54262 Predictive
Outbound
54263 Predictive
Outbound
54264 Predictive
Outbound
54265 Predictive
Outbound
54266 Predictive
Outbound
54267 Predictive
Outbound
54268 Predictive
Outbound
54269 Predictive
Outbound
54270 Predictive
Outbound
54271 Predictive
Outbound
54272 Predictive
Outbound
54273 Predictive
Outbound
54274 Predictive
Outbound
54275 Predictive
Outbound
54276 Predictive
Outbound
54277 Predictive
Outbound
54278 Predictive
Outbound
54279 Predictive
Outbound
54280 Predictive
Outbound
54281 Predictive
Outbound
54282 Predictive
Outbound
54283 Predictive
Outbound
54284 Predictive
Outbound
54285 Predictive
Outbound
54286 Predictive
Outbound
54287 Predictive
Outbound
54288 Predictive
Outbound
54289 Predictive
Outbound
54290 Predictive
Outbound
54291 Predictive
Outbound
54292 Predictive
Outbound
54293 Predictive
Outbound
54294 Predictive
Outbound
54295 Predictive
Outbound
54296 Predictive
Outbound
54297 Predictive
Outbound
54298 Predictive
Outbound
54299 Predictive
Outbound
54300 Predictive
Outbound
54301 Predictive
Outbound
54302 Predictive
Outbound
54303 Predictive
Outbound
54304 Predictive
Outbound
54305 Predictive
Outbound
54306 Predictive
Outbound
54307 Predictive
Outbound
54308 Predictive
Outbound
54309 Predictive
Outbound
54310 Predictive
Outbound
54311 Predictive
Outbound
54312 Predictive
Outbound
54313 Predictive
Outbound
54314 Predictive
Outbound
54315 Predictive
Outbound
54316 Predictive
Outbound
54317 Predictive
Outbound
54318 Predictive
Outbound
54319 Predictive
Outbound
54320 Predictive
Outbound
54321 Predictive
Outbound
54322 Predictive
Outbound
54323 Predictive
Outbound
54324 Predictive
Outbound
54325 Predictive
Outbound
54326 Predictive
Outbound
54327 Predictive
Outbound
54328 Predictive
Outbound
54329 Predictive
Outbound
54330 Predictive
Outbound
54331 Predictive
Outbound
54332 Predictive
Outbound
54333 Predictive
Outbound
54336 Predictive
Outbound
54347 Predictive
Outbound
54348 Predictive
Outbound
54349 Predictive
Outbound
54350 Predictive
Outbound
54351 Predictive
Outbound
54352 Predictive
Outbound
54353 Predictive
Outbound
54354 Predictive
Outbound
54355 Predictive
Outbound
54356 Predictive
Outbound
54359 Predictive
Outbound
61150 CCMM_LM_S Critical In Grace Period, Time
ervice Remaining = %np1 days,
%ads.
61151 CCMM_LM_S Major %nvs, Error Condition

ervice detected, Lock Code = %ads
61152 CCMM_LM_S Minor Error Condition resolved for

ervice Client %nvs
61153 CCMM_LM_S Minor %nvs Not in Grace Period,
ervice Remaining = %np1 days,
%ads
61154 CCMM_LM_S Critical %nvs, Fatal Error in License

ervice refresh. Grace Period expired,
Lock Code = %ads
61155 CCMM_LM_S Minor Client %nvs Resetting the

ervice Grace Period to 10 days.
61156 CCMM_LM_S Minor Client %nvs Grace Period not

ervice reset as invalid lock code
entered.
61157 CCMM_LM_S Minor %nvs Grace Period remaining

ervice = %np1 days, %np2 hours
Contact Center Multimedia event codes
Probable
Could not initialize COM. Please ensure all libraries
are available.
Unable to create a thread event.
Could not register a Service Control Handler.
Could not create a watcher thread.
Could not set the service status.

Pending statuses require a hint and checkpoint.
Could not create an instance of the Log object.
Unable to Post a Thread Message.

The 1% service was unable to start due to an
initialization failure.
Unable to create a new thread object.
A COM exception has been caught. No details are

available.
COM Error: Unable to access the log object interface
functions.
Unable to suspend the current thread
(id: %1).
Unable to resume the current thread
(id: %1).
COM exception: Source=%1.
COM exception: Description=%1.
Failed to connect to the registry at %1.
Failed to open the key %1 at %2.
Failed to get the value of %1 in key %2.
Starting the %1 service.
Configuring the application.
Status of %1: %2.
Opened the database %1 successfully.
Opened the local registry successfully.
Failed to create/update the key %1.
Failed to set value of %1 in the key %2.
Could not connect to the NT Service manager.
Could not install the %1 service.

Could not open the %1 service.
Could not delete the %1 service.
Could not change the start type of the %1 service.
Could not allocate a buffer to get the service

description.
Could not get the service status.
Could not start the %1 service.
Could not send a control request to the %1 service.
Could not retrieve date from the registry (parameter:

%1).
Could not create an instance of the Database object.
Could not get the CLSID of the Database object.
Errors were encountered while connecting to the

database.
registry.
logger.
Unable to start the listener thread.
Received request to exit.
Listener thread has been cleaned up and shut down.
Opened the logger successfully.

%1 service started successfully.
%1 service stopped successfully.
%1 service paused successfully.
%1 service continued successfully.
Could not set the service description.
Unable to start the service dispatcher.
No records returned for call id %1.
Exception: %1 %n
Minor: %1
Completion Status: %1
Unable to get a handle to the CCMM Event source
name in the registry.
Unable to open the CCMM Event source name from
the registry.
Unable to load the logging resource library.
Read %1 data from CCMS Database successful.
Wrote %1 data to CCMS Database.

Read %1 data from CCMS Database.
No default skillset in database.
Error on reading CCMS %1 data. Error Type: %2.
Message registration failed with %1. Message: %2.
Message registration passed with %1. Message: %2.
Message Re-registration failed with %1.

Message Re-registration passed with %1.
Skillset %1 Notification Event Received. Skillset ID:
%2.
User %1 Notification Event Received. User ID: %2.
User Delete Notification Event Received for user not

in CCM System.
Agent-Skillset Mapping %1 Notification Event
Received. Skillset ID: %2.
Application %1 Notification Event Received.
Application ID: %2.
CDN %1 Notification Event Received. CDN: %2.
ContactType %1 Notification Event Received.

ContactType: %2.
ContactType %1 Notification Event Received.
ContactType: %2.
CCMS OAM connection down.
Unable to use the logger to log a message. Please
ensure there are sufficient permissions on the log
directory and that the Event Viewer is not full.
Predictive Skillset %1 Notification Event Received.

Predictive Skillset ID: %2.
Predictive User %1 Notification Event Received.
Predictive User ID: %2.
The Predictive Controller to OAM connection has
failed.
Unable to create a new thread object for the
Predictive Server.
The Predictive Object used in the OAM to filter
Predictive Events to the Predictive Controller has
successfully started.
Wrote %1 Predictive data to the Predictive Outbound
Controller Service.
The Predictive Controller Thread has successfully
ended.

are available.

The %1 service was unable to start due to an

available.
functions.
COM Exception: Source = %1.
COM Exception: Description = %1.
Failed to get value of %1 in key %2.
Status of %1:%t%2
Opened the Database %1 at %2 successfully.
Opened the local Registry successfully.

Failed to set value of %1 in key %2.


description.

%1).

database.
registry.
logger.
Unable to get a handle to the SWCP Event source
Unable to open the SWCP Event source name from
the registry.
Closed the Database connection successfully.
Closed the Registry connection successfully.

JNI version cannot be determined or is not version

1.4.
Unable to create the Java Virtual Machine; check the
version of jvm.dll.
Unable to load the JVM. Please ensure Java has
been installed correctly and that jvm.dll is in the
system path.
Too many parameters have been passed to the
service from the registry. Please reduce the number
and try to start the service again.
Unable to locate the Email Handler archive file or

classname. Please ensure the application has been
installed correctly.
Unable to locate the main method. Please ensure the
application has been installed correctly.
An out of memory error occurred in the Java VM.

Please ensure the application has been installed
correctly.
Unable to create a jstring object. Please ensure
enough physical memory is available for this
application.
Unable to invoke the Java application's entry point.
correctly.
Java Virtual Machine loaded successfully.
Unable to attach the current thread to the JVM.

(id: %1).
(id: %1).
Worker thread has been cleaned up and shut down.
Unable to start the worker thread.

Shut down the Java Virtual Machine successfully.
Errors were encountered while starting the Java

Virtual Machine.
An exception was thrown while invoking the Java
main method.
Email Handler class invoked successfully.
An exception occurred in the Email Handler java
code.
are available.


available.
functions.
Status of %1:%t%2



configuration.

%1).

database.
registry.
logger.
the registry.


1.4.
version of jvm.dll.
system path.
Unable to locate the Multimedia Contact Manager

Client archive file or classname. Please ensure the


correctly.
application.
correctly.

(id: %1).
(id: %1).

Virtual Machine.
main method.
Multimedia Contact Manager Client class invoked
successfully.
An exception occurred in the Multimedia Contact
Manager Client java code.
are available.
Could not register Register a Service Control Handler.


available.
functions.
Status of %1:%t%2



configuration.

%1).
database.
registry.
logger.
Unable to get a handle to the SWCP Event source
Unable to open the SWCP Event source name from
the registry.


1.4.
version of jvm.dll.
system path.
Unable to locate the LDAP Manager archive file or

classname. Please ensure the application has been
installed correctly.


correctly.
application.
correctly.

(id: %1).
(id: %1).


Virtual Machine.
main method.
LDAP Manager class invoked successfully.
An exception occurred in the LDAP Manager java

code.
are available.
Could not register Register a Service Control Handler.


available.
functions.
Status of %1:%t%2



configuration.

%1).

database.
registry.
logger.
Opened the Logger successfully.
Could not set a service description.
the registry.


1.4.
version of jvm.dll.
Unable to unload the JVM. Please ensure Java has
system path.
Unable to locate the Outbound Scheduler archive file
or classname. Please ensure the application has
been installed correctly.


correctly.
application.
correctly.

(id: %1).
(id: %1).


Virtual Machine.
main method.
Outbound Outbound Scheduler class invoked
successfully.
An exception occurred in the Outbound Scheduler
java code.
SERVICE IMPACTING EVENT: Failure to connect to
the database.
the POP3 Server.
the SMTP Server.
SERVICE IMPACTING EVENT: There is no valid
default rule.
delivery failure rule.
SERVICE IMPACTING EVENT: We have detected N
e-mail from X in the past Y minutes. This may be an
e-mail loop or a Denial Of Service Attack.
SERVICE IMPACTING EVENT: The outbound
e-mail (ActionID: X, ContactID: Y) cannot be sent as
the skillset associated with it (SkillsetID: Z) does not
have an outbox
mapped to it. You must first configure an outbox for
this skillset, before any responses using it can be
sent.
The World Wide Web Publishing Service service

terminated unexpectedly.
The IIS Admin Service terminated unexpectedly.
Opening Inbound Mail Session
Caught exception in session open: %1
Session not open
Getting Mail
All Mail Retrieved in getMail
Deleting Mail
Closing Inbound Mail Session
An error has occurred while loading the mail service

properties. Using defaults!
Mail service properties file not found. Using defaults!
Cannot write HAL session statistics, %1
Opening Outbound Mail Session
Getting Sent Mail
All Sent Mail Retrieved
Unexpected response received on queue
Closing Outbound Mail Session
Creating new service
The service class %1 cannot be instantiated, %2
constr of MailStore
new id : %1
Opening Mail Store
%1 mails are present on store. Max retrieved will be

%2
An exception was caught trying to connect to host:
%1, Inbox: %2
Now attempting to connect to the alternate host: %1
There is no available alternative host to use
Retry succeeded!
First retrieve attempt failed fatally. Attempting retry!
Retry failed!
A mail has been removed from the server by a third

party during the retrieval process
Adding mail to deletion list
The mail store is not open: %1
Closing Mail Store
Tidying up
Marking messages as deleted
Connection check for delete operation failed fatally.

Attempting retry!
A mail marked for deletion has already been removed
from the server by a third party
Unable to delete some or all of retrieved mails from

server, may cause duplicate copies of mails
Creating Inbound Mail
Mail is invalid due to empty content
Mail is invalid due to missing addresses
Mail is valid
Processing Part
%1
UTF7 detected in mail - will apply UTF7 decoding to

subject line
Mail detected to have originated from an automated
source
MIME Type Is text/plain
MIME Type is text/html
MIME Type is multipart/*
MIME Type is message/rfc822

MIME Type is unknown, processing as attachment
Processing Message Envelope
%1 From Addresses found
From Address: %1
An error has occurred parsing a FROM address. Use

raw string.
To Address: %1
An error occurred parsing a TO address. Use raw

string.
CC Address: %1
An error has occurred parsing a CC address. Use raw

string.
BCC Address: %1
An error has occurred parsing a BCC address. Use

raw string.
Replyto Address: %1
An error has occurred parsing a REPLY-TO address.

Use raw string.
Processing Nested Message Envelope
Processing Plain Text Part
Plain text charset is null, this may cause problems

with display of non-ascii characters
Cannot apply filter: %1 - %2. The Find string is a

regular expression ensure it contains correct syntax,
%3
An error has occurred while loading the mail filter file!
%1
Mail filter properties file not found. No filtering will be
performed on mails
Processing HTML Text Part
Applying the Obscenity filter to the HTML mail
HTML charset is null, this may cause problems with

display of non-ascii characters
Processing Nested Message Part
Processing Multipart Part
Saving Attachment
Creating Attachment: %1
Converting attachment from UTF7

lastProcessAttempt: RawFile being Processed: %1
lastProcessAttempt: Found attachment at posn: %1
lastProcessAttempt: Filename: %1
File input error: %1
The attachment folder for this months inbound

attachments exists
The attachment folder for this months inbound
attachments does not exist - creating it
Failed to create monthly subfolder for inbound

attachments
Time taken for folder determination is: [%1ms]
The following exception was caught returning the

attachments folder: %1
An attachment with no filename or mime type has
been received, so defaulting to .txt file extension
An attachment with no specified filename has been

received, and the correct filename extension could not
be determined from its MIME type \"%1"\. Consider
adding a value for this MIME type to the
mailservice.properties file especially if this warning
occurs frequently
An attachment with no specified filename has been

received, so defaulting to txt extension as the correct
filename extension could not be determined as its
MIME type was unparseable: %1
attachment filename is null
attachment filename extracted as: %1
attachment filename truncated as: %1
processing header: %1
unfolded header: %1
processing token: %1
token with semicolon encountered adding to next

token: %1
Cannot decode header: %1 %2
Opening Mail Transport
Sending Mail
Mail sent (%1 bytes)

First send attempt failed fatally. Attempting retry!
Closing Mail Transport
Creating Message Headers for mail Contact ID: %1
No html part
Html part
Html length is: %1
Html trim length is: %1
Creating Plain Text Only Message
Creating MultiPart Message for plain text and

attachments
Creating Plain Text Part
Adding Parts To MultiPart
Adding MultiPart To Message
Creating MultiPart Message for plain text and html
Creating Plain Text multiPart
Creating html multiPart
Characterset: %1
Creating MultiPart Message for plain text and html

and attachments
Creating Plain Text multiPart
File %1 does not exist in outbound folder so trying

inbound folder
Converting %1 addresses
Converting address: %1
Attempting to reserve %1 (%2 adjusted) bytes of

memory. %3
%1 bytes of memory reserved. %2
Due to memory constraints this mail will temporarily

be queued until sufficient memory is available to
process it. If this occurs frequently it will impact the
speed of your throughput. To solve this you will need
to allocate more memory to the JVM. %1
%1
Released %1 (%2 adjusted) bytes of memory. %3

****** DUAL TESTS COMMENCING
****** DUAL TEST %1
****** DUAL Outbound TEST %1
****** pausing to allow delivery for %1 millis
****** DUAL Inbound TEST %1
****** DUAL TESTS COMPLETE
Error in test, %1
Building configs
opening session
getting and deleting mail
%1
From address: %1
From Email address portion: %1
From Personal Name portion: %1
All Mail Retrieved
Closing session
%1 mails successfully retrieved!
sending %1 mails…
Cannot handle request as service pool has not been

set! Removing request to prevent backlog
A non request object was received by the worker

thread
Thread going to sleep
Thread waking up
Successive failures have occurred retrieving mail, no

further mails will be retrieved on this mail store, during
this session
Send failure will NOT be retried later
Send failure will be retried later
Resizing pool from %1 threads with priority %2 to %3

threads with priority %4
Join process during pool resize unexpectedly
interrupted! %1
Unexpected non response object in response queue
Queue popping process unexpectedly interrupted! %1
Completing Pending Requests And Closing Services
New services created during initial wait, for which new

close messages were issued which now have to be
waited on also
Issuing Close Messages
Waiting until pending requests complete
Wait on pending process unexpectedly interrupted!

%1
All pending requests completed!
Adding Attachment: %1
Mail retrieved (%1 bytes)
Retrieving Mail
%1
Using the custom Keyword Analyzer
Using Keyword Analyzer: %1
Exception constructing KeywordAnalyzer
An error has occurred while loading the mail analyzer

property. Using defaults! %1
Time taken for KeywordAnalyzer.setMail n is: [%1ms]
Exception setting document
Query String is: %1
%1 is: %2
Query Object is: %1
Query Class is: %1
No. of hits is: %1
Time taken for KeywordAnalyzer.analyseField (%1) is:

[%2ms]
Exception analyzing %1
Building Queries
From Address: [%1]
Rule Query is: %1
Exception building queries
Keyword Group Query is: [%1]
Start Quote is: %1
Remainder is: %1
End Quote is: %1
Keyword is: [%1]
RuleAdmin is: %1
init - Rebuilding queries
Exception initializing RuleHandler
Message to be analyzed is: %1
analyze - Rebuilding queries
Truncating Mail Body
isReply: %1
isNonDelivery: %1
Checking against regular rules matching the To

address: %1 or CC address: %2
Time taken for Analyzing Message [%1] is : [%2ms]
Exception retrieving Rule Admin data
Loading rules matching the To addresses
Checking address from the To field: %1
Size of collection matching this address is: %1
Checking against rule: %1
Rule Query: [%1]
Exception getting Customer Id
Found Delivery Failure Rule
Found Default Rule
Time taken for RuleMap.load is : [%1ms]

default rule
delivery failure rule
Exception loading rule map

the POP3 Server
SERVICE IMPACTING EVENT: We have detected
%1 emails from %2 in the past %3 minutes. This may
be an email loop or a Denial Of Service Attack.
Cannot redirect stdout and stderr to log

javamailtracelog.txt. Javamail debug statements will
not be logged because of this error. %1
EmailHandler -> The following exception occurred

when creating RuleHandler object: %1
EmailHandler -> The following exception occurred

when starting up: %1
An error has occurred while loading the mail service
properties. Using defaults! %1
Alimentum -> The following exception was caught:

%1
EmailManager has attempted to send Action ID: %1
for the past %2 days without success. No further
attempt to send this mail will be made.
IMH -> The following RuleException was caught: %1
IMH -> The following exception was caught: %1
IMH -> Exception on retrieving the emails from the

active session : %1
IMH -> The following NotOpenException was caught:
%1
A Rule Exception has occurred! All further processing
of inbound mail for this interval will be suspended.
Ensure that you have configured your rules correctly.
An exception occurred processing the retrieved mail:

%1
Caught ConcurrentModificationException in %1
IMH -> Caught the following exception in

pruneLoopDetectionTable %1
AutoResponse Loop Suspected: response cancelled
to origin address %1
IMH -> Caught the following exception in detectLoop
%1
Warning - could not start IMH thread, %1
LaunchIMH -> The IMH sleep was interrupted with the

following exception: %1
LaunchIMH -> The following exception was found: %1
RH -> Exception retrieving the autoNumberStatus

from site_parameters
RH Caught exception: %1 : %2
ResponseHandler -> The following exception was

caught: %1
ResponseHandler -> exception while sending auto
reply: %1
ResponseHandler -> could not update email status to
not sent, %1
ResponseHandler -> VerifyMailSent : The following
exception was caught: %1
ResponseHandler -> could not update email status to
in queue, %1
ResponseHandler -> The following exception was
caught resending: %1
IMH thread properties not found. Using defaults!
AutoResponse Loop Detection Mail Limit Property not

found. Defaulting to 10!
AutoResponse Loop Detection Interval Limit Property
not found. Defaulting to %1!
AutoResponse Loop Detection Disabled, this may
possibly cause mail autoresponse loops to fill up
database!
A null From address has been identified - setting to
unknown
Cannot determine orig address from inbox
ResponseHandler -> RH thread properties not found.

Using defaults!
ResponseHandler -> Authentication may be enabled
but no matching credentials can be found for email
address: '%1'. An attempt to send without
authentication will be made.
ResponseHandler -> Previously tried to resend - now

email status updated to email in queue. Action ID : %1
ResponseHandler -> Could not send the mail, adding

to the retry list. Action ID: %1
ResponseHandler -> No alternate SMTP host - now
email status updated to email in queue. Action ID: %1
A null To address has been identified - setting to

unknown
A null To address has been identified - setting to
unknown
Released loopDetectionSemaphore in finally %1
ResponseHandler -> Not using SMTP Authentication

Initializing the Email Handler
Javamail debug enabled, redirecting stdout and stderr

to javamailtracelog.txt
Rescheduling the Alimentum to 00:00
Alimentum: Sleep time is (ms): %1
Alimentum starting
Now Reading properties FileInputStream
Now Reading properties file
Error Reading properties file - using defaults
Error Reading properties FileInputStream - using

defaults
Alimentum progressing
Alimentum: performing check for emails older than

%1 days
Alimentum disabled
IMH -> started the imh thread
AutoResponse Loop Detection Mail Limit set to %1
AutoResponse Loop Detection Interval Limit set to %1
IMH -> Inbound folder: %1 Outbound folder: %2
IMH -> opening session to mailserver
IMH -> Closing the InboundMailSession
IMH -> Now requesting a mail from the mail server
MailBox:%1:%2
MsgUID: %1
MsgNo: %1
IMH -> An email has been retrieved
IMH -> About to delete mail
IMH -> Email Deleted
All mails have been retrieved
Starting routine pruneLoopDetectionTable to ensure

table contains only mails within the specified interval
limit
Locked loopDetectionSemaphore-
pruneLoopDetectionTable
AutoResponse Loop Detection Table Entry %1
pruned to %2 sub entries
AutoResponse Loop Detection Table pruned to %1
entries
Ending routine pruneLoopDetectionTable
Starting routine detectLoop
Locked loopDetectionSemaphore-detectLoop
Checking the Out Of Hours status
mailConfig.isOutOfHoursRuleEnabled(): %1
parsedMail.applyOutOfHoursRule: %1
mailConfig.isContactCenterClosed(): %1
The out of hours rule is enabled
The contact center currently is closed
We are now applying the out of hours rule
Out Of Hours Rule Applies to this contact
Not applying the Out Of Hours Rule to this contact
The contact center is currently open during

processing of mail
The Out Of Hours Rule is disabled. Processing mail
Completed Out Of Hours Checks. Now checking

AutoResponse requirements
There is an acknowledgement for this rule
Not a delivery failure report or its not from an

automated source
Not a denial of service attack - send
acknowledgement
Exception in Handlemail:
The raw To address is: %1
The resolved To address is: %1
Raw From Address is: %1
HTML Only Mail Detected, converted for rule handling

to :\n %1
Parameters passed to RuleHandler are:
To: %1
CC: %1
From: %1
Subject: %1
Body: %1
IMH -> Analyze Result from the RuleHandler: %1
Orig Address is null so setting it to inbox: %1
Orig Address set by rulehandler: %1
The senders name is: %1
IMH -> This transaction will be created in a Close

State (T/F): %1
IMH -> Rule Handler decided this transaction will be
created as Closed
IMH -> Rule Handler decided this transaction will be
created as New
ParsedMail customerID: %1
PreProcessed Address is: %1
PostProcessed Address is: %1
LaunchIMH -> IMH being started…
LaunchIMH -> putting the imh thread to sleep for %1

seconds
LaunchIMH -> the imh thread has now woken up
Commencing LDAP poll and file write process
Using the following params:
--->IsEnabled = %1
---> serverUserName = %1
---> serverPassword is valid, i.e. not null or empty

string
---> pollingInterval = %1
---> searchBase = %1
---> fileLocation = %1
---> serverAddress = %1
---> serverPort = %1
Polling interval is 24 hours - rescheduling for midnight
**** ERROR: %1
formatAttributes(): result with no attributes detected
ResponseHandler -> ResponseHandler thread

created
RH -> Customer autoNumber %1
ResponseHandler -> closing session…
ResponseHandler -> Inbound folder: %1 Outbound

folder: %2
ResponseHandler -> creating session
ResponseHandler -> opening session
ResponseHandler -> sending the mail from the RH
ResponseHandler -> the ack id associated with the

mail is: %1
ResponseHandler -> the customer id associated with
the mail is: %1
ResponseHandler -> the recipients name is: %1
ResponseHandler -> Sending to : %1
Changing characterset to: %1
ResponseHandler -> Sending from: %1
ResponseHandler -> SMTP Authentication enabled
RH -> adding attachment: %1
Encountered an attempt to send an auto-response to

a barred address. Id of action is : %1
vector size: %1
Calling getUsername for customer id %1
Calling getPassword for customer id %1
ResponseHandler -> email status updated to not sent:

Action: %1
ResponseHandler -> Resending to : %1
ResponseHandler -> Not using SMTP Authentication
ResponseHandler -> SMTP Authentication enabled

with alternate credentials
IMH -> Applying a filter to an inbound mail
No from email address to filter
No subject to filter
No plain text to filter

No html to filter
No charset to filter

the SMTP Server
OMH -> The following exception was caught: %1
No valid alternate SMTP host found
No alternate SMTP host available for connection
OMH -> could not update barred email status to

unsent, %1
OMH -> could not update email status to sent, %1
OMH -> could not update email status to not sent, %1
Warning - could not start OMH thread, %1
LaunchOMH -> The OMH sleep was interrupted with

the following exception: %1
LaunchOMH -> The following exception was found:

%1
The following error occurred when instantiating the
MailConfiguration object: %1
22010 Caught exception: %1: %2
MailConfiguration -> missing attachment location

parameters when querying SiteParameters…
MailConfiguration -> problem retrieving the hostname

from the server_details table…
MailConfiguration -> problem retrieving the authState
from the server_details table…
MailConfiguration -> problem retrieving the alternate
hostname from the server_details table…
OMH thread properties not found. Using defaults!
An alternate SMTP host will be used: %1
OMH -> Authentication may have enabled but no

matching credentials can be found for email address:
'%1'. An attempt to send without authentication will be
made.
Not sending mail as this address is barred: %1
MailConfiguration -> problem retrieving the timer from

site_parameters. Using 5 Min default.
MailConfiguration -> Exception retrieving the timer

from site_parameters. Using 5 Min default.
OMH -> Inbound folder: %1 Outbound folder: %2
OMH -> opening session
OMH -> closing session…
OMH -> about to send a mail…
OMH -> SMTP Authentication enabled using

inboxname
OMH -> SMTP Authentication enabled with alternate
logon credentials
OMH -> SMTP Authentication enabled using original
inboxname: %1
OMH -> SMTP Authentication enabled with alternate
logon credentials : %1
Attempting SMTP Authentication with credentials for :
%1
OMH -> Not using SMTP Authentication
OMH -> barred email status updated updated to

unsent
OMH -> email status updated to sent
OMH -> email status updated to not sent
Connection problem with the mail server: No action

will be taken as the mail will be tried again later
LaunchOMH -> OMH is now starting…
LaunchOMH -> putting the omh tread to sleep for %1

seconds
LaunchOMH -> the omh thread has now woken up
MailConfiguration -> The retrieved count from inboxes

was: %1
IsContactCenterClosed: %1
outOfHoursAutoResponseId %1
outOfHoursRuleEnabled %1
Sleep minutes and seconds values loaded

successfully from db
MailConfiguration -> The retrieved interval was: %1
Server ID: %1
Server Name: %1
Server Port: %1
Server Backup: %1
The Attachment URL is: %1

Attachment Network Share Location is: %1
Inbox: %1
Domain: %1
Display name: %1
In Threshold: %1
Enabled Value: %1
MailConfiguration -> The retrieved hostname was: %1
SMTPAuth Inbox is: %1: Matching with : %2
Found match with authStart: %1
MailConfiguration -> The retrieved authState was: %1
Host Inbox is: %1 : Matching with : %2
Inbox is: %1 : Matching with : %2
Match found
Comparing primary host: %1 with server %2
MailConfiguration -> The retrieved alternate

hostname was: %1
MailConfiguration -> Loading all Inboxes
MailConfiguration -> Loading all Servers
Skillset ID: %1
Caught exception: %1 : %2
Creating the attachments
Rule ID: %1
Rule Name: %1
An error has occurred while loading the mail filter file!

Default filtering will be applied, %1
No filter file found! Default filtering will be applied
A Low order Ascii character with the ascii value: %1

was found in field: %2
An invalid surrogate pair was found in field: %1
Response -> Response BO OMH created
Response -> The following exception was caught: %1

Skillset Name: %1
Mailbox Name: \"%1\" <%2@%3>
Mailbox Name: %1@%2
Response -> Problem retrieving the latin-1 to latin-9

conversion status from SiteParameters. Value
retrieved was out of range. Using default value of true
Response -> NumberFormatException retrieving the

latin-1 to latin-9 conversion status from
SiteParameters. Using default value of true. Caught
exception: %1: %2
Response -> CacheException retrieving the latin-1 to

latin-9 conversion status from SiteParameters. Using
default value of true. Caught exception: %1: %2
Response -> Exception retrieving the latin-1 to latin-9

conversion status from SiteParameters. Using default
value of true. Caught exception: %1: %2
Response -> The retrieved latin-1 to latin-9

conversion status was: %1
AutoSignature: %1
Response -> Customer autoNumber: %1
MailConfiguration -> Exception retrieving the

autoNumberStatus from site_parameters
getAutoNumberContactStatus -> %1
Response -> Contact autoNumber: %1
Response -> Exception retrieving the

autoNumberStatus from site_parameters
Response Caught exception: %1 : %2
Attachment added
Action Added: %1
CallBackStatus Updated successfully: %1
Barred EmailAddress: %1
Size of List is: %1
GetUnsentMail: AutoNumberContact Status: %1
Action type is password reminder
myContact.getCustomerID().longValue(): %1
Subject: %1
Exception on Action type of password reminder
Changing characterset to: %1
lSkillID: %1
UseOriginalAddress enabled, using: %1
UseOriginalAddress disabled, using: %1
SERVICE IMPACTING EVENT: The outbound email

(ActionID: %1, ContactID: %2) cannot be sent as the
skillset associated with it (SkillsetID: %3: %4 ) does
not have an outbox mapped to it. You must first
configure an outbox for this skillset, before any
responses using it can be sent.
A CF/LF has been replaced in the auto-signature at

position: %1
the size of the attachments vector is: %1
Response Caught exception: %1: %2
Creating a new Transaction object
Passing email address: %1
Customer not found
Customer found with id: %1
its a delivery failure mail but there is no customer id in

the subject
Customer not found
Delivery Failure / External Reply Customer not found
Delivery Failure / External Reply Customer found with

id: %1
Creating the customer record
Customer Id Created: %1
Using Customer Id: %1
Creating the contact record…
The size of array is: %1
Contact parameters set
Contact Id Created: %1
No from email address to filter
No to address to filter
No cc address to filter
No subject to filter
No plain text to filter
No html to filter
No charset to filter
No username to filter
No outboundOriginator to filter
No allToAddresses to filter
KeyWordGroup Id Created: %1
Time taken for KeywordGroup.create is: [%1ms]
KeyWordGroup Updated successfully: %1
KeyWordGroup deleted successfully: %1
RuleKeyWordGroup Id Created: %1
Time taken for KeywordGroupLink.create is: [%1ms]
RuleKeyWordGroup Updated successfully: %1
RuleKeyWordGroup deleted successfully: %1
Time taken for KeywordGroupLink.delete is: [%1ms]
_______________New
RuleKeyWordGroup__________________
RuleKeywordGroup Operator: %1
RuleKeywordGroup Sequence: %1
KeyWordGroup ID: %1
KeyWordGroup Name: %1
KeyWordGroup Query: %1
Time taken for KeywordGroupLink.getLinksForRule is

: [%1ms]
Operator is: [%1]
Rule Id Created: %1
Time taken for Rule.create is: [%1ms]
Inbox ID: %1
Name: %1
type: %1
UseOutOfHoursRule: %1
Time taken for Rule.read is: [%1ms]
Rule Updated successfully: %1
Time taken for Rule.update is: [%1ms]
Rule deleted successfully: %1
Time taken for Rule.delete is: [%1ms]
Rule Priority: %1
Rule Type: %1
IsOutOfHoursRuleEnabled: %1
Number of enabled rules (rows) returned is: [%1]
Time taken for Rule.getEnabledRules is: [%1ms]
Number of Chars: %1
Search Body: %1
Search Subject: %1
Last Modified Time: %1
Time taken for RuleAdmin.read is: [%1ms]

the database
RuleAdmin Updated successfully: %1
Time taken for RuleAdmin.update is: [%1ms]
Registry information missing.
Error in starting the cache service.

Cannot create an instance of license class.
Exception in communication with CCMM Database.
Exception in service control.
Could not get a primary or shadow license.
Error connecting to Database Events - Unknown host

name.
Error connecting to port for Database Events.
No RoutePoint on Contact in database.

Error reading database Events port number from
database. Using default port.
Started EventHandler to process events from
database.
Started Updater - used to place contacts in Open
Queue.
Error parsing data and time in Event from database.
Received Cache Event. Contents: %1.

Getting Multimedia Provider from CCMS.
Exception on reading Contact given Force
Disconnect/Default Treatment.
Failed to get Multimedia Provider from CCMS.
Starting Updater - used to place contacts in Open

Queue.
Failed to start Contact Processors - required to place
contacts in Open Queue.
Received Event for DEFAULT_TREATMENT on
Contact.
Received Event for FORCE_DISCONNECT on
Contact.
Unknown contact type on provider.
Unidentified contact type in database event.
Creating Contact in CMF.

Drop Contact from CMF.
Exception on dropping Contact from CMF.
Number Format exception on reading MCMC event
port from database.
Cache Exception on reading MCMC event port from
database.
Cache event Port read from database: %1.
Read from Database. Number of New Contacts: %1.
Exception on reading contact from database.
New Contact returned as Null from Database.
Exception on synchronizing Buffers with database.
Exception on reading contact data from database.

Method Ref: %1.
Exception on creating StateChange Listeners for
provider. Exception Type: %1.
Exception on adding Listeners to provider. Exception

Type: %1.
Reading Contact from database.
Error reading contact from Database.
Exception on getting Peer. Exception Type: %1.
ServiceProviderStatus event received. Status Type:

%1.
Update restart method called to resync with CCMS.
Exception on creating OutOfProviderAddress.

Exception Type: %1.
Error parsing data in database event for %1.
Exception received from CCMS on /Drop contact.
Exception received processing buffers in Updater for

buffer number: %1.
Exception in getting contact types setup on provider.
Exception Type: %1.
Cache Exception on reading CCMS server name from
database.
Error updating CMFProperties.xml configuration file.
Error reading event on event connection to database.
Exception information: %1
Contact already exists in CCMS.
ResetOpenContact called for contact in OPEN status
on database but not in CCMS.
Next audit will occur at: %1

Audit of CCMM contact status.
Read from Database. Number of Drop Contacts: %1
Number of failure(s) attempting to current contact on

CCMS: %1
Number of contacts that failed contact creation: %1
Default setting for %1 parameter: %2

CCMS communication failure. Connection restart
required.
Contact status changed to closed since
synchronization with database.
Set Intrinsic value on Contact: %1 = %2
IM contacts not created in CCMS.
Creating Predictive Contact in CMF for Agent %1.
Drop Predictive Contact from CMF with Agent ID: %1
Invalid CMF object ID returned

Predictive Contact already assigned to Agent ID: %1
Exception on dropping Predictive Contact from CMF:

%1
Unable to drop Predictive Contact as no contact exists
for Agent ID: %1
A buffer is empty, putting associated thread to sleep
Initializing connection to CMF

Initialization of CMF connection complete
Agent %1 already has a contact on CMF (%2).
Another contact cannot be created until the current
contact has been dropped.
Predictive contact added for Agent %1 with CmfUuid:

%2
Predictive contact dropped for Agent %1 with
CmfUuid: %2
CMF connection has been reestablished by another
thread
Synchronization of buffers is required
Synchronization of buffers is complete
Starting contact processors
Started contact processors
No CMF connection, need to reestablish connection
before processing contacts
Error processing buffer: %1
CMF Connection has failed
Auditor buffer empty, finishing audit for this priority
contact
Exception adding predictive contact to CMF: %1
Exception adding predictive contact to CMF: %1
Starting Auditor
There are no Priority %1 contacts for the Auditor to
process
There are no Drop contacts for the Auditor to process
Synchronizing buffers
Number of NEW contacts from database: %1
Number of DROP contacts from database: %1
EventHandler, waiting for synchronization of buffers to

complete
Putting contact back in buffer
Waiting on the %1 Contact Processor to finish its
current contact
Drop Predictive Contact from CMF with CMF ID: %1
Predictive contact dropped with CmfUuid: %1
Dropping all predictive contacts from CMF, %1

contacts currently exist
Unable to drop all predictive contacts from CMF,
trying again
Above Max number of attempts allowed (%1) per
contact, dropping current contact and adding new one
Above Max number of attempts allowed (%1) per

contact, will not attempt to drop this contact again
Error occurred reading from properties file. Using

defaults.
Properties file not found
Connection to CMF lost after call was made.
Returning contact to buffer to be tried.
Exception interrupting Manager: %1

Manager interrupted
First valid contact received
First contact is a Drop Predictive contact, not adding
to buffer
Get list of all contacts currently on CMF and drop any
Predictive contacts
Number of contacts currently on CMF: %1
Predictive contact found, dropping this contact
Number of predictive contacts dropped: %1
No predictive contacts needed to be dropped from

CMF
No contacts were retrieved from CMF, no predictive
contacts need to be dropped
First Predictive contact received, lowering sleep time
for predictive contact processors and waking them up
Number of active predictive contacts: %1

Exception occurred during Config Handler sleep: %1
CCMS server name retrieved from Database
CCMS server name could not be retrieved from

Database, not updating CMF properties file
Beginning ONStart() Method, Starting the Predictive

Outbound Service
Starting the SER Connection Thread
ConnectToSER() Method Exception:
SER Socket was successfully shutdown
OAM Socket was successfully shutdown
Checking if the SER connection Thread is still going
SER connection Thread Stopped!
Ending OnStop() Method, Predictive Outbound

Service Successfully Stopped
Predictive Outbound Service Paused
Predictive Outbound Service Continued
SER Exception:
Loaded Skillset Name:
SER Inner Exception:
Linked the following Agent Login ID and the Skillset

successfully (LogonID, Skillset): (
Beginning UnLinkAgentFromSkillset(string LoginID)

Method, Preparing to UnLink a Skillset from the
following Login ID:
OAMBufferTimer_Elapsed Trigger is still occurring
OAMBufferTimer_Elapsed() The Wait For OAM Buffer

data was signaled
OAMBufferTimer_Elapsed() The buffered OAM Data
length is 0
Beginning UnLinkAgentFromSkillset(string LoginID,
string SkillsetName) Method, Preparing to UnLink the
following Login ID and Skillset Name (LogonID,
Skillset): (
Unlinking the following Agent and Skillset (LogonID,

Skillset): (
OnDataReceived() Waiting here for infinite time until
the set event is signaled from elapsed timer
OnDataReceived() WaitForBufferTimer set event

signaled
Buffering OAM data…
Unlinked the following Agent Login ID and the Skillset

successfully (LogonID, Skillset): (
Found the EndStartUp Element Node
There was no EndStartUp Element Node in this XML

Stream
Failed to load Agent with Login ID:
Beginning LinkAgentToSkillset(string LoginID, string
SkillsetName) Method, Preparing to Link the following
(LogonID, Skillset): (
Linking the following Agent and Skillset (LogonID,

Skillset): (
Unable to get the SER CPSEE Server Name from the
Web Services Server Reference
General Exception:
General Inner Exception:
There was no Skillset Element Nodes in this XML

Stream
Initialize the Agent Thread
There was no Agent Element Nodes in this XML

Stream
There was no Mapping Element Nodes in this XML
Stream
Ending GetSessionKey() Method with Session Key
SOAPException:
Inner SOAPException:
The following Skillset Thread is still running, (Skillset,

Skillset Thread ID): (
The following Skillset Thread has terminated, (Skillset,
The following Agent Thread is still running, (Agent
LogonID, Agent Thread ID): (
The following Agent Thread has terminated, (Agent

Beginning ConnectToSER() Method, Setting up the

connection to the SER CPSEE Server
Connecting to the following SER CPSEE Server:
Ending TryReConnectToSER() Method, Connected to

the SER CPSEE Server at:
Socket Inner Exception:
Socket Exception:
Setting up the Socket to connect to the OAM
Connecting to the OAM Component

Connected to the OAM Component at:
SER Socket is Disconnected, Closing this side of the

connection
Checking that the OAM Socket property 'Connected'
has its Boolean value set as true
Object Disposed Inner Exception:
Retrying Connection to the OAM Component using

the ConnectToOAM() Method over a 1 minute interval
Object Disposed Exception:
Socket connection lost with the OAM
SER Socket is Connected.
Sleeping for 1 minute before trying to re-commit the

Agent Addition
Agent Deletion
Agent Update
Thread State Exception:
Thread State Inner Exception:
XML Exception
XML Inner Exception

Skillset Addition
Retrying to delete the following LogonID:

Skillset Deletion
Beginning SynchronizeStartUpData() Method
Removing unwanted Skillset (not present in OAM

Skillset HashTable):
Removing unwanted Agent Logon ID (not present in
OAM Agent HashTable):
Completed Synchronizing the OAM and SER…

Agent Skillset Assignment
The following Skillset does not exist on SER C2PSE
Server:
The following Skillset exists on SER C2PSE Server:

Agent Skillset De-Assignment
Agent Skillset Assignment Query
Retrying to add the following Skillset:
Retrying to delete the following Skillset:
The following Agent does not exist on SER C2PSE

Server:
The following Agent exists on SER C2PSE Server:

Agent Query
Retrying to add the following LogonID:
Retrying to update the following Agent (LogonID,

Fullname): (
Skillset Query
Ending WaitForOneMinuteIfServiceActive() Method,
Service is still going returning true
Retrying to delete the Skillset assigned to LogonID:
Retrying to add the following assignment (LogonID,

Skillset): (
Retrying to delete the following assignment (LogonID,
Skillset): (
Beginning WaitForOneMinuteIfServiceActive()
Method
The following Agent Login ID was created

successfully:
Entered AgentLinkedToSkillsetOnCPSEE()
Getting the AmiMessage
Getting the XMLNode
he following Login ID has a Skillset linked to it and will

be unlinked now LogonID:
The following Agent Logon ID and SAMGroup are
linked and will be unlinked now (LogonID,
SAMGroup): (
The following Agent Logon ID was deleted:
Checking the XMLNode is not Null
Checking the AmiMessage Header Result
Entered SkillsetOnCPSEE()
Entered AgtSsMappingOnCPSEE()
Loading Instance to update Agent Login ID:
Trying to lock for editing of Agent Login ID:
The following Agent Login ID was updated:

Entered AgentNameOnCPSEE()
Entered AgentOnCPSEE()
Failed to lock the following Login ID to update:
Beginning UnLinkAgentFromSkillset(List(string)
LoginIDs, string SkillsetName) Method
The following Skillset was added:
About to loop through all the Agent LogonIDs
Removing the following LogonID from the LoginIDs

List, LogonID:
Failed to load the following Skillset:
Beginning LinkAgentToSkillset(List(string) LoginIDs,

string SkillsetName) Method
The following Skillset Thread has terminated, (Skillset,
Checking if Skillset object is linked to any Work
Sessions
The following Skillset was deleted:
The following Agent Thread has terminated, (Agent

Ending OnStart() Method
Ending GetServerNames() Method
Ending ConnectToSER() Method
The Site Parameters Web Service has returned the

following Port Number to connect to the OAM
Component:
The Administrator Web Service has returned the
following SER Admin Username:
The Server Web Service has returned the following

SER Server Name and Port:
Beginning OnStop() Method, Stopping the Predictive
Service…
Releasing the Handle on the SER Thread
Released the Handle on the SER Thread to allow the

Thread to complete
Checking if the SER Socket is still connected
Closing the SER Socket
Checking if the OAM Socket is still connected
Closing the OAM Socket

Aborting the SER Thread
Waiting for the SER Thread to finish Aborting
Beginning GetServerNames() Method, Acquiring the

Session Key…
Initializing the Site Parameters Web Service
About to Query the GetSiteParameterValue() method

in the Site Parameters Web Service to get OAM
Communication Port
Converting the OAM Communication Port value from

a string to an Integer
Initializing the Administrator Web Service
About to Query the GetPredictiveUsername() method

in the Administrator Web Service to get the SER
Username to login to SER CPSEE
About to Query the GetPredictivePassword() method

in the Administrator Web Service to get the SER
Password to login to SER CPSEE
Initializing the Server Web Service
About to Query the GetServersByType() method in

the Server Web Service to get a list of Servers for the
SER server
Getting the SER CPSEE Server Name from the list
Beginning GetSessionKey() Method, Creating the

Instance of the Utility Multimedia to obtain the Session
Key
Utility Web Reference Instance created. Logging off
the Administrator if it was previously logged in
Administrator was successfully logged off
Logging the Administrator on to obtain the Session

Key
The SER Socket instance was successfully created.
Now setting up connection details to SER CPSEE
Server
Beginning ReadSERData() Method, Reading in the
Agents From SER
Agent Data successfully read in from SER. Now
reading in the Skillsets From SER
Ensuring the HashTables that will contain the SER

data are empty
Now adding the following Skillsets to the Skillset
Hashtable
Adding Skillset:
Now adding the following SER Agents to the SER

Agent Hashtable
Adding Agent (LogonID, Fullname): (
Successfully added all the Skillsets to the HashTable.

Now reading in the Stations From SER
Stations successfully read in from SER. Adding

Stations to the Station Hashtable
Adding Station:
Successfully added all the SER Stations to the

HashTable. Now reading in the Switches From SER
Switches were successfully read in from SER. Finding

out how many Switches are Physical Switches on
SER
Checking if the following Switch is a Physical Switch
or a Simulator Switch:
The following Switch is a Physical Switch:
The current number of Physical Switches found is:
The Physical Switch was successfully set and hence

all the DN Addresses will be assigned to:
There is more than one Physical Switch present on

the SER CPSEE and therefore there isn't a single
Physical Switch will not be used for assigning DN
addresses to
Checking if the OAM Skillset HashTable contains the

following Skillset:
About to clear the SER/OAM Agent and SER/OAM
Skillset HashTables
OAM Socket Instance successfully created. Now
creating the IP End Point
At the end of the SER Thread at a Wait Handle which
is released upon stopping the Predictive Service
Ending ConnectToOAM() Method, SER Thread has

reached its completion point
Beginning OAMBufferTimer_Elapsed() Method
Ending OAMBufferTimer_Elapsed() Method
Beginning Finally part of OAMBufferTimer_Elapsed()

Method
Ending Finally part of OAMBufferTimer_Elapsed()
Method
Beginning mySerSocket_ChannelStatusChanged
Method
Beginning SendDataToOAM() Method, Sending the

following message:
Encoding the data to send
Sending the data to the OAM Component

Data sent to the OAM Component
Beginning CloseOAMConnection() Method, Checking

if the OAM Socket is not Null
Sending Shutdown message to OAM
Closing the OAM Socket
Setting the OAM Socket to Null
Beginning TryReConnectToOAM() Method, Creating

an instance to reference the Predictive Outbound
Service
Checking if the Predictive Outbound Service is in the
process of Stopping or is Stopped
SER Socket instance created. Setting up the Logging

details to the SER CPSEE"
Beginning WriteDataToSER() Method, Attaching XML
Root tags onto the data received from OAM
Component
The Data received with Root XML tags is as follows:
Creating an XML Document instance
Loading the XML data received into the XML

Document instance
Loading of the XML Data successful. Now trying to
Parse the XML data
Ending mySerSocket_ChannelStatusChanged()
Method
Ending ReadSERData() Method
Ending SynchronizeStartUpData() Method
Beginning ConnectToOAM() Method
Beginning WaitForData() Method
Ending WaitForData() Method
Received the 'ShutdownSocket' event from the OAM

Component.
Sleeping for 1 minute before trying to reconnect to the
OAM Component
Entered the ThreadToWriteSkillsetDataToSER()
Method
Will try to Delete Skillset:
Will try to Add Skillset:
Beginning OnDataReceived() Method
Entered the ThreadToWriteAgentDataToSER()

Method
Will try to Delete Agent LogonID: (
Will try to Add Agent (LogonID, Fullname): (
Ending OnDataReceived() Method
Will try to Update Agent (LogonID, Fullname): (
Checking is the Agent Name needs to be updated
Ending SendDataToOAM() Method
Ending CloseOAMConnection() Method
Ending TryReConnectToOAM() Method
Beginning AddAgent() Method, Setting up agent

object
Creating the Agent LogonID:
Checking if the Agent object is not Null, LogonID:
Setting the Agent Fullname to:
Committing the Agent to SER CPSEE
Disposing the Agent object, LogonID:
Ending WriteDataToSER() Method
Beginning WaitForAgentAndSkillsetThreadsToFinish()
Method
Failed to create Agent with Login ID:
Beginning DeleteAgent() Method, Setting up agent

object
Loading the Agent LogonID:
Checking if the Agent object is linked to any other

objects
Agent object is linked to other objects. Checking if its
linked to any Skillset objects
Checking if Agent object is linked to any SAM Groups
Successfully unlinked all objects from the Agent

object
Deleting Agent from the SER CPSEE Server
Committing the Agent deletion to the SER CPSEE

Server
Beginning UpdateAgent() Method, Setting up agent
object
Ending WaitForAgentAndSkillsetThreadsToFinish()
Method
Locked Agent successfully for editing and now
beginning Edit of the Agent object
Ending Edit of the Agent object
Releasing the Lock on the Agent object
Beginning CleanUpAnyActiveThreads() Method
Beginning AddSkillset() Method, Setting up Skillset

object
Creating the Skillset:
Checking if the Skillset object is not Null, Skillset:
Committing the Skillset to SER CPSEE
Disposing the Skillset object, Skillset:
Ending CleanUpAnyActiveThreads() Method
Beginning ThreadToWriteSkillsetDataToSER()
Method
Beginning DeleteSkillset() Method, Setting up Skillset
object
Loading the Skillset:
Checking if the Skillset object is linked to any other

objects
Skillset object is linked to other objects. Checking if it
is linked to any User objects
Skillset object has a Work Session linked to it.
Unlinking the following Worksession:
Deleting Skillset from the SER CPSEE Server
Committing the Skillset deletion to the SER CPSEE

Server
Ending ThreadToWriteSkillsetDataToSER() Method
Beginning ThreadToWriteAgentDataToSER() Method
Ending ThreadToWriteAgentDataToSER() Method
Ending AddAgent() Method
Ending DeleteAgent() Method
Beginning IsServiceStopping() Method, Creating an

instance to reference the Predictive Outbound Service
Ending UpdateAgent() Method
Ending AddSkillset() Method
Ending IsServiceStopping() Method, Returning true as

the Predictive Outbound Service is stopping
Ending IsServiceStopping() Method, Returning false
as the Predictive Outbound Service is still running
Entered GetEventCodesFromFile() method
Created new instance for the XML Document for the

Event Error Codes
The Directory Path for the Event Codes isn't set,
querying registry…
Registry Instance created
Query root Installation Path of Nortel Software
Path found to be:
Closing Registry Instance
Could not access the registry to find the Nortel

Contact Center Install Location.
Loading the Event Error Codes XML File…
File Loaded. Reading in the Event Error Code

events…
The Total number of Error Event Codes read was:
Unable to open the XML file that contains the Event

Error Codes, Exception:
Ending DeleteSkillset() Method
Ending LinkAgentToSkillset(string LoginID, string

SkillsetName) Method
Ending LinkAgentToSkillset(List(string) LoginIDs,
string SkillsetName) Method"
Ending UnLinkAgentFromSkillset(string LoginID)
Method
Ending UnLinkAgentFromSkillset(string LoginID,
string SkillsetName) Method
Managed to catch a change in the connection status
for the SER socket, will check if we need to re-
connect…
According to Changed Channel Status, the SER
Socket Connection Status and Channel Status are
(Socket Connection Status, Channel Status):
The SER Socket Connection to the SER CPSEE has

been restored
The SER Socket Connection to the SER CPSEE is
not connected
Channel Exception:
Channel Inner Exception:
Ending UnLinkAgentFromSkillset(List(string)
LoginIDs, string SkillsetName) Method
Service is going down returning false
The WaitForDataSERStartUp trigger didn't signal,

continuing…
Checking if the OAM Buffer Timer is enabled
Stopping the OAM Buffer Timer
OAM Buffer Timer stopped
Disposed OAM Buffer Timer
Predictive Service is in the process of stopping,

aborting the reset of the timer
The Service is still running, continuing the OAM
connection loop
Beginning WaitOneMinToConnectToSER() Method
Ending WaitOneMinToConnectToSER() Method
Predictive Service is stopping, Breaking out of the

OAM connection loop
aborting the waitfordata() recall
The OAM Socket is still connected
The OAM Socket is NOT connected
EndReceive returned nothing, closing the socket

aborting the skillset stage
The waiting for the Skillset was successful and
service still running
The waiting for the Skillset has returned false and
service is shutting down
aborting the agent stage
Mapping XML:
Mapping SkillsetName:
Mapping LogonID:

aborting the link stage
Predictive Service is still running, adding Logon IDs to
the Skillset:
aborting the unlink stage
Predictive Service is still running, unlinking Logon IDs
from the Skillset:
aborting the
WaitForAgentAndSkillsetThreadsToFinish stage
Unable to Write Skillset as there is no Skillset Name

passed from OAM or One of these isn't true:
Unable to Write Agent as there is no Login ID passed

from OAM or One of these isn't true:
Checking if the OAM Skillset HashTable contains the

following Agent LoginID:
aborting the writedatatoser stage

aborting the SynchroniseStartUpData stage
About to Set the WaitForDataSERStartUp event

handle
Set the WaitForDataSERStartUp event handle
Method, Predictive Service is in the process of
stopping, aborting the wait for Skillset Threads to
finish stage
stopping, aborting the wait for Skillset Threads to
finish stage
stopping, aborting the wait for Agents Threads to
finish stage
stopping, aborting the wait for Agents Threads at end
of method to finish stage
The Following Skillset thread is still running (
The Following Skillset thread was cleaned up (
The Following Agent thread is still running (
The Following Agent thread was cleaned up (
The following Login ID exists:
Failed to get the Name of the User from the SER

CPSEE
Failed to get the Name of the User from the SER
CPSEE
The LoginID doesn't exist:
The following are already linked:
The Skillset doesn't exist:
The Login ID is not linked to this Skillset:
The Login ID is not linked to a Skillset:
The following Login ID was linked to a different

Skillset:
aborting the WaitForOneMinuteIfServiceActive stage
Retrying Connection to the OAM Component using

the TryReConnectToOAM() Method after a 1 minute
interval
Calling the ReadSERData() Method again
ReadSERData() Could load the following SER Switch

object:
The SER Agent Name didn't require any updates
ReadSERData() The following SER Switch object is a

simulator Switch:
ReadSERData() Disposing the following SER Switch
object:
Checking if Agent object is linked to any Stations
Agent linked to Station. Unlinking Logon ID:
The Agent Skillset Mapping exists on SER CPSEE

(Agent, Skillset): (
The Agent Skillset Mapping does not exists on SER
CPSEE (Agent, Skillset): (
The following Agent has not Skillset assigned to it,
LoginID:
No data received from the OAM
There has been a communication error. The current

length of the grace period is displayed. There is a
maximum of 10 days allowed.
There has been a communication error. The current

length of the grace period is displayed. There is a
maximum of 10 days allowed.
The error condition between the License Manager

and client has been resolved.
Communication is okay. The length of time remaining
in the grace period is displayed.
Grace period has expired due to the inability to

communicate with the License Manager. Client
application is shut down.
If attempting to reset the grace period, the code

entered in the Reset Grace Period tool is incorrect.
The length of time remaining in the grace period is

displayed.
Recovery
Action Type
Error
Error
Error
Error
Error
Error
Error
Warning
Warning
Warning
Warning
Error
Warning
Critical
Warning
Warning
Warning
Warning
Warning
Warning
Warning
Communication Control Toolkit
Event
1001 CCT Server Information


1009 CCT Server Minor
1011 CCT Server Major

1033 CCT Server Critical


1045 CCT server Major




3100 TAPI Connector Major
3200 TAPI Connector Critical


3300 TAPI Connector Minor

3614 TAPI Connector Information

4098 TAPI Service Information
Provider
4099 TAPI Service Warning
Provider
4100 TAPI Service Information
Provider
4101 TAPI Service Error
Provider

Provider
Provider
Provider
Provider
4117 ACDProxy Info/Warning
4118 ACDProxy Information

4119 ACDProxy Information
5000 NCCT Logging Information
Service
Service
Service
Service

Service
Service
Service
Service
Service
5100 NCCT Logging Error
Service
Service
Service

Service
Service
Service
Service
Service
6000 DAL Major
6005 DAL Information


100 NCCT SMON Error
101 NCCT SMON Error
102 NCCT SMON Error

103 NCCT SMON Warning
104 NCCT SMON Information
105 NCCT SMON Information

Communication Control Toolkit event codes
Probable
CCT server starting (<version info>). Informational message
Connected to CMF (<version info>). Informational message
CMF Contact Manager acquired: ID={o}, Master Informational message

Status={1}
CMF provider acquired: ID={0}, MasterStatus={1}, Informational message
State={2}, ContactTypes={3}
CCT server startup complete ({0}). Informational message
CCT server shutting down. Informational message

CCT server shutdown complete. Informational message
CMF provider released. Informational message
Service provider has gone in-service. Informational message

Service provider has gone out-of-service. [Reason: {0}] All devices (such as addresses and terminals) associated
with the service provider cannot be controlled by CCT until
the service provider returns to service.
Service provider has shut down. All devices (such as addresses and terminals) associated
the service provider is restarted and returns to service.
CMF Contact Manager not found. No multimedia agent support will available in CCT.
CMF provider "{0}" not found. All devices (such as addresses and terminals) associated
the service provider object is located in the CMF and
returns to service.
Unable to find consult contact {0} in the CMF. The impact should be localized to a single contact.
Terminal mapped to CCT user has an unknown provider: The specified terminal will remain out of service.
Terminal={0}, Provider={1}
Terminal associated with Contact Center user has an The specified terminal will remain out of service.
unknown provider: Terminal={0}
Terminal associated with Contact Center user has an The specified terminal will remain out of service.
unknown provider: Terminal={0}, Provider={1}
Address mapped to CCT user has an unknown provider: The specified address will remain out of service.
Terminal={0}, Provider={1}
Terminal mapped to CCT user cannot be found: The specified terminal will remain out of service.
Terminal={0}
Address mapped to CCT user cannot be found: The specified terminal will remain out of service.
Address={0}
{0} Contact Center user(s) mapped to CCT user cannot The affected Contact Center user objects will not appear
be found. in the CCT user's session.
User session has no active resources associated. Check The CCT session will have no resources to control.
configuration.
Address related to terminal not found: Terminal={0}, The terminal will have an incomplete set of addresses
Related Address={1} associated with it.
Service Provider Status Event Error: providerName is Possible loss of all CCT functionality
null
or
Service Provider Status Event Error: statusType is null
or
Provider State Event Error: provider is null
Connection State Event Error: {0} is null Incorrect connection state displayed on CCT clients and/or
or stale contacts left around.
Connection State Event Error: (State={0}): {1} is null
or
Connection State Event Error (State={0}: Contact {1} has
already been deleted.
TerminalConnection State Event Error: {0} is null Incorrect terminal connection state displayed on CCT
or clients and/or stale contacts left around.
TerminalConnection State Event Error: (State={0}): {1} is
null
or
TerminalConnection State Event Error (State={0}):
Contact {1} has already been deleted.
Address Property Event Error: property=null CCT clients do not receive all the address property events
that are expected.
Terminal Property Event Error: property=null CCT clients do not receive all the terminal property events
that are expected.
Contact Property Event Error: property=null or Contact CCT clients do not receive all the contact property events
Property Event Error: contact=null that they expect.
Connection Property Event Error: property=null or CCT clients do not receive all the connection property
Connection Property Event Error: contact=null events that they expect.
Null contact reference in ContactReferenceArray or Got Failures or unexpected results occur when conference or
null ControllerTerminalConnectionID from contact transfer features are invoked by CCT clients.
reference.
TerminalConnection received from the CMF with a null CCT clients do not receive all the terminal connection
connection: ID={0} state events that are expected.
<JAVA exception type>\n--------\nCONTEXT: <object Possible loss of CCT functionality
causing exception>\nCAUSE: <what caused
exception>\nJAVA EXCEPTION: <java exception stack
trace>
<.NET exception stack trace>\n--------\nCONTEXT: Possible loss of CCT functionality
<object causing exception>\nCAUSE: <what caused
exception>
Event delivery thread {0} has exited. No impact if seen as part of a system shutdown.
Otherwise, a brief loss of events to one CCT client may
occur.
Contact Center User \"{0}\" mapped to CCT user does The CCT user cannot use the specified Contact Center
not exist in the CMF users.
or
{0} Contact Center Users ({1}) mapped to CCT user do
not exist in the CMF.
User Property Event Error: property=null CCT clients do not receive all the agent property events
that they expect.
Failed to acquire a {0} license for {1} : LimitExceeded The voice terminal specified by {1} will be out of service.
Failed to acquire a {0} license for {1} : {2} The voice terminal specified by {1} will be out of service.
Master CCT license acquired. Informational message

Failed to acquire master CCT license: LimitExceeded CCT clients cannot connect.
Terminal mapped to CCT user with no related address The specified terminal will not be part of the CCT user's
mapped. Access to terminal "{0}" not granted. available devices.
Address mapped to CCT user with no related terminals The specified address will not be part of the CCT user's
mapped. Access to address "{0}" not granted. available devices.
CCT server startup failed - see exception logs. CCT is not operational.
CCT/CMF terminal type mismatch for terminal {0}: The terminal will not be available for use by CCT clients.
CCT={1}, CMF={2}.
CCT API service endpoint started with public address Informational message
"{0}". [Maximum Sessions: {1}]
CCT API service endpoint stopped. Informational message
Communication with the License Manager is operational Informational message
or
Communication with the License Manager is unknown
or
Communication with the License Manager has been
restored.
Null contact reference in ContactReferenceArray or Got No impact until the grace period expires.
null ControllerTerminalConnectionID from contact
reference.
The grace period for restoring communication with the CCT is not operational.
License Manager has expired.
The performance counter category "{0}" does not exist No operational impact other than a loss of performance
or counters.
The performance counter category "{0}" appears to be
disabled
or
Unable to verify performance counter category "{0}". No
OMs will be collected for this category.
Contact State Event Error: {0} is null Possibility for stale contacts to be left around
or
Contact State Event Error: (State={0}): {1} is null
Contact Force Timer Event Error: connection=null CCT clients do not receive all the ForcedAnswer events
or that they expect.
Contact Force Timer Event Error: Connection has a null
contact
or
terminal connection array
or
Contact Force Timer Event Error: A terminal connection
is not to an agent terminal
or
address.
Unable to read JavaHome for JRE {0}. CCT is inoperable.
Unable to read version and variant of JRE required. CCT is inoperable.
The client endpoint cannot be determined. Please NCCT security logs cannot display the IP address of the
ensure that the .NET Framework Version 3.5 is installed. client that is connected to the server.
A database error has occurred performing the operation: CCT is inoperable.

{0}
Failed to acquire master CCT license: {0} CCT clients cannot connect.
Failed to release master CCT license None likely

Failed to release a {0} license for {1} : {2} Licenses may not be able to be acquired later.
The CMF has recovered from a replication failure: {0} Possible loss of service
CCT session startup failed: The maximum capacity of {0} The affected CCT client will fail to connect to the CCT
{1} resources has been reached. These resources are server.
currently being consumed by {2} active sessions.
Addition of resources to session failed: The maximum The affected CCT client will not see the new recourses
capacity of {0} {1} resources has been reached. These that have been assigned.
resources are currently being consumed by {2} active
sessions.
Failed to read parameters for CMF request: <request CCT request fails
type>
Failed to set external ID for CMF request: <request CCT request fails
type>
An unexpected error occurred during processing of CMF CCT request fails
request: <request type>
<request type> error: No address found for terminal %s. The request made by the CCT application failed due to a
CommServerError.
<request type> error: No forwarding instructions in The terminal forwarding the instructions request made by
request. the CCT application failed due to a CommServerError.
An unexpected error occurred during processing of a CCT request fails

service provider request.
Failed to initialize CMF logger. CCT is inoperable.
Failed to create CMF peer object. CCT is inoperable.
Failed to initialize peer object. CCT is inoperable.
Failed to create CMF provider object. CCT is inoperable.
Failure during installation of CMF request listeners. CCT is inoperable.
Failed to set static <object type> capabilities. CCT client applications may not operate correctly.
Failed to set provider to IN_SERVICE state. CCT is inoperable.
Failed to set initial "Do Not Disturb" state for terminal The DN state for the specified terminal may be incorrect.
"%s".
Failed to set initial "Forwarding" state for terminal "%s". The forwarding state for the specified terminal may be
incorrect.
Setup of initial device states failed. The DND or forwarding state of one or more terminals
may be incorrect.
Failed to set initial agent state for terminal "%s" The logged in or the ready status of one or more agent
or terminals may be incorrect.
Failed to set initial agent states.
Failed to remove (logout) agent from terminal "%s". The logged in status of the agent terminal may be showing
an incorrect state.
An unexpected error occurred while processing a "%s" One or more of the properties associated with the
event for terminal "%s". specified terminal may be incorrect.
Failed to update <ReadyStatus | The ready status or not ready reason code (or both)
NotReadyReasonCode> on terminal "%s". showing on the terminal may be incorrect.
Failed to update ActivityCode on terminal "%s". The activity code showing on the terminal may be
incorrect.
Failed to set state to %s on connection to address %s. The connection to the specified address may appear to be
in the incorrect state.
Attempted invalid state transition from %s to %s on The connection to the specified address may appear to be
connection to address %s. in the incorrect state.
Attempted invalid state transition from %s to %s on The terminal connection to the specified address may
terminal connection to address %s. appear to be in the incorrect state.
Failed to remove contact from the CMF. Possible stale contacts appearing on CCT client
applications.
Failed to create connection/terminal-connection in the Inaccurate contact state information appearing on CCT
CMF. client applications
Failed to remove Contact Reference from contact %s. Inaccurate transfer or conference state information
appearing on CCT client applications
Failure during processing of call event: %s Inaccurate contact state information appearing on CCT
client applications
Failed to create contact %ld (%#lx) in the CMF. The contact does not appear on CCT client applications.
Failed to set up %s contact references for consult Inaccurate transfer or conference state information
contact %s. appearing on CCT client applications
Failed to set CallingAddress on contact. Inaccurate CallingAddress property seen on a contact.
Failed to set CalledAddress on contact. Inaccurate CalledAddress property seen on a contact.
Failed to set CallingAlias(DNIS) on contact. Inaccurate OriginalDestination property seen on a contact
Failed to add address "%s" to the CMF. The specified address will not be usable in CCT.
Failed to add address to terminal in the CMF. Address: The specified address will not be usable in CCT.
"%s", Terminal: "%s"
Failed to add terminal "%s" to the CMF. The specified terminal will not be usable in CCT.
Failed to remove address "%s" from the CMF. Potential resource shortages or problems can be
encountered if the address is re-added at a later date.
Failed to remove terminal "%s" from the CMF. Potential resource shortages or problems can be
encountered if the terminal is re-added at a later date.
Failed to create treatment address "%s" in the CMF. A contact currently controlled at a Route Point Address
may have an incorrect treatment type displayed.
Failed to create treatment terminal "%s" in the CMF. A contact currently controlled at a Route Point Address
may have an incorrect treatment type displayed.
Failed to read AttachedData from contact. Data attached to a contact may be incorrect.
Failed to set AttachedData on contact. Data attached to a contact may be incorrect.
Failed to open address "%s". TAPI error code: %#lx. The specified address will not be usable in CCT.
TAPI configuration mismatch: <error text> Missing or inoperable addresses or terminals in CCT.
<address type> address \"%s\" is mapped to %d enabled The specified address will not be usable in CCT.
terminals. This address will not be available until it is
mapped to exactly one terminal.
<terminal type> terminal "%s" is mapped to %d The specified terminal will not be usable in CCT.
addresses. This terminal will not be available until it has
been mapped to 1 or 2 addresses.
RoutePoint address "%s" is mapped to %d terminal(s). The specified Route Point Address will not be usable in
This address will not be available until the terminal CCT.
mappings are removed.
Database error: <error text> CCT may be unusable.
Failed to set up address<->terminal relationship "%s"<- The specified address and terminal will not be usable in
>"%s". The <address|terminal> does not exist in the CCT.
CMF.
Found address<->terminal relationship "%s"<->"%s" None

already existing in the CMF.
Could not obtain JRE path from registry. CCT is inoperable.
Failed to connect to the CCT database. CCT is inoperable.

Please make sure that the NCCTDALS service is
running and that the CCTTapiC.exe.config file is present.
Initialization failed. Please make sure the NCCTDALS CCT is inoperable.

service is running and restart the NCCT TAPI Connector
Service.
No enabled terminal found mapped to address "%s" in The specified address will not be usable in CCT.
the CCT database.
No enabled address(es) found mapped to terminal "%s" The specified terminal will not be usable in CCT.
in the CCT database.
No terminal matching "%s" was found in the CCT The specified terminal will not be usable in CCT.
database.
No enabled address matching "%s" was found in the The specified address will not be usable in CCT.
CCT database.
%sTerminal "%s" is mapped to a RoutePointAddress in The specified terminal will not be usable in CCT.
the CCT Database. The terminal will not be added to the
CMF
or
%sTerminal "%s" is not mapped to any enabled
addresses in the CCT Database. The terminal will not be
added to the CMF
or
%sTerminal "%s" is mapped to more than two enabled
addresses in the CCT Database. The terminal will not be
added to the CMF.
%sAddress "%s" is mapped to %d enabled terminal(s) in The specified address will not be usable in CCT.
the CCT database. This address will not be added to the
CMF.
Failed to send success response for <request type> A CCT client request may receive a timeout error.
[Req: %ld]
or
Failed to send failure response for <request type> [Req:
%s]
Failed to delete contact object %ld. Memory leak or possible problems creating contacts in the
future.
Performance warning: deadline for setting master status The voice devices may go out of service.
to ENABLED missed by %dms.
The call event queue has increased to a minor level CCT client applications may be slow in displaying contacts
(Current=%ld, Peak=%ld). to the users.
The call event queue has increased to a major level CCT client applications may be slow in displaying contacts
(Current=%ld, Peak=%ld). to the users.
The call event queue has increased to a critical level CCT client applications may be slow in displaying contacts
(Current=%ld, Peak=%ld) to the users.
or
The call event queue is at a critical level and has peaked
higher (Current=%ld, Peak=%ld).
The call event queue has returned to a normal level Informational message
(Current=%ld, Peak=%ld).
The call event queue has decreased to a minor level None
The call event queue is no longer at critical levels None
Service failed to create provider. CCT is inoperable.
CCT TAPI Connector IN_SERVICE (Version %s). Informational message

[Waiting for initialization to complete.]
CCT TAPI Connector Initialized Informational message
CCT TAPI Connector IN_SERVICE Informational message
CCT TAPI Connector Service Stopped. Informational message

TAPI SP is shut down. Informational message
Link loss detected. All CCT lines go out of service.
TAPI SP has reinitialized. Informational message
TAPI SP has failed to initialize CCT lines are out of service.
TAPI SP - Memory allocation failure. A CCT operation has failed.
Error processing sockets. A CCT operation may have failed.
TAPI SP Failed to Shutdown. The TAPI SP shutdown has not completed within the
allotted timeout period.
TAPI SP Timeout problem. A CCT operation has failed.
ACDProxy number of lines opened and failed to open. Informational message. Any lines that failed to open will
be out of service in CCT.
ACDProxy service started. Informational message
ACDProxy Initialization complete. Informational message
NCCT Logging Service is running. Informational message
NCCT Logging Service is stopped. Informational message
NCCT Logging Service installation finished Informational message
NCCT Logging Service removal The Logging service has been removed and will no longer
run. No more trace logs will be written by the NCCT
components.
Starting logging for log <component_name> Informational message
Stopping logging for log <component_name> Informational message
Initializing output for <filename> Informational message
Reader shutting down: <component_name> Informational message
Registry Changed Informational message
Could not create service Cannot install NCCT Logging Service
Could not [create|open|read|write <value_name> to] Cannot configure the NCCT Logging Service
registry key <key_name>.
Failed to open file <filename> Cannot log messages to file
FileName too long: <filename> Cannot log messages to file
Wait [failed|abandoned] . Ending logging for log Logging for the component has stopped.
<component>
Couldn't create a reader for stream <component> Cannot log messages to file
NCCT Logging Service EventLoggerSingleton NCCT Logging Service events will be logged to the
constructor: error accessing NCCT Error log Application event log instead of to the NCCT Error log.
Fatal error in NCCT Logging service NCCT Logging Service cannot continue. No more trace
(EventLoggerSingleton constructor) logs will be written.
Cannot read from or write to Database Cannot configure CCT
Resource Added CCT resource change

Resource Deleted CCT resource change
Resource Updated CCT resource change
Resource Mapped CCT resource change
Resource UnMapped CCT resource change
Resource UnMapped User From: CCT resource change
Mapped Address to User Group CCT resource change
Mapped Address to Terminal CCT resource change
UnMapped Address from User Group CCT resource change
UnMapped UserGroup from Agent CCT resource change
UnMapped Address from Terminal CCT resource change
UnMapped Address from Terminal Group CCT resource change
Mapped Terminal to User Group CCT resource change
UnMapped Terminal from User Group CCT resource change
Mapped UserGroup to Terminal Group CCT resource change
Mapped User Group from Terminal Group CCT resource change
Mapped UserGroup to Address Group CCT resource change
Mapped UserGroup to Agent Group CCT resource change
UnMapped User Group from Address Group CCT resource change
Mapped Terminal to Work Station CCT resource change
Update Snapin logging file details Logging configuration change
Update DAL logging file details Logging configuration change
Update CCT Server logging file details Logging configuration change
Update SMON logging file details Logging configuration change
Update TAPI Connector logging file details Logging configuration change
Update TAPI SP logging file details Logging configuration change
Update CMF Settings CCT CMF change
Update License Manager Settings CCT LM change
Update TAPI SP for CS1000 Provider CCT CS 1000 configuration change
Update TAPI SP for CS1000 Host CCT CS 1000 configuration change
Update TAPI SP for CS1000 Host Machine CCT CS 1000 configuration change
Update TAPI SIP for CS1000 Host Association CCT CS 1000 configuration change
Delete Network/IVR from TAPI for CS1000 CCT CS 1000 configuration change
Update TAPI SP for CS1000 Network/IVR CCT CS 1000 configuration change
Add Network/IVR to TAPI SP for CS1000 CCT CS 1000 configuration change
Failed to start service The indicated CCT service is not started, which is likely to
leave CCT inoperable. SMON will keep retrying.
Failed to start service in a timely fashion The indicated CCT service is not started, which is likely to
leave CCT inoperable. The service may start, given more
time.
Failed to stop service Informational message
SMON failed to stop service in a timely fashion. Service Informational message
killed.
Starting SMON, so starting the following services: Informational message
Stopping SMON, so stopping the following services: Informational message
Restart attempt n of n. Restarting the following services: Informational message
Stopping SMON timed out, so killing the following Informational message

services:
Recovery
Action Type
NCCT Error Log
NCCT Error Log
NCCT Error Log
NCCT Error Log
NCCT Error Log
NCCT Error Log

NCCT Error Log
NCCT Error Log
NCCT Error Log

NCCT Error Log
NCCT Error Log
NCCT Error Log
NCCT Error Log
NCCT Error Log
NCCT Error Log
NCCT Error Log
NCCT Error Log

NCCT Error Log
NCCT Error Log
NCCT Error Log
NCCT Error Log
NCCT Error Log
NCCT Error Log
NCCT Error Log
NCCT Error Log
NCCT Error Log
NCCT Error Log
NCCT Error Log
NCCT Error Log
NCCT Error Log
NCCT Error Log
NCCT Error Log
NCCT Error Log

NCCT Error Log
NCCT Error Log
NCCT Error Log
NCCT Error Log
NCCT Error Log
NCCT Error Log
NCCT Error Log

NCCT Error Log
NCCT Error Log
NCCT Error Log
NCCT Error Log
NCCT Error Log
NCCT Error Log
NCCT Error Log

NCCT Error Log
NCCT Error Log
NCCT Error Log

NCCT Error Log
NCCT Error Log
NCCT Error Log
NCCT Error Log
NCCT Error Log
NCCT Error Log
NCCT Error Log
NCCT Error Log
NCCT Error Log

NCCT Error Log
NCCT Error Log

NCCT Error Log
NCCT Error Log
NCCT Error Log
NCCT Error Log
NCCT Error Log
NCCT Error Log
NCCT Error Log
NCCT Error Log
NCCT Error Log
NCCT Error Log
NCCT Error Log
NCCT Error Log
NCCT Error Log
NCCT Error Log
NCCT Error Log
NCCT Error Log
NCCT Error Log
NCCT Error Log

NCCT Error Log
NCCT Error Log
NCCT Error Log
NCCT Error Log
NCCT Error Log
NCCT Error Log
NCCT Error Log
NCCT Error Log
NCCT Error Log
NCCT Error Log
NCCT Error Log
NCCT Error Log
NCCT Error Log
NCCT Error Log
NCCT Error Log
NCCT Error Log
NCCT Error Log
NCCT Error Log
NCCT Error Log
NCCT Error Log
NCCT Error Log
NCCT Error Log
NCCT Error Log

NCCT Error Log
NCCT Error Log
NCCT Error Log
NCCT Error Log
NCCT Error Log
NCCT Error Log
NCCT Error Log
NCCT Error Log
NCCT Error Log
NCCT Error Log
NCCT Error Log
NCCT Error Log
NCCT Error Log
NCCT Error Log
NCCT Error Log
NCCT Error Log
NCCT Error Log
NCCT Error Log

NCCT Error Log
NCCT Error Log
NCCT Error Log
NCCT Error Log
NCCT Error Log
NCCT Error Log
NCCT Error Log
NCCT Error Log
NCCT Error Log
NCCT Error Log
NCCT Error Log
NCCT Error Log
NCCT Error Log
NCCT Error Log
NCCT Error Log
NCCT Error Log

NCCT Error Log
NCCT Error Log
NCCT Error Log
NCCT Error Log
NCCT Error Log
NCCT Error Log
NCCT Error Log
NCCT Error Log
NCCT Error Log
NCCT Error Log
NCCT Error Log
NCCT Error Log
NCCT Error Log
NCCT Error Log
NCCT Error Log
Application log
Application log
NCCT Error Log
NCCT Audit Log

NCCT Audit Log
NCCT Audit Log
NCCT Audit Log
NCCT Audit Log
NCCT Audit Log
NCCT Audit Log
NCCT Audit Log
NCCT Audit Log
NCCT Audit Log
NCCT Audit Log
NCCT Audit Log
NCCT Audit Log
NCCT Audit Log
NCCT Audit Log
NCCT Audit Log
NCCT Audit Log
NCCT Audit Log
NCCT Audit Log
NCCT Audit Log
NCCT Audit Log
NCCT Audit Log
NCCT Audit Log
NCCT Audit Log
NCCT Audit Log
NCCT Audit Log
NCCT Audit Log
NCCT Audit Log
NCCT Audit Log
NCCT Audit Log
NCCT Audit Log
NCCT Audit Log
NCCT Audit Log

NCCT Audit Log
NCCT Audit Log
Application
Application
Application
Application
Application
Application
Application
Application

NN44400-713 01.03 FAULT Event Codes

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

NN44400-713 01.03 FAULT Event Codes

Uploaded by

Copyright:

Available Formats

Nortel Contact Center 7.0 Event Codes Version 01.

Copyright © 2009 Nortel Networks. All Rights Reserved.

41002 NGEN Performance Critical OM Server Startup Failed. RC=

41065 NGEN Performance Critical Failed to start RPC Server. rc=

41552 NGEN System Critical The SM could not query

41559 NGEN System Critical Too many services.

42510 TSM Major %nvs: Link state changed to

42605 TSM Minor Server logon to switch attempt

42606 TSM Minor Server logon to switch attempt

42609 TSM Minor Server logon to switch attempt

42610 TSM Minor Server logon to switch attempt

42612 TSM Minor Switch rejected the logon

42613 TSM Minor Server logon to switch attempt

42614 TSM Critical Server is unable to log onto the

42615 TSM Information ELAN connection with switch

42616 TSM Major ELAN connection with switch

42617 TSM Information Logon to the switch was

42618 TSM Major Switch is not responding.

42619 TSM Minor Unexpected CONNECTION

42620 TSM Critical Dongle check failed.

42621 TSM Minor Insufficient amount of disk

42622 TSM Critical ACCESS LINK is DOWN

42652 TSM Major IVR initialization failure.

42654 TSM Major Server has refused connection

42672 TSM Major IVR port not monitored.

42673 TSM Major Too much data received from

42674 TSM Major Calls queued in system have

42675 TSM Information Calls queued in system have

42676 TSM Critical Voice processing Meridian Mail

42677 TSM Critical AML link failure owing to

42678 TSM Major Communication error between

42679 TSM Information Switch link up.

42680 TSM Critical Switch link down.

42683 TSM Major Switch has initialized after

42684 TSM Minor Switch overload (flow control

42685 TSM Minor Switch overload (flow control

42686 TSM Major Switch overload (flow control

42687 TSM Information Overflow condition has been

42689 TSM Minor Insufficient amount of disk

42690 TSM Minor Insufficient amount of disk

42691 TSM Minor Insufficient amount of disk

44903 RSM Major System failed to launch RSM

44906 RSM Minor RSM is not enabled in

45019 OAM Information Service has started.

45023 OAM Information Service is stopping.

45145 Network Information NCC is in Configuration mode.

45300 TOOLKIT Critical Failed to start service due to

45304 TOOLKIT Critical "%ads"

45305 TOOLKIT Major %nvs, WaitForMultipleObject()

45320 TOOLKIT Information A Toolkit service has started,

45321 TOOLKIT Information A Toolkit service has started,

45322 TOOLKIT Information A Toolkit service has started,

45323 TOOLKIT Information A Toolkit service has started,

45324 TOOLKIT Information A Toolkit service has started,

45325 TOOLKIT Information A Toolkit service has started,

45326 TOOLKIT Information A Toolkit service has started,

45327 TOOLKIT Information A Toolkit service has started,

45329 TOOLKIT Information A Toolkit service has started,

45330 TOOLKIT Information A Toolkit service has started,

45331 TOOLKIT Information A Toolkit service has started,

45332 TOOLKIT Information A Toolkit service has started,

45333 TOOLKIT Information A Toolkit service has started,

45334 TOOLKIT Information A Toolkit service has started,