Error Log Manual: Mitel Nupoint Messenger Technical Documentation - Release 7.0

Mitel NuPoint Messenger Technical Documentation - Release 7.
Error Log Manual

NuPoint Messenger
DOCUMENT HISTORY
Revision Date Issued Part Number
Revision A January 1988 2700-1397-01
Issue 1 November 1999 2700-1397-B1
Contents ©Copyright 2002, Mitel Networks Corporation
Distributed Courtesy of
http://www.promemoinc.com
P.O. Box 1899

Brentwood, CA 94513
Main: (925) 513-7510
Fax: (925) 775-7039
Support: support@promemoinc.com
Sales: sales@promemoinc.com
General: info@promemoinc.com
©Copyright 2002, Mitel Networks Corporation 1

Mitel NuPoint Messenger Technical Documentation - Release 7.0
About This Manual

This manual is divided into three sections:
• The first section contains all error messages that begin with special characters and numbers,
for example, ***, \, 2.
• The second section contains all error messages that begin with letters, which are listed in
alphabetical order according to the first letter in the error message.
• The third section contains all error messages that begin with special variables, for example,
%s, %d, [%.
Each error message description is divided into four sections: message, description, severity, and
action.
Messages
The message section contains the actual message printed in the logfile. The message text
appears in bold.
Message Conventions
If a variable field appears within the message, one of the following notations can be found in the
message text: i, x, y, nnnn, xxx, %d, %s, %t, %02x, %04x, %02d, %04d, %08ld, %lx, and so on.
Description
The description section contains a brief description of the error.
Severity
The severity section assigns one of four designations to the error at hand. The possible
severities are P1, P2, P3, and P4, with P1 being the most severe. The implications of these error
messages to the NuPoint Messenger server are as follows:
P1 The server is down or the system requires immediate attention.
P2 The server is up. However, there are major service impacts. Therefore, 20% or
more of the ports are down, or 20% or more of the contacts are not being
serviced correctly.
P3 The server is up. However, there are minor service impacts. Therefore, less
than 20% of the ports are down, or less than 20% of the contacts are not being
serviced correctly.
P4 The server is up, and the error is benign. No action is required.
Action
The action section tells you what to do when the specified error message appears in the logfile.
In general, you should check the server configuration as well as collect and check available error
data before contacting your Support Representative.

Special Character and Numeric
(irq) out-of-window collision (bad hardware)
Description: This error message is reported by QNX. This problem is caused by out-of-
specification hardware or cabling on your network. The most likely cause of
these out-of-window problems is the use of a low-quality mini-hub. Out-of-
window problems occur when certain Ethernet timing specifications are
violated. This could be caused by: Lower quality mini-hubs, cabling whose
length exceeds the maximum permitted or cascading too many hubs in
series.
Severity: P4
Action: Check your network cable length and hubs.
*** DBN: scan died
Description: Either the scan died (scan is the task holding the dial-by-name database) or
an arcnet problem exists if it is a multi-host.
Severity: P3
Action: If it is a multi-host situation, check the arcnet. Look for the death of the scan
in the logfile. Then reset the system. If the problem persists, contact your
Support Representative.
*** DBN: send to scan failed
Description: Either the scan died (scan is the task holding the dial-by-name database) or
an arcnet problem exists if it is a multi-host.
Severity: P3
Action: If it is a multi-host situation, check the arcnet. Look for the death of the
scan in the logfile. Then reset the system. If the problem persists, contact
your Support Representative.
*** DTA_AGENT: Unable to attach name!
Description: An attempt to register the DTA_AGENT process failed.

Severity: P2
Action: If the problem persists, contact your Support Representative
*** DTA: Unable to attach name!
Description: An attempt to register the DTA process failed.

Severity: P2
Action: Contact your Support Representative if the problem persists.
*** GL_QUE: Another GL_QUE is running in the system, Abort
Description: An internal error exists.

Severity: P1
Action: Contact your Support Representative.
*** GL_QUE: can not register with master

Severity: P1
*** GL_QUE: invalid queue index %d

Severity: P1
*** GL_QUE: no memory available for global queues, abort
Description: The system is out of memory.

Severity: P1
Action: Add more memory.
*** GL_QUE: res %d GL_SB %d differ

Severity: P3
HOLD queue is full. Reqs will be discarded.
Description: There is a problem manipulating the request queue.

Severity: P1
*** NETQ: Unable to attach name!
Description: An attempt to register the NETQ process failed.

Severity: P2
*** NETQ_AGENT: Unable to attach name!
Description: An attempt to find the named process used to establish communication

failed.
Severity: P2
*** NTA_AGENT: Unable to attach name!
Description: An attempt to register the NTA_AGENT process failed.

Severity: P2
*** QUE_RELAY: invalid queue index %d

Severity: P1

*** QUE_RELAY: Out of queue %d space

Severity: P1
*** QUE_RL: rl_agent died, commit suicide

Severity: P1
*** RAM ***: could not register to master, abort

Severity: P1
*** ram at Node %d: Out of queue %d space

Severity: P4
*** RAM: agent is dead, commit suicide
Description: The ram_agent died for some reason, causing ram to exit.
Severity: P4
*** RAM: Another ram is running in the system, Abort

Severity: P4
*** RAM: Could not attach RAM PORT %d, abort

Severity: P4
*** RAM: Could not spawn ram_agent, abort
Description: Ram is unable to start up agent task.

Severity: P1
*** RAM: For task %d:%04x, RAM req %d, OAA req %d

Severity: P4
*** RAM: get a unknown result %d

Severity: P4
*** RAM: No memory for directory buffer
Description: There is a shortage of memory within the system.

Severity: P1
Action: Add more memory to the system (on all modules).
*** RAM: record %s

Severity: P4
*** RAM: relay to standby failed due to broken vc -1
Description: This message pertains to internal information keeping.

Severity: P4
Action: None required. This is only an informational message.
*** RAM: req %d, node %d, tid %04X
Description: This message pertains to internal information keeping.

Severity: P4
Action: None required. This is simply an informational message.
*** RAM: res from RAM %d and RAM_SB %d differ

Severity: P4
*** RAM: Standby dead
Description: This message pertains to the internal information log.

Severity: P4
Action: None required. This is simply an informational message.
*** RAM: This should not have been put into backup queue %d
Description: This message pertains to the internal information log.

Severity: P3

*** SCAN: close oaa rcrd: %s update failed
Description: System could not open the scan database record.

Severity: P3
Action: A result code will be logged.
*** SCAN: Could not setup scan database
Description: This message normally appears when there is no account space in the
system.
Severity: P3
Action: Add more account drives. Otherwise, dial-by-name will be affected.
*** SCAN: Could not spawn scan_agent, abort
Description: The scan_agent was not started.

Severity: P1

*** SCAN: open oaa rcrd: %s failed, result %d
Description: System could not open the scan database record.

Severity: P3
Action: A result code will be logged.
\t...sndr: %s, node %d
Description: Further data on NETVM message length limit being exceeded.

Severity: None
Action: None. This is an informational message only.
2 successive OPEN failures for mbox %s
Description: Corruption might exist in the mailbox database (for this mailbox).
Severity: P2
Action: Run a vac ASAP. The relevant mailbox might not receive any messages
until a vac is run.
740D Data Link [%s] Initialization completed.
Description: This is a normal message after link initialization following a system reboot.
Severity: P4
Action: None.
A
AAMIS: failed [%d] to create list [%s]
Description: The NuPoint Voice software failed to create a new amis copy list that stores
the addresses of AMIS recipients. This error message might be due to a
software problem that does not handle the amis copy list properly. It could
also be caused by a hardware error on the account drive. Or maybe the
account drive itself is full. If this error message appears frequently, along
with any other error log messages related to failure to read mailbox records
or a copy list, then the problem could be related to the disk drive.
Severity: P3
Action:
• Check the system's total statistics to make sure there are at least
several hundred free/unused account records. These records are
needed by NuPoint Voice to store the copy lists used in delivery of
messages.
• Run a verify on the system.
• Check the logfile often after the verify for at least a week. If the problem
still exists, contact your Support Representative.
AAMIS: failed [%d] to open list [%s]

Description: The NuPoint Voice software failed to open the amis copy list that stores the
addresses of AMIS recipients. This error message might be due to a
software problem that does not handle the amis copy list properly. It could
also be related to a hardware error on the account drive. If this error
message appears frequently, along with any other error log messages
related to failure to read mailbox records or the copy list, then the problem
could be related to the disk drive.
Severity: P3
Action:
AAMIS: failed [%d] to read list [%s]
Description: NuPoint Voice software failed to read the amis copy list that stores the
addresses of AMIS recipients. This error message might be due to a
software problem that does not handle the amis copy list properly. It might
related to the failure to read mailbox records or the copy list, then the
problem could be related to the disk drive.
Severity: P3
Action:
AAMIS: failed [%d] to save list [%s]
Description: The NuPoint Voice software failed to close the amis copy list that stores the
addresses of AMIS recipients. This error message might be caused by a
software problem that does not handle the amis copy list properly. It might
related to the failure to read mailbox records or the copy list, then the
problem could be related to the disk drive.
Severity: P3
Action:
ACCESS TEN: bad ten_num -->%d
Description:
Severity: NP2
Action:
Activatecfg: Unable to talk to mail resolver

Description: The resolver task is not running.
Severity: P1
Action: Reset the system.
ACTIVATECFG: can't locate (mwla), unable to init mwla queues.
Description: During activation of a configuration, the Message Waiting Light

Administrator task cannot be located by the activatecfg task. The message
waiting queues will not be initialized.
Severity: P3
Action: Activate the configuration again. Contact your Supporrt Representative.
ACTIVATECFG: can't locate (pga), unable to init pga queues.
Description: During activation of a configuration, the pager administrator task cannot be

located by the activatecfg task. The Pager queues will not be initialized.
Severity: P3
Action: Activate the configuration again. Contact your Support Representative.
ACTIVATECFG: can't send to mwla, unable to init queues.
Description: During activation of a configuration, the activatecfg task cannot send to the
Message Waiting Light Administrator task. The message waiting queues
will not be initialized.
Severity: P3
ACTIVATECFG: can't send to pga, unable to init queues.
Description: During activation of a configuration, the activatecfg task cannot send to the
pager administrator task. The Pager queues will not be initialized.
Severity: P3
Activate ioctl to DK driver failed
Description: The request to activate the MTP processor failed.

Severity: P2
Action: Review the SS7 troubleshooting guide.
Adapter command timed out, retry #%d
Description: Attempted operation is not responding.

Severity: P3
Action: None.
Adapter returned id=%x camstat=0x%x mbstat=0x%x hastat=0x%x

scsistat=0x%x
Description: This is an adapter internal status report.

Severity: P3

Adapter returned status=0x%x
Description: This is a status report on the internal adapter.

Severity: P3
Adapter shows internal diagnostic failure
Description: A system hardware problem exists.

Severity: P1
add_new_disk()Invalid disk id %d
Description: Invalid SCSI disk ID passed to sfa when adding a disk online.
Severity: P3
Action: Verify the disk ID was entered correctly in disk add procedure.
add_new_disk()Vid %d exists for disk %d
Description: An attempt was made to add a new SCSI disk with the same ID as an
existing disk.
Severity: P4
Action: Rejump the disk to be added to an unused SCSI ID and attempt to add
again.
ADMIN 75 : CTI task fails to start !
Description: The system cannot start CTI program.

Severity: P3
Action: Check the CTI card and smart card table configuration. If the problem
persists, the CTI card may be bad. If no anomalies are found, contact your
Agent died, exit
Description: The resource manager detects a death of its agent, thereby exiting.
Severity: P1
aglib qnx_ioctl failed, errno:9
Description: A system binary changed and caused the running software to fail.
Severity: P2
Action: Reboot the system.
ALSPCH: speech allocation ptr in reserve area.apt:%u, rpt:%u,

msp=%u
Description: This message will appear after a software update from Release 5.01. If

seen at any other time, then it is a software error.
Severity: P4 or P2
Action: Contact your Support Representative if this message appears during
normal system operation.
Another WPC is running on the same node, EXIT
Description: An attempt was made to run wpc program when the program was already
running.
Severity: P4
Action: None.
aopen fail reslt=%d,rcrd=%s
Description: Request to open a mailbox record failed.

Severity: P3
ApplName: FATAL !!!!

ApplName: message
ApplName: sleep forever
Description: A fatal error occurred in the application ApplName. The message shows
the fatal error that occurred, causing the program to enter a zombie state.
Severity: P1
ATLG: %s unable to read configuration record.
Description: There is a problem reading the configuration record from oaa.

Severity: P3
Action: Reconfigure audit trail parameters.
ATLOG: %s %x is inactive, unable to attach name
Description: A QNX error or another copy of atlogad is running.

Severity: P3
Action: The audit train information will not be recorded. Reboot the system to clear
this condition.
ATLOG: %s %d inactive, unable to create configuration record
Description: System was unable to create the record in order to store configuration data
on disk. This only happens when configuring the audit trail.
Severity: P4
Action: Retry configuration.
ATLOG: %s,%d unable to create %s
Description: Some of the components of the audit trail could not be started.
Severity: P2

Action: Reboot the system. If the problem persists, contact your Support
Representative.
ATLOG: %s %d unable to read %s
Description: Could not read some of the database from disk. Uses oaa records.
Severity: P3
Action: Rerun the configuration of the audit trail.
ATLOG: %s unable to find %s.
Description: The agent task could not find admin task.

Severity: P3
Action: Restart the audit trail. If the problem persists, reset the system.
ATLOG: %s %x unable to read msg record %d
Description: Indicates a problem reading or writing the database into oaa records.
Severity: P3
ATLOG: %s %x unable to open msg record %s
Severity: P3
ATLOG: %s %x unable to close msg record %s
Severity: P3
ATLOG: %s %x failed to open cfg record for write
Severity: P3
ATLOG: %s %x cannot close cfg record
Severity: P3
ATLOGAD: %s %x stop request from %x
Description: There is no error. This message indicates the audit trail was stopped (from
menus).
Severity: None.
Action: This is an informational message only.

ATLOGAD: %s %x delete request from %x
Description: There is no error. This message indicates request to delete the audit trail
(from menus).
Severity: None.
Action: This is an informational message only.
ATLOGAD: %s %x invalid req %d from %x
Description: Indicates a software bug in the audit trail software.

Severity: P4
ATLOGAD: sender queue full
Description: System could not write the audit trail data to disk fast enough, or one of the
components of the audit trail is not running.
Severity: P3
Action: Run sin and contact your Support Representative with the results.
atlogad: %s %d is INACTIVE!!
Description: A problem occurred with the audit trail. The records will no longer be
written to disk.
Severity: P2
Action: Reset the system to clear.
atlogag: %d,%s unable to attach name
Description: System error or multiple copies running.

Severity: P2
Action: Reset the system.
ATLOGSD: %s %x inactive, unable to read configuration record
Description: Problem reading configuration record from oaa.

Severity: P3
Action: Reconfigure the audit trail parameters.
ATLOGSD can not find atlogad,%04x\n
Description: The send agent could not find the admin task.
Severity: P3
Action: Try restarting the audit trail. If this does not work, reset the system.
ATLOGSD can not Send to ATLOGAD, result %04x\n
Description: The send agent could not find the admin task.
Severity: P3
Action: Try restarting the audit trail. If this does not work, reset the system.

AUDIT TRAIL is 85 percent full at %s,%s
Description: This is an informational message only, not an error message.

Severity: P3
Action: Be sure to report the audit trail before 100% or it will be overwritten.

Severity: P3

Severity: P3
AUDIT TRAIL is re-used at %s,%s,
Severity: P3
Action: Rerun the configuration of the database.
B
bcst_pc: aopen %s = %d
Description: When attempting to broadcast a passcode, the mailbox could not be

opened or closed.
Severity: P2
Action: Check the mailbox for corruption or check if it exists.
bcst_pc: aclose %s = %d
Description: When attempting to broadcast a passcode, the mailbox could not be

opened or closed.
Severity: P2
Action: Check the mailbox for corruption or check if it exists.
Board number %d already configured in atSlot %d\n
Description: Driver received a request to configure a board a second time.

Severity: P3
boot_count%d: Unable to create %s
Description: The control file was not found and cannot be created.

Severity: P3
boot_count%d: Unable to create %s
Description:
Severity: P3
Action:
boot_count%d: Unable to disable node
Description: System problem occurred in updating configuration.

Severity: P3
Action: Contact your Support Representative.RT:0,FI:0>

boot_count%d: Unable to fseek on %s
Description: A failure in reading boot control file occurred.

Severity: P3
boot_count%d: Unable to disable node
Description: The module was not successfully disabled. If the module continues to
reset, an attempt will be made to disable it again.
Severity: P3
Action: If the problem persists, contact your Support Representative.
boot_count%d: Unable to fseek on %s
Description: A disk error was detected when an attempt was made to create the boot
record. The boot record logs the frequency of a module's reboots. This
information is used to disable modules that have reset excessively. The
system will recover if the disk error is not fatal.
Severity: P3
Action: No action required here. A fatal disk error will result in other log messages
indicating the condition.
boot_count%d: Unable to read from %s
Description: A failure in reading boot control file occurred.

Severity: P3
boot_count%d: Unable to write to %s
Description: A failure to updating boot control file occurred.

Severity: P3
boot_count%d: Unable to write to %s
Description: A disk error was detected when an attempt was made to create the boot
record. The boot record logs the frequency of a module's reboots. This
information is used to disable modules that have reset excessively. The
system will recover if the disk error is not fatal.
Severity: P3
Action: No action is required here. A fatal disk error will result in other log
messages indicating the condition.
boot_count: Too many reboots within %d sec. Disabling node
Description: The system is rebooting too frequently. The module considered unreliable
and disabled.
Severity: P3

Action: Contact your Service Representative to determine the cause of the
reboots. If the system was rebooted manually, use the host.status option to
enable the module.
boot_count: Too many reboots within %d sec. Disabling node
Description: A node has rebooted more than four times in one hour. It has been
disabled.
Severity: P2
Action: Examine the logfile to determine why the module has reset. The host
status menu can be used to re-enable the module.
C
Contacted node %d but reached node %d. Disc. Check Node Table.
Description: The node table is possibly misconfigured, thus misrouting the MESA-NET
connection attempt.
Severity: P1
Action: Fix configuration errors in the node table.
Cannot find sfa on node[%d], i
Description: NP View is looking for the Speech File System on the specific node. The
Speech File System is needed for operation.
Severity: P1
can not become a server:%s
Description: Resource manager fails to become a server task, thereby exiting.

Severity: P1
“can not locate user part”
Description: Before a message can be sent the user part must be located. When it
cannot be located this error is logged.
Severity: P4
Action:
Cannot mark disk %d:%d out of sync: rdn disk out of svc
Description: Primary and redundant failures caused loss of drive.

Severity: P1
Cannot mark disk %d:%d out of sync: rdn disk out of sync
Description: Primary and redundant failures caused loss of drive.

Severity: P1
Cannot mark QNX %d out of sync: QNX %d out of sync
Description: Both software drives are down.

Severity: P1
Cannot mark QNX %d out of sync: QNX %d out of sync
Description:
Severity: P1
Action:
Cannot read directory for vid=<xxx> (retry = <xxx>)
Description: The account directory is unreadable. Disk may be faulty.

Severity: P1
Cannot send to COSSERVER
Description: An attempt to execute a send from MKLIB failed.

Severity: P2
Cannot send to NTA_AGENT
Description: A NTALIB based SEND to NTA_AGENT failed.

Severity: P2
Cannot send to OTA_AGENT
Description: Cannot send to DTA task.

Severity: P3
Can't attach fax chan %d. Fax init done?
Description: The fax startup procedure cannot complete itself.

Severity: P3
Action: Check that the fax dimmer and initialization programs have run to
completion.
Can't attach \%s\ on node %d, DEFAULT_MBOX_SERVER, getnid()
Description: NP View could not connect to the default voice memo server.
Severity: P1
Action: NP View will not start. There is not much the user can do about this.

Contact your Support Representative.
can't locate %s within MCSS
Description: The application cannot find the admin task (SFA). This is either a software
error, or SFA is not running.
Severity: P1
Action: If SFA has not halted, contact your Support Representative.
Can't name attach faxmgr.
Description: The operating system failed to register program faxmgr.

Severity: P4
Action: The system will retry four times and then stop trying. Reboot.
Can't send to wua, did not cancel wakeups for mbox %s
Description:
Severity: P2
Action:
Can't set time on node %d\n
Description: The admin attempted to set the time using admin by phone and the system
failed to set it on a particular node, using either the hardware or software
clock.
Severity: P3
Action: Check time for accuracy on all the nodes and if they are wrong, set them
from the console.
Can't set hardware clock on node %d\n
failed to set it on a particular node. using either the hardware or software
clock.
Severity: P3
Action: Check time for accuracy on all the nodes and if they are wrong, set from the
console.
Can't set hardware clock on node %d\n
failed to set it on a particular node. Either the hardware or software clock.
Severity: P3
Action: Check time for accuracy on all nodes and if they are wrong, set from the
console.
Card %s on slot %d does not have the authorized Centigram

signature
Description: Linecard does not have proper authorization.

Severity: P1

Action: Need to get linecard signature. Contact your Support Representative.
CATCH ROLM: can't send to sfa!
Description: rolmcatch could not find sfa.

Severity: P1
Action: sfa may have died, or system resources may be running out. If sfa died,
reboot system and reload the Rolm extra-cost diskette.
cdr overflow, lost 16 msgs in blk %d
Description: Event recorder overflowed, and 16 messages were thrown away before
they could be written to the disk.
Severity: P4
Action: Try logging less information, or try a less busy time..
CFG_APACK:bad acct #, len=%d
Description:
Severity: P2
Action:
“CFN message received on CIC %d”
Description: SS7 received a message from the adjacent point code that was not
expected.
Severity: P3
Action:
Circuit %d on board in slot %d is not being used by SS7!
Description: This is a warning issued when a board circuit has not been allocated to any
SS7 line groups.
Severity: P4
Action: None required, if it is consistent with line group definition.
cm_oaa_fns: Send to OAA timed out
Description: NP View sent a request to the OAA process, and it was not returned within
the time allocated.
Severity: P1
Action: There is probably a very bad system problem. Verify VMEMO is running.
CM_SERVER: Error reading configuration
Description: NP View cannot read its configuration file.

Severity: P1
Action: Check to see the configuration file is in usr/vm/config. Run CM_CONFIG to
create another configuration file.
CM_SERVER: ERROR Out of memory for new handles

Description: NP View needs memory for each mailbox that logs onto the system.
Severity: P1
Action: Kill some other processes, or install more RAM.
Cmd failed, locator %d, (%(errno))
Description: A general disk error occurred.

Severity: P2
Config ioctl to DK driver failed
Description: The request to download and configure the MTP processor failed.
Severity: P2
COSSTART: task %x cannot find COSSERVER
Description: An attempt to find the COSSERVER process failed.

Severity: P2
Could not spawn rm_agent (%s), exit
Description: Resource manager could not spawn its agent, thereby exiting.
Severity: P1
CQM message received on CIC %d
Description: SS7 received an unexpected message from the adjacent point code.
Severity: P3
CQR message received on CIC %d
Severity: P3
CSOIOTEST: bad card type in print status %c
Description: The wrong card is installed on the CSOIO hardware.

Severity: P1
Action: Check to make sure that all of the cards installed on the CSOIO hardware
are of the type PCC (primary control card). SIC (serial interface card), or
BOC (busy out card).

D
Deallocating invalid tspch block %02x%04x
Description: An attempt was made to deallocate an invalid speech block. The system
will remain functional.
Severity: P2
Action: Run a system verify. If the problem recurs after the system verif, or if the
verify report shows an excessive amount of errors, contact your Support
Representative.
delete_msg: aclose failed, rslt = %d
Description:
Severity: P2
Action: This message will not be deleted for a mailbox.
delete_msg: delete_links failed for %s
Description: System failed to delete links for a receipt. This can only happen for the
receipt to over 190 mailboxes.
Severity: P2
Action: Run a verify.
delete_msg: error %d msg %d sib %d\n
Description: An error in deleting a message occurred. The mailbox may be corrupted.

Severity: P2
del_mbox: delete of msgs failed (%s)
Description: The mailbox may be corrupted.

Severity: P2
detected module %x went down
Description: The NP View task that does meet me/ contact me has lost contact with the
module reported. This is benign if the module does not exist.
Severity: P3
Action: If the module went down for the normal maintenance reasons, no action is
needed. When it comes up, all should be well. If the module is actually up,
then test the meet me/ contact me functionality on a given host. If is does
not work, a reset may be necessary.
Dev.DK Started
Description: This is a normal alarm when SS7 is started.

Severity: P4
Action: None.

Dev.T1/E1: CARD %02d TRUNK %01d: Unknown event.\n
Description: A software fault was detected. The driver received an unknown event on
the specified card and trunk. Repeated errors indicate a problem.
Severity: P4
Dev.T1/E1: Event queue full\n
Description: An operating system failure was encountered by the T1/E1 driver. Future
events might not get queued.
Severity: P2
Dev.T1/E1: Host Clock Ref. changed from TRUNK %01d to TRUNK %01d
Description: The clock reference for this host was moved to an alternate PCM due to a
failure.
Severity: P4
Action: None.
Dev.T1/E1: TRUNK %01d: Local Alarm Cleared.\n
Description: This PCM trunk is no longer in a failed state.

Severity: P4
Action: None.
Dev.T1/E1: TRUNK %01d: Local Alarm.\n
Description: This PCM trunk has entered a local carrier failure state.
Severity: P3
Action: Troubleshoot the T1/E1 facility connecting NuPoint Voice to switch/PBX.
Dev.T1/E1: TRUNK %01d: Remote Alarm Cleared.\n
Description: This PCM trunk is no longer receiving an alarm indication from the far end.
(The other side is no longer in a failed state.)
Severity: P4
Action: None.
Dev.T1/E1: TRUNK %01d: Remote Alarm.\n
Description: This PCM trunk is receiving an alarm indication from the far end. (The other
side is in a failed state.)
Severity: P3
Action: Troubleshoot the T1/E1 facility connecting NuPoint Voice to switch/PBX.
Dev.T1/E1: Unable to Reply() to agent\n
Description: The T1/E1 driver encountered an operation system error.

Severity: P3

Disable cards that use this loader program
Description: Disable cards that need this loader program have failed.
Severity: P4
Action: This is a result of another prior error. Check the previous error message.
DISABLE FLOAT: CAN'T CLOSE MASTER CONFIG REC(%d).
Description: An error occurred while turning off the continuous system operation optional
feature. The task was unable to communicate with the Account
Administrator program. This is probably due to a temporary fault, a module
death, for example. The optional feature will not be disabled.
Severity: P3
DISABLE FLOAT: CAN'T READ MASTER CONFIG REC(%d).
Description: An error occurred while turning off the continuous system operation optional
feature. The task was unable to communicate with the Account
Administrator program. This is probably due to a temporary fault, a module
death, for example. The optional feature will not be disabled.
Severity: P3
Disable the card
Description: Mark the card unusable due to the problem of communicating with the card
Severity: P4
Action: This is a result of another error occurring prior to this. Look at the previous
error message.
Disabling all cards which use MVIP
Description: Due to a failure in configuring the MVIP clock, all the cards using the MVIP
bus are disabled and unusable.
Severity: P1
Action: Check and verify the MVIP clock configuration and I/O address
configuration.
Disk %d:%d: partition 88 start %d, size %d
Description: Comment on partition characteristics.

Severity: P4
Action: None.
dist_copy: BEFORE loop: end = %d, lst %s ...net_sndr = %d,

dl_outside = %d, dl_cnt = %d, ms_node = %d
Description: The indicated copy list's local member counter is corrupted. This results in
the list not being processed.

Severity: P3
Action: Run a verify. If the problem persists, contact your Support Representative.
DK config failed! Trying again..
Description: The request to download and configure the MTP processor failed.
Severity: P2
DK start failed! Trying again..
Description: The request to active the MTP processor failed.

Severity: P2
DK: DK board configuration sequence failed!
Description: System is unable to download and configure the board.

Severity: P2
DK: DK board download sequence failed!
Description: The image download to the MTP coprocessor board did not complete.
Severity: P4
DK: Failed to activate ss7 links!
Description: The activate command to the MTP coprocessor board failed.

Severity: P4
DK: Failed to configure DK board!
Description: The configure command to the MTP coprocessor board failed.

Severity: P2
DK: Failed to deactivate ss7 links!
Description: The deactivate command to the MTP coprocessor board failed.

Severity: P4
Action: Retry. If the problem persists, contact your Support Representative.
DK: Failed to reset DK board, error code : %s
Description: The MTP processor board did not respond to the reset sequence.
Severity: P4

DK: Failed to reset mvip on DK board
Description: The MVIP reset command to the MTP coprocessor board failed.
Severity: P2
DK: Failed to set clock on DK board
Description: The MVIP clock configure command to the MTP coprocessor board failed.
Severity: P2
DK: SS7 link %d Alignment not ready!
Description: The MTP alignment procedure failed.

Severity: P3
DK: SS7 link %d Alignment started!
Description: MTP restarted the link alignment procedure.

Severity: P4
Action: None.
DK: SS7 link %d is aligned and ready!
Description: The MTP alignment procedure succeeded.

Severity: P4
Action: None.
DK: SS7 link %d is experiencing a processor outage!
Description: MTP received a remote processor outage indication.

Severity: P4
Action: None.
DK: SS7 link %d is in service!
Description: MTP has successfully aligned the specified SS7 task.

Severity: P4
Action: None.
DK: SS7 link %d is out-of-service!
Description: MTP experienced a link failure.

Severity: P3
DK: SS7 Link MTP test failed!
Description: The periodic MTP test message failed.

Severity: P3
DK: Unable to start SS7 board!
Description: The start command to the MTP coprocessor board failed.

Severity: P2
DK: Unexpected User Part Message Received!
Description: A software failure resulted in the device driver receiving an SS7 user part
message.
Severity: P4
DMA test failed on adaptor @0x%x on pass %d
Description: A system hardware problem occurred.

Severity: P1
Double open from %x, rcrd %s opened rcrd is %s
Description: Internal information log.

Severity: P4
Action: Contact your Support Representative, along with task name.
Driver contact (config clock) failed
Description: The resource manager received a failure from the driver when trying to
configure the clock.
Severity: P1
Action: Restart the system, and/or replace the hardware. If the problem persists,
contact your Support Representative.
Driver contact (mvip connect) failed, Brd %d OutSM %d OutSlot %d,

InSM %d InSlot %d Dir %D
Description: The resource manager received a failure from the driver when trying to
make the MVIP connection.
Severity: P1
Driver contact (mvip disconnect) failed, Brd %d SM %d Slot %d Dir

%d
Description: The resource manager received a failure from the driver when trying to tear
down the MVIP connection.
Severity: P1

Driver contact (set pattern) failed
Description: The resource manager received a failure from driver when trying to send a
pattern.
Severity: P1
Action: Restart the system, and/or replace the hardware. If it still fails, contact your
Driver %s died, exit
Description: The resource manager detects a death of one of the drivers, exiting.
Severity: P1
DTA_AGENT: can't send to DTA
Description: Process DTA_AGENT cannot complete a send_name to DTA.

Severity: P2
DTASTART: task %x cannot find DTA_AGENT
Description: System cannot find DTA task from the task id.
Severity: P3
Action: Contact your Support Representative if the problem occurs repeatedly.
DTI ADMIN : bad msg type = %d, tid %x
Description: Software error exists in dti_comm or dti_admin.

Severity: P2
DTI ADMIN : dti_a2c_q full!!
Description: dti_comm is not responding or dti_a2c is not responding.

Severity: P2
Action: If this problem occurs repeatedly, contact your Support Representative.
dti ADMIN: bad card num = %x, type=%d
Description: Misconfigured DTI card jumpers.

Severity: P1
Action: Check DTI card hardware switch settings. Reference Technical Memo
91013.
dti ADMIN: bad msg origin=%d, tid=%x
Description: Software error or incompatible software.

Severity: P2
Action: Check software revision dates and support disk compatibility.
DTI ADMIN: BOARD [%d] contact xfer SEQ [%d]
Description: Software error.

Severity: P3
dti ADMIN: can't attach_name [%s].
Description: Another task has registered the dti_admin name.

Severity: P1
Action: Verify the configuration (offline menu). Contact your Support
Representative.
DTI CONyour Support RepresentativeTXFR: bad inform type for ixfr:

USER_ABORT Contact your Support Representative Department

Severity: P3
DTI CONyour Support RepresentativeTXFR: bad inform type for

ixfr:%d Contact your Support Representative Department

Severity: P3
Action: If the problem persists, contact your Support Representative.j
DTI COMM: admin msg not recognized: %d
Description: Software error in dti_comm or dti_admin.

Severity: P2
dti COMM: bad amsg_org = %d, tid= %04x
Description: Software error or incompatible software revisions.

Severity: P2
Action: Check software revision dates and support disk compatibility.
DTI COMM: bad xy0 type!
Description: Software error in dti_comm or dti_admin.

Severity: P2
Action: If the problem occurs frequently, contact your Support Representative.
DTI TIMER: can't locate (%s)
Description: dti_timer cannot locate <tsk_name>.

Severity: P4
Action: The system should correct itself. If this message appears often, contact
DTI(%d): software sync error; ixfr msg
Description: Software timing problem.

Severity: P3
DTI: bad ixfr cmd for board %d
Description: Software error or incompatible software.

Severity: P2
Action: Check software revision dates.
DTI: queue full, element size:%d
Description: The dti_ixfragnt died or is not responding.

Severity: P2
DTI_ADMIN: initialized board %d
Description: Informational message only.

Severity: P4
Action: None.
DTI_ADMIN: starting to initialize board %d
Description: Informational message only.

Severity: P4
Action: None.
DTI_COMM: interrupt out_q full. Address = %x

Severity: P2
DTIA2C: can't locate (%s)
Description: dtia2c cannot locate dti_admin name.

Severity: P4
Action: The system should correct itself. If not, contact your Support
Representative.
DTIC2A: can't locate (%s)
Description: dtic2a cannot locate a task name.

Severity: P4

Representative.
DTICOMM: dti_c2a_q full!!
Description: The dti_admin task or the dti_c2a task died or not responding.
Severity: P2
DTIIXFRAGNT: can't locate (%s)
Description: dti_xfragent cannot locate dti_admin.

Severity: P4
Representative
E
EAGENT: can't open queue <queue name>
Description: The system is unable to open the queue for incoming integration packets.
The integration data received by the ecrcv is written to the queue. Then
eagent reads the queue and sends the data to sfa. Since eagent is unable
to open the queue, integration information will not be received for incoming
contacts. Therefore, incoming contacts will get general greeting. EAGENT
will continually retry until it successfully opens the queue.
Severity: P2
ECDR is re-used at %s,%s
Description: This is a warning, not an error. The CDR log file is getting full and is being
overwritten.
Severity: P4
Action: Download your CDR records as soon as possible. It this problem occurs
repeatedly, it may be necessary to increase the CDR file size.
ECDR: %s %x cannot close cfg record
Description: Task ecdrad of Contact Detail Recorder failed to close an account record
used to store the CDR configuration. This problem can cause loss of CDR
records.
Severity: P2
Action: Do not reboot the system. Contact your Support Representative to
determine the cause of this problem.
ECDR: %s %x failed to open cfg record for write
Description: Task ecdrad of Contact Detail Recorder failed to open an account record
used to store the CDR configuration. This problem can cause loss of CDR
records.

Severity: P2
Action: Do not reboot the system. Contact your Support Representative.
ECDR: %s %x inactive, unable to create configuration record
Description: Task ecdrad was started by the system but was unable to create its internal
configuration record. This problem is caused by a software error that failed
to create or read the Contact Detail Recorder account record. The inactive
task will remain on the system to prevent system from being rebooted.
However, this problem should be fixed immediately.
Severity: P2
Action: Do not reboot the system. Contact your Support Representative for
instructions on how to fix this problem.
ECDR: %s %x inactive, unable to read configuration record
Description: Contact Detail Recorder send agent failed to read the CDR configuration.
This can cause a command issued by user to be ignored by CDR.
Severity: YYP4
ECDR: %s %x is INACTIVE !!
Description: This error message shows up once every hour to remind the user of
inactive ecdrad task(s) on your system.
Severity: P4
ECDR: %s %x is inactive, unable to attach name
Description: Task ecdrad was started by the system but was unable to register its name
on the QNX network. This can be caused by a software error that starts too
many ecdrad tasks on the same system (only one ecdrad should be active
on the system at any one time), or by a problem with the QNX network.
The inactive task will remain on the system to prevent it from being
rebooted. However, it should be removed manually by the administrator
immediately.
Severity: P2
ECDR: %s %x unable to close msg record %s
Description: Task ecdrad of Contact Detail Recorder failed to close an account record
after writing CDR records to it. This problem prevents CDR records from
being stored on the system.
Severity: P2
ECDR: %s %x unable to open msg record %s
Description: Task ecdrad of Contact Detail Recorder failed to open an account record to
write CDR records. This problem prevents CDR records from being stored
on the system.

Severity: P2
ECDR: %s %x unable to read %s

or
ECDR: %s %x unable to read msg record %d
Description: Task ecdrad of Contact Detail Recorder failed to read an account record
used for storing CDR records. This problem prevents CDR records from
being properly stored on the system.
Severity: P2
ECDR: %s unable to find %s.
Description: Contact Detail Recorder agent failed to locate the administrator task
(ecdrad) to send CDR records to. This problem can prevent CDR records
from being written to disk.
Severity: P3
ECDR: %s unable to read configuration record.
Description: Contact Detail Recorder agent failed to read the latest configuration for
CDR. This problem can cause unwanted contact type CDR records to be
recorded.
Severity: P4
ECDR: %s,%x unable to create %s
Description: Task ecdrad of Contact Detail Recorder failed to create its agent ecdrsd for
some reason. This problem will block all commands issued by CDR menu
program such as start/stop/configuration.
Severity: P3
ECDRAD: %s %x delete request from %x
Description: This is not an error. This log message tells the system administrator when
Contact Detail Recorder file was deleted.
Severity: P4
Action: None.
ECDRAD: %s %x download cfg from %x
Description: This is not an error. This log message informs the system administrator of
when Contact Detail Recorder file was downloaded.
Severity: P4
Action: None.
ECDRAD: %s %x invalid req %d from %x

Description: An invalid request was received by ecdrad from another task on the system.
This was caused by incompatible Contact Detail Recorder software or by
problem with the QNX network. Depending on the type of request received,
this could be a severe error, possibly causing the loss of CDR records or
some minor error sent by the menu program.
Severity: P4
ECDRAD: %s %x stop request from %x
Description: This is not an error. This log message informs the system administrator
when the Contact Detail Recorder was stopped.
Severity: P4
Action: None.
ECDRSD can not find ecdrad,%04x
Description: Contact Detail Recorder send agent failed to locate the CDR administrator
task and would not retry. This was caused by the administrator task
(ecdrad) dying unexpectedly. Is usually restarted by the system.
Severity: P4
Action: Contact your Support Representative if more than one log messages of this
type appears in the logfile (agent does not get restarted).
ECDRSD can not send to %s,%04x result %d
Description:
Severity:
Action: Most of the time the agent is restarted. Contact your Support
Representative if more than one log message of this type appears in the
logfile (agent cannot be restarted).
ECDRSD can not send to ECDRAD, result %04x
Description: Contact Detail Recorder send agent failed to send a request to the CDR
administrator task (ecdrad). At this point, it should terminate itself
(assuming the administrator is terminated by the user or by the system).
Severity: P3
Action: Contact your Support Representative only if you get this log message while
CDR is supposed to be running.
ECRCV: can't get stty on RS232 port
Description: Unable to read from the serial port.

Severity: P2
Action: Check the system configuration for possible problems/inconsistencies.
Check for possible hardware problems. If no anomalies are found, contact
ECRCV: can't open <port name> for read
Description: The system is configured incorrectly. Cannot open serial link <port name>.

Severity: P1
Action: Check the system configuration for possible problems/inconsistencies. If no
anomalies are found, contact your Support Representative.
ECRCV: could not open record = %s
Description: System is configured incorrectly. Could not open the configuration record.
Severity: P2
ecrcv: could not open rs232 port
Description: The system is configured incorrectly.

Severity: P2
ECRCV: no prefixes defined for centrex; aborting
Description: The system is configured incorrectly.

Severity: P1
ECRCV[<host>:<serial port>]: BAD MD: %d
Description: The system is unable to match Message Desk number.

Severity: P2
Action: Check the configuration. If the error continues, check the switch.
ec_resync: Unable to locate MWLA, aborting.
Description: MWLA died.

Severity: P1
EECO: link is down.
Description: EECO PMS sends a character followed by the ETX character to the
NuPoint Voice integration. If this character is not echoed back within two
seconds, the link between the integration and the PMS is assumed down
and this error message is sent. No integration can occur while the link is
down.
Severity: P1
Action: Reactivate the link by sending a C from the PMS.
EECO: link is up.
Description: Informational message to notify the user that the link between the EECO
PMS and the NuPoint Voice Integration is working correctly.
Severity: P4

Action: None.
Emulation task is not running! exit
Description: SFA cannot locate the emulation software for linecard, thereby exiting
Severity: P1
Error: can't send to wakeup administrator.
Description: A NuPoint Voice or NYNEX task cannot communicate with the wakeup
administrator. This can result in being able to place wakeup and/or
reminder contacts.
Severity: P2
Action: Reset the system if more occurrences are found. This might resolve the
problem if the system resources were temporarily exhausted. If the
problem persists, contact your Support Representative.
Error from Receive but continuing.\n
Description: The fax application received an illegal request that was ignored.
Severity: P3
Action: None. The software receives it automatically.
Error in reading line exception records
Description: NuPoint Voice cannot read the line exception record.

Severity: P3
Action: All defaults will be used, but check the line exceptions with a verify or the
menus.
Error starting allocator\n
Description: Software module (allocater) cannot be found or is corrupted.

Severity: P1
F
F960_ADM: bad message origin ($x)
Description: Internal software error. F960_admin task received unexpected messages.

Severity: P3
Action: Investigate the problem. Check the system configuration for possible
problems/inconsistencies. If no anomalies are found, contact your Support
Representative.
F960_ADM: can't read OAA data!
Description: F960_admin cannot access the oaa data records for necessary

configuration parameters.
Severity: P1
Action: Check the system configuration to verify that the Fujitsu 960 Integration was
installed and properly configured. If the problem persists, check the system
configuration for possible problems/inconsistencies. If no anomalies are
found, contact your Support Representative.
F960_ADM: creatl error for IN task, link ($s),Ports (%s).
Description: F960_admin can't create F960_in task.

Severity: P1
Action: Check the system configuration to verify that the Fujitsu 960 Integration has
been installed and properly configured. If the problem persists, check the
system configuration for possible problems/inconsistencies. If no
F960_ADM: creatl error for OUT task, link ($s),Ports (%s).
Description: F960_admin can't create F960_out task.

Severity: P1
F960_ADM: general receive failure
Description: This message indicates that the F960_admin task received an invalid
message or event. F960_admin task will resynchronize itself.
Severity: P3
F960_ADM: IN started, awaiting PBX initialization
Description: This message indicates that F960_in task has been started properly and is
ready to service incoming contacts from the Fujitsu switch.
Severity: P4
Action: None.
F960_ADM: IN task for link %d already running.
Description: Informational message. This is logged after F960_admin task finds that
F960_in task has been started.
Severity: P3
Action: If the problem persists, check the system configuration for possible
Representative.
F960_ADM: IN task for link %d re-started.
Description: F960_admin task has successfully restarted the F960_in task.

Severity: P4

F960_ADM: lost a msg for F960_OUT (Q full) for lk:%d.
Description: Informational message. The internal queue for F960_admin task has
received more events due to some unexpected activities.
Severity: P3
problems/inconsistencies, reboot the system, or reinstall the software in an
attempt to clear the error.
F960_ADM: lost messages from SFA (queue full)
Description: Informational message. The internal queue for F960_admin task has
received more events from the Fujitsu switch than expected.
Severity: P3
Representative.
F960_ADM: OUT started, awaiting PBX initialization
Description: This message indicates that F960_out task has been started properly and is
ready to service incoming contacts from the Fujitsu switch.
Severity: P4
Action: None.
F960_ADM: OUT task for link %d already running.
Description: Informational message. This is logged after F960_admin task finds that
F960_out task has been started.
Severity: P3
Representative.
F960_ADM: OUT task for link %d re-started.
Description: F960_admin task has successfully restarted the F960_out task.

Severity: P4
F960_ADM: receive failed due to exception
Description: This message indicates that F960_admin task received an invalid message
or event. F960_admin task will resynchronize itself.
Severity: P3
F960_ADM: received bad timer type. Type: %d
Description: Informational message.

Severity: P3
F960_ADM: unable to send to undertaker
Description: F960_admin task is unable to report the task death to the undertaker.
Severity: P1
Action: Reboot the system in an attempt to clear the error. If the problem persists,
check the system configuration for possible problems/inconsistencies. If no
F960_ADMIN: *** Unable to attach name (%s)!
Description: F960_admin was unable to start up properly.

Severity: P1
F960_ADMIN: utility request in unknown for lk:%d.
Description: Informational message. F960_admin task found the request from debug
utility was invalid.
Severity: P3
Representative.
F960_DBTOOL: Unable to send to F960_ADMIN
Description: The debug utility is unable to send messages to F960_admin task.

F960_admin task may have died or is not responding.
Severity: P3
been installed and properly configured. Reinstall the Fujitsu 960
Integration.
F960_IN task for lk:%d died.
Description: F960_in task has died. F960_admin task will attempt to start it.
Severity: P4
F960_IN: %s re-started, awaiting PBX initialization
Description: F960_in task has died and F960_admin task has successfully restarted it.
Severity: P4

F960_IN: **** Unable to name_locate F960ADM
Description: Informational message. F960_in task will attempt to resynchronize itself.

Severity: P3
F960_IN: can't read oaa data!
Description: Software error. F960_in task is unable to read oaa data record for
necessary configuration parameters.
Severity: P1
F960_IN: Error in opening %g (lk:%d) for read
Description: F960_in task was unable to open ctix device for read. x is 1-16.
Severity: P1
F960_IN: Error in opening %g (lk:%d) for write
Description: F960_in task was unable to open ctix device for write. x is 1-16.
Severity: P1
F960_IN: Invalid msg_type in message to F960_ADMIN.
Description: Informational message. F960_in task will recover from this error.
Severity: P3
F960_IN: Started

Severity: P4
Action: None.
F960_IN: Unable to initialize serial port:%s

Severity: P1

F960_IN: Unable to read oaa record.

Severity: P1
F960_IN: Unable to send to F960_ADMIN
Description: Informational message. F960_in task will attempt to resynchronize itself.

Severity: P3
F960_IN: usage: %s link_number, link_name.

Severity: P3
F960_MWAGENT: Cannot send to mwla !
Description: F960_mwagent task of the Fujitsu 960 Integration is unable to locate the
mwla task.
Severity: P3
Action: F960_mwagent task will retry forever. If the problem persists, check the
system configuration for possible problems/ inconsistencies, or reinstall the
software. If no anomalies are found, contact your Support Representative.
F960_MWI: Could not locate MWLA!
Description: F960_mwagent task of the Fujitsu 960 Integration is unable to locate the
mwla task.
Severity: P3
Action: F960_mwagent task will retry forever. If the problem persists, check the
system configuration for possible problems/ inconsistencies or reinstall the
software. If no anomalies are found, contact your Support Representative.
F960_MWAGENT: Invalid request from mwla
Description: F960_mwagent task received an invalid request from the mwla task.
Severity: P3
Representative.

F960_OUT task for lk: %d died.
Description: F960_out task has died. F960_admin task will attempt to start it.
Severity: P4
F960_OUT: %s re-started, awaiting PBX initialization
Description: F960_out task has died and F960_admin task has successfully restarted it.
Severity: P4
F960_OUT: *** Unable to name_locate F960ADM
Description: Informational message. F960_out task will attempt to resynchronize itself.

Severity: P3
F960_OUT: rec'd invalid msg(%d) fr ADMIN,lk:%d.
Severity: P3
F960_OUT: rec'd invalid reply, orig(%d),lk:%d.
Severity: P3
F960_OUT: Started

Severity: P4
Action: None.
F960_OUT: Unable to initialize CTI port:%s

Severity: P1
F960_OUT: Unable to read oaa record.

Severity: P1
F960_OUT: Unable to send to F960_ADMIN. Link number: %d.

Severity: P1
F960_OUT: usage: %s link_number, link_name.

Severity: P3
F960_SFAGENT: *** Node ID out of range!
Description: This message indicates that F960_sfagent task found the F960_admin task
has an invalid node ID. F960_sfagent task will attempt to locate the
F960_admin task again.
Severity: P3
F960_SFAGENT: can't send to f960admin!
Description: Informational message. F960_sfagent task cannot send messages to

F960_admin task and will try again later.
Severity: P3
“Failed in getm()for NUP_MSG_CNF_GRP”
Description: The getm() function allocates a message to send to the message parameter
part. If the message for NUP_MSG_CNF_GRP (NUP configuration group)
cannot be allocated, then this message is logged.
Severity: P4
Action:
“Failed in getm()for NUP_MSG_CONFIG”
part. If the message for NUP_MSG_CONFIG cannot be allocated, then this

error is logged.
Severity: P4
Action:
“Failed in getm()for TUP_MSG_CONFIG”
part. If the message for TUP_MSG_CONFIG cannot be allocated, then this
error is logged.
Severity: P4
Action:
Failed in getm()for TUP_MSG_CNF_GRP”
part. If the message for TUP_MSG_CNF_GRP (TUP configuration group)
cannot be allocated, then this error is logged.
Severity: P4
Action:
“Failed in receiving user part config confirmation”
Description: Waits for confirmation messages from TUP / NUP and if no confirmation
message is received, then this error is logged.
Severity: P4
Action:
Failed request on disk %d:%d due to out of service
Description: Redundant disk failed operation.

Severity: P4
Action: None.
Failed to access NVRAM (EXIT)
Description: System error during startup.

Severity: P3
“Failed to allocate memory, can’t config circuit groups”
Description: Memory cannot be allocated to configure the nup circuit groups. This error
is therefore logged.
Severity: P1
Failed to allocate redundant info structures
Description: System failure.

Severity: P2

Failed to attach interrupt handler: %s(EXIT)

Severity: P3
Failed to attach name space: %s (EXIT)

Severity: P3
Failed to attach timer: %s(EXIT)

Severity: P3
Failed to configure grp %d”
Description: Waits on a confirmation message from the user part. If no such message is
received, then the group has failed to configure and this error is logged.
Severity: P4
Action:
“Failed to configure user part, status: %d”
Description: When the confirmation message is received, its confirmation status is

checked. If the status is incorrect, then this error is logged as the user part
has failed to configure.
Severity: P4
Action:
Failed to get proxy: %s (EXIT)
Description: A system error occurred during startup.

Severity: P3
Failed to get sector 0 lock, owner %d
Description: Lock out control sector is in use.

Severity: P4
Action: Try again later.
Failed to map physical memory: %s (EXIT)
Description: A system error occurred during startup.

Severity: P3

Failed to malloc sector 0 (%c)
Description: A system failure occurred on startup.

Severity: P3
Failed to prefix to FAM node%d
Description: A system failure occurred..

Severity: P1
Failed to Reassign block (request=%d block=%lx)
Description: Device failure.

Severity: P2
Action: Contact for service. Disk might need replacing.
“Failed to receive CKT FREE on cic %d”
Description: A circuit free indication was not received on the circuit identification code.
Severity: P4
Action:
“Failed to receive BLOCK ACK on cic %d”
Description: A block acknowledgment was not received on the circuit identification code.
Severity: P4
Action:
“Failed to receive UNBLOCK ACK on cic %d”
Description: An unblock acknowledgment was not received on the circuit identification

code.
Severity: P4
Action:
Failed to remount as READ ONLY

Severity: P1
Action: Contact your Support Representative
Failed to send message, dst id 0x%x”
Description: Once the parameter area of the message has been successfully formatted
it is sent to the call processing module. If it cannot be sent then this error is
logged.
Severity: P4
Action:

“Failed to send message to user part”
Description: Wait for an acknowledgment that the message has been sent and if it is not
received then this error is logged.
Severity: P4
Action:
Fam node reassigned & mounted READ ONLY
Description: QNX file cannot be written due to loss of control over cache coherency.
Severity: P4
Action: None.
FAM: Unexpected Message%d
Description: Program interface error or system failure.

Severity: P1
Forcing system reboot
Description: A module has determined the system (all modules) must be reset. This
occurs in the event of multiple failures that result in the loss of a critical
resource and its hot standby.
Severity: P1
Action: If the multiple failures are related to a hardware failure, the faulty hardware
should be replaced. If other messages indicate a software problem, contact
Forcing system reboot\n
Description: Reboot event.

Severity: P4
Action: None.
FOT message received on CIC %d
Description: SS7 received a message from the adjacent point code that was not
expected.
Severity: P3
FREE_ENTRY: invalid pointer %d

Severity: P4

G
getapi1: long str %s
Description: The one contact application is using a string longer than the buffer allocated
for it. The string will be shortened.
Severity: P3
Action: The one contact application might have a bug. Contact the author.
get_api2: date str too long [%s]
Description: The one contact application instructs date-setting, and the string containing
the date was too long for the buffer.
Severity: P3
Action: The one contact application probably contains a bug. Contact the author.
get_api3: time str too long [%s]
Description: The string for time is too long.

Severity: P3
get_api2: digit str too long [%s]
Description: The string for digits too long.

Severity: P3
get_copylist: acreate rslt = %d, list = %s
Description: A failure occurred in creating a copy list data record. This is done
whenever a message is recorded and sent for delivery. As a result, a
message did not get delivered. This error indicates a serious problem with
the system. Perhaps the account data capacity of the system has been
reached and there are no free data records to be used for copy list creation.
Severity: P1
Action: Delete all unneeded mailboxes in attempt to free up data records. If the
problem still occurs, or there are no mailboxes that can be deleted, contact
get_cpy_list: acreate rslt = %d, list = %s
Description:
Severity: P4
Action:
get_sib_list: acreate rslt = %d, list = %s
Description:
Severity: P4
Action:

GET_TIME: delay was %d ticks, will retry later
Description: Indicates system performance level.

Severity: P4
Action: None.
GET_TIME: delay was %d ticks, will retry later
Description: Informational message, indicating a delay was detected while reading the
system time.
Severity: P4
Action: If this message is seen repeatedly, (more than 20 times in a day), contact
GET_TIME: Resolver returned an error
Description: Task 'resolver' died. It will be restarted.

Severity: P3
Action: If this happens repeatedly, contact your Support Representative. Otherwise
it is not a problem.
GET_TIME: Resolver returned an error
Description: System control module communication failure.

Severity: P4
Action: None.
GET_TIME: Send to resolver failed
Description: Problem in communicating to system control module.

Severity: P4
Action: None.
GET_TIME: Send to resolver failed
Description: Task 'resolver' died. It will be restarted.

Severity: P3
Action: If this happens repeatedly, contact your Support Representative.
Otherwise, it is not a problem.
GET_TIME: Unable to find primary resolver
Description: The system was unable to select a primary host for allocating system
resources. The system should reboot.
Severity: P1 or P4
Action: Might be seen when the system boots up or if a module dies. If seen at any
other time, check QNET connections, as this message could indicate a
QNet problem. If still having problems, contact your Support
Representative.
GET_TIME: Unable to find primary resolver

Description: Startup comment.
Severity: P4
Action: None.
GET VSEQ for %d failed, result=%d, retrying
Description: An application failed in an attempt to get information from the SFA. This
could be due to an SFA death. The request will be retried.
Severity: P4
Action: None.
H
Hard disk %d error.Key=%02x, Code=%02x, Sect=%s
Description: Hard disk error.

Severity: P1-4
Action: Take action based on the specific error reported.
Hard disk %d error=%04x, Sect=%s
Description:
Severity: P3
Action:
Hard disk %d is down!!!
Description:
Severity: P3
Action:
Hardware lost mailboxes, reiniting try %d
Description: Restarting request to device after failed attempt.

Severity: P4
Action: None.
HCXMWI: cannot send to mwla
Description: hcxmwi cannot communicate with the mwla task.

Severity: P2
Action: Reboot module, then reboot the system. Contact your Support
Representative if the problem persists.
HCXMWI: Unable to locate hcxsnd
Description: hcxsnd cannot find hcxsnd and cannot give it any requests. The integration
will not work properly.
Severity: P1

Action: Reboot the module, then the system. Contact your Support Representative
if the problem persists.
HCXMWI: Unable to locate mwla
Description: The hcxmwi task cannot locate mwla and cannot process message waiting
requests.
Severity: P1 if received more than once.
Action: Reboot the module, then the system. Contact your Support Representative
if the problem persists.
HCXMWI: Unable to update MWI %s for mailbox %.6s
Description: This happens if the link goes down during the message wait process or if
hcxmwi has tried to send to hcxsnd twice and has been unsuccessful. If
this happens often, there may be other problems with the link or with
hcxsnd.
Severity: P2 or P3
Action: Check both sides of the serial link to make sure communication is set up
properly. Contact your Support Representative if the problem persists.
HCXRCV: Bad RS232 port name
Description: This message is logged if hcxrcv is started up without a valid port name.
hcxrcv will abort.
Severity: P1 if the system is starting hcxrcv. P3 if the user started hcxrcv from the
QNX prompt.
Action: Check the configuration and make sure there is a valid port configured for
the Hitachi integration. Reboot the module. If this message appears after a
reboot, contact your Support Representative.
HCXRCV: Bad value %d for checkin FCOS

or
HCXRCV: Bad value %d for checkout FCOS
Description: A value less than 0 or greater than the maximum FCOS number (currently
64) was entered in the configuration data for the checkin FCOS. The task
will abort
Severity: P1
Action: Check the configuration data. Contact your Support Representative if this
problem persists.
HCXRCV: Bad value %d for checkin FCOS
Description: This error occurs when the value of the checkin FCOS, which is read in
from the Eeecooaa record, is not valid, meaning the value is less than zero.
Severity: P1
Action: Amend the Eeecooaa record by reconfiguring the FCOS checkin value from
the console.
HCXRCV: Bad value %d for checkout FCOS
Description: This error occurs when the value of the checkout FCOS, which is read in

from the Eeecooaa record, is not valid, meaning the value is less than zero.
Severity: P1
Action: Amend the Eeecooaa record by reconfiguring the FCOS checkout value
from the console.
HCXRCV: Bad value %d for clear greet on checkin

or
HCXRCV: Bad value %d for clear greet on checkout
Description: A value other than 0 or 1 is in the configuration data for clear greet on
checkin. If a 'y' or 'Y' was entered, the value should be 1, otherwise it
should be 0. The task will abort.
Severity: P1
problem persists.
HCXRCV: Bad value %d for clear msgs on checkin

or
HCXRCV: Bad value %d for clear msgs on checkout
Description: A value other than 0 or 1 is in the configuration data for clear messages on
Severity: P1
problem persists.
HCXRCV: Bad value %d for clear name on checkin

or
HCXRCV: Bad value %d for clear name on checkout
Description: A value other than 0 or 1 is in the configuration data for clear name on
Severity: P1
problem persists.
HCXRCV: Bad value %d for clear passcode on checkin|

or
HCXRCV: Bad value %d for clear passcode on checkout
Description: A value other than 0 or 1 is in the configuration data for clear passcode on
Severity: P1
problem persists.
HCXRCV: Failed to swap mailbox %s with %s
Description: hcxrcv received a ROOM_SWAP request and failed while processing it. A
log message indicating what part of the swap failed will appear before this

one. If the ..Deleted mailbox xxx, unable to recreate.. message is NOT
logged before this one, the old mailbox still exists.
Severity: P2
Action: Check the mailboxes for corruption and delete any bad mailboxes. If this
message appears often, contact your Support Representative.
HCXRCV: Failed to swap mailbox %s with %s
Description: This error occurs when the source oaa record cannot be unlocked or read.
This results in a room swapping failure as the data from the source mailbox
cannot be read into a new location.
Severity: P2
Action: Check that a mailbox has been created and that the mailbox number falls
within the dialing plan.
HCXRCV: Incorrect HCX data config'd in re-read eeco rec
Description: The configuration data is not valid. A log message indicating what part of
the configuration is incorrect will appear before this one.
Severity: P1
Action: Check the configuration. If the configuration is correct and the problem
persists, contact your Support Representative.
HCXRCV: Incorrect HCX data configured in eeco record
Description: The configuration data is not valid. A log message indicating what part of
the configuration is incorrect will appear before this one.
Severity: P1
Action: Check the configuration. If the configuration is correct and the problem
HCXRCV: Unable to find eeco OAA record
Description: hcxrcv is unable to read the configuration data for the integration. hcxrcv
will abort and the integration will not run.
Severity: P1
Action: Go to the Offline menu and reconfigure the application. Save changes
when you exit the Offline menu and activate the inactive configuration. If
the record was corrupted, doing this will write it to disk again and hopefully
correct the problem. If the problem persists, contact your Support
Representative.
HCXRCV: Unable to get stty on RS232 port
Description: hcxrcv is unable to get tty information (baud rate, parity, etc.) on the
configured port. The task will abort.
Severity: P1
Action: Make sure that a valid port is configured and that it is good. Try moving the
application to another port. If the same thing happens on a known good
port, contact your Support Representative.
HCXRCV: Unable to locate hcxsnd

Description: The hcxrcv task tried to locate hcxsnd 5 times and failed. The link is
probably down.
Severity: P1
Action: Check the serial link connections. If the problem persists, contact your
HCXRCV: Unable to open serial port
Description: hcxrcv is unable to open the serial port to read from it. hcxrcv will abort.
Severity: P1
Action: Check the configuration and make sure that no other application is trying to
use the same serial port. Make sure that a valid serial port is configured. If
the problem persists, contact your Support Representative.
HCXRCV: Unable to SET stty on RS232 port
Description: hcxrcv is unable to set the tty information (baud rate, parity, etc.) on the
Severity: P1
HCXSND: Bad RS232 port name
Description: This message is logged if hcxsnd is started up without a valid port name.
hcxsnd will abort.
Severity: P1 if the system is starting hcxsnd. P3 if the user started hcxsnd.
Action: Check the configuration and make sure that a valid port is configured for the
Hitachi integration. Try rebooting the module. If this message appears
after a reboot, contact your Support Representative.
HCXSND: Bad RS232 port name
Description: The integration serial port cannot be opened because the name does not
begin with S. This means that HCXSND cannot send data packets to the
PMS. Thus the integration fails.
Severity: P1
Action: Contact your Support Representative. There is little that you can do. The
QNX library function open_device has corrupted the cti serial port name,
and the name no longer begins with S.
HCXSND: Unable to attach name
Description: The QNX library function qnx_name_attach was unable to attach HCXSND
to HCXSND_NAME. This means that HCXSND cannot be located. Thus
the integration fails.
Severity: P1
Action: Contact your Support Representative. Errno is a Watcom C error file that
contains a value indicating the type of error detected. There is nothing you
can do.
HCXSND: Unable to attach name

Description: hcxsnd cannot start up and the task will abort.
Severity: P1
Action: Reboot the module, then the system. If the problem persists, contact your
HCXSND: Unable to get stty on RS232 port
Description: hcxsnd is unable to get tty information (baud rate, parity, etc.) on the
Severity: P1
HCXSND: Unable to open serial port
Description: hcxrcv is unable to open the serial port to read from it. hcxrcv will abort.
Severity: P1
Action: Check the configuration and make sure that no other application is trying to
use the same serial port. Make sure that a valid serial port is configured. If
HCXSND: Unable to open serial port
Description: The integration serial port cannot be opened. The number could be out of
range, or an error could have occurred in the function open_device. The
integration cannot send or receive information. Thus the integration fails.
Severity: P1
Action: Check the configuration. If an AG 8 card is used, the allowable port range
is 0 to 7. If a Digi board is used, the allowable port range is 0 to 23. If the
port number is within range, then this is a hardware problem.
HCXSND: Unable to SET stty on RS232 port
Description: hcxsnd is unable to set the tty information (baud rate, parity, etc.) on the
Severity: P1
HD assertion failed: %d %d line %d, file %s
Description: Program error.

Severity: P3
HD: Can't allocate disk info structure

Severity: P4

HD: Can't allocate disk request buffers

Severity: P1
HD: Can't attach name (%(errno))
Description: Startup failure.

Severity: P3
HD: Failed to select disk %d:%d
Description: Disk failure.

Severity: P3
Action: Contact service.
HD: Failed to send to hdfsys process (%(errno))

Severity: P1
HD: mmap failed during update of DOS part for disk %d:%d

Severity: P3
HD: No hard disks in the system
Description: Disks not installed or not deleted.

Severity: P1
Action: Check cables and power to drive bays.
HD: Out of request buffers

Severity: P1
HD: Process %d updating sector 0
Description: Configuration record update. Comment only.

Severity: P1
Action: None.
HD: RDN_cbf - read failed from disk %d:%d, submitting rdn read
Description: Primary attempts to read data failed on disk attempting data read on

redundant disk.
Severity: P3
HD: Received invalid message (op %d)
Description: System or interface error.

Severity: P3
HD: Received invalid message (type %d)
Description: System or interface error.

Severity: P3
HD: Unable to add disk %d:%d -- no units available
Description: Unable to complete add disk operation.

Severity: P4
Action: None.
HD: Unable to locate hdfsys process

Severity: P1
HD: unable to open shmem to update DOS part for disk %d:%d
Description:
Severity: P3
Action:
HD: write of block 0 on disk %d:%d invalid DOS part table
Description: Corrupted boot disk.

Severity: P3
HD: XPT_action() failed with status 0x%x
Description: Device fault.

Severity: P3
HDFSYS: Can't attach name (%(errno))

Severity: P1

HDFSYS: Can't attach proxy (%(errno))

Severity: P1
HDFSYS: Can't locate Fsys

Severity: P1
HDFSYS: Can't share segments with Fsys (%(errno))

Severity: P1
HDFSYS: Error connecting to Fsys (%(errno))

Severity: P1
HDFSYS: MAP_seg can't get Fsys segment (%(errno))

Severity: P1
HDFSYS: MAP_seg Fsys segment too large (%d)

Severity: P1
HDFSYS: MAP_seg unable to get segment info (%(errno))

Severity: P1
HDFSYS: Receive from CAM failed (%(errno))

Severity: P1
HDFSYS: Unable to allocate DMA memory (%(errno))

Severity: P1
HDFSYS: Unable to get segment info (%(errno))

Severity: P1
HDFSYS: Unknown message type: %d

Severity: P1
HD_cbf: error from SIM: camErr:%x, senseKey:%x
Description: Device failure.

Severity: P3
HD_cbf: XPT_action() failed with status 0x%x
Description: Device error.

Severity: P3
HISADMIN: Close cpy_list failed, MB%s msg#%d !merged
Description: To merge mailboxes hisadmin must copy the siblings attached to

messages. A copy list is needed to hold sibling information. If the cpy_list
of a message is not closed after copying, then the message is not moved.
Integration carries on as normal but the mail merge is incomplete.
Severity: P3
Action: Check the system resources. If these are too low, the system will not be
running correctly. Reactivate and renew tasks by rebooting and reloading
the HIS extra-cost diskette. The his tasks may have gotten into an incorrect
state due to other problems. Check the logfile for other problems. Contact
your Support Representative if assistance is needed.
HISADMIN: Close sib list failed, MB%s msg#%d !merged
Description: If the sibling list cannot be closed, then the message is not sent and the
mail merge is incomplete. Integration continues as normal.
Severity: P3
Action: Check the system resources. If these are too low, the system will not be
running correctly. Reactivate and renew tasks by rebooting and reloading
the HIS extra-cost diskette. The his tasks may have gotten in an incorrect
state due to other problems. Check the logfile for other problems. Contact
your Support Representative if assistance is needed.

HISADMIN: Excessive Q_Open Errors
Description: HISADMIN has tried to open the queue 10 times in a row. It is unlikely that
the queue is busy for this long, so there is a problem with opening the
queue. HISADMIN cannot operate if it cannot receive instructions from
HISRCV. Thus the process dies and the integration fails.
Severity: P1
Action: Check the system resources. If the memory is sufficient, reactivate tasks to
execute a new hisadmin. This can be done by rebooting. If the problem
still exists notify your Support Representative. There may be a problem
with queue_open, a QNX library function.
HISADMIN: Excessive Q_Read Errors
Description: HISADMIN has tried to read the queue 10 times in a row. It is unlikely that
the queue is busy for this long, so there is a problem with reading the
queue. HISADMIN cannot operate if it cannot receive instructions from
HISRCV. Thus the process dies and the integration fails.
Severity: P1
Action: Check the system resources. If the memory is sufficient, reactivate tasks to
execute a new hisadmin. This can be done by rebooting. If the problem
still exists notify your Support Representative. There may be a problem
with queue_read, a QNX library function.
HISADMIN: Get_cpy_list failed, MB%s msg#%d !merged
Description: Each message has a cpy_list associated with it that contains the message
script and to whom the message has been sent. This error is reported
during mail merging when the contents of the source mailbox must be
moved and merged with the destination mailbox. Failure to get a cpy_list of
a message means that mail merging has no message to transfer. Thus
mail merging for this particular message does not take place and the mail
merge is incomplete. Integration continues as normal.
Severity: P3
Action: Check the system resources. Check that tasks are in the correct states. If
there is no apparent problem, contact your Support Representative as this
may be a software problem.
HISADMIN: Get_sib_list failed, MB%s msg#%d !merged
Description: A message has a sibling list attached to it. A sibling list is a list of the
forwarding history of the message. Most messages have an empty sibling
list. Only messages that have been forwarded have information in the
sibling list. However, Get_sib_list should not fail. If it fails, the message is
not copied and mail merging is incomplete.
Severity: P3
Action: Check the system resources. If these are normal, this must be a software
problem associated with the message attributes of the messages stored in
the source mailbox. Report this problem to your Support Representative.
HISADMIN: Lock Error MB %s. No msgs merged
Description: An error occurred when locking the source mailbox. The mailbox was
located but cannot be locked. This is an internal oaa record problem. No

mail is merged.
Severity: P2
Action: The mailbox has already been checked that it is valid and not in use. So
this appears to be a software problem. Check the system resources. If
these are sufficient, contact your Support Representative and report the
software bug.
HISADMIN: MB %s in use. No msgs merged
Description: The source mailbox was in use then the PMS tried to lock it for merging.
No merging could take place.
Severity: P4
Action: Try again later, and make sure no one is using the source mailbox that
needs to be merged.
HISADMIN: No MB %s. No msgs merged
Description: PMS could not locate the oaa record for the given source mailbox number.
This should not happen since the mailbox number has previously been
validated. No mail merge takes place.
Severity: P2
Action: Verify that the source mailbox number exists. Check the system resources.
If these are sufficient, report a software bug to your Support
Representative.
HISADMIN: Open cpy_list failed, MB%s msg#%d !merged
Description: This error is reported during mail merging when a cpy_list of a particular
source mailbox message fails to open. There is a cpy_list associated with
each mailbox message. Failure to open a cpy_list of a message means
that the message cannot be merged into the destination mailbox. Thus mail
merging of the source mailbox to the destination mail box is incomplete.
Severity: P3
Action: Check the system resources. If these are sufficient, there could be a
software problem associated with messages stored in the source mailbox.
Try merging messages using another source mailbox. If the problem still
exists, contact your Support Representative and report the bug.
HISADMIN: Open sib list failed, MB%s msg#%d !merged
Description: The sibling list of a message could not be opened. All messages possess a
sibling list, a list that contains the forwarding history of the message.
However, most sibling lists are empty lists. If the sibling list cannot be
opened, the message is not copied and an incomplete mail merge occurs.
Severity: P3
Action: Check the system resources. If these are sufficient, there could be a
software problem associated with messages stored in the source mailbox.
Try merging messages using another source mailbox that has sibling
messages. If the problem still exists, contact your Support Representative
and report the bug.
HISADMIN: Q_Open Error %d

Description: Unable to open the queue that holds requests for action from HISRCV.
This error means the queue is busy.
Severity: P4
Action: None. HISADMIN will try to open the queue again.
HISADMIN: Q_Read Error %d
Description: Unable to read from queue. This error means the queue is busy.
Severity: P4
Action: None. HISADMIN will try to read the queue again.
HISADMIN: Read Error MB %s. No msgs merged
Description: The destination mailbox oaa record could not be read, causing the mail
merge and the room swapping function to fail.
Severity: P2
Action: Check that the destination mailbox address is within the required range.
There is a problem with the oaa record reading function or the mailbox
address.
HISADMIN: Read Error MB %s. No msgs merged
Description: The source mailbox oaa record could not be read even through it has been
located and locked to prevent others from changing the contents while
merging. The mail merge and the room swapping function fails.
Severity: P2
Action: There is a problem with the oaa record reading function found in oa_send.
This is not a user related problem.
hisinit: Exit mailbox resynchronize loop
Description: Informational message. Either there are no mailboxes to update during the
resync mailbox process or all updates have been completed.
Severity: P4
Action: None.
hisinit: Unable to attach to HISINIT name
Description: As HISINIT is unable to attach a name to itself, HISRCV cannot contact it.
HISRCV contacts HISINIT to RESYNC mailboxes and turns on any pending
message waiting light indicators. Thus the message waiting light indicators
fail.
Severity: P2
Action: This is a QNX qnx_name_attach library function error. Contact your
hisinit: Unable to locate MWLA
Description: HISINIT turns on message waiting lights following a link resync message in
HISRCV. This error message indicates that the message waiting light
administer cannot be located. Thus, the message waiting light does not go
on; the message waiting light fails.

Severity: P2
Action: This is a MWLA problem. Contact your Support Representative.
HISMWI: Unable to locate mwla
Description: The message waiting light administrator cannot be located. HISMWI gets
requests from the administrator and translates the formats of the request so
that the HISSSND can read them. A failure to locate the message waiting
light administrator means a message waiting light failure.
Severity: P2
Action: This is a MWLA problem. Contact your Support Representative.
HIS PMS Link is down
Description: Data was sent across the PMS link and not acknowledged. Since the other
end of the link is not responding, NuPoint Voice logs this link down
message.
Severity: P2 (link is down but NuPoint Voice is up)
Action: Check the serial link connections and make sure that the PMS is
communicating with the NuPoint Voice. If the problem persists, contact
HIS PMS Link is up
Description: NuPoint Voice received data over the PMS link.

Severity: P4
Action: None. Informational message only.
HISMWI: cannot send to mwla
Description: hismwi cannot communicate with the mwla task.

Severity: P2
Action: Reboot the module, then try rebooting the system. Contact your Support
HISMWI: Unable to update MWI %s for mailbox %.6s
Description: This happens if the link goes down during the message wait process, or if
hismwi tried to send to hissnd twice and was unsuccessful. If this happens
often, there may be other problems with the link or with hissnd.
Severity: P2 or P3
Action: Check both sides of the serial link to make sure communications are set up
properly. Contact your Support Representative if the problem persists.
HISRCV: Failed to swap mailbox %s with %s
Description: hisrcv received a MOVE_MBOX request and failed while processing it. A
log message indicating what part of the move failed will appear before this
one. If the ..Deleted mailbox xxx, unable to recreate.. message is NOT
logged before this one, the old mailbox still exists.
Severity: P2
Action: Check the mailboxes for corruption and delete any bad mailboxes. If this

message happens often, contact your Support Representative.
HISRCV: Q_Open Error %d
Description: Unable to open queue in which the requests to HISRCV for mailbox merge
have been placed. This error may occur because the queue is busy. The
queue ID number will thus be incorrect and the mail merge corrupted.
Severity: P2
Action: Try again later.
HISRCV: Q_Write Error %d
Description: Queue is open but there is a failure in writing to the queue. This means that
HISRCV cannot send instructions to HISADMIN about mailbox merging. As
a result, mail merging will not occur.
Severity: P2
Action: QNX queue failure. Contact your Support Representative.
HISRCV: Unable to locate hissnd
Description: HISRCV has tried five times to attach HISSND by name and failed.
HISSND must have died so no integration can take place.
Severity: P1
Action: Restart the integration.
HISSND: Unable to attach name, retrying.
Description: HISSND cannot attach a name to itself. Therefore, others are unable to
locate it. HISSND will keep trying to attach a name to itself. If it succeeds,
the integration resumes as normal. Otherwise, the integration fails.
Severity: P1 if the loop is not exited. P4 if the system recovers.
Action: QNX library function.
Hitachi PMS link is down
Description: Data was sent across the PMS link and not acknowledged. Since the other
end of the link is not responding, NuPoint Voice logs this link down
message.
Severity: P2 (link is down but NuPoint Voice is up)
Action: Check the serial link connections and make sure that the PMS is
communicating with the NuPoint Voice. If the problem persists, contact
Hitachi PMS link is down
Description: The integration polls the PMS three times. If there is no answer, it assumes
that the link is down and sends the error message. If a reply is received
after this time period then a subsequent message confirms the link is up.
This message indicates the link is unresponsive, rather than down.
Severity: P4
Action: Reactive the link by sending an ack or aok from the PMS.

Hitachi PMS link is up
Description: NuPoint Voice received data over the PMS link.

Severity: P4
Hold queue is full. Reqs will be discarded
Description: Request will be discarded.

Severity: P3
Action: None.
I
Ignoring an offhock cmd in active stare in ln %d\n
Description: Some misconfiguration makes the application try to go offhook while it is

already offhook.
Severity: P4
Action: Check the configuration, usually the pager configuration.
INBAND: Cannot find SFA
Description: Inband cannot find SFA. This is a software error. SFA must be running for
InBand to work.
Severity: P1
Action: Check the system resources. Restart tasks so that they reinitialize to the
original states. Do this by rebooting the system. If the problem persists,
report it to your Support Representative as a possible software bug.
INBAND: Invalid Action (%c) in template
Description: Invalid character n in the action field of a template.

Severity: P2
Action: Correct the template from online menu.
INBAND: Invalid character (%c, hex %x) in template
Description: Invalid character n in the data field of a template. The hex value is xx.
Severity: P2
Action: Correct the templates from online menu.
INBAND: Invalid input %d in state %d. Software error
Description: This is a software error that indicates the state machine is lost. Inband will
not be operational. The message is repeated every 60 seconds.
Severity: P1
Action: Check the system resources. Reboot the system and reload InBand
integration. If the problem persists, contact your Support Representative.

INBAND: Not enough memory to run application
Description: InBand unsuccessfully tried to allocate scratch pad memory.

Severity: P1
Action: There is not enough memory in the system. Add more memory.
INBAND: Please install application and reactivate configuration
Description: The InBand template has not yet been installed.

Severity: P2
Action: Install the template and reactivate the configuration.
infoadmin: cannot create QUERY_REC
Description: This may be seen if a module has died. If the continuous operation feature
is enabled, the system will recover. Otherwise, the system will reboot.
Severity: P3
Action: None.
infoadmin: cannot register name, node %d
Description: This may be seen if a module has died. If the continuous operation feature
is enabled, the system will recover. Otherwise, the system will reboot.
Severity: P3
Action: None.
infoadmin: could not read FAX GROUP REC %s
Description: Fax configuration information cannot be accessed.

Severity: P3
Action: Check the fax configuration or check for a possible disk failure.
infoadmin: could not read GROUP REC %s
Description: Line configuration information cannot be accessed,

Severity: P3
Action: Check the line configuration or check for a possible disk failure.
informing process %s failed (%s)
Description: The agent task fails to inform sfa with some data.
Severity: P2
Initial loading of card %s failed (%s)
Description: Resource manager fails to spawn the loader program. This will disable all
the cards.
Severity: P1

INIT WKUP LIST: oa send returns %d
Description: The wua program upon start up tries to read the wakeup account from disk.
If the wakeup account does not exist, wua tries to create a new one. This
error message comes up when wua fails to create a record for the wakeup
account (there are 12 records per wakeup account). This is caused by a
corrupted record. If it happens frequently, it can signal a hard disk problem.
Severity: P2
Action: If more than one message shows up each time the system is reset, the hard
disk may need to be replaced or reformatted.
INIT: spchblk %ld(pt=%u) in rsrv msg %u, rsrv=%u
Description: sam task allocated a reserved speech block for a non-reserved message.
Severity: P2
Action: Run a system verify. If the problem persists, contact your Support
Representative.
Initialize 7404D Data Link [%s]
Description: This is a normal message during a system reboot. In other cases, vmemo
is receiving an unknown data packet from SYS75/SYS85 on the host
system at a different baud rate, so vmemo will try to re-synchronize with the
SYS75/85 by reinitializing the link.
Severity: None during system reboot. P2 during normal operation.
Action: If this message appears during normal system operation, turn on CDR and
log CDR to a file. Also check your SYS75/85 for any discrepancy in user
phone setup. Immediately contact your Support Representative.
Invalid disk error queue. No disk errors reported.
Description:
Severity: P1
Action:
Invalid disk index %d. Num account disks is %d
Description: Internal error.

Severity: P1
Invalid fax channel assigned. Check line and fax configuration.
Description: At fax application startup, the H:S:P: specified is not a fax HW

Severity: P3
Action: Check the fax configuration.
Invalid Maint Msg %d
Description: If an invalid maintenance message is received when the user maintenance

request is being performed then this informational error is logged.
Severity: P4

Action: None.
Invalid Record compression rate, default used
Description: An invalid compression rate was received from the application. This is a
software error.
Severity: P3
Invalid sector 0, initializing to default values
Description: Corrupted or blank boot disk.

Severity: P1
irq) out-of-window collision (bad hardware)
Description: This error message is reported by QNX. This problem is caused by out-of-
specification hardware or cabling on your network. The most likely cause of
these out-of-window problems is the use of a low-quality mini-hub. Out-of-
window problems occur when certain Ethernet timing specifications are
violated. This could be caused by: Lower quality mini-hubs, cabling whose
length exceeds the maximum permitted or cascading too many hubs in
series.
Severity: P4
Action: Check your network cable length and hubs.
ISUP alarm event 0x%x
Description: An unexpected event was forwarded by the ISUP protocol layer.

Severity: P3
I/O request while redundant disk %d:%d not present
Description: Attempted request on uninstalled, undeleted redundant disk.

Severity: P4
Action: Disable the disk having the address noted.
ISUP cir grp maint msg on CIC %d failed
Description: The ISUP SS7 message on the circuit group was not acknowledged by the
adjacent point code.
Severity: P2
Action:
ISUP cir maint msg on CIC %d failed
Description: The ISUP SS7 message on the circuit was not acknowledged by the
adjacent point code.
Severity: P3
Action: Review the SS7 troubleshooting guide for further action.

ISUP error indication on ckt %d
Description: The SS7 state machine and the protocol layer are out of sync.
Severity: P3
ISUP failed to receive BLA on CIC %d
Description: The adjacent point code did not respond to our blocking message.
Severity: P3
ISUP failed to receive CGBA on CIC %d
Description: The adjacent point code did not respond to our circuit group blocking
request.
Severity: P3
ISUP failed to receive CGUA on CIC %d
Description: The adjacent point code did not respond to our circuit group unblocking
request.
Severity: P3
ISUP failed to receive GRA on CIC %d
Description: The adjacent point code did not respond to our circuit reset request.
Severity: P3
ISUP failed to receive RLC on CIC %d
Description: The adjacent point code did not respond to our reset request.
Severity: P3
ISUP failed to receive UBA on CIC %d
Description: The adjacent point code did not respond to our unblocking request.
Severity: P3
ISUP high level conjestion
Description: The system messaging capacity is exceeding operating level and is now in
congestion.
Severity: P2

ISUP low level conjestion
Description: The system messaging capacity is exceeding the normal level.

Severity: P3
ISUP maintenance request on CIC %d failed
Description: An administrator initiated maintenance action failed.

Severity: P3
ISUP reattempt indication on ckt %d
Description: The SS7 state machine and the protocol layer are out of sync.
Severity: P3
ISUP received message for unequipped CIC %d
Description: SS7 activity was received for a circuit that is not configured in SS7 line
groups.
Severity: P3
ittmwi: cannot send to mwla
Description: ittmwi cannot send to mwla, will not be able to get message waiting
requests from mwla, or send the result of any previously processed request
to mwla. The integration will not process message waiting requests. ittmwi
will try to locate mwla, then try to start mwla, then exit if it cannot get the
task id.
Severity: P1
Action: Check the system resources. Try rebooting the module. If the problem
ITTMWI: could not find ittsnd
Description: The ittmwi task tries to locate ittsnd by doing a detach_port on the argument
passed to ittmwi. ittmwi will continually try to find ittsnd.
Severity: P1
ITTRCV: can not send to sfa, aborting
Description: The ITT 3100 phase II integration program was unable to talk to the sfa
program.
Severity: P2 or P3
Action: Check the logfile for other errors. The ittrcv task should be seen to have
died and restarted. If it repeatedly dies, look for some other system
anomaly in the log file. If no other anomalies are found, verify that the

communication over the QNET is still working. If still no problems are
IVMSXFR: bad dtiagnt type %d. Contact your distributor
Description: Bad dti agent type.

Severity: P3
Action: Check the DTI/MRO configuration. Check the SL1-IVMS configuration.
Check the PBX group configuration. Check the line from the SL1-IVMS
PBX. Check the mailbox configuration. Check the online configuration
transfer type. Contact your Support Representative.
IVMSXFR: bad snd type %d. Contact your distributor
Description: Software communication error. Incompatible software revisions.

Severity: P2
Action: Check the software revision.
IVMSXFR: bad transfer logical line (%d)
Description: Software communication error. Line range is from 0 to the number of active
logical lines.
Severity: P2
Action: Check the MRO/SL1-IVMS configuration.
IVMSXFR: Got transfer fail msg from xfr line %d.

No request match states:%d,%d
Description: Got transfer fail message from transfer line.

Severity: P3
Check the PBX group configuration. Check the line from the SL1-IVMS
PBX. Check the mailbox configuration. Check the online configuration
transfer type. Contact your Support Representative.
IVMSXFR: queue full, element size:%d
Description: Software resource error.

Severity: P3
IVMSXFR: state syn err: req st:<state>, ln st:<xfer state>

Severity: P3
Action: The system should correct itself. Check the MRO and SL1-IVMS
configurations. Check the MRO card.
IXFAGNT: can't locate (%s)
Description: ixfragnt cannot locate [task name].

Severity: P3
Action: The system should correct itself. Check the DTI/MRO configuration. Check
the SL1-IVMS configuration. If changes are made to any configuration via
the offline menu, be sure to activate the inactive configuration. If the
system is still having problems, contact your Support Representative.
IXFR DTIAGNT: can't locate (%s)
Description: dti_agent cannot locate [task name].

Severity: P3
the offline menu, be sure to activate the inactive configuration. If problems
persist, contact your Support Representative.
IXFR SNDAGNT: can't locate snd
Description: Cannot locate ixfr send task.

Severity: P3
the offline menu, be sure to activate the inactive configuration. If problems
persist, contact your Support Representative.
IXFR: bad message origin, contact Centigram
Description: The task ixfr is receiving a bad request message from another task.
Severity: P3
Action: The system should correct itself. Check the SL1-IVMS configuration, the
MRO card, and the DTI/MRO configuration. If this message occurs often,
IXFR: bad sndagnt type %d. Contact Centigram
Description: Software communication error. Incompatible software revisions.

Severity: P2
Action: Check the software revision. Contact your Support Representative.
IXFR: dti msg %s, no request match

Severity: P2
IXFR: Task <id> attached to IXFR PORT
Description: Task <id> attached to ixfr port.

Severity: P4
Action: Informational message for the user/administrator only.
IXFR: Unable to attach name (%s)

Description: Unable to attach name.
Severity: P4
Action: The system might have a util already running. The utility is for internal use
only.
IXFR_DTIAGNT: *** Send to dti(%x) failed
Description: The dti_admin task died.

Severity: P3
Action: None. The tasks will re-synchronize.
IXFR_DTIAGNT: *** Unable to send to ixfr
Description: The ixfr task died.

Severity: P3
IXFR_SNDAGNT: *** Unable to send to ixfr

Severity: P3
IXFR_SNDAGNT: *** Unable to send to snd (%x)
Description: The ixfr send task died.

Severity: P3
IXFRAGENT: can't send to slave%d
Description: Cannot send to slave task id.

Severity: P3
IXFRAGENT: Unable to get slave%d tid!
Description: Unable to get slave task id.

Severity: P3
Replace the DTI/MRO card. Check the system memory.
IXFRSLAVE(%d): *** Unable to locate %s

Severity: P3
IXFRSLAVE(%d): out of request space
Description: Software resource problem or the ixfr task died.

Severity: P3
IXFRSLAVE(%d): send to ixfr failed
Description: Cannot send to ixfr.

Severity: P3
Replace the DTI/MRO card.
IXFRSLAVE(%d): Unable to attach name (%s)
Description: There are multiple copies of the ixfrslave task running.

Severity: P2
Action: Check the configuration (offline menu).
IXFRSLAVE: can't find tid %x, link %d for reply.

Contact Centigram
Description: Cannot find tid [task_id] and line [line_number] to reply.

Severity: P2
Action: Check the SL1-IVMS and SL1-MRO configurations. If the system does not
correct itself, reboot the system.
L
Last 20 requests to PGA SB:
Description: When standby gets out of sync, it prints out the last 20 requests received
before it terminates itself.
Severity: P1
listparser: cannot read request record <%s>
Description: List parser cannot read the copy list record that it was told to parse.
Severity: P2
Action: This could be caused by an error in the system. Run a verify.
listparser: copy list not meant for list parser <%s>
Description: A copy list was sent to listparser and read but the flag indicates that the
record should not have gone to listparser.
Severity: P2
Action: Most likely caused by an error in the system. Contact your Support
Representative.
listparser: failed to create copy_link
Description: Either oaa is not running or the account space is full.

Severity: P1
Action: Check the statistical output. If the account space is full, you must delete
mailboxes/contact boxes, dist lists, cdr records, etc., to free up space. If the
account space does not show as full, contact your Support Representative.
listparser: failed to create head net copy_link

Severity: P1
Listparser: failed to create net copy_link

Severity: P1
listparser: fail to create head copy_link
Description: Listparser could not create an oaa record. Either all records are used up or
oaa is not functioning properly.
Severity: P1
Action: Check statistics to verify that all records are used up. If so, you must
correct this situation before any contacts can be processed. Either add a
disk, delete mailboxes, or run a verify to clean up any orphaned records
that should not be present on the system.
logmenu: could not write to %s
Description: System problem, corrupt log directory, or log full.

Severity: P3
Action: chkfsys /usr/vm/log to determine whether log directory is corrupt. Contact
LPA message received on CIC %d -- not part of Q.767
Severity: P3
Action: Contact your Support Representative if this happens repeatedly.
lstart: no MWLA running!
Description:
Severity: P2
Action:

M
MA: bad link #x rcvd from mitelsnd.
Description: The link number received by miteladmin is out of bounds. That is, it is <
zero and >= max integration links (16). The integration will not work.
Severity: P1
MA: bad software type x in MITEL_IO
Description: The mitel software type is not 217, 1001, or 1003 (0,1,2). The integration
will not work. The integration would not know how to treat different events.
Severity: P1
MA: bad software type x in MITEL_MWI
Severity: P1
MA: bad software type x in REFRESH_MWI
Severity: P1
MA: bad software type x in timer
Severity: P1
main_menu exit: aread failed, rslt = %d
Description: This log message comes up when a user's mailbox record could not be
read. Users may hear incorrect count of messages if they have received
new messages during the session.
Severity: P3
main_menu x: aread failed, user[%s] rslt = %d
Description: Cannot read a user account - function proceeds and returns to attendant.
Severity: P2
Action: As this message indicates an error in the system, report this to your

Master priority set to %d
Description: Startup comment.

Severity: P4
Action: None.
Master%d: unable to find shutdisk on node %d after 10 min, reboot
Description:
Severity: P4
Action:
Master%d: unable to send to shutdisk on node %d, reboot
Description:
Severity: P4
Action:
mb_totals: Reached the max number of mbox codes (%d)
Description: Warning that you have too many department codes for the report to count.
This message is logged because the report can be run automatically by
configuring it in the gather menu.
Severity: P4
Action: You could reduce the number of different department codes below 200 or
ignore the error.
“MessageServer gets an unknown/unsupported event type %d”
Description: Message from sfa in the state machine is processed and the event type is
determined. If the message server gets an unknown/unsupported event
type then this informational error is logged to indicate that SS7 transfer is
not supported.
Severity: P5
Action: Configuration error. The operator extension number in the online
configuration menu should be removed.
MCB2 MONITOR is already running (EXIT)
Description: Attempted load of mcb2_monitor program is already running.

Severity: P4
Action: None.
MCSS reattach(%d): locate(sfa) failed
Description: An application has tried for 16 seconds and failed to relocate the SFA after
an SFA death. This will result in a death of the application (and the loss of
a contact if one was active). Both the SFA and the application should be
restarted. On a busy system it is possible that it can take longer than 16
seconds for the SFA to be restarted; hence this message appears.

Severity: P3
Action: If the sfa death is unexplained, contact your Support Representative.
MITELADM: can't read oaa data!
Description: Miteladmin cannot successfully read from the open oaa record.
Severity: P1
Action: Check the system resources. If these are low, check that no duplicate
tasks are running. If the resources seem fine, restart Miteladmin by
reactivating the configuration or rebooting the system. If problems persist,
notify your Support Representative.
MITELADM: No extn# configured for link %d!
Description: No ext # configured for link.

Severity: P3
Action: Configure ext # in offline menu
MITELADM: No pick up access code configured!
Description: No pick up access code configured.

Severity: P3
Action: Configure pick up access code in offline menu.
MITELADMIN: Net status changed
Description: Network status has change; will update status.

Severity: P4
Action: None, informational message only.
MITELMWI can't read oaa data!
Description: Cannot locate MWLA, cannot get admin task id, or cannot read oaa record.
Severity: P1
Action: Check the system resources. If these are low, check that no duplicate
tasks are running. If the resources seem fine, restart Mitelmwi by
reactivating the configuration or rebooting the system. If problems persist,
MITELADMIN: unable to attach name MITELADMIN
Description: As the name_attach failed, other tasks will not be able to find miteladmin. If
this message is logged, the miteladmin program will exit and the integration
will not come up. No contacts will be answered.
Severity: P1
Action: Restart miteladmin by rebooting system. Check the system resources. If
these are low, check to make sure that multiple copies of the same task
aren't using up system resources. If the error persists, contact your Support
Representative.
mitel admin unable to create rcv task. link=x

Description: miteladmin was unable to create mitelrcv for a particular link. This link will
not work properly because NuPoint Voice would not read from it. This link
will not answer any contacts.
Severity: P1
mitel admin unable to create snd task. link=x
Description: miteladmin was unable to create mitelsnd for a particular link. NuPoint
Voice will not be able to send to this link. If this is a dedicated link, NuPoint
Voice will not be able to operate mw lights. If this is a regular link AND it is
already initialized, it will be able to answer contacts. If it is not initialized,
the integration will not work.
Severity: P1
MITEL MWI: cannot send to MITEL ADMIN
Description: Cannot send to miteladmin task id. As a result, no message waiting lights
will be set.
Severity: P1
Action: Restart miteladmin, by either activation from the console or by rebooting. If
the problem persists, check the system resources. If these are low, find out
if any multiple tasks are running that could be terminated. If problems still
exist, contact your Support Representative.
MITEL MWI: *** Unable to get miteladmin tid!
Description: Cannot find miteladmin task id. As a result, no message waiting lights will
be set.
Severity: P1
Action: Restart miteladmin, by either activation from the console or by rebooting. If
the problem persists, look at system resources. If these are low, find out if
any multiple tasks are running that could be terminated. If problems still
exist, contact your Support Representative. There could be a software
problem associated with qnx_name_locate.
MITEL MWI: could not find mwla
Description: Cannot locate MWLA. As a result, no message waiting lights will be set.
Severity: P1
Action: Restart mwla and mitelmwi by rebooting. If the problem persists, contact
your Support Representative. There could be a software problem
associated with qnx_name_locate.
MITELRCV **** Cannot find miteladmin
Description: Mitelrcv could not locate miteladmin.

Severity: P1
Action: Restart mitelrcvand miteladmin by rebooting. If the problem persists,
contact your Support Representative. There could be a software problem

associated with qnx_name_locate. Check the system resources to see if
they are sufficient.
MITELRCV:...can't read oaa data!
Description: Failed to read the open configuration record. The program will terminate
and a new one will start.
Severity: P1
Action: Check the system resources. Reboot the system. If the problem persists,
MITELSND can't read oaa data!
Description: Cannot connect the cti link or cannot read oaa data.
Severity: P1
Action: Check Smartcard links and hardware. Reboot. Check the system
resources. If problems persist, notify your Support Representative.
MITELRCV: Error in reading contact info from device
Description: Cannot establish the link, cannot connect to admin, cannot read oaa, or
cannot contact info from the device.
Severity: P1
Action: Check hardware connections and Smartcard links. Check the system
resources. If there is no apparent problem, notify your Support
Representative.
MITELRCV: Error opening link %d for read
Description: Cannot establish the link, cannot connect to admin, cannot read oaa, or
cannot contact info from the device.
Severity: P1
Action: Check the system configuration to make sure that the port being used is
configured. Is the port assigned to Mitel Integration? Check hardware
cables and cards. Try using another port. If assistance is needed, contact
MITELRCV: Error. link %d name incorrect
Description: Link name does not start with $. Cannot read information from the device.
Severity: P1
Action: If the correct name appears on the configuration table, this is a software
error occurring when information is copied to the local Link Tab array.
Check the system resources. If the problem persists, contact your Support
Representative.
MITELRCV: io t/o on link %d after digit
Description: I/O time-out on link after reading a digit. Informational message associated
with receiving a contact.
Severity: P4
Action: None.

mitel rcv task died,link %d. rcv restarted
Description: mitelrcv has died and miteladmin has successfully restarted it.
Severity: P2
Action: This should be investigated, but it is not fatal. Check the system
MITELSND: **** Cannot find %s\n
Description: Mitelsnd could not locate Miteladmin. The integration fails.

Severity: P1
Action: Restart Mitelsnd and miteladmin by rebooting the system. If the problem
persists, check the system resources.
MITELSND...no cti link configured
Description: No link configured.

Severity: P4
Action: Configure a link in the offline menu.
Mitelsnd: Signal %d rcvd, resetting link
Description: Received interrupt signal. Commit suicide and restart.

Severity: P4
mitel snd task died,link %d. snd restarted
Description: mitelsnd has died and miteladmin has successfully restarted it.
Severity: P2
Action: This should be investigated, but it is not fatal. Check the system
MITELADMIN: cannot start mwi refresh task

Status of create is x
Description: The create of the mitelrefresh task was not successful. The message
waiting lights will not be refreshed. In 1001 and some revisions of 217,
message waiting lights will be turned off after 24 hours.
Severity: P1 on 1001 PBX software.
MITELADMIN: Could not set DND on link %d
Description: During the integration initialization, DND could not be set on the message
waiting link. DND is used to try to keep people from contacting the
message waiting phone. If DND is not set and people contact the phone, it
will ring-no-answer. It could interfere with message waiting because if the
message waiting set's display shows a contact, it doesn't show date/time,
which is the link alive message.

Severity: P2 or P3
Action: Check the PBX COS for the Message Waiting Set. Check the system
MITELADMIN: error BAD DATA from link %d
Description: The firmware on the integration phone did not understand what was sent to
it and returned an error.
Severity: P1, P2
Action: If the error continues, there are firmware problems. If the error occurs once
in a while, it should be investigated but is not fatal. Contact your Support
Representative.
MITELADMIN: invalid ext nnn for MSG light(TIMEOUT)/no MSG_ON/no

INDIV_MSG_ON
Description: System has timed out while dialing during the message waiting process.
Possible causes are:
• the extension number was not a valid PBX number
• the extension number could not be used as a forward-to-target
• there is a link problem.
Severity: P2, P3, P4
Action: The severity of this depends on whether the first two problems are found to
be the cause. If the ext is not a valid PBX number, severity is P4 because
there is no phone to light. If the ext cannot be forwarded to, severity is P3
because there is a phone and NuPoint Messenger can't light it. If this log
occurs repeatedly, and the first two problems are ruled out, this message is
more of a severity P2 as lights are not being lit. Check the system
MITELADMIN: link %d initialized
Description: Link %d has completed the initialization sequence.

Severity: P4
MITELADMIN: link %d not communicating. Attempting to initialize

link %d
Description: The link was not heard from for the link alive time (currently 2 minutes).
The integration will send the initialization message and try to get it going
again.
Severity: P1, P2
Action: Check the integration sets to see if they have the date/time display.
The severity of this depends on whether the link comes back up right away
or stays down. If the link stays down, there is a problem. If you get this
message often, this also indicates problems. If you get this message
intermittently, and the link comes right back up, the error should be
investigated, but it is not fatal.

MITELADMIN: no links for msg waiting.
Check mitel link configuration
Description: There is no dedicated link configured, the link is being used right now, or
the link is down. Message waiting lights cannot be lit.
Severity: P2
Action: Check the integration sets to see if they have the date/time display. Check
the system configuration for possible problems/inconsistencies. If no
MITELADMIN: no links for mwi refresh.

Check mitel link configuration
Description: There is no dedicated link configured or the link is down. The refresh
cannot be done.
Severity: P2
Action: Check the integration sets to see if they have the date/time display. Check
the system configuration for possible problems/inconsistencies. If no
MITELADMIN: T/O in EXIT for xxx
Description: In normal operation, this state is reached after the target number is dialed
and the light is turned on, off, or left alone because it is in the correct state.
Also ends up in this state if NuPoint Voice timed out in FEAT SEL, QUERY,
or MWI_DO.
Severity: P2, if continuous.
Action: Check to make sure the link is connected properly. If the problem persists,
MITELADMIN: T/O in FEAT SEL for xxx:
Description: The first phase of 1003 message waiting is to press the select feature key.
System timed out while waiting for 4:MSG to appear in the upper right hand
display on the message waiting phone.
Action: If this is happening continually with all extensions, check the Mitel COS of
the Message Waiting set and make sure it matches the recommended
values in the Integration manual. Use the phone test program from the
Mitel Utilities menu to troubleshoot the phone. Have someone on site verify
that the display shows 4:MSG when it is sent the lowercase letter 'b'. If this
happens once in a while, there could be a problem with the switch not being
able to accept digits even though it says it is. Make sure the link is
connected properly. If the problem persists, contact your Support
Representative.
MITELADMIN: T/O in FWDED START for xxx
Description: A time-out occurred in the first phase of message waiting.

Action: Check the Mitel COS of the Message Waiting set and make sure it is
configured properly. Make sure that it is allowed to forward. If the problem

MITELADMIN: T/O in FWDEND for xxx
Description: A time-out occurred while waiting to press the 'Save' and 'Exit' keys and
save the forwarding on the message waiting set.
Action: Have someone on site verify the 'Save' and 'Exit' prompts are appearing on
the message waiting set. Have them try the forwarding sequence manually
using 'Test Integration Sets' from the Mitel utility menu. If it works manually,
there might be a switch problem. The mitelsnd that delays before pressing
'Save' and 'Exit' should be sent to the site to see if that happens. If the
MITELADMIN: T/O in HUNGUP for xxx
Description: A time-out was received while trying to end the message waiting process.
Action: The integration will try to initialize the link if this happens. Make sure the
link is connected properly. If the problem persists, contact your Support
Representative.
MITELADMIN: T/O in MWI_DO for xxx
Description: In the fourth phase of message waiting (phase 3 already has an existing log
message), a decision is made on whether to set or remove message
waiting. This message appears if the system timed out while waiting for the
send msg prompt.
Action: Check the Mitel COS of the Message Waiting set and make sure it matches
the recommended values in the Integration Manual. Make sure the link is
connected properly. If the problem persists, contact your Support
Representative.
MITELADMIN: T/O in OFF_DIALED for xxx
Description: A time-out was received while the message waiting set was dialing itself (for
an OFF request).
configured properly. If the problem persists, contact your Support
Representative.
MITELADMIN: T/O in OFF_MSG_KEY for xxx
Description: A time-out was received while waiting for prompt information on the
message waiting set after it dialed itself (for an OFF request).
Action: Check the Mitel COS of the target extension and make sure it is configured
properly. Have someone on site see if the message waiting set is getting
the 'MSG' or 'SEND MSG' prompt after it dials itself. If the problem persists,
MITELADMIN: T/O in ON_DIALED for xxx

Description: A time-out was received while the message waiting set was dialing itself (for
an ON request).
configured properly. If the problem persists, contact your Support
Representative.
MITELADMIN: T/O in ON_MSG_KEY for xxx
Description: A time-out was received while waiting for prompt information on the
message waiting set after it dialed itself (for an ON request).
Action: Check the Mitel COS of the target extension and make sure it is configured
properly. Have someone on site see if the message waiting set is getting
the 'MSG' or 'SEND MSG' prompt after it dials itself. If the problem persists,
MITELADMIN: T/O in QUERY for xxx
Description: The second phase of 1003 message waiting is dialing the number 4 to
select the 4:MSG feature. The system expects to get back a msg flag on
the Message Wait set. This message appears if the system timed out.
Action: Check the Mitel COS of the Message Waiting set and make sure it matches
the recommended values in the Integration Manual. Check to make sure
the link is connected properly. If the problem persists, contact your Support
Representative.
MITELADMIN: unable to register for net status with master
Description: If a module dies and is restarted, any integration lines on that module may
not answer contacts. Also, miteladmin may attempt to dispatch contact
pickup requests to the dead module.
Severity: P2
Action: Try rebooting the module, then rebooting the system. Then contact your
MITELADMIN: unable to send to undertaker
Description: The mitel receive task and/or mitel send task has died and the mitel
administrator task cannot send to the undertaker task.
Severity: P2
MITELAGENT: can't send to miteladmin. Error(0x%x)
Description: mitelagent cannot talk to miteladmin. The task will abort, the integration will
not work, and the system will try to restart the task. If mitelagent aborts 4
more times, the module will reboot.
Severity: P1
MITELAGENT: can't send to sfa%d.

Description: mitelagent cannot tell sfa that it has a contact to be picked up from the
integration set. The task will continue to the next message but the contact
on the integration set may ring no answer.
Severity: P2
Action: If this message occurs more than once, contact your Support
Representative.
MITELAGENT: Node ID (%d) out of range!
Description: mitelagent received a bad node number. The task will abort, the integration
will not work, and the system will try to restart the task. If mitelagent aborts
four more times, the module will reboot.
Severity: P1
MITELAGENT: Unable to get miteladmin tid, aborting
Description: mitelagent tried to locate miteladmin for 10 minutes and did not find it. The
task will abort, the integration will not work, and the system will try to restart
the task. If mitelagent aborts four more times, the module will reboot.
Severity: P1
MITELAGENT:node %d out of range
Description: The node number in the message from sfa is out of range. The task will
continue to the next message.
Severity: P2
Action: If this message occurs more than once, contact your Support
Representative.
MITELCATCH: *** Unable to get miteladmin tid!
Description: The mitelcatch program cannot find miteladmin. mitelcatch will exit and the
integration will not work.
Severity: P1
MITELCATCH: *** Unable to get sfa tid!
Description: The mitelcatch program that transports messages between sfa and
miteladmin cannot find the sfa program. The integration will not work and
other problems may be present in the system.
Severity: P1
Action: Reboot the module. If the problem persists, contact your Support
Representative.
MITELCATCH: can't locate admin after send failed.
Description: mitelcatch cannot send messages from its queue to miteladmin. It will retry
sending the current message twice before this message is logged. It will
then try the next message. The integration will not work properly if this

message continues to be logged.
Severity: P2
Action: If this message continues to be logged, reboot the module, then the system.
If the problem persists, contact your Support Representative.
MITELCATCH: can't send to sfa!
Description: mitelcatch cannot send a message to sfa. The program will exit and the
integration will not work.
Severity: P1
MITELCONMWI: *** Unable to get miteladmin tid!
Description: mitelconmwi cannot find miteladmin. The program will not run. This
program is used for converting from the 217 and 1001 method of message
waiting to the 1003 method. If this message is logged, message waiting
lights will probably be out of synchronization.
Severity: P2
MITELCONMWI: can't close record %s
Description: The convert is trying to close the oaa record that it just opened and
updated. The message waiting light can be out of synchronization for this
mailbox.
Severity: P2
MITELCONMWI: can't open record %s
Description: The convert is trying to open the oaa record for the mailbox that is
converted and put the status in. The message waiting light can be out of
synchronization for this mailbox.
Severity: P2
MITELCONMWI: can't send START PROCESSING msg to admin
Description: The convert could not send a message to the admin during its normal
processing, so it sends another telling the admin to resume normal mwi
because the convert is going to quit. miteladmin will only wait for two
minutes without hearing from mitelconmwi before it decides it has waited
long enough for the convert and will continue with regular mwi. Some lights
could be out of synchronization. This message is logged when mitelconmwi
cannot send the second message (see MITELCONMWI: unable to send
msg type x to admin error message description).
Severity: P2
MITELCONMWI: out of retry space

Description: There is a list 1000 entries long for convert entries. An entry is made when
the convert cannot do mwi for any reason on the first pass. The message
waiting light may possibly be out of synchronization, but will resynchronize
when the user gets and listens to new messages.
Severity: P2, P3
MITELCONMWI: unable to send msg type x to admin

Terminate convert and start normal mwi
Description: The convert is trying to send a message to the admin and the admin either
is not there or has not responded to the task. The convert will send another
message to the admin telling it to start normal mwi and will then exit.
mitelconmwi is not running to completion and some lights may be out of
synchronization.
Severity: P2
MITELMWI: can't close record xxx
Description: mitelmwi has updated the mailbox record and cannot close the oaa record.
The message waiting light for this mailbox may end up out of
synchronization.
Severity: P2
MITELMWI: can't open record xxx
Description: mitelmwi wants to update the mailbox record and cannot open the oaa
record. The message waiting light for this mailbox could end up out of
synchronization.
Severity: P2
MITEL MWI: cannot send to mwla
Description: mitelmwi cannot send messages to the message wait light administrator.
The task will log this message and exit. The integration will not work.
Severity: P1
MITEL MWI: rcvd unknown request from mwla (request, ext#)
Description: mitelmwi received something other than an ON or an OFF from mwla. The
message waiting light for this mailbox may end up out of synchronization.
Severity: P2
Action: This should be investigated, but it is not fatal. Contact your Support
Representative.
MITELRCV: io t/o on link %d after Clear display.

Description: The integration has timed out trying to get data from the cti port after the
display on the integration set was cleared.
Severity: P2, P3
Action: This is a problem if it occurs often. Contact your Support Representative. If
it occurs once in a while, it is worth investigating, but is not fatal.
MITELRCV: io t/o on link %d after FROM outside clr dspy
Description: The integration has timed out trying to get data from the cti port.
Severity: P2, P3
MITELRCV: io t/o on link %d after FROM
Description: The integration has timed out trying to get data from the cti port. After
'FROM' the integration expects an extension number. This could be a
hangup of a forwarded contact.
Severity: P2, P3
MITELRCV: io t/o on link %d after Ring cadence off.
Description: The integration has timed out trying to get data from the CTI port.
Severity: P2, P3
MITELRCV: io t/o on link %d after set flag
Severity: P2, P3
MITELRCV: io t/o on link %d after set indv prompt
Severity: P2, P3
MITELRCV: io t/o on link %d after set prompts
Severity: P2, P3
MITELRCV: io t/o on link %d after str_match.

Severity: P2, P3
MITELRCV: io t/o on link %d getting a %d digit extn.
Description: The integration is waiting for x number of digits from the integration set and
has not received all of them. The contact may ring-no-answer on the
integration set.
Severity: P3
Action: Check the Mitel dial plan in the offline configuration and verify it accurately
reflects the PBX dial plan. This tells the integration how many digits to wait
for.
MITELRCV: io t/o on link %d getting Trunk digits
Severity: P2, P3
MITELRCV: Message wait limits exceeded
Description: The PBX has sent EXCEEDED LIMITS to the integration set when it tried to
do a message wait. The 217 and 1001 switch software and lower releases
of 1003 have a limit of 100 message waits possible in the system at any
one time. Later releases of 1003 can have 250 message waits.
Severity: P3
Action: Since this is a switch issue, nothing can really be done. Contact your
MITELREFRESH: *** Unable to get miteladmin tid!
Description: mitelrefresh cannot find miteladmin. The program will not run. Message
waiting lights will not be refreshed. In 1001 and some 217 systems, the pbx
will turn them off after 24 hours.
Severity: P2
MITELREFRESH: can't close record %s
Description: The refresh is trying to close the oaa record that it just opened and updated.
This could also be during the first or second half of the refresh. The
Message waiting light can be out of synchronization for this mailbox. The
light will resynchronize with the next message cycle (receive new msg,
listen, delete).
Severity: P2
MITELREFRESH: can't open record %s
Description: The refresh is trying to open the oaa record for the mailbox that is refreshed

and put the status in. This could be during the first or the second half of the
refresh. The message waiting light can be out of synchronization for this
mailbox. The light will resynchronize with the next message cycle (receive
new msg, listen, delete).
Severity: P2
MITELREFRESH: can't send START PROCESSING msg to admin
Description: The refresh could not send a message to the admin during its normal
processing, so it sends another telling the admin to resume normal mwi
because the refresh is going to quit. miteladmin will only wait for two
minutes without hearing from mitelrefresh before it decides it has waited
long enough for the refresh and will continue with regular mwi. Some lights
could be out of synchronization. This message is logged when mitelrefresh
cannot send the second message (see MITELREFRESH: unable to send
msg type x to admin error message description).
Severity: P2
MITELREFRESH: out of retry space
Description: There is a list 1000 entries long for refresh entries. An entry is made when
the refresh cannot do mwi for any reason on the first pass. The message
waiting light may possibly be out of synchronization, but will resynchronize
when the user gets and listens to new messages.
Severity: P2, P3
MITELREFRESH: unable to send msg type x to admin

Terminate refresh and start normal mwi
Description: The refresh is trying to send a message to the admin and the admin isn't
there. The refresh will send another message to the admin telling it to start
normal mwi and will then exit. mitelrefresh is not running to completion and
some lights may be out of synchronization.
Severity: P2
mitelsnd cannot open cti port
Description: The fopen on the cti port failed. The mitelsnd task will not be able to send
information to the integration phone through the CTI port.
Severity: P1
ml_sum_fax(): Message queue loop found! q=%d
Description: Corrupt mailbox.

Severity: P2

ml_sum_fax: count exceeds que limit: %d, q=%d

Severity: P2
Monitoring request returned bad paremeters!\n
Description: A software fault was detected.

Severity: P4
Monitoring request to T1 driver failed!\n
Description: A software fault was detected.

Severity: P4
move_to_played_queue: aclose failed, rslt = %d

... current_queue = %d, current = %d
Description: These two lines always come together. The user kept a message, but the
message could not be saved to disk. The message will remain in the
Unplayed queue.
Severity: P3
Action: Mailbox could be corrupt, or oaa died. Run a verify. If OK, corruption is
only in the memory.
ms_alloc: free que head %d, mb_id: %s\n

Severity: P4
ms_alloc_sib: free que head %d, mb_id: %s\n

Severity: P4
MS: bad action type x
Description: The mitelsnd task was sent a bad request by the message waiting state
machine.
Severity: P1
ms_queue_move: bad idx %d, mb_id: %s\n

Severity: P2
ms_sibling_move: bad idx %d, mb_id: %s\n

Severity: P2
msg %s secs for %s
Description: It is normal with NP Net to see these messages right after a reset. These
are for NP Net messages that could not be processed before the reset. If
this message appears more than a few minutes after a reset, a delayed
message has been delivered.
Severity: P2
MTP Pause indication!
Description: No SS7 links are available to the adjacent point code.

Severity: P3
MTP Resume indication!
Description: SS7 links to the adjacent point code are now in service.
Severity: P4
Action: None.
MTP Started

Severity: P4
Action: None.
MTP: Adding message to output queue failed
Description: The software detected a failure.

Description: P2
MTP: invalid length of %d in pause/resume msg!
Description: The MTP coprocessor board forwarded an invalid message.

Severity: P2
MTP: receive error
Description: The SS7 task encountered an operating system failure.

Severity: P2
MTPTX Started

Severity: P4
Action: None.
MTPTX: board tried to pass up non isup message!
Description: MTP received an SS7 message for a user part that is not part of this
integration.
Severity: P2
MTPTX: invalid length of %d received from board!
Description: An invalid message was received from the MTP coprocessor board.
Severity: P2
MTPTX: IOCTL to DK failed! Errno of %s
Description: This task is unable to communicate with the device driver.

Severity: P2
MTPTX: Unable to allocate message

Severity: P2
MTPTX: Unable to attach name

Severity: P2
MTPTX: Unable to set priority pid

Severity: P2
MTPTX: Unknown message of type 0x%x length %d status 0x%x from

board!
Description: The MTP coprocessor board forwarded an invalid message.

Severity: P2

MTP: Unable to attach name

Severity: P2
MTP: Unable to attach timer proxy

Severity: P2
MTP: unable to send to server

Severity: P2
MTP: Unable to set priority pid

Severity: P2
MWISL1: *** Unable to get snd tid!
Description: The mwi task of the SL1 IVMS integration is unable to locate the snd task in
an attempt to send message wait notifications to the PBX. This error
message relates to the message wait inconsistency problems that users
may experience.
Severity: P2
Action: If the problem persists, reboot the system. If the problem still persists,
“MTP status indication = %d”
Description: Reports the status of the Message Transfer Part

Severity: P2
Action:
“MTP User Part Unavailable!”
Description: Message Transfer Part user part unavailable.

Severity: P2
Action:
“mwi call type is invalid”
Description: There is a communication error. The mwi call type parameter is invalid.

Severity: P4
Action:
mwi switch type is invalid”
Description: There is a communication error. The mwi switch type parameter in the mwi
configuration is invalid.
Severity: P4
Action:
MWISL1:cannot sent to mwla !
Description: The mwi task of SL1 IVMS integration could not find mwla or mwla_slave
task.
Severity: P2
Action: If the problem persists, reboot the system. If the problem persists, contact
MWLA_AGENT: can't locate (%s) on node %d
Description: mwi administrator died, system will reset.

Severity: P1
Action: If the problem persists, run maintenance from the hard drive, choose
console, and run the offline menu. Verify the system configuration, save
the configuration, then enable the inactive configuration. If the error still
occurs, contact your Support Representative.
MWLA_AG: Can't send to local MWLA(%d)
Description: The MWLA agent cannot send to the local MWLA.

Severity: P1
MWLA_AG: Can't send to MWLA_SLAVE
Description: The MWLA agent cannot send to the MWLA slave on the remote host.
Severity: P1
MWLA, agent checkin: bad node: %d
Description: mwla agent checked in with a bad node number. This is a software error.
Severity: P2
MWLA: active q timeout, dialer not active (%d)
Description: mwla timer for the retry queue expired, but the dialer was not alive. The
dialer must have died.
Severity: P3
Action: If the dialer does not come up, contact your Support Representative.

MWLA: agent(%d) died
Description: mwla agent died. This is recreated. If this message repeats, it is a

software error.
Severity: P3
MWLA: bad agent q item node: %d
Description: Bad node number in the message in mwla queue. The request is lost. This
is a software error.
Severity: P3
MWLA: BAD ALL PROMOTE FROM %x
Description: A primary mwla received ALL_REMOTE message. The mwla dies since
this is passed to standby mwla, and it was promoted. This is a software
error.
Severity: P2
MWLA: bad host num (%d) in get hoststatus
Description: This is a software error.

Severity: P2
Action: If the module does not come up, contact your Support Representative.
MWLA: bad ml_node. tid=%x, request=%d,%d
Description: Bad node number in a request from a dialer. This is a software error.
Severity: P2
MWLA: BAD ML_TIMER FROM:%x, aborting
Description: The primary mwla received the timer message. This is a software error.
Severity: P2
MWLA: bad od node. od=%d
Description: The node number of the dialer is recorded incorrectly. This is a software
error.
Severity: P3
MWLA: bad q type for set_req_qtimer:%d

Severity: P2

MWLA: bad reply from MWLA SB: %d

Severity: P2
MWLA: can't send init queue data to standby. %d

Severity: P2
MWLA: can't send startinit data to standby. %d
Description: mwla could not send the init message to standby mwla. This is a software
error.
Severity: P2
MWLA: can't send to mwla standby: %d
Description: MWLA standby must have died, or the host went down.
Severity: P3
Action: If MWLA does not come up, contact your Support Representative.
MWLA: Cannot FREE OLD req, no index entry E=%s R=%d G=%d
Description: The lookup table for mwla queues is corrupted. E=mailbox, R=mwi
number(0,1), G=switch group for UI mappings. This request will not be
processed.
Severity: P2
Action: If this message appears repeatedly, reboot the system to clear. This is a
software error. Contact your Support Representative.
MWLA: Cannot move NEW request to AGENT_PENDING
Description: Due to a software error, the task could not move a new request to pending
queue. Request is lost.
Severity: P3
MWLA: cannot move req from queue %d to HOLD queue.
Description: Hold queue in full. Request will be discarded.

Severity: P3
Action: None.
MWLA: Could not open outputfile %s for MWLATOOL
Description: Diagnostic routine could not print results to the output file.

Severity: P4
Action: None.
MWLA: could not set lkalive_flag for outdialer:link(%d) node(%d)
Description: Cannot set link alive flag for outdialer. This message should never appear
unless the system completely locks up.
Severity: P1
MWLA do_q_timers():Index entry NOT FOUND, E=%s, R=%d
Description: System is unable to remove a page or repage from the queue due to no
entry being found in the index table.
Severity: P2
MWLA: Duplicate request NOT in NEW, E=%s R=%d Q=%d
Description: Lookup table for mwla queues is corrupted. E=mailbox, R=mwi

number(0,1) This request will not be processed.
Severity: P2
MWLA: Error from UIMAP. mbox = %s
Description: No Uimapping created for mailbox.

Severity: P2
Action: Create Uimapping for mailbox.
MWLA: Failed to spawn '%s'!
Description: Failed to spawn.

Severity: P1
MWLA: Failed to spawn '%s'!
Description: MWLA cannot spawn an agent process.

Severity: P1
MWLA: got bad reply from standby:%d req:%d, node:%d, tid:%x

Severity: P2
MWLA: Invalid Parameter %s

Description: mwla was started with an invalid command line argument. This is a
software error.
Severity: P2
MWLA: Out of memory for index file
Description: Out of memory for the index file. Could not malloc() more memory.
Severity: P1
MWLA: Out of memory for ml queues
Description: Out of memory to allocate for lookups and init queue elements. Could not
malloc() more memory.
Severity: P1
MWLA move_request(): Cannot update OLD reqs table, dtype=%d,

reqs=%d
Description: Lookup table for mwla queues is corrupted. dtype=dialer type, reqs=n/a.
This request will not be processed.
Severity: P2
MWLA move_request(): Cannot update NEW reqs table, dtype=%d,

sw_grp=%d reqs=%d
Description: Problem manipulating the request queue. dtype=dialer type, reqs=n/a, sw-
grp=PBX sw group.
Severity: P1
MWLA move_request(): QUE %d should have no index
Description: Problem manipulating the request queue. Benign. This message appears
when the user moves items between queues of an identical type.
Severity: P4
Action: None.
MWLA outdialer(%d) comes alive in fast timer test
Description: MWLA outdialer comes alive. Benign. This is a status message.

Severity: P3
MWLA: pending TID already exists
Description: Software error. An mwla_slave process has already sent a request off to
the master. The previous request will be ignored.

Severity: P3
MWLA: Q segments are used up. Req discarded.
Description: The message wait request queue segment is full. Unable to allocate more
memory.
Severity: P1
MWLA: Rcv'd illegal direct msg:%d, %x
Description: mwla received an invalid request from someone. This is a software error.
Severity: P2
MWLA: Receive error
Description: MWLA was interrupted by other signals while updating the dialer timer.
Severity: P1
MWLA: request queue overflow
Description: Current mwla configuration limits were exceeded. The oldest entry will be
dropped.
Severity: P3
MWLA_SB: bad msg(%d) received during init
Description: MWLA cannot locate mwla_sb or cannot send to or receive from mwla_sb.
Severity: P1
MWLA_SB: cannot create extra segments, aborting

Severity: P2
MWLA_SB: can't attach name
Severity: P1
MWLA_SB: can't locate MWLA

Description: Primary MWLA died.
Severity: P1
MWLA_SB: current od sync error:%d, %d

Severity: P2
MWLA_SB: got an all promote during name locate
Description: Standby is promoted to primary.

Severity: P3
Action: None.
MWLA_SB: index count sync error:%d, %d

Severity: P2
MWLA_SB: ML_SB_INIT send failed with -1 5 times, aborting
Severity: P1
MWLA_SB: Msg %d from %d, not MWLA TID(%d)
Description: Invalid message from a task other than primary MWLA. This is a software
error.
Severity: P2
MWLA_SB: num od sync error:%d, %d

Severity: P2
MWLA_SB: num segs sync error:%d, %d

Severity: P2
MWLA_SB: pending agent sync error:%x, %x

Severity: P2

MWLA_SB: qsize sync error, q=%d: %d, %d

Severity: P2
MWLA_SB: recv'd %d from %d while locating pri
Description: MWLA cannot locate mwla (receive message from task ).

Severity: P1
MWLA_SB: starting up on host %d
Description: The MWLA standby process is starting.

Severity: None.
Action: None.
MWLA_SB: too many qinit msgs: %d
Description: Standby received too many qinit messages - more qinit messages than the
number of segments.
Severity: P3
Action: None.
MWLA_SB: Unable to detach name

Severity: P2
MWLA_SLABE: bad request %d
Description: Bad request sent from outdialer to MWLA.

Severity: P3
Action: No action; MWLA_SLAVE will reply back to sender.
MWLA_SLAVEAG: can't locate (%s)
Description: mwi administrator has died, system will reset.

Severity: P1
console and run the offline menu. Verify the system configuration, save the
configuration, then enable the inactive configuration. If the error still occurs,
MWLA_SLAVEAG: can't locate (%s) on node %d
Description: Unable to locate MWLA on node.

Severity: P1
MWLA_SLAVEAG: Can't send to MWLA
Description: System error.

Severity: P1
MWLA_SLAVEAG: Can't send to MWLA_SLAVE, abort!

Severity: P1
MWLA_SLAVEAG: MWLA_SLAVE is not my dad!

Severity: P1
MWLA_SLAVE: agent(%d) died
Description: mwlaslave agent died. It is recreated by mwlaslave. If this repeats, it is a

software error.
Severity: P3
MWLA_SLAVE: bad request %d
Description: Bad request.

Severity: P1
MWLA_SLAVE: %d already in register array
Description: The task id is already in the register array.

Severity: P2
Action: None.
MWLA_SLAVE: dialer(%d) died
Description: The dialer has died.

Severity: P3
Action: Check if outdialer has started again.
MWLA SLAVE %d: request queue overflow
Description: mwlaslave queue if full. Request is ignored. This is a software error.

Severity: P3

MWLA_SLAVE: register array full, aborting
Description: mwla_slave could not register a task with undertaker. This is a software
error.
Severity: P3
MWLA_SLAVE: unable to send %d to undertaker
Description: mwi administrator will not be notified if a dialer dies. May result in lost
pages if a dialer dies.
Severity: P2
Action: If this message appears repeatedly, or if dialer deaths are noted in the
logfile, rebooting the system should correct the error.
MWLA%s: Link for switchgroup %d is down
Description: Link from PBX to NuPoint Voice is down.

Severity: P3
Action: Check serial connection between PBX and NuPoint Voice.
MWLA STBY: recv'd STANDBY INIT MSG
Description: The standby mwla received wrong request. This is a software error.
Severity: P2
MWLA: starting up on host %d
Description: mwla starts. Not an error.

Severity: P4
Action: None.
MWLA: test_lktest(), bad node_id. od=%d
Description: Bad node id is being detected.

Severity: P1
MWLA: UIMAP Queue full, request lost
Description: Uimap queue is full.

Severity: P3
Action: None.
MWLA: uimapagent(%d) died
Description: Uimapagent has died.

Severity: P1

MWLA: Unable to register name
Description: mwi administrator could not register a name so that other tasks could send
messages to it; system will reset.
Severity: P1
console and run the offline menu. Verify the system configuration, save the
configuration, then enable the inactive configuration. If the error still occurs,
MWLA: unable to send %8d to undertaker
Description: Undertaker died.

Severity: P2
mwltr: cannot send to mwla
Description: The Tip/Ring Message notification task (which also controls the Message
Dispatch Board) was unable to set up communication with mwla (Message
Waiting Light Administrator).
Severity: P3
Action: Following this error should be another message logged from the master
stating that the task mwltr died and was restarted. If the Cannot send to
mwla error does not get logged again, the problem has been resolved. If
the error recurs, contact your Support Representative. This problem will
only affect the Message Waiting Indication for mailboxes that use the
Tip/Ring Message Waiting or the Message Dispatch Board.
MWPBXDD: cannot send to mwla
Description: The DTMF-to-PBX task was unable to set up communication with the mwla
(Message Waiting Light Administrator).
Severity: P3
stating that the task mwpbxdd died and was restarted. If the Cannot send
to mwla error does not get logged again, the problem has been resolved. If
the error recurs, contact your Support Representative. This problem will
only affect the Message Waiting Indication for mailboxes that use DTMF-to-
PBX Message Waiting.
MWPBXDD: could not attach phoneline %d
Description: The DTMF-to-PBX task was unable to set up communication with the
linecard.
Severity: P3
stating that the task mwpbxdd died and was restarted. If the Could not
attach phoneline error does not get logged again, the problem has been
resolved. If the error recurs, check the linecard. If the problem continues to
recur, contact your Support Representative. This problem will only affect
the Message Waiting Indication for mailboxes that use DTMF- to-PBX
Message Waiting.

mwrs232: could not find MWLA

Severity: P2
mwrs232: could not send to MWLA

Severity: P2
mwrs232: device type error
Description: Configuration program error.

Severity: P2
mwrs232: error opening serial port for read (init_link)
Description: The mwrs232 task cannot open the serial port for read access. The task
will abort.
Severity: P1
Action: Check the configuration data for the serial port and make sure it is correct.
Try configuring a different serial port. Make sure that the port is good. If
mwrs232: error opening serial port for read
Description: The mwrs232 task cannot open the serial port for read access. The task
will abort.
Severity: P1
MWRS232: Ext [%s], ML OFF: no verify of DN string
Description: NuPoint Voice sent the configured DN ON or OFF string to the serial port.
NuPoint Voice did not receive an expected response from the PBX at the
other end of the serial port. Message waiting will not work.
Severity: P2
Action: Check the serial link and make sure that the PBX is responding from the
other end.
MWRS232: Ext [%s], ML OFF: no verify of Post-string
Description: NuPoint Voice sent the configured DN ON or OFF Post string to the serial
port. NuPoint Voice did not receive an expected response from the PBX at
the other end of the serial port. Message waiting will not work.

Severity: P2
other end.
MWRS232: Ext [%s], ML OFF: no verify of Pre-string
Description: NuPoint Voice sent the configured Pre-DN ON or OFF string to the serial
port. NuPoint Voice did not receive an expected response from the PBX at
the other end of the serial port. Message waiting will not work.
Severity: P2
other end.
MWRS232 INIT: Error on link %s, initializing.
Description: The program got an error on the link and is trying to reinitialize the link.
This could be caused by a bad connection and could result in lost data.
Severity: P2
Action: Check the connection.
mwrs232: successfuly opened serial port for write
Description: The mwrs232 task opened the serial port for write access.
Severity: P4
mwrs232: unable to open serial port for write, retrying
Description: The mwrs232 task cannot open the serial port for write access. The task
will retry indefinitely.
Severity: P2
mwrs232: unable to open %s for write, retrying
Description: The program is cannot open the serial port device for write access. It will
keep retrying.
Severity: P2
Action: Check the serial port configuration. If using a smart card, check the
configuration and hardware setting.
N
name register failed:%s
Description: Resource manager fails to register a name.

Severity: P1

NETQ add: aopen failed [%s]
Description: An open failure occurred during NETQ_AGENT request, NetQ queuing.

Severity: P2
NETQ: *** Cannot find %s
Description: An attempt to locate the named process with which to establish

communication failed.
Severity: P2
NETQ: *** invalid node number (%02d)
Description: The node number that NETQ is being asked to send a message to is
invalid.
Severity:
Action: The local NTA table needs to be reconfigured to only refer to legal node
numbers.
NETQ: Cannot map memory for queues, exiting...
Description: Mapped memory request for queues failed.

Severity: P2
NETQ: LTRUNC failure, errno=
Description: An LTRUNC contact failed.

Severity: P2
NETQLIB: can't send to NETQ

or
NETQLIB: cannot send to NETQ
Description: Cannot send to netq.

Severity: P3
NETQ: Retry limit exhausted, %u msgs to node %u purged
Description: The number of times Mesa-Net retries a connection is configurable. This

limit has been reached.
Severity: P2
Action: The Mesa-Net link to this node is not working and needs to be debugged.
NETQ: MSG_DELIVERED fail skip %s
Description: Reply data from VMNET contains a reply status of MSG_DELIVERED, but
is flagged as in error.

Severity: P2
NETQ: MSG_PURGED fail skip %s
Description: An attempt to purge a message failed due to an incorrect MPTR.

Severity: P2
NETQ: SHN_OPEN Failure,errno=
Description: A SHM_OPEN contact failed

Severity: P2
NETQ: NOT_DELIVERED fail skip %s
Description: Reply data from VMNET contains a reply status of NOT_DELIVERED, but
is flagged as in error.
Severity: P2
NETQ: Unable to attach a timer proxy.
Description: A timer proxy attach failure is probably due to a lack of free process entries
or inadequate process manager memory.
Severity: P2
NETQ: unable to send %04x to undertaker
Description: An attempt to register NETQ with the undertaker failed.

Severity: P2
NETQLIB: can't send to NETQ
Description: NETQLIB cannot successfully execute a send_name to NETQ.

Severity: P2
NETQLIB: can't send to NETQ_AGENT
Description: NETQLIB cannot successfully execute a send_name to NETQ.

Severity: P2
NETQLIB: \ (exit for clean up)
Description: NETQ has died as has the NETQ_AGENT. NETQ and the NETQ_AGENT
are automatically restarted.

Severity: P2
NETQ_AGENT: *** Cannot find %s\n
Description: An attempt to find the named process with which to establish

communication failed.
Severity: P2
NETVM: %d frms in hdr, %d frames in limit
Description: The NETVM message length limit was exceeded.

Severity: P4
Action: Reconfigure in the offline menu to accept larger messages or have
correspondents send smaller messages.
NETVM: can't send to agent %x, rslt = %x
Description: NETVM cannot send to NETVM_STAT to update statistics.

Severity: P2
NETVM: Cannot locate NETQ_AGT
Description: NETVM is unable to locate NETQ_AGENT with which to establish

communication.
Severity: P2
NETVM: Cannot locate NETVM
Description: NETVM is unable to locate the NETVM agent.

Severity: P2
NETVM: check_bcst_mb: %s is not an MMG box
Description: The recipient mailbox is not of the correct type.

Severity: P2
NETVM: deliv_msg: can't close sib2 %s, rslt %d
Description: An attempt to close a second sibling copy list for this item failed.
Severity: P2
NETVM: deliv_msg: fail close sib1 %s, rslt %d
Description: An attempt to close a sibling copy list in NETVM failed.

Severity: P2
NETVM: deliv_msg: fail create 1, lst %s
Description: An attempt to create a HEAD copy list in NETVM failed.

Severity: P2
NETVM: deliv_msg: fail create 2, lst %s
Description: An attempt to create a second HEAD copy list for this item failed.
Severity: P2
NETVM: deliv_msg: fail open sib1 %s, rslt %d
Description: An attempt to open a sibling copy list in NETVM failed.

Severity: P2
NETVM: deliv_msg: fail open sib2 %s, rslt %d
Description: An attempt to open a second sibling copy list for this item failed.
Severity: P2
NETVM: deliv_msg: fail to create sib list 1
Description: An attempt to create a sibling copy list during message delivery failed.
Severity: P2
NETVM: deliv_msg: fail to create sib list 2
Description: An attempt to create a second sibling copy list for this item failed.
Severity: P2
NETVM: deliv_msg: recip_cnt = %d
Description: This message reports when distribution lists longer than 200 members have
been sent to recipients.
Severity: None
NETVM: deliv_nm_gr: fail create 1, lst %s
Description: An attempt to create a HEAD copy list for a broadcast list failed.
Severity: P2

NETVM: deliv_nm_gr: fail create 2, lst %s
Description: An attempt to create a second HEAD copy list for a broadcast list failed.
Severity: P2
NETVM: deliv_nm_gr: recip_cnt = %d
Description: This message reports when a broadcast list contains more than 200
recipients.
Severity: P4
NETVM: sfclose err %d, idx %d\n
Description: Speech file could not be closed.

Severity: P2
NETVM: slots=%d, mcnt=%d, node %d, mb %s
Description: Message received via MesaNet has (mcnt) message components (i.e., one
message plus attachments). MesaNet application protocol header
indicated (slots) components were to be sent, but only (mcnt) components
were received.
Severity: P4 or P2
Action: This message may be benign. This problem is still under investigation. If
the problem affects service, this indicates that one or more message
attachments did not get delivered. Contact your Support Representative.
There may be a fix available.
NETVM: spch_blk: sfput failed
Description: An attempt to write the speech file from NETVM failed.

Severity: P2
NETVM: unable to attach %s
Description: An attempt to register the named process failed.

Severity: P2
new_status %d %d %d %d
Description: This message appears when a node is disabled. It shows the new network
status.
Severity: P4
Action: None.
No MCB2 Installed on this host. (EXIT)

Description: MCB2 hardware was not detected.
Severity: P3
No memory avail. Can't add wakeup record.
Description: The module wakeup is running on is out of memory.

Severity: P1
Action: You must reconfigure your system to use less memory, or if the system is
not at a memory limit, get more memory on the CPU. Contact your Support
Representative.
Node disabled, booting into maintenance mode\n
Description: System has been configured inactive.

Severity: P4
Action: If the module was manually disabled, ignore this message. Otherwise,
enable a module via the host.status option.
No driving clock for MVIP is available with the current

configuration. Unable to initialize MVIP BUS\n
Description: Resource manger cannot find any card in the configuration that can provide
the MVIP clock source.
Severity: P2
Action: Check and verify the configuration to ensure it follows the recommended
configuration.
No more oaa disk space to save the billing data.
Description: All data records (mailboxes, distribution lists, billing records, etc.) have
been used. Cannot complete gather due to lack of free data records.
Severity: P2
Action: Delete unneeded mailboxes. If the problem persists, add an additional disk
to the system.
Node disabled, booting into maintenance mode
Description: This message is logged when a disabled node is rebooted. (Provides

information only.)
Severity: P4
Action: None.
no ss7 config data found
Description: All of the entries provided by mkconf are searched to find the module
holding the associated user part integration. When the user part integration
cannot be found this error is logged.
Severity: P4
Action:
Not enough memory to process query

Description: Resource manager is running out of memory to process a query request.
Severity: P2
Action: Add memory.
Note: disk %d:%d not in PDT
Description: Disk present, but not configured.

Severity: P4
Action: None. Configure the disk and speech to add hours and capacity.
NTA: *** Unable to attach name!
Description: An attempt to register the NTA process failed.

Severity: P2
NTALIB: task %x cannot find NTA_AGENT
Description: Unable to locate the named process.

Severity: P2
NTA_AGENT: can't send to NTA
Description: NTA_AGENT can't successfully execute a send_name to NTA.

Severity: P2
NTAPP_InitApplication: Number of groups don’t match %d
Description: A number of groups are defined for each board with a max of 30 circuits per
group. If they do not match then this error is logged.
Severity: P1
NTAPP_InitApplication: Number of groups don’t match %d
Description: A number of groups are defined for each board with a max of 30 circuits per
group. If they do not match then this error is logged.
Severity: P1
NTAPP_UserPartInit failed
Description: When the appropriate user part cannot be initiated this error is logged.
Severity: P1
NTAPP_InitApplication: Num Circuits %d Num Groups %d
Description: For a single E1 span for DataKinetics 32 circuits need to be specified. This

informational error shows the number of circuits and the number of groups
on board.
Severity: P4
Action: None.
NTAPP_InitApplication: CIC Base %d CID Base %d Grp Options %d
Description: Informational error to show the status in CIC Base, CID Base and Group
Options.
Severity: P4
Action: None.
NTAPP_InitApplication Configuring 2nd Group
Description: Two groups are defined for each board with a maximum of 30 circuits per
group. This informational error is logged to indicate that the second group is
being configured.
Severity: P4
Action: None
NTAPP_InitApplication: CIC Base %d CID Base %d
Description: Informational message to show the status in CIC Base and CID Base.
Severity: P4
Action:
NTL: Cannot find nta

Severity: P2
NTT: Cannot locate %s,
Description: Cannot perform a system name locate. ntt is aborting.

Severity: P1-P2
Action: Reboot the system and contact your Support Representative.
NTL: cti driver died
Description: CTI driver died as determined by serial_wait (20,30).

Severity: P2
NTL: ntl_que size=%d too big for queue_write
Description: The message size passed to procedure NTTOUT is larger than NTL_QUE.
Severity: P2

NTL: ntl_que size=%d too big for queue_write
Description: Message size is bigger than ntl_que. Unable to queue write.

Severity: P3
Action: This is a software error. Contact your Support Representative.
NTL: ntrcv died,link %d disabled
Description: As the process for this link has died, the link will be disabled until the
process is restarted.
Severity: P4
Action: None, if part of a reboot. If excessive, contact your Support Representative.
NTL: ntsnd died,link %d disabled
Description: As the NTSND process for this link has died, the link will be disabled until
the process is restarted.
Severity: P4
Action: None for rare failures. For frequent failures, contact your Support
Representative.
NTL: Unable to register name! Aborting
Description: Over 100 attempts to register the NTL process have failed. Must abort.
Severity: P2
NTL: Unable to register name
Description: An attempt to register the NTL process failed.

Severity: P2
ntrcv: cannot send to ntl
Description: An NTRCV process attempted to send a message to the NTL process via
our send_name procedure and was notified. This process failed.
Severity: P2
NTSND: Cannot find %s
Description: Unable to find NTL OR NTA process with which to establish

communication.
Severity: P2
ntsnd: cannot send to ntl
Description: Process NTSND was unable to complete a send_name to process NTL.

Severity: P2

NTSND: could not open %s\n
Description: An attempt to open a MesaNet port for write access only failed.
Severity: P2
NTSND: cti driver died
Description: The Digi Board (Dg.Ser) or cti Smartcard driver died.

Severity: P1
NTT_AGENT: Cannot attach name ntlagent
Description: An attempt to register the ntlagent process failed.

Severity: P2
NTT_AGENT: Cannot locate %s
Description: The named process with which to establish communication could not be
located.
Severity: P2
Description: The named process with which to establish communication could not be
located by NTT_AGENT.
Severity: P1
Description: ntt_agent cannot locate ntt.

Severity: P3
Action: Check the network configuration. If this problem persists, contact your
NTTAGENT: Cannot locate %s,
Description: Cannot locate ntl.

Severity: P3
Action: Check the network configuration. If this problem persists, contact your
NTTAGENT: Could not open queue, result <qid>

Severity: P2
NTTAGENT: Could not open queue, result = %d
Description: Could not open queue with queue name. This is a system error.
Severity: P2
NTT_AGENT: Name conflict on node
Description: An attempt to register the NTT agent process failed due to a name conflict
Severity: P1
NTT_AGENT: Name space full on node
Description: An attempt to register the NTT agent process failed due to a full name
space.
Severity: P1
NTT: Cannot locate %s
Description: NTT is unable to locate the named process with which to establish
communication.
Severity: P2
NTTLIB: Cannot locate %s
Description: Cannot locate ntt. This task is aborting.

Severity: P3
Action: Check the NP Net configuration. Contact your Support Representative.
NTT: mismatch node state in nc_create - node = %d

Severity: P2
NTT: Unable to register name! Aborting
Description: Cannot do a name_attach() at all. ntt is aborting.

Severity: P3
NTT: Unable to register name! Aborting

Description: Over 100 attempts to register the NTT process have failed.
Severity: P2
NTT: Unable to register name
Description: An attempt to register the NTT process failed. The task must abort.
Severity: P2
NTT: Unable to register name
Description: Cannot do a name_attach() at this moment.

Severity: P4
Action: The system should correct itself.
NTT: unable to send to undertaker
Description: NTT was unable to register with the undertaker.

Severity: P2
NYNEX: * get_recipients: %s dl_cnt %d is bad

or
NYNEX: ** get_recipients: %s dl_cnt %d is bad
or
NYNEX: *** get_recipients: %s dl_cnt %d is bad
or
NYNEX: **** get_recipients: %s dl_cnt %d is bad
Description: While the user was addressing messages, the count went out of range.
The copy list could be corrupted.
Severity: P3
nynex: error reflocking tel_name
Description: A message number that was allocated could not be locked to prevent being
used by another task.
Severity: P3
Action: If too many messages of this kind appear, there could be a problem with
task sfa. The system might have to be reset.
NYNEX: get_trecipients: %s dl_cnt %d is bad
Description: While phone numbers were being entered for reminder contacts, the count
went out of range. The valid count is 0 to 200.
Severity: P3
Action: This could be caused by an error in the nynex program. Run a verify to
check for corruption.

nynexrec_vm: reflock err, ms_num2, tel_name = %s
Description: A message number that was allocated could not be locked to prevent being
used by another task.
Severity: P3
Action: If too many messages of this kind appear, there could be a problem with
task sfa. The system might have to be reset.
O
oa_send: can't alloc copy segment
Description: Out of memory.

Severity: P1
Action: Add more memory.
oa_send: can't copy record, copy_seg is 0, abort

Severity: P4
Oamis: cpylist<%s> is bad
Description: The record storing the outgoing aamis message is corrupted. The contact
will not be placed, and the message will be lost.
Severity: P3
Action: Run a verify. If the problem persists, contact your Support Representative.
Oamis: cpylist<%s> msg is too long <%d>
Description: AMIS - protocol violation for amis.

Severity: P4
Action: None.
OAREF: FAILED, type:%d, req:%d, rec:%s

Severity: P3
One View: Mbox<mbox2>using Lic.<license#>, used by

<mbox 1>
Description: When a user tries to log into the server, the user must supply a unique
license number. If this license is already in use by another session, this
message is logged. [mbox2] indicates the mailbox that is already using that
license. [license#] is the license in question.
Severity: P3
Action: Find out to whom the license actually belongs and make sure that it is used

only by that user. This is how Mitel Networks enacts royalties to OEM
products in NP View.
ONLINE CONFIGURATION FAILED, SYSTEM SHOULD REBOOT
Description: While doing an online hardware configuration, the system encountered a

fatal error and initiated a system reboot.
Severity: P1
Action: Do NOT repeat the configuration process that was being performed without
contacting your Support Representative. Have on hand the system logfile
and details of the procedure you were attempting on when you contact your
Out of range message num %04x. Cannot allocate
Description: An out-of-range message number was detected during sam initialization.

System will remain functional.
Severity: P2
Action: Perform a system verify. If the problem recurs after the system verify, or if
the verify report shows an excessive amount of errors, contact your Support
Representative.
Out of range message num %04x. Cannot deallocate
Description: An attempt was made to deallocate an invalid message. System will

remain functional.
Severity: P2
Action: Perform a system verify. If the problem recurs after the system verify. or if
Representative.
Out of range tspch block ptr %02x%04x
Description: An out-of-range speech block was detected during sam initialization.

Severity: P2
Representative.
P
PGA AG: can't send to PGA_SLAVE(%x), rslt=%d
Description: Error in sending a message. The process aborts. This is a software error.
Severity: P1
PGA SB: can't attach name
Description: PGA cannot register a name. System resources may be running out. PGA

will try again later, up to 30 times.
Severity: P1
PGA SB: can't locate PGA
Description: PGA standby cannot locate the PGA and aborts. This is a software error.
Severity: P1
PGA SB: can't send to PGA
Description: Error in sending the message to primary. This is a software error or the
primary task has died.
Severity: P1
PGA SB: got an all promote during name attach
Description: The primary PGA died before the standby was initialized and ready to be
promoted.
Severity: P1
Action: Look for other error messages that may explain why the primary PGA died.
PGA SB: got an all promote during name locate
Description: The primary PGA died before the standby was initialized and ready to be
promoted.
Severity: P1
Action: Look for other error messages that may explain why the primary PGA died.
PGA SB: locating primary
Description: The standby is locating the primary PGA. Informational message

Severity: None
Action: This is a normal log message when the standby appears.
PGA SB: recv'd %d from %x while locating pri
Description: Received an unexpected message while still locating the primary PGA.
Severity: P3
Action: This message is ignored. Contact your Support Representative.
PGA SB: too many qinit msgs: %d
Description: Received too many initialization messages. So the PGA standby will ignore
the extra initialization message. This only happens when there is a
software problem in PGA.
Severity: P2

PGA SLAVE(%d: request queue overflow
Description: The PGA request queue overflowed. The paging request will be lost until
space becomes available.
Severity: P2
Action: If possible, increase the number of paging ports. Otherwise, contact your
PGA SLAVE: bad request %d
Description: The PGA got an illegal request. This is a software error.

Severity: P3
PGA STBY: bad init msg type:%d
Description: Received an unrecognized initialization message. The process aborts.

Severity: P1
PGA STBY: recv'd STANDBY INIT MSG
Description: PGA standby is getting a message from another standby. This should
never happen; it is a software error. There should be only one standby
PGA in the system The message is ignored.
Severity: P2
Action: Make sure there is only one primary PGA and only one standby PGA in the
overall system.
PGA(%d): bad dialer in set_dialer_ac_codes:%d
Description: PGA gets a bad dialer number in the request. This is a software error.
Severity: P1
PGA(%d,%d) do_q_timers():Index entry NOT FOUND

E=%s R=%d\n I=%u Q=%d\n
Description: The request was not found in the index list when PGA tried to resend a
failed request. This is a software error.
Severity: P2
PGA: active q timeout, dialer not active (%d)
Description: The request from the active queue timed out, but there is no active
outdialer. This is a software error.
Severity: P2

PGA: agent(%d) died
Description: The PGA agent task died. A new one will be created. If this keeps
happening, all of the paging applications will malfunction.
Severity: P1
PGA: Attach pga_proxy failed
Description: PGA failed to attach a timer proxy from OS or may need a new OS boot
image file.
Severity: P1
PGA: BAD ALL PROMOTE FROM %x
Description: The primary PGA got an illegal message. This is a software error. The
process aborts.
Severity: P1
PGA: BAD ML_TIMER FROM:%x, aborting
Description: The primary PGA got an illegal message. This is a software error. The
process aborts.
Severity: P1
PGA: bad reply from PGA SB: %d
Description: PGA is getting a bad reply from the standby task. Standby initialization
aborts. The CSO feature of PGA will malfunction.
Severity: P1
PGA: can not create timer
Description: PGA failed to create a timer, is running out of OS resources, or needs a

new OS boot file.
Severity: P1
PGA: can't find seg ptr in remote_seg[]

seg:%x r_seg[0]:%x r_seg[1]%x, id=%d
Description: PGA cannot convert an address of the primary PGA data pointer. It may
not get the initialization message correctly. The process aborts.
Severity: P1
PGA: can't find seg ptr in remote_seg[], %d

seg:%x seg[0]=%x, rseg[0]:%x r_seg[1]%x, q=%d

Description: PGA cannot convert an address of the primary PGA data pointer. It may
not get the initialization message correctly. The process aborts.
Severity: P1
PGA: can't send init queue data to standby. %d
Description: Error in sending the message to standby. This is a software error or the
standby task has died.
Severity: P1
PGA: can't send startinit data to standby. %d
Severity: P1
PGA: can't send to pga standby: %d
Severity: P1
PGA: Cannot dispatch NEW request, no index entry E=%15s R=%d I=%u
Description: PGA cannot find the new request in the index list. This is a software error.
Severity: P1
PGA: Could not open outputfile %s for PGATOOL
Description: PGA could not open the output file. Disk space may be full or write
protected.
Severity: P2
Action: Remove unnecessary files from the disk or change the write permission.
PGA: got bad reply from standby req:%d, node:%d, tid:%x
Description: PGA is getting a bad reply from the standby task. Standby initialization
aborts. The CSO feature of PGA will malfunction.
Severity: P1
PGA: Invalid Parameter use: pga [-S]
Description: PGA was started with an invalid parameter. This is a software error.
Severity: P1

PGA: Invalid request REQ=%d E=%15s H=%d T=%04x
Description: PGA got an illegal request. This is a software error.

Severity: P3
PGA: pending TID already exists
Description: The PGA slave got multiple STATS requests from the primary PGA.
Severity: P4
PGA: Rcv'd illegal direct msg:%d, %x
Description: PGA got an illegal request. This is a software error.

Severity: P3
PGA: receive error no: %d
Description: Error in receiving a message.

Severity: P1
PGA: request queue overflow
Description: The PGA request queue overflowed. The paging request will be lost until
space becomes available.
Severity: P2
Action: If possible, increase the number of paging ports. Otherwise, contact your
PGA: Unable to register name! Aborting
Description: PGA cannot register a name and is aborting. System resources may be
running out.
Severity: P1
PGA: Unable to register name
Description: PGA cannot register a name. System resources may be running out. PGA
will try again later, up to 30 times.
Severity: P1
PGA: unable to send %04x to undertaker
Description: PGA cannot register dialer tid or its agent tid to the undertaker. Either the
undertaker is not running or it cannot process this tid.
Severity: P1

Action: Make sure that the undertaker is running.
PGA_AG: Can't send to PGA_SLAVE, result=%d
Description: Error in sending a message. The process aborts. This is a software error.
Severity: P1
PGA_AGENT: can't locate (%s)
Description: The PGA agent cannot locate the PGA. This is a software error.
Severity: P1
PGA_SB: cannot create segments, aborting
Description: Cannot allocate memory segments. The system may be running out of
memory. The process aborts.
Severity: P1
Action: Check the amount of memory available. Contact your Support
Representative.
PGA_SB: Msg %d from %x, not PGA TID(%x)
Description: PGA received an illegal message from a task that is not the primary PGA .
Ignore the message.
Severity: P2
PGA_SB: qsize sync error, q=%d: %d, %d

PGA_SB: index count sync error:%d, %d
PGA_SB: current od sync error:%d, %d
PGA_SB: num od sync error:%d, %d
PGA_SB: num segs sync error:%d, %d
PGA_SB: pending agent sync error:%x, %x
Description: PGA standby is getting out of sync with the primary PGA. The process
aborts.
Severity: P1
PGA_SB: Unable to detach name
Description: Unable to detach a name. This is a software error.

Severity: P1
PGA_SLAVE: agent(%d) died
Description: The PGA slave agent task died. A new one will be created. If this keeps
happening, all of the paging applications will malfunction.
Severity: P1

PGA_SLAVE: register array full, aborting
Description: The PGA task registration list is full. This should never happen. It is a
software error. The process aborts.
Severity: P1
PGA_SLAVE: unable to send %04x to undertaker
Description: PGA cannot register the dialer tid or its agent tid to the undertaker. Either
the undertaker is not running or it cannot process this tid.
Severity: P1
Action: Make sure the undertaker is running.
PGA_SLAVEAG: can't locate PGA
Description: The PGA agent cannot locate the PGA. This is a software error. The
process aborts.
Severity: P1
PGA_SLAVEAG: can't locate PGA_SLAVE
Description: The PGA agent cannot locate the PGA slave. This is a software error. The
process aborts.
Severity: P1
PGA_SLAVEAG: Can't send to %s, result=%d
Description: Error in sending a message to the PGA slave. This is a software error.
Severity: P1
PGLA_SLAVE: %x already in register array
Description: The task had been registered to the undertaker previously. This is a
software error.
Severity: P4
play_rcpt: aread rslt %d, mb %s lst %s
Description: A message's receipt could not be played due to vmemo failing to read the
message's record holding the recipients' information. The receipt is lost.
Severity: P3
Action: Could indicate a problem with the open accounts administrator program.
Or, the hard drive could be bad if this problem keeps happening. Run a
verify. If the message appears often, contact your Support Representative.

play_receipt: dl_cnt out of range
Description: The in memory copy list count is too high. This can only happen if vmemo
is corrupted.
Severity: P2
Action: Contact your Support Representative, or reset the system.
Prefix to FAM node %d completed successfully
Description: Normal startup message indicating QNX file system prefix setting.
Severity: P4
Action: None.
Primary task %s died when standby is suspended
Description: Critical system task failure with standby task is unable to recover.
Severity: P2
procs admin msg:event: x out of range
Description: This message indicates a software error. However, the system will try to
recover by itself.
Severity: P2
Action: If this message occurs repeatedly, review the Smartcard configuration, or
reinstall the SL1 Meridian integration software in an attempt to clear the
error. If the problem persists, contact your Support Representative.
procs admin msg:link: x out of range
Description: This message indicates a configuration error with the CTI port assignments.
NuPoint Voice will try to service the incoming contacts on the next
integration set in the hunt chain.
Severity: P2
Action: If this message appears repeatedly, review the Smartcard configuration, or
reinstall the SL1 Meridian integration software in an attempt to clear the
error. If the problem persists, contact your Support Representative.
PURGE: sfa stats failed, cannot do report
Description: Same as above but purge found sfa and, after purging, could no longer find
it.
Severity: P2
Action: Check the logfile to see if sfa died during the purge. If not, rerun the purge.
PURGE: sfa stats failed, nothing purged
Description: Purge needs sfa running in order to run. sfa must not be running. This
should not happen if the system is running and answering contacts.
Severity: P2

pwdaily: file errors encountered; run manually to diagnose
Description: Run automatically at midnight to update password file.

Severity: P2
Action: Run pwdaily manually.
pwdaily: not run; must be by root
Description: Attempted to run pwdaily but user is not logged on as root.

Severity: P2
Action: Log on as root.
Q
QUE_REALY: free an invalid pointer %d

Severity: P1
Query_extrcost: cannot locate INFOADMIN on node %d
Description: For any one of several reasons, the infoadmin task could not be located.
This means that the query of extra-cost features failed.
Severity: P2
Query_extrcost: Cannot send to INFOADMIN, node %d
Description: For any one of several reasons, the extra-cost query could not talk to the
infoadmin task.
Severity: P2
R
RAM: Cannot allocate lookup table space
Description: Not enough memory to build internal structures of ram. System will reboot
itself.
Severity: P1
Action: Check memory card for enough memory.
RAM: Cannot set bitmap entries
Description: Internal message for logic error. System will reboot.

Severity: P1

RAM: Could not find any account drives
Description: No account drive is configured in the system. System will reboot.

Severity: P1
Action: Check the hard disk connections and the system configuration for possible
Representative.
RAM: Invalid account disk structure vid %02d
Description: The master sector on the account drives in the disk is invalid. System will
reboot.
Severity: P1
Action: Check the connections and check the system configuration for possible
Representative.
RAM: no match for record number, create_ok on %s

Severity: P4
Action: Contact your Support Representative with task name indicated.
RAM: no match for tid, create_nok from %x04x, tid is from queue
%04x

Severity: P4
RAM: no match for tid, create_ok from %x04x, tid is from queue
%04x

Severity: P4
RAM:::Double open ERROR from tid %04x, node %d

Severity: P3
Action: Contact your Support Representative with the task name indicated.
RAM:::existing rec %s, openning rec %s
Description: Internal information log. This message goes with RAM::Double open
ERROR from tid %04x, node %d.
Severity: P3
Action: Contact your Support Representative with the task name indicated.

RAM:at sector %04x offset %03x in vid %d
Description: Message indicating corruption of account directory on disk.

Severity: P4
Action: None.
RAM:Bitmap deallocation error (vid %02d, look %04d)
Description: Account deallocation in memory resulted in an error. System will remain

functional.
Severity: P3
Action: Perform a system verify. If the problem recurs after the system verify or if
Representative.
RAM:Directory not updated on delete (%08ld%08ld)
Description: Could not delete an account. System will remain functional.

Severity: P2
Action: If the problem persists, check the hard disks. Contact your Support
Representative.
RAM:Directory update failed (account %08ld%08ld)
Description: Could not create an account. System will remain functional.

Severity: P2
Action: If the problem persists, check the hard disks. Contact your Support
Representative.
RAM:Invalid directory entry (%s,%s)
Description: Message indicating corruption of account directory on disk. System will

remain functional.
Severity: P4
Action: None.
RAM:VID(%02d) Cannot allocate (out of range: %04u)
Description: Internal message for informational purposes. Appears TOGETHER with

the RAM:Terminating on request from OAA message.
Severity: P1
RAM:VID(%02d) Cannot deallocate (out of range: %04u)
Description: Message indicating deallocation error during account deletion in memory.

Severity: P3
Representative.

RAM:VID(%02d) Double deallocation offset %04u
Description: Message indicating an attempt to deallocate account space twice. System

will remain functional.
Severity: P3
Representative.
raw_send_name_greet: aclose %s = %d
Description: The system failed to close a recipient's mailbox after depositing a

greet/name speech.
Severity: P3
Action: Run a verify. If this message still appears, delete the complaining mailbox,
then recreate it.
raw_send_name_greet: aopen %s = %d
Description: In a name/greet broadcast, the system failed to open a recipient's mailbox.

Severity: P3
Action: Run a verify. If this message still appears, delete the complaining mailbox,
then recreate it.
raw_send_vm: aclose %s = %d
Description: The system failed to close a mailbox without a broadcast light FCOS bit
after depositing a message. The message is not in the mailbox.
Severity: P3
Action: Run a verify. If this message still appears, reboot the system and run
another verify. If this message does not go away, contact your Support
Representative.
raw_send_vm: aopen %s = %d
Description: System failed to open the indicated mailbox to deposit a message.

Severity: P3
Representative.
raw_send_vm: rotated aopen %s = %d
Description: The recipient of a message rotated on full feature and the system failed to
open the rotate-to mailbox.
Severity: P3
Representative.
raw_send_vm2: aclose %s = %d
Description: The system failed to close a mailbox that has a broadcast light FCOS bit

after depositing a message.
Severity: P3
Representative.
raw_send_vm3: aclose %s = %d
Description: The system failed to close a mailbox without a broadcast light FCOS bit
after encountering an error while setting the message waiting indicator.
The message is therefore not in the mailbox.
Severity: P3
Representative.
RC: init(), cannot malloc iobuf
Description: The program is running out of memory and has terminated.

Severity: P2
Action: Check the memory availability.
RC: statistics(), cannot malloc segment
Description: The program is running out of memory and terminated.

Severity: P2
Action: Check the memory availability.
RC: Update for msg:%lx that is %s
Description: vac aborted due to a corrupted message sent by another task.

Severity: P3
Action: Run the verify again. Contact your Support Representative.
RC: Update for msg:%lx results in -refcnt(%d,%d)
Description: Occurs during an online verify. The online verify fails. If any module goes
down during the verify, you get several of these errors.
Severity: P3
Action: Run an offline verify.
rcrd is %s

Severity: P4
Action: Contact your Support Representative along with the task name for the
module indicated.
rcv:could not open rs232 port
Description: The rcv task of SL1 IVMS integration could not open the rs232 port as
configured.

Severity: P1
Action: Visually inspect the Smartcard hardware for possible configuration errors
(i.e., setting of interrupt jumpers, memory address, etc.), review the
Smartcard configuration in the offline menu, or reconfigure the system as
required, then enable the inactive configuration if changes were made via
the offline configuration. If the problem persists, contact your Support
Representative.
Reassigned block (request=%d block=%lx)
Description: Device media error recovery.

Severity: P4
Action: None.
Reboot request received from pid %d\n
Description: System reboot request.

Severity: P4
Action: None.
reboot: system rebooting.
Description: Comment indicating reboot event.

Severity: P4
Action: None.
Receive error in faxmgr.
Description: The fax application received an illegal request that was ignored.
Severity: P3
Action: None. The software recovers automatically.
Receive failed
Description: An operating system failure was encountered by the SS7 task.

Severity: P2
Receive() failed:%s
Description: Failure on receiving a message or a request.

Severity: P2
Received an unknown line exception
Description: Software bug in the application tried to access a nonexistent line exception.
Severity: P3
Redundant cmd failed, locator %d, (%(errno))

Description: Disk error on redundant.
Severity: P3
Receive request %d nid %d tid %04X of same sequence number!

Severity: P4
Action: Contact your Support Representative along with the task name for module
indicated.
refalldl fail: %d, %d

Severity: P3
refallmbox failed: %d, %d

Severity: P3
REFCHANGE(%d) for <message #> failed, result=%d
Description: A reference count change (the amount indicated in the parentheses) failed
due to the death of SAM or SFA. This message is likely to appear when a
module has died. The refchange will be retried.
Severity: P4
Action: If many of these messages appear, run an online verify.
REFCLEAR for <message #> failed, result=%d
Description: The task sam or sfa has died, and task nynex cannot send a request to
change or clear a message's reference count.
Severity: P3 or P4
Action: The dead task should be restarted automatically by the system. If not, reset
the system. Contact your Support Representative if a reset does not help.
REFDOUBLELOCK for <message #> failed, result=%d
Severity: P4
Action: None.
REFDOWN for <message #> failed, result=%d
Severity: P3 or P4

refdwn mbox failed: %d, %d

Severity: P3
refdwndl fail: %d, %d

Severity: P3
REFLOCK for <message #> failed, result=%d
Severity: P4
Action: None.
REFUNLOCK for <message #> failed, result=%d
Severity: P4
Action: None.
REFUNLOCK for <message #> failed, result=%d
Severity: P3 or P4
REFUP for <message #> failed, result=%d
Severity: P3 or P4
REFUP for <message #> failed, result=%d, retrying
Description: A reference count change failed due to the death of SAM or SFA. This
message is likely to appear when a module has died. The refchange will be
retried.
Severity: jP4
Action: If many of these messages appear, run an online verify.

refupdl fail: %d, %d

Severity: P3
refupmbox failed: %d, %d

Severity: P3
Reinit of mailbox path %d detected
Description: System hardware problem.

Severity: P1
Remounted READ ONLY & prefixed to local node
Description: Module in system has rebooted or network has disconnected.

Severity: P4
Action: None.
Reply error in faxmgr
Description: The memo program requesting the fax has died.

Severity: P3
Action: None. The software recovers automatically.
Reply failed

Severity: P2
Reply to %d failed (%s)
Description: Failure in trying to reply to a task with the pid shown

Severity: P2
Reply to trace failed

Severity: P4
Reply() failed:%s
Description: Failure in trying to reply to a task.

Severity: P2
Request executed already IN %d REQ %d

Severity: P4
Action: Contact your Support Representative along with the task name for the node
identified.
Request from %d for non existant task %d
Description: The undertaker received a request to monitor a nonexistent task. This

request is queued in case the relevant task starts later. This is a software
error.
Severity: P2
Request not executed yet IN %d REQ %d

Severity: P4
Action: Contact your Support Representative along with the task name for the node
identified.
Reserve speech in non reserve message tSpeech aptr=%u, Reserve

ptr:%u
Description: sam task allocated a reserved speech block for an unreserved message.
Severity: P2
Action: Perform a system verify. If the problem persists, contact your Support
Representative.
Reset of card in slot %d failed! Check I/O configuration
Description: Resource manager cannot communicate with the card when it tries to
initialize it.
Severity: P1
Action: There is a possibility that the switch setting for the I/O address does not
match the software resource configuration. Check to ensure they match.
*** RESYNC_SCAN: database not initialized
Description: The task resync_scan got a message back from scan that it could not
perform its command successfully.
Severity: P3
Action: Check the dial-by-name database by doing a phone book report. If
anything looks strange, contact your Support Representative.
rm_history:Unable to give up write access error (0x%x)
Description: The system was unable to give up write access after updating the disk.

Severity: P2
Action: Check the logfile for any disk errors, then take action based on the result of
this check. If there are no disk errors, contact your Support Representative.
rm_on:Unable to give up write access error (0x%x)
Description: The system was unable to give up write access after updating the disk.
Severity: P2
Action: Check the logfile for any disk errors, then take action based on the result of
this check. If there are no disk errors, contact your Support Representative.
ROLM CATCH: *** Unable to get rolm tid!
Description: rolmcatch could not find rolmadmin. Integration fails.

Severity: P1
Action: Check the system resources. If these are sufficient, restart rolmio and
rolmcatch by rebooting the system. If problems persist, contact your
ROLM CATCH: *** Unable to get sfa tid!
Description: rolmcatch could not find sfa. Integration fails.

Severity: P1
Action: Sfa may have died. Restart sfa by rebooting the system. If the problem
Rolm mwi: cannot send to mwla
Description: rolmmwi could not find mwla. Integration fails.

Severity: P1
Action: Mwla may have died. Restart mwla by rebooting the system. If the
ROLM: unable to register for net status with master
Description: If a module dies and is restarted, any integration lines on that module may
not answer contacts; also rolmadmin may attempt to dispatch contact
pickup requests to the dead module.
Severity: P2
Action: Reboot the module, then reboot the system. If the problem persists,
ROLM: unable to register for net status with master
Description: Rolm failed to register for net status to master. This indicates either a
software error or that the master is not running.
Severity: P2
Action: Reboot the system to restart the master. If the problem persists, notify your
ROLM_ADM: dispatching StartUp msg for node %d

Description: This message confirms the Rolm integration was started and initialized.
Severity: P4
rolmADMIN: lost a message for SFA (queue full)
Description: The internal queue to pass data between tasks is full. A contact integration
may be lost.
Severity: P1
Action: The load on the system is too heavy at this time. Contact your Support
Representative about getting extra hardware or, if possible, configure more
lines devoted to Rolm Integration.
ROLMADMIN: *** Unable to attach name (ROLMADM)!
Description: rolmadmin could not attach name. This a software error.

Severity: P1
rolmadmin: bad state in p_admin_msg s:x, lnk:x

Severity: P1
ROLMADMIN: Contact Pickup Latency reset to 0.
Description: The contact pickup latency was reset to 0 from the online menu by the
system administrator. Subsequent log messages New Contact Pickup
Latency is ... will be logged as the value grows back up.
Severity: P4
ROLMADMIN: host %d went down
Description: Rlomadmin received a net_status request from the master. Rolmadmin

checks the net status and logs the appropriate message. If a host is no
longer functional, it logs the above message.
Severity: P2
Action: If the host has terminated unintentionally, check hardware cables. Also
check logfile errors to see if there is any apparent reason why the host died.
ROLMADMIN: Net status changed
Description: Notification from master. Not an error.

Severity: P4
rolmadmin: Proc_admin_msg, state=x, message=y, link=z
Description: State machine for rolm received a Hangup from the contacter before it
could process the contact. Informational message.

Severity: P4
ROLMADMIN: registered for net status
Description: rolmadmin registered with master. Not an error.

Severity: P4
rolmadmin: send_to_sfa, bad link %d
Description: rolmio gave an invalid link number to rolmadmin. This is a software error.
Severity: P1
Action: Reboot the system, If the problem persists, reinstall the software.
rolmadmin: send_to_sfa, bad message x
Description: rolmadmin sending an unknown message to sfa.

Severity: P1
Action: Reboot the system, If the problem persists, reinstall the software.
rolmadmin: state=x, message=y, link=z
Description: rolmadmin is in a wrong state. This a software error. The states are: INIT
(0), IDLE (1), CI (2, contact pickup started), CP (3, PACK received from
SFA). This is a software error.
Severity: P1
rolmadmin: Timed out waiting for Pack
Description: rolmadmin task timed out while waiting for pack from sfa. sfa may have
died.
Severity: P2
Action: If the problem message persists, contact your Support Representative.
rolmadmin: Timed out waiting for Release on link %d
Description: rolmadmin timed out while waiting for release on this link. This a software
error.
Severity: P1
ROLMADMIN: Unable to attach name (ROLMADM) !

Severity: P1
ROLMADMIN: Unable to read oaa record.

Description: oaa record could not be read by rolmadmin. Software error. rolmadmin will
kill itself. As a result, the system will reboot.
Severity: P1
Action: If the problem persists, reinstall the software.
ROLMADMIN: unable to send to undertaker
Description: rolmadmin could not send to the undertaker.

Severity: P1
ROLMAGENT: *** Unable to get rolmadmin tid!
Description: rolmagent could not find rolmadmin. This is a software error.

Severity: P1
ROLMAGENT: can't send to rolmadmin!
Description: rolmagent could not find rolmadmin. This is a software error.

Severity: P1
ROLMAGENT: can't send to sfa%d!
Description: rolmagent could not find sfa.

Severity: P1
ROLMAGENT: Node ID (%d) out of range!
Description: The module number is greater than seven.

Severity: P1
ROLMAGENT: Unable to get sfa%d tid, aborting
Description: rolmagent could not find sfa.

Severity: P1
ROLMCATCH: can't locate admin after send failed.
Description: rolmcatch could not find rolmadmin. This is a software error.

Severity: P1
ROLMIO: can't locate ROLMADM
Description: rolmio could not find rolmadmin. Rolmcatch could not send to rolmadmin
even though it had its location..

Severity: P1
Action: Admin must have died. Restart Admin by rebooting the system. Check the
system resources. If the problem persists, contact your Support
Representative.
ROLMIO: Configuring for 9006!!
Description: Detecting Rolm 9006 switch in repdial .

Severity: None
ROLMIO: Could not pick up contact. Refer to the manual
Description: NuPoint Voice could not pick up the contact on the NuPoint Voice port.
Severity: P3
Action:
• Make sure that the 244PC extensions and the contact pickup strings are
programmed correctly.
• Make sure that all the contact pickup lines are plugged in.
• Make sure that all the line exceptions have default values unless they
were changed for some reason.
• Increase DTMF durations (line exceptions 164 and 166) but to not more
than 12.
• Try increasing line exception 41 (pause before dialing pickup string) to
1.5s.
• Make sure that the line group is set up correctly, and the corresponding
NuPoint Voice tasks are running.
• Make sure no one is contacting directly in to the NuPoint Voice ports.
To track this, run the CDR at level sfa for all the lines.
• Increase the DTMF power level (line exception 176) to full scale.
• Test the line ports in the CBX by plugging them into 500 sets and
picking up contacts (like NuPoint Voice).
ROLMIO: Could not reset DND, Check 244PC
Description: rolmio could not reset the DND (Do not disturb).
Severity: P2
Action: Check the class of service of the 244PC phone in the CBX to make sure
that bit 9 (DND) is included. Try pressing the DND key (Repdial key 7)
manually and check if the phone goes into DND. Make sure the phone
power supply is plugged in. Try replacing the phone.
ROLMIO: Could not set DND, Check 244PC
Description: rolmio could not set the DND (Do not disturb).
Severity: P2
Action: Check the class of service of the 244PC phone in the CBX to make sure
that bit 9 (DND) is included. Try pressing the DND key (Repdial key 7)
manually and check if the phone goes into DND. Make sure the phone
power supply is plugged in. Try replacing the phone.

ROLMIO: Incorrect input %d in state %d
Description: State machine error for rolmio. The system reinitializes itself and tries
again. If the error persists in the logfile, then this is a software bug.
Severity: P1
Action: Try restarting proc_admin (the state machine) and restarting rolmio by
rebooting the system. Check that the system resources are sufficient. If
problems persist, contact your Support Representative.
ROLMIO: New Contact Pickup Latency is %d. Not an error
Description: Not an error.

Severity: P4
ROLMIO: serial link %d is up

Severity: P4
ROLMIO: Unable to read oaa record.
Description: rolmio could not read oaa record. This is a software error.
Severity: P1
ROLMIO:$ctix: Could not reset DND, Check 244PC

ROLMIO:$ctix: Resetting Link
Description: rolmio could not get the 244PC out of Do Not Disturb mode after ten
attempts. It then resets the link. If it gets stuck trying, then there is a bad
phone or link. Otherwise, this is a nonfatal error and reflects on the switch
not accepting our request. In any case, this error, like the one before,
should occur rarely.
Severity: P2, P3
Action: Check phone and class of service in CBX.
ROLMIO:$ctix: New Contact Pickup Latency is y. Not an error
Description: Whenever rolmio detects a contact pickup latency greater than the value
sent to it by rolmadmin, it logs this message.
Severity: P4
Action: This is the value that will be used from now on to keep DND on. If this
value ever gets close to the max value entered in the offline menu, reset it
using the online menu.
ROLMMWI: $ctix: Unable to send to rolmadmin
Description: Tasks could not send data to rolmadmin. This is a software error. rolmmwi
will kill itself and will be restarted by rolmadmin.
Severity: P1

Action: If the problem persists, reinstall the software.
ROLMMWI: *** Unable to get rolmadmin tid!
Description: rolmmwi could not find rolmadmin. This is a software error.

Severity: P1
ROLMMWI: Could not turn ABCD ON/OFF (%u)
Description: rolmmwi could not switch the light for mailbox ABCD. The number in
parentheses is the number of successful messages with requests since the
current failure. On a failure, rolmmwi tries once again. If it fails again, the
number will be zero, and rolmmwi will move to the next request.
Severity: P2
Action:
• Check the class of service of the target extension in the CBX.
• Check that the target phone is plugged in.
• Increase the MWI query time from the off line menu (but not more than
5).
• Ensure that the MWI 244PC is in DND.
• Ensure that the MWI 244PC is plugged in (all cables).
• Check the cabling between the MWI 244PC and the CTI card.
• Ensure that the baud rate for the MWI link is 9600 (and not 19200 used
for the contact pickup links).
ROLMMWI: serial link %d is up

Severity: P4
ROLMMWI: Unable to read oaa record.
Description: rolmmwi could not read oaa record. This is a software error.
Severity: P1
S
send to user part failed, errno=%d
Description: This error notifies that a message sent to the user part has been attempted
without success.
Severity: P4
Action:

SL1MP: unable to register for net status with master
Description: Cannot get net status. This is a software error.

Severity: P2
sl1nadmin: bad type in start_contact_timer (x)
Description: The admin task is unable to start the contact timer due to an invalid type.
Severity: P2
Action: Review the system configuration for possible errors or reinstall the software,
then reboot the system in an attempt to clear the problem. If the problem
sl1nADMIN: cti driver did not start up
Description: Software error. The cti driver, required for the SL1 Meridian integration to
function, did not start up properly.
Severity: P1
sl1nadmin: hangup, bad link (x)
Description: The admin task finds the link parameter invalid. The contact will be
released.
Severity: P1
sl1nadmin: link: x queuing contact, no lines
Description: Incoming contacts are being queued because the line ports for contact
pickup are all busy.
Severity: P2
Action: Review the system line group assignments for possible errors. If the
problem persists, add more line ports to support additional traffic.
sl1nadmin:bad event in CI ln:x, event:y
Description: This message is logged whenever the state machine associated with logical
link x of the admin task receives an invalid event while in Contact
Information (CI) state. This event will be ignored.
Severity: P2
Action: The admin task will recover from this error. However, if the message is
logged repeatedly, reboot the NuPoint Voice system in an attempt to clear
the error or reinstall the SL1 Meridian integration software.
sl1nadmin:bad event in CIQ ln:x, event:y

link x of the admin task receives an invalid event while in Contact Release
Queuing (CRQ) state. This event will be ignored.
Severity: P2
sl1nadmin:bad event in CP ln:x, event:y
link x of the admin task receives an invalid event while in Contact Pickup
(CP) state. This event will be ignored.
Severity: P2
sl1nadmin:bad event in CQ ln:x, event:y
Description: This message is logged whenever the state machines associated with
logical link x of the admin task receive an unexpected event while in
Contact Queuing (CQ) state. This event will be ignored.
Severity: P2
sl1nadmin:bad event in CQ ln:x, event:y
link x of the admin task receives an invalid event while in Contact Queuing
(CQ) state. This event will be ignored.
Severity: P2
sl1nadmin:bad event in CR ln:x, event:y
(CR) state. This event will be ignored.
Severity: P2
sl1nADMIN:bad event in CRW ln:x, event:y
Waiting (CRW) state. This event will be ignored.
Severity: P2

sl1nadmin:bad event in IDLE ln:x, event:y
link x of the admin task receives an invalid event while in IDLE state. This
event will be ignored.
Severity: P2
sl1nadmin:bad state in p_admin_msg s:xx, lnk:yyyy
link yyy of the admin task detects an error with the message that it receives.
Severity: P2
sl1nadmin:BdRq while in CI y
link y of the admin task receives an invalid request while in Contact
Information (CI) state. This event will be ignored.
Severity: P2
sl1nadmin:BdRq while in CIQ y
link y of the admin task receives a bad request while in Contact Information
Queuing (CIQ) state. This event will be ignored.
Severity: P2
sl1nADMIN:BdRq while in CP y
link y of the admin task receives a bad request while in Contact Pickup (CP)
state. This event will be ignored.
Severity: P2

sl1nadmin:BdRq while in CQ y
link y of the admin task receives a bad request while in Contact Queuing
(CQ) state. This event will be ignored.
Severity: P2
sl1nadmin:BdRq while in CR y
link y of the admin task receives a bad request while in Contact Release
(CR) state. This event will be ignored.
Severity: P2
sl1nadmin:BdRq while in CRQ y
Queuing (CRQ) state. This event will be ignored.
Severity: P2
sl1nadmin:BdRq while in CRW y
Waiting (CRW) state. This event will be ignored.
Severity: P2
sl1nadmin:BdRq while in IDLE y
link y of the admin task receives an invalid request while in idle state. This
Severity: P2
sl1nadmin:cancel_contact_timer, bad link (x)
Description: The admin task is unable to cancel the contact timer due to an invalid link

parameter.
Severity: P2
Action: The admin task will try to recover from this error. However, if the message
is logged repeatedly, review the system Smartcard configuration for
possible errors or reinstall the SL1 Meridian integration software.
sl1nadmin:cleanup_contacts, bad link (x)
Description: The admin task releases the contact due to an invalid link parameter.
Severity: P2
sl1nadmin:get_node, bad link (x)
Description: The admin task detects an error relating to link parameter (x) when it tries to
get the node number to process the pending contact.
Severity: P2
sl1nadmin:get_tstamp: bad type (x)
Description: The admin task detects an error relating to event type (x) during normal
processing of the pending contact.
Severity: P2
sl1nadmin:PACK while in CP x
Description: This message is logged whenever the state machines associated with
logical link x of the admin task receives a Pack event unexpectedly while in
Contact Pickup (CP) state. This event will be ignored.
Severity: P2
sl1nadmin:Pack while in CQ x
Description: This message is logged whenever the state machine associated with each
logical link x of the admin task receives a Pack event unexpectedly while in
Contact Queuing (CQ) state. This event will be ignored.
Severity: P2
sl1nadmin:re-created sl1nio

Description: Informational message logged after the admin task restarted the sl1nio
task.
Severity: P4
Action: None
sl1nadmin:receive failed
Description: This message is logged whenever the admin task is unable to receive
messages from other tasks properly.
Severity: P2
Action: The admin task will try to resynchronize itself. However, if the message is
logged repeatedly, reinstall the SL1 Meridian integration software.
sl1nadmin:Release while in CRQ y
Description: Informational message. This message is logged whenever the state

machine associated with logical link y of the admin task receives a Release
event unexpectedly while in Contact Release Queuing (CRQ) state. This
Severity: P4
sl1nadmin:Rls while in CRW y
Description: Informational message. This message is logged whenever the state

machine associated with logical link y of the admin task receives a Release
event unexpectedly while in Contact Release Waiting (CRW) state.
Severity: P4
sl1nadmin:send_to_sfa, bad link (x)
Description: The admin task detects an error relating to link parameter (x) when it tries to
pass the contact information to sfa task.
Severity: P2
sl1nadmin:show_ts, bad contact_index (x)
Description: The admin task detects an error relating to logical link index (x).
Severity: P2
sl1nadmin:show_ts, bad link (x)

Description: The admin task detects an error relating to link parameter (x).
Severity: P2
sl1nadmin:show_ts, xx, yy, zz
Description: Informational message that provides information for other messages.

Severity: P4
Action: None.
sl1nadmin:start_contact_timer, bad link (x)
Description: The admin task is unable to start the contact timer due to an invalid link
parameter.
Severity: P2
sl1nadmin:store_crw, bad link (x)
Severity: P2
sl1nadmin:store_node, bad link (x)
Description: The admin task detects an error relating to link parameter (x) during normal
processing of the pending contact.
Severity: P2
sl1nadmin:store_timestamp, bad link (x)
Severity: P2
sl1nadmin:t/o while in CI y
Description: Informational message. This message is logged whenever the guard timer
associated with logical link y of the admin task expired while in Contact
Information (CI) state.
Severity: P3

sl1nadmin:t/o while in CIQ y
Information Queuing (CIQ) state.
Severity: P3
sl1nadmin:t/o while in CR y
Release (CR) state.
Severity: P3
sl1nadmin:t/o while in CRQ y
Release Queuing (CRQ) state.
Severity: P3
sl1nadmin:t/o while in IDLE y
associated with logical link y of the admin task expired while in idle state.
Severity: P3
SL1NADMIN:unable to send to undertaker
Description: The admin task of SL1 Meridian integration is unable to report the task
death to the undertaker.
Severity: P1
Action: If the problem persists, reboot the system in an attempt to clear the error. If
SL1NAGENT:*** Unable to get sl1admin tid!

Description: The agent task of SL1 Meridian integration is unable to locate the admin
task. Indicates a possible software error.
Severity: P1
Action: If the problem persists, reboot the system in an attempt to clear the error. If
sl1nio:Error SL-1 M2317 not responding on link x
Description: This message indicates that there is a problem with the contact pickup set
(M2317) associated with CTI port x.
Severity: P1
Action: If the problem persists, reinitialize the contact pickup set by temporarily
removing the DC power modules from the set. Then reboot the NuPoint
Voice system in an attempt to clear the error or reinstall the SL1 Meridian
integration software. If the problem persists, contact your Support
Representative.
sl1nio:Error starting SL-1 M2317 on $cti (link x)
Description: This message indicates that there is a problem with the contact pickup set
(M2317) associated with CTI port x.
Severity: P1
Action: If the problem persists, reinitialize the contact pickup set by temporarily
removing the DC power modules from the set. Then reboot the NuPoint
Voice system in an attempt to clear the error or reinstall the SL1 Meridian
integration software. If the problem persists, contact your Support
Representative.
sl1nio:reinitialized link x
Description: Informational message. This message is logged to report that the CTI
port/link x has been successfully initialized. x values are between 1 and 16.
Severity: P4
Action: None.
sl1nio:servicing x links
Description: Informational message. This message is logged to report the number of

CTI ports/links in use.
Severity: P4
Action: None.
SMSMWI_ADM: %s initialized.
Description: smsmwi_adm has successfully established the link %s and is ready to send
messages. This message is informational.
Severity: P4
Action: None.
SMSMWI_ADM: %s initialized.
Description:

Severity: P2
Action:
SMSMWI_ADM: %s is not functional.
Description:
Severity: P2
Action:
SMSMWI_ADM: %s re-initialized.
Description: When a link is lost due to read/write, time out, etc. and later established,
this message is logged.
Severity: P4
Action: None.
SMSMWI_ADM: All links are disabled
Description: smsmwi_adm has been unable to allocate a link slot. It should not happen.
smsmwi_adm will try to attempt to allocate a free slot.
Severity: P3
Action: Verify links are recovered properly. If not report to your customer
representative.
SMSMWI_ADM: bad message origin (%x)
Description: smsmwi_adm process has received a message from a process that it did
not expect to receive. This condition should not happen.
Severity: P4
Action: If it continues, report to your customer representative.
SMSMWI_ADM: Bd_event:%s[%d] in IDLE st.Lk#:%d
Description: smsmwi_adm has received an event from smsmwi_in that is not what was
expected in the state machine. The state machine should resync
automatically.
Severity: P4
Action: None.
SMSMWI_ADM: Bd_event:%s[%d] in INIT st.Lk#:%d
automatically.
Severity: P4
Action: None.
SMSMWI_ADM: Bd_event:%s[%d] in LKET st.Lk#:%d
automatically.

Severity: P4
Action: None.
SMSMWI_ADM: Bd_event:%s[%d] in LOGIN st.Lk#:%d
automatically.
Severity: P4
Action: None.
SMSMWI_ADM: Bd_event:%s[%d] in MSGPROC st.Lk#:%d
automatically.
Severity: P4
Action: None.
SMSMWI_ADM: Call your Distributor Rep
Description: smsmwi_adm process could not attach it’s name. This only happens if
some other process has already attached to the name. This is a software
error.
Severity: P2
Action:
SMSMWI_ADM: can't read OAA data!
Description: The smsmwi_adm process cannot read the oaa configuration. This is
severe and causes the sms_admin process to exit.
Severity: P2
Action: Recreate the SMS configuration and activate it. If, after reconfiguring, the
problem continues to exist, contact your Customer Representative.
SMSMWI_ADM: creatl error for IN task, link (%s), Port(%s).
Description: smsmwi_adm cannot start smsmwi_in for link <link number> on port <port
number>. smsmwi_adm task will try again.
Severity: P3
Action: Verify links are recovered properly. If not, contact your Customer
Representative.
SMSMWI_ADM: creatl error for OUT task, link (%s), Port(%s).
Description: smsmwi_adm cannot start smsmwi_in for link <link number> on port <port
number>. smsmwi_adm task will try again.
Severity: P3
Action: Verify links are recovered properly. If not, contact your Customer
Representative.
SMSMWI_ADM: event: %d out of range

Description: smsmwi_adm has received an invalid event.
Severity: P3
Action: If this continues, contact your Customer Representative.
SMSMWI_ADM: IN task for link %d already running.
Description:
Severity: P3
Action:
SMSMWI_ADM: IN for lk:%d died.
Description: The smsmwi_in process for the link has died. The smsmwi_out process is
halted and both the smsmwi_in and smsmwi_out processes are restarted.
This can happen when the SMSC has dropped the link and the smsmwi_in
and smsmwi_out processes are trying to re-establish the link.
Severity: P3
Action: Verify links have recovered properly. If not, verify the SMSC is functioning
properly.
SMSMWI_ADM: IN_DIED,link=%d,in=%d,out=%d
Description: The smsmwi_in process for link <link number> is dying. smsmwi_adm will
restart both the smsmwi_in and smsmwi_out processes. This can happen if
the link to the SMSC is down for extended periods of time. smsmwi_adm
will automatically restart smsmwi_in.
Severity: P3
Action: This is an indication that there is a problem with the connection to the
SMSC. If the link does not recover (check the log file), Troubleshoot the link
and make any necessary corrections.
SMSMWI_ADM: IN for link %d re-started.
Description: smsmwi_adm has successfully restarted smsmwi_in after it was previously

terminated. This is an informational message.
Severity: P4
Action: None.
SMSMWI_ADM: IN for link %d already running.
Description: smsmwi_adm has attempted to start smsmwi_in at a point when smsmwi_in

is already running. This would indicate the software state is out of sync.
This could happen if the smsmwi processes are being started by hand.
Severity: P4
Action: If this occurs and is not the result of user intervention, report to your
customer representative.
SMSMWI_ADM: IN_TCPIP_ERROR link=%d,in=%d,out=%d
Description: smsmwi_in has lost the TCP/IP connection with the SMSC. smsmwi_adm
will restart both smsmwi_in and smsmwi_out.
Severity: P3

SMSMWI_ADM: IN task for link %d re-started.
Description:
Severity: P4
Action:
SMSMWI_ADM: link:%d out of range
Description:
Severity: P3
Action:
SMSMWI_ADM: receive failed due to exception
Description: smsmwi_adm usually is blocked waiting for messages from the other
smsmwi processes. This message indicates a receive attempt has failed.
smsmwi_adm will go back and try to receive again.
Severity: P4
Action: Verify the smsmwi subsystem is working. If not, contact your Customer
Representative.
SMSMWI_ADM: received bad timer type,Type: %d
Description: smsmwi_adm has received an invalid timer type message.

Severity: P4
Representative.
SMSMWI_ADM: terminating out task
Description: A signal has been sent to the smsmwi_adm process instructing it to

terminate. It first halts the smsmwi_in and smsmwi_ou processes and then
exits. This message indicates that the smsmwi_out process is being
terminated. Normally, the master process restarts sms_admin.
Severity: P2
Action: If this message occurs frequently (and is not a result of user intervention)
first verify the smsmwi processes are restarting properly. If not, contact your
Customer Representative.
SMSMWI_ADM: timer error, lk:%d\n
Description: smsmwi_adm has received a timer proxy message for a link with negative
timer value. This would indicate that the state machine is out of sync.
Severity: P4
Representative.
SMSMWI_ADM: link:%d out of range

Description: smsmwi_adm has received an event for an invalid link number. This would
indicate a software error exists in some other process.
Severity: P3
Action: Contact your Customer Representative.
SMSMWI_ADM: lost a msg for OUT (Q full) for lk:%d.
Description: smsmwi_adm queues messages for smsmwi_out. If these messages are

not serviced, then the queue overflows and generates this message.
Severity: P3
Action: Check the states of the processes and make sure the system is operating
correctly. Especially the drivers (serial or TCP/IP) and smsmwi_out.
SMSMWI_ADM: lost a msg for SMSMWI_OUT (Q full) for lk:%d.
Description:
Severity: P3
Action:
SMSMWI_ADM: no outdial
Description: The SMSC has sent an outdial request to smsmwi due to a subscriber
present message. The smsmwi_outdial process is not running.
Severity: P3
Action: If the smsmwi_outdial feature is enabled, then troubleshoot why the
smsmwi_outdial process is not running. If the feature is not enabled, then
the configuration on the SMSC is incorrect and needs to be modified.
SMSMWI_ADM: OUT_DIED,link=%d,in=%d,out=%d
Description: The smsmwi_out process for link <link number> is dying. smsmwi_adm will
restart both the smsmwi_in and smsmwi_out processes. This can happen if
the link to the SMSC is down for extended periods of time. smsmwi_adm
will automatically restart smsmwi_in.
Severity: P3
SMSMWI_ADM: OUT for link %d already running.
Description: smsmwi_adm has attempted to start smsmwi_out at a point when

smsmwi_out is already running. This would indicate the software state is
out of sync. This could happen if the smsmwi processes are being started
by hand.
Severity: P4
Action: If this occurs and is not the result of user intervention, contact your
SMSMWI_ADM: OUT for link %d re-started.
Description: smsmwi_adm has successfully restarted smsmwi_out after it was previously

terminated. This is an informational message.

Severity: P4
Action: None.
SMSMWI_ADM: OUT for lk: %d died.
Description: smsmwi_adm has been notified that smsmwi_out has died.

Severity: P3
SMSMWI_ADM: OUT task for link %d already running.
Description:
Severity: P3
Action:
SMSMWI_ADM: OUT task for link %d re-started.
Description:
Severity: P3
Action:
SMSMWI_ADM: OUT_TCPIP_ERROR link=%d,in=%d,out=%d
Description: smsmwi_out has lost the TCP/IP connection with the SMSC. smsmwi_adm
will restart both smsmwi_in and smsmwi_out.
Severity: P3
SMSMWI_ADM: receive failed due to exception
Description:
Severity: P2
Action:
SMSMWI_ADM: received bad timer type. Type: %d
Description:
Severity: P3
Action:
SMSMWI_ADM: terminating in task
Description: A signal has been sent to the sms_admin process instructing it to terminate.
It first halts the smsmwi_in and smsmwi_out processes and then exits. This
message indicates that the smsmwi_in process is being terminated.
Normally, the master process restarts sms_admin.
Severity: P2

first verify the smsmwi processes are restarting properly. If not, contact your
SMSMWI_ADM: terminating out task
Description: A signal has been sent to the smsmwi_adm process instructing it to

terminate. It first halts the smsmwi_in and smsmwi_out processes and then
exits. This message indicates that the smsmwi_out process is being
terminated. Normally, the master process restarts sms_admin.
Severity: P2
first verify the smsmwi processes are restarting properl. If not, contact your
SMSMWI_ADM: timer error, lk:%d\n
Description:
Severity: P3
Action:
SMSMWI_ADM: Unable to attach name SMSMWIADM,module #: %d!
Description: The smsmwi_adm process could not attach it’s name. This only happens if
some other process has already attached to the name. This is a software
error.
Severity: P2
SMSMWI_ADM: Unable to attach timer proxy
Description: The smsmwi_adm process could not attach to a timer proxy. This happens
when system resources are overused.
Severity: P2
Action: Verify that smsmwi_adm process and links recover properly. If not, cut
down on the number of ports allocated on the module, and contact your
SMSMWI_ADM: Unable to create timer,errno=%d
Description: The smsmwi_adm process could not create a timer proxy. This happens
when system resources are overused.
Severity: P2
Action: Verify that smsmwi_adm process and links recover properly. If not, cut
down on the number of ports allocated on the module, and contact your
SMSMWI_ADM: Unable to send to outdial task
Description: smsmwi_adm process is unable to send messages to the sms_outdial

process, implying it is dead. The sms_outdial process will be restarted
automatically.
Severity: P3
Action: Verify the sms_outdial process is restarted (note: this is not used at

present).
SMSMWI_ADM: unable to send to undertaker
Description:
Severity: P3
Action:
SMSMWI_ADM: Unknown utility request for lk:%d.\n
Description:
Severity: P3
Action:
SMSMWI_AGENT: can't read oaa data!
Description: smsmwi_agent has been unable to read configuration information.

smsmwi_agent will terminate and master will restart it.
Severity: P3
Action: Reconfigure the smsmwi subsystem.
SMSMWI_AGENT: Cannot send to admin
Description: smsmwi_agent task has been unable to send messages to smsmwi_adm.

Severity: P3
Action: Verify the smsmwi subsystem is functioning properly.
SMSMWI_CAGENT: %s Cannot send to admin task!
Description: smsmwi_cagent has been unable to send to smsmwi_adm.

smsmwi_cagent will terminate and master will restart it (used for the
smsmwi callback feature).
Severity: P3
SMSMWI_AGENT: Cannot send to mwla!
Description: smsmwi_agent task has been unable to send messages to mwla.

Severity: P3
Action: If this continues, verify the mwla subsystem is functioning properly.
SMSMWI_CAGENT: %s Cannot send to pga_slave
Description: smsmwi_cagent has been unable to send messages to pga_slave.

smsmwi_cagent will terminate and master will restart it. (Used for the
smsmwi callback feature)
Severity: P3
Action: If this continues, verify the pga subsystem is functioning properly.

SMSMWI_CAGENT: Could not locate admin
Description: smsmwi_cagent has been unable to locate smsmwi_adm. smsmwi_cagent

will terminate and master will restart it. (Used for the smsmwi callback
feature.
Severity: P3
SMSMWI_CAGENT: %s Could not locate pga_slave
Description: smsmwi_cagent has been unable to locate pga_slave. smsmwi_cagent will

terminate and master will restart it. (Used for the smsmwi callback feature)
Severity: P3
Action: If this continues, verify the pga subsystem is functioning properly.
SMSMWI_DBTOOL: Unable to send to SMSMWI_ADM task
Description:
Severity: P2
Action:
SMSMWI_IN task for lk:%d died.
Description:
Severity: P1
Action:
SMSMWI_IN: %s re-started.
Description: smsmwi_in has successfully restarted after termination. This is

informational.
Severity: P4
Action: None.
SMSMWI_IN: %s started.
Description: smsmwi_adm displays this message the first time smsmwi_in for link <link
number> is started. This is informational.
Severity: P5
Action: None.
SMSMWI_IN: Error in opening %s (lk:%d) for read\n
Description:
Severity: P2
Action:
SMSMWI_IN: Error in opening %s (lk:%d) for read
Description: smsmwi_in has been unable to open the read link. smsmwi_in will terminate
and smsmwi_adm will automatically restart it.
Severity: P3

Action: Verify the smsmwi subsystem is functioning properly. If this continues to
happen, check the configuration and the state of the IO driver (TCP/IP or
serial).
SMSMWI_IN: got bad default
Description: smsmwi_in has read an invalid packet from input port or socket. It is
ignored.
Severity: P4
Action: None.
SMSMWI_IN: smsmwi_read TCPIP or serial lost connection errno=%d
Description: smsmwi_in has lost its read socket. smsmwi_in will try to re-establish the
link.
Severity: P3
Action: Verify the smsmwi subsystem is functioning properly. Check the state of the
I/O connection and the state of the SMSC.
SMSMWI_IN: Unable to get stty on RS2323 port %s
Description: smsmwi_in has been unable to get the terminal parameters for the read
port. smsmwi_in will terminate and smsmwi_adm will automatically restart it.
Severity: P3
happen, check the configuration and the state of the IO driver (serial).
SMSMWI_IN: Unable to name_locate admin task!
Description: smsmwi_in has been unable to locate smsmwi_adm. smsmwi_in will

terminate and smsmwi_adm will automatically restart it.
Severity: P3
SMSMWI_IN: **** Unable to name_locate SMSMWIADM
Description:
Severity: P2
Action:
SMSMWI_IN: Unable to open socket, errno=%d
Description: smsmwi_in has been unable to open the read socket. smsmwi_in will
Severity: P3
happen, check the state of the TCP/IP driver. The module may need to be
restarted. If this does occur, contact your Customer Representative.
SMSMWI_IN: Unable to read oaa record!
Description: smsmwi_in has been unable to read the oaa configuration record

smsmwi_in will terminate and smsmwi_adm will automatically restart it.
Severity: P3
Action: Reconfigure the smsmwi subsystem.
SMSMWI_IN: Unable to send to admin task,link=%d
Description: smsmwi_in has been unable to send a message to smsmwi_adm.

Severity: P3
SMSMWI_IN: Unable to set stty on RS232 port %s
Description: smsmwi_in has been unable to set terminal characteristics on the read link.
Severity: P3
SMSMWI_IN: Unable to open serial port %s
Description: smsmwi_in has been unable to open the serial port for reading. smsmwi_in
will inform the smsmwi_adm and both smsmwi_in and smsmwi_out are
restarted.
Severity: P3
SMSMWI_MWAGENT can't read oaa data!
Description:
Severity: P2
Action:
SMSMWI_MWAGENT: Cannot send to mwla !
Description:
Severity: P2
Action:
SMSMWI_MWAGENT: Cannot send to mwla !
Description:
Severity: P2
Action:
SMSMWI_MWAGENT: Could not locate MWLA!
Description:
Severity: P2
Action:

SMSMWI_MWAGENT: Invalid request from mwla
Description:
Severity: P3
Action:
SMSMWI_OAGENT: Cannot send to admin task!
Description: smsmwi_oagent has been unable to send to smsmwi_adm.

smsmwi_cagent will terminate and master will restart it. (Used for the
smsmwi message delivery feature)
Severity: P3
SMSMWI_OAGENT: Could not locate outdial task
Description: smsmwi_oagent could not locate smsmwi_outdial. smsmwi_oagent will

terminate and master will restart it. (Used for the smsmwi message delivery
feature)
Severity: P3
SMSMWI_OAGENT: Invalid request from outdial
Description: smsmwi_oagent has received an invalid request from smsmwi_outdial. This

message is ignored.
Severity: P4
Action: If this continues to happen, contact your Customer Representative.
SMSMWI_OUTDIAL: Invalid request recd in outdial
Description: smsmwi_outdial has received an invalid request. This message is ignored.

Severity: P4
Action: If this continues to happen, contact your Customer Representative.
SMSMWI_OUTDIAL: No free port entries available
Description: smsmwi_outdial could not find free port to dial out on. Either all ports are
busy, or ports are hung up.
Severity: P4
Action: Verify that all ports allocated to the smsmwi_outdial linegroup are
functioning properly. If they are, then system expansion is indicated.
SMSMWI_OUTDIAL: this voicememo port %x not in use
Description: smsmwi_outdial has received an outdial result from a voicememo port that
was thought to be idle. This indicates that there is a mismatch in an internal
resource table. The system continues to process requests.
Severity: P4
SMSMWI_OUTDIAL: Specified vmemo entry not available

Description: smsmwi_outdial cannot reference the session record for an outdial call that
has just completed. This indicates that there is a mismatch in an internal
resource table. The system continues to process requests.
Severity: P4
SMSMWI_OUTDIAL: this voicememo port already in use
Description: smsmwi_outdial has attempted to use a port that is already in use. This
indicates that there is a mismatch in an internal resource table. The system
continues to process requests.
Severity: P4
SMSMWI_OUTDIAL: Unable to attach name!
Description: smsmwi_outdial could not attach its name. smsmwi_outdial will terminate
and master will restart it.
Severity: P3
Action: Verify smsmwi_outdial is running. Check the logfile for other processes
reporting problems attaching names. If problems persist, contact your
SMSMWI_OUT task for lk: %d died.
Description:
Severity: P1
Action:
SMSMWI_OUT: %s re-started.
Description:
Severity: P4
Action:
SMSMWI_OUT: %s started.
Description:
Severity: P4
Action:
SMSMWI_OUT: invalid MISDN length, gsm:%s, mbox:%s
Description: smsmwi_out has been given a MISDN + GSM code that is less than 20
digits in length.
Severity: P4
Action: None.
SMSMWI_OUT: out_handler,signo=%d,rfd_fd=%d
Description: smsmwi_out has detected an exception. smsmwi_out will terminate and

smsmwi_adm will automatically restart it. This is the mechanism used by

smsmwi_adm to terminate smsmwi_in and smsmwi_out during link recovery
procedures.
Severity: P5
Action: None.
SMSMWI_OUT: rec'd invalid msg(%d) fr. ADMIN,lk:%d.\n
Description: smsmwi_out has received an invalid request from smsmwi_adm. This

request is ignored.
Severity: P4
Action: Verify the smsmwi subsystem is functioning properly. If this continues,
SMSMWI_OUT: smsmwi_write TCPIP lost connection errno=%d
Description: smsmwi_out has lost its write socket. smsmwi_out will try to re-establish the
link.
Severity: P3
Action: Verify the smsmwi subsystem is functioning properly. Check the state of the
I/O connection and the state of the SMSC.
SMSW_OUT: Unable to get stty on RS2323 port %s
Description: smsmwi_out has been unable to get the terminal parameters for the write
port. smsmwi_out will terminate and smsmwi_adm will automatically restart
it.
Severity: P3
SMSMWI_OUT: Unable to set stty on RS232 port %s
Description: smsmwi_out has been unable to set terminal characteristics on the write
port. smsmwi_out will terminate and smsmwi_adm will automatically restart
it.
Severity: P3
SMSMWI_OUT: Unable to initialize CTI port(%s).
Description: smsmwi_out has been unable to initialize its serial port. smsmwi_out will
Severity: P3
SMSMWI_OUT: Unable to name_locate admin task
Description: smsmwi_out has been unable to locate smsmwi_adm. smsmwi_out will

Severity: P3

SMSMWI_OUT: Unable to open serial port %s
Description: smsmwi_out has been unable to open the serial port for reading.
smsmwi_out will terminate and smsmwi_adm will automatically restart it.
Severity: P3
SMSMWI_OUT: Unable to open socket,errno=%d
Description: smsmwi_out has been unable to open the write socket. smsmwi_out will
Severity: P3
happen, check the state of the TCP/IP driver. The module may need to be
restarted. If this does occur, contact your Support Representative.
SMSMWI_OUT: unable to read mbox_record of %s
Description: smsmwi_out has been unable to read a mailbox record. This could happen
if the mailbox number in the MWI request is invalid, if the mailbox has been
deleted, or if the OAA subsystem is having problems.
Severity: P3
Action: Verify the system is still functioning properly.
SMSMWI_OUT: Unable to send to admin task, Link number: %d
Description: smsmwi_out has been unable to send a message to smsmwi_adm.

smsmwi_out will terminate and smsmwi_adm will automatically restart it.
Severity: P3
SND:bad line (x) in ivms transfer message
Description: The snd task of the SL1 IVMS integration detected errors with the port
number from the data packet when it tried to initiate a contact transfer.
Severity: P2
Action: Review the line group configuration in the offline menu for possible errors or
reconfigure the system as required, then enable the configuration. If the
snd:could not open rs232 port
Description: The snd task of the SL1 IVMS integration could not open the RS232 port
as configured.
Severity: P1
Action: Review the Smartcard configuration in the offline menu or reconfigure the
system as required, then enable the configuration. If the problem persists,

SND:operator revert ACK time-out line:x
Description: The snd task of the SL1 IVMS integration failed to transfer the pending
contact to the operator properly.
Severity: P2
Action: If the problem persists, reboot the system or reinstall the integration in an
attempt to clear the error. If the problem persists, contact your Support
Representative.
SND_IXFRAGNT: *** Unable to send to ixfr

Severity: P3
Action: None. The tasks will resynchronize.
SND_IXFRAGNT: *** Unable to send to snd (%x)
Description: The ixfr send task died.

Severity: P3
Action: None. The tasks will resynchronize.
SR_CLOSE for %lx failed, result=%d.
Description: An application was unable to close a message that it had open. This
results in an error message if an online verify is run before this msg is
closed by the system. The system will detect that this message is open and
close it within 48 hours.
Severity: P3
Action: None.
SRegTmr failed

Severity: P2
SR_OPEN for %lx failed, result=%d.
Description: An application cannot open a message for writing. The record or network
delivery fails.
Severity: P3
Action: If this message appears repeatedly, contact your Support Representative.
ss7admin%d: no config data
Description: This task was unable to read the SS7 configuration record.
Severity: P2
ss7admin%d: Unable to attach name
Description: An operating system failure was encountered by the T1/E1 driver.

Severity: P2
ss7admin%d: Unable to attach timer proxy

Severity: P2
ss7catch%d: can not locate isup\n
Description: This task was unable to communicate with the required SS7 task.
Severity: P2
ss7catch%d: no config data
Severity: P2
ss7catch%d: send to isup failed, errno=%d
Description: This task experienced a failure while communicating with ISUP.

Severity: P2
ss7catch: send to sfa failed\n
Description: This task experienced a failure while communicating with SFA.

Severity: P2
Standby dead
Description: Internal information keeping.

Severity: P4
Action: None. Information message only.
Start ioctl to DK driver failed
Description: The request to start the MTP processor failed.

Severity: P2
STT: can't get linestats
Description: stt, the program that gathers statistics, could not talk to one of the SFAs on
a host. You might be missing some statistics for the 15-minute time interval
when the error occurred.
Severity: P4

Action: Check the logfile for other clues as to why a module or its sfa could not be
contacted. If this error occurs frequently, contact your Support
Representative.
STT: can't get linestats for module %d
Description: stt, the program that gathers statistics, could not talk to the sfa on module
X. (This stat comes from sfa.)
Severity: P3
Action: Make sure the module in question is up and running.
STT: can't get sfa stats
Description: stt, the program that gathers statistics, could not talk to the sfa on module
X. (This stat comes from sfa.)
Severity: P3
Action: Make sure the module in question is up and running.
STT: cannot send to %s NETVM
Description: stt, the program that gathers statistics, could not talk to the networking
program to get networking stats.
Severity: P3
Action: Networking may be configured but not running. Check to see if the extra-
cost feature is loaded. If the problems still persist, contact your Support
Representative.
STTLIB: task %x cannot find NETVM
Description: The networking extra-cost feature is loaded but stt cannot find the task
netvm to gather networking statistics.
Severity: P2
Action: Check if networking is running and working on the system. This error
should only occur soon after startup.
SYS75 Agent: *** Unable to get admin tid!
Description: The System 75 agent task was unable to locate the System 75
administration task. It will retry forever.
Severity: P2
Action: Terminate sys75_agent. Check the configuration to ensure that System 75
Administration is configured. Reboot the system and reinstall the extra-cost
diskette. If problems persist, contact your Support Representative.
SYS75 CATCH: *** Unable to get admin tid!
Description: The System 75 catch task was unable to locate the System 75
administration task. It will retry forever.
Severity: P2
Action: Check the configuration to ensure that System 75 administration is
configured.

SYS75 MWI: *** Unable to get admin tid!
Description: The System 75 message waiting indication task was unable to locate the
System 75 administration task. It will retry forever.
Severity: P2
Action: Check the configuration to ensure that System 75 Administration is
configured.
Sys75_admin - al off hook bad link number =%d
Description: The system was unable to pick up the specified contact.

Severity: P3
Sys75_admin - bad access table command %xh
Description: Bad access table command.

Severity: P2
Action: Turn on the Event Recorder and log it to a file/printer. Contact your Support
Representative.
Sys75_admin - bad link number %d pass to access table

or
Sys75_admin - bad node number %d pass to access table
Description: Bad link/node number defined in integration configuration.

Severity: P2
Action: Reconfigure the integration from the Offline Menu and enable the inactive
configuration. If the problem persists, contact your Support Representative.
Sys75_admin - can't open cti port for data link [%d]
Description: Cannot open the CTIn port for data link.

Severity: P2
Action: Verify the 7404D and vmemo are connected and the 7404D has a
clean/surge protect power line. If both are okay, the serial/CIT board may
be failing. Verify the serial cable is shielded. If the cable is shielded, you
may need to perform an analysis of AC power. Turn on Event Recorder and
log current events to a printer. Contact your Support Representative.
Sys75_admin - incorrect link data entry for link number [%d+1]
Description: Incorrect link description.

Severity: P2
Action: Correct the link number entry from the NuPoint Voice Offline Configuration
Menu. Then, enable the inactive configuration. If the problem persists,
Sys75_admin - pbx sw version out of range - default value to r1v2
Description: The PBX software version defined in the vmemo configuration is incorrect.
Severity: P2

Action: Correct the PBX SW version from the NuPoint Voice Offline Configuration
Sys75_admin - pbx sw version out of range - default value to r2v2
Description: The PBX software version defined in the vmemo configuration is incorrect.
Severity: P2
Action: Correct the PBX SW version from the NuPoint Voice Offline Configuration
Sys75admin - bad msg origin =%xh
Description: Bad byte in message packet.

Severity: P2
Action: Turn on the Event Recorder and log it to a file/printer. Contact your Support
Representative.
Sys75admin - timeout error...link was disconnected
Description: Serial link between 7404 and NuPoint Voice is not connected.
Severity: P1
Action: Verify the serial link is properly installed. Reset 7404 and verify whether the
integration is working. If the problem persists, contact your Support
Representative.
Sys75parser - getting pkt msg %d %d
Description: Error in getting a packet of data from the serial port. The first %d indicates
the number of bytes the serial port has received. The second %d indicates
the read error code. Example: getting two bytes 5 0 means the serial port
received 5 bytes and error code 0 on the 6th byte. Error code 0 =
disconnect/end of file. Note: Read error also causes an error code 0.
Usually after receiving this error, the Sys75/85 integration still tries to
reinitialize the link to make sure the 7404 comes up. If the initialization
sequence did not start, vmemo can enter the hang mode forever. This error
can occur when the 7404 goes into self test mode, sys75/85 telset test,
serial link disconnect, or power surge.
Severity: P2
Action: Verify the 7404D and vmemo are connected and that the 7404D has a
may need to perform an analysis of AC power. Turn on the Event Recorder
and log current events to a printer. Contact your Support Representative.
Sys75parser - getting two bytes %d %d
Description: Error in getting two bytes of data from the serial port. The first %d indicates
the number of bytes the serial port has received. The second %d indicates
the read error code. Example: getting two bytes 1 0 means the serial port
received 1st byte and error code 0 on 2nd byte. Error code 0 =

sequence did not start, vmemo can enter the hang mode forever. This error
can occur when the 7404 goes into self test mode, sys75/85 telset test,
serial link disconnect, or power surge.
Severity: P2
Action: Verify the 7404D and vmemo are connected and the 7404D has a
Sys75parser - receive a link reset from 7404
Description: Received a link reset command, or the 7404 is sending I'm exiting 'PCX'
mode and entering 'modem' mode. When the system 75 integration
receives this data packet, it has to initialize the 7404 or the link will not
work. This often happens during a cold boot. Ignore this message if the
link initialization has finished.
Severity: P2, if the system was up and running.
P4, if system was started from a cold boot.
Action: If the system was up and running, turn on the Event Recorder and log
current events to a file/printer. Then contact your Support Representative.
Otherwise, ignore this message.
Sys75parser - remote 7404 sending lots of junk

Sys75parser - can not find packet header after 240 bytes
Description: The 7404 is probably in modem mode and is sending a non-PCX data
packet. Sys75parser will attempt to find the data packet header in 240
bytes (maximum buffer size of a 7404 Telst). If no packet header is found,
the sys75parser will assume that the 7404 is in modem mode and will try to
reinitialize the 7404 into PCX mode. This message also appears after a
disconnect and reconnect of the serial cable.
Severity: P4, if system is starting up.
P2, if system is operational.
Action: Verify the 7404D and NuPoint Voice are connected and the 7404D has a
Sys75parser - time out result %d %d
Description: Error in getting a sync character (0x7f) from the serial port. The first %d
indicates the number of bytes the serial port has received. The second %d
indicates the read error code. Example:getting two bytes 1 0 means the
serial port received 1st byte and error code 0 on 2nd byte. Error code 0 =
sequence did not start, NuPoint Voice can enter the hang mode forever.
This error can occur when the 7404 goes into self test mode, sys75/85
telset test, serial link disconnect, or power surge.
Severity: P2

Action: Verify the 7404D and NuPoint Voice are connected. Verify the 7404D has
a clean/surge protect power line. Probably the serial/CIT board is failing.
Verify the serial cable is shielded. You probably need to perform an
analysis of AC power. Turn on the Event Recorder and log current events
to a printer. Contact your Support Representative
Sys75rcv - link [%s] error message encountered
Description: Link CTIn received an unknown data packet.

Severity: P2
Action: Turn on the Event Recorder and log current events to a file/printer. Contact
Sys75rcv - system 75/definity software release version [%s]
Description: Informational message printed during system 75 integration startup. Valid

versions are: R1V2, R1V3, R1V4, G1, and G2.
Severity: P4
Action: Verify that the version is the same as your pbx software version. If not,
reconfigure your NuPoint Voice system using the Offline Configuration
Menu, then enable the inactive configuration.
Sys75rcv - system 85 software release version [%s]
Description: Informational message printed during system 85 integration startup. Valid

versions are: R2V2, R2V3, and R2V4.
Severity: P4
Action: Verify that the version is the same as your pbx software version. If not,
reconfigure your NuPoint Voice system using the Offline Configuration
Menu, then enable the inactive configuration.
Sys75snd - error in opening cti port to read =%s
Description: Task is unable to open a cti serial port to read.

Severity: P3
Action: Verify that a CTI card has been installed in your system. If the problem
Sys75snd - error in opening cti port to write = %s
Description: Task is unable to open a cti serial port to write.

Severity: P3
Action: Verify a CTI card has been installed in your system. If the problem persists,
Sys75snd - error in reading queue =%d
Description: Task cannot open queue to read. Possible error codes are:
-9 = invalid message
-10 = invalid open mode
-11 = open for read or write denied
-12 = unable to create
-13 = no memory for request

-14 = queue does not exist
-15 = queue window is full
-16 = network error
-17 = invalid queue name
-18 = can't locate queue task
-19 = too many open queues
-20 = send fail
-21 = message too big to read
-22 = contact Quatum/your Support Representative
Severity: P2
Action: Reboot the system and run a verify. If the problem persists, contact your
Sys75snd - incoming message not recognized
Description: Incoming message is not recognized.

Severity: P3
Action: Reboot the system and reconfigure as necessary. If the problem persists,
Sys75snd - queue creation failed: send=%d
Description: Task cannot open queue to read. Possible error codes are:
-9 = invalid message
-10 = invalid open mode
-11 = open for read or write denied
-12 = unable to create
-13 = no memory for request
-14 = queue does not exist
-15 = queue window is full
-16 = network error
-17 = invalid queue name
-18 = can't locate queue task
-19 = too many open queues
-20 = send fail
-21 = message too big to read
-22 = contact Quatum/your Support Representative
Severity: P2
Action: Reboot the system and run a verify. If the problem persists, contact your
system shutdown
Description: Manual system shutdown was initiated from the console.

Severity: P4
Action: None.
T
Task %x can't set ADMIN flag.

Severity: P3
E=%s, R=%d G=%d
Description: A problem manipulating the request queue exists.

Severity: P1
TCP_NTT: Cannot open and bind TCP socket
Description: The level 4 to level 4 communication link cannot be established.

Severity: P1
Timed out while trying to send command
Description: Request failed to respond.

Severity: P3
Action: None.
...net_name = %d, nt_mcnt = %d

Severity: None
no index entry E=%s R=%d G=%d
Description: System cannot locate the index position of the request in the index file.
Severity: P1
tnpp admin can't create mwi task. link=%d,err=%x
Description: Same as tnpp admin can't create... snd or rcv task. In this case, the
application will come up and talk to the link if snd and rcv started OK, but
the tnppmwi task will not be there to get page requests from pga.
Severity: P1
Action: Check that the port configured for this tnpp link is a valid port on the
system. Reboot the system. If this does not resolve the problem, contact
tnpp admin can't create rcv task. link=%d,err=%x
Description: tnppadmin received a system error when trying to create the tnpprcv task.
The application cannot run. There will be no tnpprcv task to look at data
coming in on the tnpp link.
Severity: P1

tnpp admin can't create snd task. link=%d,err=%x
Description: Same as tnppadmin can't create rcv task. The tnppadmin cannot start
tnppsnd and the application cannot run.
Severity: P1
tnpp admin unable to attach name after 1 min
Description: The tnppadmin task cannot attach its name after trying for one minute. As
this message is in a loop, the admin will continue to try to attach its name
forever. The application will not run if it is stuck here.
Severity: P1
Action:
tnpp admin unable to attach timer port, exiting.
Description: This is similar to the unable to attach name log message. In this case,
tnppadmin is not in a loop and will exit. The system will try to start
tnppadmin again.
Severity: P1
Action: If this happens repeatedly, reboot the system. If the problem persists,
TNPP: can not find smart serial
Description: TNPP cannot find the Smartcard serial port.

Severity: P2
Action: Check the Smartcard configuration and switch the setting. Make sure the
hardware is plugged in properly.
TNPPRCV: Error in reading from device
Description: Error in reading contact info from the serial port.

Severity: P2
Action: Check the serial port connection.
TNPP_UTILS: unable to send to tnppadmin.
Description: The tnpputils program cannot send to tnppadmin. Run-time inquiries and
changes cannot be done. It is possible that tnppadmin is not running and
that is why tnpputils cannot send.
Severity: P2 or P3
Action: Check that tnppadmin is actually running. If the application is running and
tnpputils cannot send, check the system resources. Reboot and reload the
extra-cost diskette, as tnpp_utils may have been corrupted.
TNPPADM: ev TIDLE in st XMITTING on link %d!
Description: The TIDLE and XMIT_TIMEOUT are time-out events to get the state
machine out of the transmitting state in case something goes wrong. As the

other RCV events are not expected during transmission, something is
assumed to be wrong and an ENQ is sent out on the serial link.
Severity: P2
TNPPADM: ev XMIT_TIMEOUT in st XMITTING on link %d!
Description: The TIDLE and XMIT_TIMEOUT are time-out events to get the state
machine out of the transmitting state in case something goes wrong. As the
other RCV events are not expected during transmission, something is
assumed to be wrong and an ENQ is sent out on the serial link.
Severity: P2
TNPPADM: Link %d disabled from tnpp utility program
Description: The application will not operate on this link because it has been disabled
(through software).
Severity: P4
Action: To enable the link, the customer can use the tnpp utilities from the Utilities
submenu of the System Maintenance menu.
TNPPADM: Link %d enabled from tnpp utility program
Description: The application should begin operating on this link again.

Severity: P4
Action: None.
TNPPADM: unknown msg %d from TNPP_MWI link %d.
Description: tnppadmin and the tasks tnppsnd, tnpprcv, tnppmwi, and tnpputils have
message numbers that they send to each other. Each task has to think that
the messages mean the same thing. If this log message occurs, it is
possible that some files are out of sync, i.e. an older version of tnppadmin
that does not know about a message that a newer version of tnppsnd is
sending. This message should not occur in any new install.
Severity: P1
TNPPADM: unknown msg %d from TNPP_RCV link %d.
possible that some files are out of sync, i.e. an older version of tnppadmin
Severity: P1
TNPPADM: unknown msg %d from TNPP_SND link %d.

possible some files are out of sync, i.e. an older version of tnppadmin that
does not know about a message that a newer version of tnppsnd is
Severity: P1
TNPPADM: unknown msg %d from TNPP_UTIL link %d.
Description: tnppadmin and tasks tnppsnd, tnpprcv, tnppmwi, and tnpputils have
message numbers that they send to each other. Each task has to assume
that the messages mean the same thing. If this log message appears, it is
possible that some files are out of sync, i.e., an older version of tnppadmin
Severity: P1
TNPPADM: zero pkt failed on link %d, no mwi reply
Description: The tnpp allocation sent a zero packet to the paging terminal and did not
receive a valid response. Sending a zero packet is part of initializing the
link. Depending on the requirements of the paging terminal, subsequent
pages sent to the paging terminal may not be processed.
Severity: P2
Action: If pages are not being processed, send a zero packet on the link using the
link utilities. If pages are still not being processed, reset the module, then
the system if necessary. If still unable to process pages, contact your
TNPPADMIN: bad state %d for link %d
Description: There are currently five states for a tnpp link. If the state of this link is not
INIT, AWTG_ENQ_RESP, RDY_TO_COMM, XMITTING, or
AWTG_XMIT_RESP, this message will be logged. This message should
never appear during normal operation.
Severity: P1
TNPPADMIN: link %d down, %d enq retries, no eot rec'd
Description: The tnpp application is up and running and sending ENQs on the serial link.
The other end is not responding. This message will be logged when the
cenq value has been met. The cenq value is configured in the tnpp timing
parameters menu. cenq sets a limit on how many times the application will
send an ENQ without getting a response before it logs this message.
Severity: P2
Action: Make sure the serial link is connected to both NuPoint Voice and the paging
terminal. Check the baud rate and other link parameters to make sure that
they match on both devices. If the devices are connected by a modem,
make sure both ends are communicating.

TNPPADMIN: link %d is not checked in, cannot snd
Description: The tnppsnd task has not checked back in with the tnppadmin task and it
cannot be dispatched.
Severity: P1
Action: If this happens occasionally, your Support Representative should look into
why it happens. If this is happening continually, the customer should
probably reboot and see if the application comes up OK.
TNPPADMIN: pkt held too many times, discarding
Description: A packet has received an RS after it was sent and has been held and re-
sent Chold times. An RS means the paging terminal cannot process this
packet at this time. tnppadmin will wait Thold seconds before trying to
resend the packet and will do this up to Chold times. Chold and Thold are
both configured in the tnpp timers menu in the tnpp offline selection.
Severity: P2 or P3
Action: This error points towards the paging terminal rather than towards NuPoint
Voice. The customer should check the paging terminal. The customer
should already know what to look for.
TNPPADMIN: pkt retry limit exceeded, discarding.
Description: A packet is normally sent once and then it receives an ACK. If the packet
receives a NAK, it will be re-sent Cretry times. Cretry is configured in the
tnpp timers menu in the tnpp offline selection. If a packet has been re-sent
Cretry times and still not ACK'd, it will be discarded and this message will
be logged. This log will be followed by a PAGE_FAILED log to indicate
which mailbox had the problem.
Severity: P2 or P3
Action: Check the TNPP configuration of the mailbox. If the mailbox is correct,
check the configuration of the tnpp link. If this error occurs all the time with
all packets, there could be a communications problem between the paging
terminal and NuPoint Voice. When packets get NAK'd and everything looks
OK, there could be a problem with the checksum value calculated for each
packet. NuPoint Voice calculates the checksum according to the TNPP
specification. Check how the paging terminal on the receiving end
calculates the checksum.
TNPPADMIN: Rcvd CAN on link %d, discarding pkt
Description: The paging terminal has sent a CAN back for a packet, telling us to cancel it
and not send it again. This message will be followed by a PAGE_FAILED
message that indicates which mailbox had the problem.
Severity: P2 or P3
Action: Check the TNPP configuration of the mailbox. If the mailbox is correct,
check the configuration of the tnpp link. If this error occurs all the time, it is
likely a link config problem. If it only occurs on some mailboxes, it is likely
related to the mailbox configuration.
TNPPADMIN: tnpp mwi task died,link %d. mwi restarted
Description: The state task died and was successfully restarted. If this happens once in
a while, it isn't good but it isn't a disaster. This message would appear in

the logfile if you were to slay one of these tasks. If this log message
appears often, there's trouble.
Severity: P1 or P3
Action: Try a reboot, reinstall the optional feature, and contact your Support
Representative.
TNPPADMIN: tnpp rcv task died,link %d. rcv restarted
Description: The state task died and was successfully restarted. If this happens
intermittently, it isn't good but it isn't a disaster. This message would
appear in the logfile if you were to slay one of these tasks. If this log
message appears often, there's trouble.
Severity: P1 or P3
Representative.
TNPPADMIN: tnpp snd task died,link %d. snd restarted
Description: The state task died and was successfully restarted. If this happens
intermittently, it isn't good but it isn't a disaster. This message would
appear in the logfile if you were to slay one of these tasks. If this log
message appears often, there's trouble.
Severity: P1 or P3
Representative.
TNPPADMIN: unable to send to undertaker
Description: This is another case where there are problems in the system beyond the
tnpp application.
Severity: P1
Action: Reboot. Contact your Support Representative if the problem persists.
TNPPMWI%d: can't do page for mbox %s
Description: This message is logged when an unknown reply comes back from
tnppadmin.
Severity: P1
TNPPMWI%d: can't make page block for mbox %s.
Description: This message is logged if the mailbox is configured for one type of tnpp
paging and the link is configured for another (e.g. the mailbox is CAP and
the link is ID). If this is the case, another message will be logged indicating
what the mismatch is. The other way this message can be logged is if the
mailbox does not have tnpp configured in it at all, but has pager message
waiting and is using the tnpp pager system number.
Severity: P2
Action: Check the mailbox configuration and the link configuration.
TNPPMWI%d: can't open mailbox %s

Description: tnppmwi received a page request and cannot open the mailbox oaa record
to get the data it needs.
Severity: P1 or P2
Action: If this is happening on one mailbox, it might be corrupted or locked.
Investigate the problem with the particular mailbox. If it is happening all the
time, contact your Support Representative as there are probably other
problems with the system.
TNPPMWI%d: can't send page to tnppadmin for mbox %s.
Description: tnppmwi tried and failed to send the page message to tnppadmin. The
page will not be sent out. The inter-task communication failed.
Severity: P1 or P2
Action: Reboot. If condition persists, reinstall the software, and contact your
TNPPMWI%d: cannot send to pga, aborting
Description: The tnppmwi task needs to send to the pga task to get tnpp paging
requests. If tnppmwi cannot send to pga, the application will not work.
There may also be something wrong with the system if pga is not running.
Severity: P1
Action: Reboot and contact your Support Representative.
TNPPMWI%d: invalid ml_request %d from pga.
Description: tnpp only accepts ml_on as a valid request from the pga admin. Any other
message from pga will produce this log message. Tnppmwi will reply back
to pga with ml_error and will wait for the next request.
Severity: P2
TNPPMWI%d: link %d is CAP, mbox %s is ID, no match
Description: The page will not be sent.

Severity: P2
Action: Check the configuration of either the mailbox or the link--whichever is
configured for the wrong paging type.
TNPPMWI%d: link %d is ID, mbox %s is CAP, no match
Description: The page will not be sent.

Severity: P2
Action: Check the configuration of either the mailbox or the link--whichever is
configured for the wrong paging type.
TNPPMWI%d: link %d's paging type %s is invalid.
Description: The valid value for the paging type is CAP or ID. The paging type cannot
be left blank. It is configured in the offline tnpp configuration menu. Pages
cannot be performed if they are sent to this link.
Severity: P2

Action: Check the tnpp configuration for completeness. If the configuration is okay
and the problem persists, contact your Support Representative.
TNPPMWI%d: no tnpp_flag set in mailbox %s.
Description: tnppmwi received a page request for a mailbox that is not configured for
tnpp. The page will not be sent.
Severity: P2
Action: If the mailbox is not supposed to be tnpp, check the pager system number.
If the mailbox is supposed to be tnpp, verify it is configured correctly.
TNPPMWI%d: PAGE_FAILED for mbox %s
Description: page_failed was returned to tnppmwi from tnppadmin after it processed the
page.
Severity: P2
Action: This log message is preceded by a message from tnppadmin indicating
what event in what state caused the page to fail.
TNPPMWI%d: The new paging type %s sent to link is %d invalid.
Description: A run-time change to tnppmwi's paging type was made using the tnpp
utilities and an invalid value was sent. The existing run-time value will not
be changed.
Severity: P3
Action: Retry the change using either CAP or ID as the paging type.
tnpprcv cannot open serial port for link %d
Description: The tnpprcv program cannot open the configured serial port. Tnpprcv will
not start.
Severity: P1
Action: Check that the port configured for the tnpp link(s) is a valid port name that
exists on the system. If the configuration is okay, try to determine if the
serial port is bad or not. Check that another application is not accessing the
serial port.
TNPPRCV%d: unable to send to tnppadmin.
Description: tnpprcv cannot send information to tnppadmin. The application will not
work.
Severity: P1
Action: Restart the application. If the problem persists, contact your Support
Representative.
TNPPRCV: link re-open failed, error_status = %d
Description: tnpprcv had problems with its first attempt to get data from the serial link. It
closed and reopened the link, but the reopen failed. It will not receive data
from serial link.
Severity: P1
Action: Reboot the system. Check the configuration and check the serial port
hardware.

TNPPRCV: link re-open ok, error_status = %d, rfd = %x
Description: tnpprcv recovered from a serial link problem. This log message appears
when tnpprcv fails to get something from the serial link. The task will close
and reopen the serial link and try again.
Severity: P3
Action: None, unless the problem persists. If so, contact your Support
Representative.
tnppsnd cannot open serial port for link %d
Description: The tnppsnd program cannot open the configured serial port. tnppsnd will
not start.
Severity: P1
Action: Check that the port configured for the tnpp link(s) is a valid port name that
exists on the system. If the configuration is okay, try to determine if the
serial port is bad or not. Make sure another application is not accessing the
serial port.
TNPPSND: unable to send to tnppadmin.
Description: tnppsnd cannot send information to tnppadmin. The application will not
work.
Severity: P1
Action: Restart the application. If the problem persists, contact your Support
Representative.
\t...sndr: %s, node %d

Severity: None
U
UIMAP_AGENT: can't locate (%s)
Description: Cannot locate MWLA.

Severity: P1
UIMAP_AGENT: can't send to MWLA!
Description: Cannot send to MWLA.

Severity: P1
UIMAP_AGENT: can't send to UIMAP!
Description: Cannot send to UIMAP.

Severity: P1
UIMAP: chksm BAD, mbxsum = %u, extsum = %u
Description: The UIMAP request was unsuccessful. The number of entries in the
extension mappings is not the same as in the mailbox mappings. The
message shows the sum of mailbox mappings and the sum of extension
mappings..
Severity: P2
Action: Re-initialize UIMAPping.
UIMAP: chksm BAD, requst = %s
message shows the type of request.
Severity: P2
Action: Re-initialize UIMAPping.
UIMAP: Could not get network status
Description: Unable to get network status and register with master.

Severity: P1
UImap: *** could not resynch segment %d.
Description: Configuration or hard disk problem.

Severity: P2
UIMAP%d: I am master
Description: The UIMAP starting on node is the primary UIMAP.

Severity: P4
UIMAPMASTER: Could not attach name
Description: The contacting process is unable to register the name UIMAPMASTER on

the node. Either the name space is used up or the name already exists on
that node.
Severity: P1
uimap: *** master record read failed.
Description: The master SMDI record cannot be read from disk to be reinitialized. The
program will log this message, sleep 5 seconds, then try to open the record
again. It will remain in this loop until it can successfully read the record.
The map database will not be updated. Data will be out of sync.

Severity: P2
Action: Reboot the system. If the master record cannot be read, there may be
other problems with the system. Contact your Support Representative.
UIMAP: MBox = %s, Ext = %s
message shows the mailbox number and the extension number.
Severity: P2
Action: Reinitialize UIMAPping.
UIMAP: my own agent checked in as an update agent
Description: My own agent checked in as an update agent.

Severity: P3
Action: The system should ignore this type of request. Check the ui configuration.
If the problem persists, contact your Support Representative.
UIMAP: PBX = %d, Tenant = %d
message shows the PBX number and the tenant number.
Severity: P2
Action: Reinitialize UIMAPping.
UIMAP: request not sent to other hosts - read_msg bad
Description: Request cannot send to other modules. The other modules might be in a
reboot state.
Severity: P3
Action: Check if the other module is rebooting. Check if the other module needs to
be restarted. Check if you can use the other module. Check if the QNet
card is working. Reboot the system. Check the system configuration. If
UIMAP: request queue is full - need to resync.
Description: Queue is full, and cannot write to queue.

Severity: P3
Action: Check the ui configuration. The system might have too many tasks wanting
to talk to uimap. Repartition the ui group to multiple-cti card on multiple
modules or have fewer linecards. Reboot the system. Contact your
uimap: *** resynch failed after master reinitialized.

Severity: P2

uimap: *** Unable to attach name UIMAP/UIMAPMASTER
Description: The contacting process is unable to register the name

UIMAP/UIMAPMASTER on the node. Either the name space is used up or
the name already exists on that node.
Severity: P1
UIMAP: unable to register for net status with master
Description: Unable to get network status and register with master.

Severity: P1
uimap: unable to send to undertaker, abort sending
Description: uimap tried to register its agent task to the undertaker ten times, but failed.
It will not try again.
Severity: P2
uimap: unable to send to undertaker, trying again
Description: uimap tried to register its agent task to the undertaker, but failed. It will
retry 10 times.
Severity: P3
uimapagent(%d): *** My parent UIMAP task is DEAD!
Description: uimap communications problem. Task terminated.

Severity: P1
uimapagent(%d): *** OAA closure/update failed for %s

Severity: P2
uimapagent(%d): *** OAA open failed for %s

Severity: P2
uimapagent(%d): *** OAA readback failed for %s

Severity: P2
Unable to add resource %x for line (%d, %d), Error %d
Description: SFA fails to add the resources needed to make up a line port for the slot
and port number specified. This port will be unusable.
Severity: P2
Action: This problem can occur when users try to configure more ports than there
are dsp processing cards in the system. Check the system for the
recommended configuration.
Unable to add resources %x for line (%d, %d), Error %d
Description: SFA fails to add the resources needed to make up a line port for the slot
Severity: P2
are dsp processing cards in the system. Check the system for the
Unable to add SS7 link to board in slot %d, Error %d
Description: The SS7 ISUP request for an SS7 link failed.

Severity: P2
Unable to alloc ccb to release sim queue

Severity: P1
Unable to allocate memory
Description: System resource problem. May need more memory.

Severity: P2
Action: Run sin info from QNX and contact your Support Representative.
Unable to allocate memory for agent queue
Description: There is not enough memory in the system.

Severity: P1
Action: Confirm the amount of memory left in the system.
Unable to allocate memory of size %d

Severity: P2

Unable to allocate resource %x for line (%d %d) Error %d
Description: SFA fails to allocate a resource needed to make up a line port for the slot
Severity: P2
are dsp processing cards in the system. Check whether the system has the
unable to allocate segment, exit
Description: SFA fails to overlay the linecard memory segment due to a system
resources shortage.
Severity: P1
Unable to allocate SS7 link on board in slot %d, Error %d
Description: The Resource Manager request for an SS7 link failed.

Severity: P2
Unable to attach Proxy for timer
Description: System failure during program startup.

Severity: P1
Unable to attach timer
Description: System failure during program startup.

Severity: P1
Unable to attach name
Description: QNX error or npa admin routine is already running.

Severity: P2
Action: Reboot. If the message reappears, contact your Support Representative.
Unable to attach name
Description: Program cannot attach a name. Most likely to occur on startup.

Severity: P2
Action: As this indicates a problem with the system resources, reset the system.
Unable to attach timer proxy

Severity: P2

Unable to become a server\n

Severity: P2
Unable to clear agent request, code %d
Description: The agent task could not clear a request from the resource manager.
Severity: P2
Unable to config MVIP clock on card %d
Description: Resource manager fails to configure the MVIP clock source of a card.
Severity: P2
configuration.
Unable to configure PCM trunk %d on board %d\n
Description: Resource manager fails to configure the T1/E1 PCM trunk carrier, and the
card will be made unusable.
Severity: P1
Action: Check and verify the hardware configuration. If the problem persists,
Unable to connect SS7 link to board in slot %d, Error %d
Description: The resource manager request for an MVIP connection failed.

Severity: P2
Unable to create timer, errno=%d\n
Description: Resource allocation problem.

Severity: P2
Unable to create timer: %s
Description:
Severity: P4
Action:
Unable to define line (%d %d)
Description: Emulation software fails to initialize the line port specified. The line will be
unusable.
Severity: P2
Action: Try to run an offline configuration and reactivate the configuration. If it still

fails, contact your Support Representative.
Unable to execute application
Description: Error in attempting to start or load executable module.

Severity: P1
Unable to find a pending entry for agent
Description: Resource manager could not find any pending request for its agent.
Severity: P2
Unable to find SS7 integration data for host %d!
Description: The SS7 configuration record and the write_cmds output are in
disagreement.
Severity: P2
Action: Review the SS7 configuration before contacting your Support
Representative.
Unable to find SS7 integration for host %d
Description: The SS7 configuration record and the write_cmds output are in
disagreement.
Severity: P2
Action: Review the SS7 configuration before contacting your Support
Representative.
Unable to get a free agent list entry
Description: Resource manager fails to get a list entry to make a request to its agent.
The system resources are running out.
Severity: P1
Unable to get agent request, code %d
Description: The agent task could not get a request from the resource manager.
Severity: P2
Action: Check if the resource manager is still running. Restart the system if
necessary. If it still fails, contact your Support Representative.
Unable to get hardware info of Card %s on slot%d
Description: Unable to read data from eeprom in the card.

Severity: P1
Action: Possible defect in hardware. Contact your Support Representative.
Unable to get network paths for line (%d %d), Error %d\n

Description: SFA could not get the network path information from the resource manager
for initializing the line. The line port specified will be unusable.
Severity: P2
Unable to get pending entry %d from agent list
Description: Resource manager fails to get a pending entry in the agent list due to a
system resources shortage.
Severity: P2
Unable to get process pid

Severity: P2
Unable to initialize mailbox, resetting card path %d
Description: Failure on startup.

Severity: P1
Unable to load process
Description: Corrupt or missing software module.

Severity: P3
Unable to locate %s
Description: This task is unable to communicate with the specified task.

Severity: P2 j
Unable to obtain linecard segment for line (%d %d)
Description: SFA could not get the linecard memory segment from emulation. A
possible memory shortage exists in the system.
Severity: P1
Unable to open device(%s)
Description: Resource manager fails to find the device. A driver or loader problem may
exist.
Severity: P1
Action: Check if the I/O address and card type in the configuration are correct.
Unable to open device /dev/ag

Description: Resource manager fails to find the device. A driver or loader problem may
exist.
Severity: P1
Action: Check if the I/O address and card type in the configuration are correct.
Unable to open file descriptor to DK driver
Description: The MTP processor driver is not running on this host.

Severity: P2
Unable to put entry %d into agent list
Description: Resource manager fails to put an entry into its agent list.
Severity: P1
Unable to read %d %d record
Description: Unable to read the configuration record. Inband will not be operational.
Severity: P1
Unable to read SS7 configuration record
Severity: P2
Action: Contact your Support Representative., and review the SS7 configuration
entries.
Unable to read oaa record
Description: Could not read a record of the npa database.

Severity: P2
Action: Rerun the RCOS configuration from the menus and check for any missing
data. If all looks okay, this should fix any missing record.
Unable to register name %s
Description: System resource problem.

Severity: P3
Unable to release entry %d from agent list
Description: Resource manager fails to release an entry from its agent list.
Severity: P1
Unable to Reply to agent %d(%s)

Description: Failure in trying to reply to the agent task.
Severity: P2
unable to segment_get:%s
Description: SFA could not access the linecard memory segment due to a system
resources shortage.
Severity: P1
Unable to send to %s
Description: This task is unable to communicate with the specified task.

Severity: P2
Unable to Send to cgrm/resmgr, errno 3
Description: There is not resmgr running.

Severity: P2
Action: Reboot the node or start the resmgr
Unable to Send to resmgr, exit
Description: The agent task could not send a message to the resource manager, exiting.
Severity: P1
Unable to send to undertaker
Description: This message will appear only at startup. If this message stops, then it
indicates a temporary, startup condition.
Severity: P2
Unable to set busy pattern at Card %d SM %d Slot %d
Description: Resource manager fails to send a busy pattern to the card specified.
Severity: P3
Unable to set master MVIP clock on card %d
Description: Resource manager fails to configure a card to be the MVIP clock source.
Severity: P2
configuration.
Unable to set MVIP clock reference on card %d

Description: Resource manager fails to configure a card to be the MVIP clock reference.
Severity: P2
Action: Check and verify the MVIP clock reference and I/O address configuration.
Unable to create a timer id
Description: Unable to create a timer id when attempting to allocate a QNX timer.

Severity: P2
Action:
Unable to set priority pid

Severity: P2
Unable to setup data connection for line (%d %d), Error %d
Description: SFA fails to set up the data path in the linecard for the slot and port number
specified. This port will be unusable.
Severity: P1
Unable to setup signal connection for line (%d %d), Error %d
Description: SFA fails to set up the signaling path in the linecard for the slot and port
number specified. This port will be unusable.
Severity: P1
Unable to spawn agent\n

Severity: P2
Unable to start %s(%s)
Description: Resource manager fails to spawn a device driver. It will disable all the
cards that use this driver.
Severity: P1
Action: Check whether all the optional features have been installed properly.
Unable to start CTI.(CTI may not be installed properly)
Description: Could not find the Smartcard serial port.

Severity: P2
Action: Check the Smartcard configuration and switch setting. Make sure the
hardware is plugged in properly.
Unable to start emul, exit

Description: SFA fails to spawn the emulation software for linecard. Exiting.
Severity: P1
Action: Check whether the software has been installed properly and check for file
corruption. If it still fails, contact your Support Representative.
Unable to start relative timer:%s

Severity: P3
Unable to talk to master, exit
Description: SFA was unable to talk to the master task and thus could not start the
application.
Severity: P1
Unable to talk to Resource Manager, ERROR: %d, exit
Description: SFA was unable to communicate with resource manager, exiting.

Severity: P1
Unassigned cic %d on the UpConInd msg
Description: There is an unassigned circuit identification code on the connection

indicator message.
Severity: P4
Action: A configuration error was made. Re-check the codes configured in the SS7
integration menu. (CIC base.)
Unassigned cic %d in the UpConCfm msg
Description: There is an unassigned circuit identification code in the connection confirm

message.
Severity: P4
Unassigned cic %d in the UpCnStInd msg
Description: There is an unassigned circuit identification code in the user part

connection status indicator message.
Severity: P4
Unassigned cic %d in the UpCpgInd msg
Description: There is an unassigned circuit identification code in the user part call
progress indicator message.

Severity: P4
Unassigned cic %d in the UpRelCfm msg
Description: There is an unassigned circuit identification code in the release confirm

message.
Severity: P4
Unassigned cic %d in the UpRelInd msg
Description: There is an unassigned circuit identification code in the release indicator

message.
Severity: P4
Action: A configuration error was made. Re-check the3 codes configured in the
SS7 integration menu. (CIC base.)
UNDER_AGENT%d: Invalid command received (%d)
Description: under_agent received an invalid command from another task. This is a

software error.
Severity: P2
UNDER_AGENT%d: Relay failed. To %d about %d msg %x ret %x
Description: under_agent could send the death notice. The task could have died. This
may appear when the configuration is activated.
Severity: P2
Action: None.
UNDER_AGENT%d: Send to master failed
Description: under_agent could not find undertaker. This is a software error.

Severity: P2
UNDERTAKER%d: Exiting
Description: undertaker received a terminate request. This is not an error.

Severity: P4
Action: None.
UNDERTAKER%d: Unable to attach name \%s
Description: undertaker could not attach name. This is a software error.

Severity: P2

UNDERTAKER%d: Unable to launch under_agent
Description: undertaker could not start the under_agent task. This is a software error.
Severity: P2
UNDERTAKER: out of list space
Description: undertaker queue is full. This is a software error.

Severity: P2
Unexpected event %d from state %s on ckt %d\n
Description: The SS7 state machine was not expecting the specified event in the
specified state.
Severity: P3
Unexpected Message: %s
Description: Program interface or system error.

Severity: P3
Unexpected WPC Message%d
Description: Program interface or system error.

Severity: P1
Unknown agent request %d
Description: The agent task gets an unknown request type from the resource manager.
Severity: P2
Unknown case (1) in ntl_blk_rcvd. Link no: %d Node state: %d
Description: A contact to get_node_state returned a value outside the legal range

(connected, connecting, disconnecting, or idle).
Severity: P2
Unknown case (2) in ntl_blk_rcvd. Request: %d Link no: %d
Description: The pkt - 13_nreg state must be Node_Connect, Node_Disconnect, or

Node_MSG. The value stored in pkt - 13nreg falls outside of this range
Severity: P2

Unknown case in dispatch_ntrcv. Link state: %d
Description: A contact to get_link_state returned an out-of-boards value. Possibly a

corrupted get_link, state table or bad link number exists.
Severity: P2
Unknown case in do_link_setup. CS state: %d
Description: The contact_setup state table has eight valid states. A contact to
ge_cs_state returned a value equal to none of these states.
Severity: P2
Unknown case in do_link_start. Link start state: %d
Description: The starting state table has two valid states. A contact to
get_link_start_state returned a value equal to neither of these states.
Severity: P2
Unknown case in ntl_blk_sent. Node message: %d Link no: %d
Description: The pkt - ntl_node_msg state must be Node_Connect, Node_Disconnect,

or Node_MSG. The value stored in pkt - ntl_node_msg falls outside of this
range.
Severity: P2
Unknown case in ntl_connect. Node state: %d

Severity: P2
Unknown case in ntl_disconnect. Node state: %d

Severity: P2
Unknown case in nts_in. Header class: %d
Description: Decoding of message type from NTSND failed.

Severity: P2
Unknown inform type %d
Description: The agent task gets an unknown inform request type from the resource

manager.
Severity: P2
Unknown message for shutdisk %02x
Description: System error or program interface error.

Severity: P3
Unknown NUP message on the network on cic %d
Description: An unknown NUP message has been received on the network on the circuit
identification code.
Severity: P4
Action: Note the error, and report to your next level of support.
UNLOCKR: cannot malloc iobuf
Description: System has run out of resources. As unlockr runs at midnight, this is the
only time you should see this message.
Severity: P3
Action: Check the amount of memory available by doing a sin info. Contact your
Unknown RAM return code %d for request %s

Severity: P4
Unknown type of status indication, status:%d, id=%d
Description: Informational error to notify of an unknown type of status indication.

Severity: P4
Action:
UNLOCKR: cannot get sam tid
Description: sam died when unlockr was started. unlockr was unable to run.
Severity: P4
Action: None.
UNLOCKR: send to sam failed: %d
Description: sam died when unlockr was started. unlockr was unable to run.
Severity: P4
Action: None.
UPDATEOAA: can't read CTITABLE_REC(%d): %d

Description: Either oaa is not running, or the cti record is missing.
Severity: P2
Action: Reconfigure using the offline menu. If the problem persists, contact your
update_rcpt: aclose failed, rslt = %d
Description: aclose failed because the account is corrupt or OAA died.

Severity: P3
Action: If the system is still running, no action needed, as the corruption checker
does not allow accounts corrupted in memory to be written to disk. If oaa is
really dead, the system will reset on its own.
update_rcpt: bad msg index = %d
Description: The message is out of range (<0 or >73).

Severity: P3
Action: Run a verify to check for any corruption on the hard disk. If all is OK, then
the memory was corrupted. If the problem persists, contact your Support
Representative.
update_rcpt: ms sender not copylist %s
Description: A corrupt receipt exists on the system.

Severity: P3
Action: Run a verify to clean up any corruption. Contact your Support
Unassigned cic %d in the UpRelCfm msg
Description: There is an unassigned circuit identification code in the release confirm

message.
Severity: P5
Action:
UpMaintCfm cic_mask 0x%08x gid %d does not match with any lines
Description: User part status indication. Referring to the UpMaintCfm (user part
maintenance confirmation) function cic_mask, which is the bit mask for
effected circuits, the group id, which is used to communicate with the user
part, that does not match with any lines.
Severity: P4
Action: This is a probable configuration error. Check the configuration for the CIC
base in the SS7 integration menu.
UpMaintCfm gets an unknown event type %d
Description: Informational error to indicate that the user part maintenance confirmation
message gets an unknown event type.
Severity: P4
Action:

Unsupported TUP message from the network on cic: %d
Description: An unsupported TUP message has been received from the network on this
circuit identification code.
Severity: P4
Action:
Variables
Note: The following error messages start with the symbols “%s,” “%d,” and “[%.” These
messages do not contain a specific value or string associated with the variable. They
should be read as though the symbol(s) do not exist. Locate the error message by
referring to the first word that appears after the variable string.
%s: Bad character in dial string: %c
Description: An invalid digit got into a dial string. This can be caused by poor integrity
checking by a console routine or by data corruption.
Severity: P3
Action: Contact your Support Representative, and identify the character.
%s Bad data type %s (host %d), Func = %s, Tag = %s
Description:
Severity: P2
Action:
%s: Bad RCOS %d
Description: An out-of -range error for RCOS value. Indicates the existence of a
software bug.
Severity: P3
%scannot attach name<%s>
Description: The Vmemo system could not attach its name for one contact applications.
Severity: P2
Action: The one contact application will not work. Check system resources by
doing sin info and contact your Support Representative.
%s: Can't attach \%s\ on node %u, program, taskname,

node_for_attach
Description: NP View could not 'attach' the program and task listed.
Severity: P1
Action: Verify the program name is valid and the program is still running. Note the
taskname and node number and contact your Support Representative.
%s can't read oaa data!

Description: System failed to read the configuration record. The program will terminate.
Severity: P2
%s can't read oaa data!\n
Description:
Severity: P2
Action:
%s: Could not send to %s, aborting
Description: Some or all of the routines for npa are not running.
Severity: P2
Action: Check the log file for task deaths, and contact your Support Representative.
Then reboot to clear this condition.
%s Could not spawn oaa_agent, abort
Description: The system was unable to find the oaa agent.

Severity: P1
%s Could not spawn relay agent, abort
Description: The system was unable to run the agent task.

Severity: P1
%s: creatl error (%d)
Description: System cannot perform the basic administration jobs, or get status from the
other processes.
Severity: P1
%s %d: creatl error (%x)
Description: An error invoking the tnppsnd task occurred. System resources may be
running out.
Severity: P2
Action: Check the system resources. (i.e., memory)
%s: Error in reading contact info from device
Description: An error in reading contact info from the serial port occurred. Will try to
reset the integration set 244PC.
Severity: P2
%s: Error reading configuration., program

Description: NP View could not read its configuration file.
Severity: P1
Action: Check that the configuration file is in usr/vm/config. Run CM_CONFIG to
create another configuration file.
%s: Error in reading contact info from device
Description: An error in reading contact info from the serial port occurred.
Severity: P2
%s: Error while starting allocator, exiting.
Description: The module is unable to start critical task.

Severity: P3
%s: fast_poll2 send hangup to admin
Description:
Severity:
Action:
%sget input's count <%d>
Description: Requested time-out on keystrokes by one contact application was more

than allowed. A limit of five seconds as used as the maximum.
Severity: P4
Action: Contact the author of the application.
%sget input's count <%d>
Description: User input less digits than the one contact application asked for.
Severity: P4
%sget input's timeout <%d>
Description: Requested time-out on keystrokes by one contact application was more

than allowed. A limit of five seconds is used as the maximum.
Severity: P4
%sget input's timeout <%d>
Description: This is for a one contact application and indicates the one contact
application did not respond to the Nynex task within the allotted time.
Severity: P4
%d:%d invalid handle (%d)

Description: At the fax application startup, the H:S:P: specified is not a fax HW.
Severity: P3
Action: Check the fax configuration.
%d:%d invalid handle(%d)
Description: The program received a bad parameter for the slot number and port
number, resulting in an invalid handle. The program will terminate.
Severity: P2
Action: Make sure the offline configuration has been invoked after the hardware
resource configuration is changed.
Description: The line handle manager does not recognize the triplet as valid.
Severity: P2
Action: Reconfigure the system from resmgr, to the offline menu, activate cfg, and
try again.
Description: The application running on slot:port has an invalid handle.

Severity: P2
Action: Redo the offline configuration and activate the new configuration.
%s: Invalid msg_type in message to SL1MP_ADMIN.
Description: This is an unknown request message. This is a software error. 5/13/98

The request is ignored.
Severity: P3
%s: Invalid request, %d, program, req_p->func_code
Description: NP View received a request to process a function not supported from the
program 'program'.
Severity: P1
Action: Verify the program name is valid and the program is still running. Note the
function code returned and contact your Support Representative.
%s no line
Description: The application could not attach to the port.

Severity: P2
Action: Check the offline configuration and make sure the line does exist. Contact
your Support Representative if the configuration looks OK.
%s: network query during resolution failed, retrying
Description: A system error occurred when communicating to other modules in the

network.

Severity: P4
Action: None.
[%d:%d:%d] pager_mailbox cannot send voice msg
Description: A voice pager mailbox cannot send a recorded voice message to sendvm
for delivery. The message is consequently lost.
Severity: P3
Action: Try to place another contact on the voice pager mailbox. If the problem
%s: Queue full, request lost
Description: The npa admin routine could not keep up with the requests coming in.
Severity: P2
Action: If this message appears more than once, contact your Support
Representative.
%s: Rebooting. '%.30s' died too many times
Description: Multiple failures for critical system task occurred.

Severity: P2
%s: receive failed
Description: An error in receiving a message occurred.

Severity: P1
%s<%s> receive timeout after <%d> seconds
Description: This is a time-out condition for vmemo. It will wait only so long on a one
contact application.
Severity: P3
Action: Possible problem with the one contact application. Contact the writer of
your one contact application.
%s: Reply to %d failed., program, pid
Description:
Description: NP View sent a message to the program 'program' with the program ID pid,
without success.
Severity: P1
Action: Verify that the program name is valid and the program is still running. If not,
try to restart the program. If the problem persists, either reboot or contact
%s: SCSI UP & QNET failure, rebooting
Description: A network problem in cabling or interface card exists.

Severity: P2
%d]%d: send to sfa failed
Description: The speech file service is not available or accessible.

Severity: P3
Action: Reboot.
[%d]%d: sfopen for read failed
Description: The speech file system is not responding properly .

Severity: P3
Action: Reboot.
[%d]%d: sfopen for write failed
Description: The speech file system is not responding properly.

Severity: P3
Action: Reboot.
%s: spawn error = %d, link %s, %s.
Description: System cannot spawn a task. This is a software error.

Severity: P1
%s: Too many restarts (%d) for allocator, exiting.
Description: The system is unreliable and unable to operate NuPoint Voice.

Severity: P3
%s: *** Unable to attach name (%s), module #: %d!
Description:
Severity: P1
Action:
%s: Unable to attach timer proxy %d
Description: Rolm failed to attach a timer proxy from OS. Roladmin dies because a
timer is needed for synchronization.
Severity: P1
Action: Restart rolmadmin by rebooting the system. If the problem still exists, try
reloading rolm extra-cost diskette. Rolmadmin may have been corrupted.
If problems persist, contact your Support Representative.
%s: UNABLE to disable myself. Rebooting.
Description: Problem encountered in attempt to configure module as inactive.

Severity: P4
Action: None.
%s: Unable to get stty on RS232 port
Description:
Severity: P2
Action:
%s: Unable to open serial port
Description:
Severity: P2
Action:
%s: Unable to read OAA record.
Description:
Severity: P2
Action:
%s: Unable to read OAA record.
Description: System failed to read the configuration record. The program will terminate.
Severity: P2
%s: Unable to read oaa record.
Description:
Severity: P2
Action:
%s: unable to read oaa record!
Description: System failed to read the configuration record. The I/O task will terminate
and a new one will be started.
Severity: P1
%s: Unable to send to rolmadmin
Description: An error in sending a message to admin task occurred. This is a software

error. The I/O task will terminate and a new one will be started.
Severity: P2
Action: Problem might rectify itself. If not, check the system resources, such as
memory. If these resources are OK, reactivate the software from the
configuration menu or reboot. This will restart the tasks. If the problem
persists, reload the software as rolmadmin may have been corrupted.
%s: Unable to send to SL1MP_ADMIN

Description: An error in sending a message to admin task occurred. This is a software
error. The I/O task will terminate and a new one will be started.
Severity: P2
Action: Problem might rectify itself. If not, check the system resources, such as
memory. If these resources are OK, reactivate the software from the
configuration menu or reboot. This will restart rolm tasks. If the problem
persists, reload the software as rolmutil1 may have been corrupted.
%s: Unable to send to SMSMWI_ADM
Description:
Severity: P2
Action:
%s: Unable to SET stty on RS232 port
Description:
Severity: P2
Action:
%s: **** unknown record error(%d)\n
Description: A one contact application was recording speech and received an error.
Severity: P4
Action: Contact the writer of the one contact application.
%s: **** unknown record error(%d)\n
Description: An error occurred from sfa while recording a message.

Severity: P2
Action: Check statistics to make sure speech is not full. Contact your Support
Representative.
%s: wait_pkup send hang up to admin.
Description: The contacter hangs up while the integration is collecting data from the
PBX.
Severity: P5
Description:
%s<%s> vmvg task not ready after <%d> seconds
Description: This is a time-out condition for vmemo. It will wait only so long on a one
contact application.
Severity: P4
Action: Possible problem with the one contact appplication. Contact the writer of
your one contact application.

Error Log Manual: Mitel Nupoint Messenger Technical Documentation - Release 7.0

Uploaded by

Copyright:

Available Formats

You might also like

Error Log Manual: Mitel Nupoint Messenger Technical Documentation - Release 7.0

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

Error Log Manual: Mitel Nupoint Messenger Technical Documentation - Release 7.0

Uploaded by

Copyright:

Available Formats

Mitel NuPoint Messenger Technical Documentation - Release 7.

Error Log Manual

P.O. Box 1899

©Copyright 2002, Mitel Networks Corporation 1

About This Manual

©Copyright 2002, Mitel Networks Corporation 2

*** DBN: scan died

*** DBN: send to scan failed

*** DTA_AGENT: Unable to attach name!

Description: An attempt to register the DTA_AGENT process failed.

*** DTA: Unable to attach name!

Description: An attempt to register the DTA process failed.

*** GL_QUE: Another GL_QUE is running in the system, Abort

Description: An internal error exists.

*** GL_QUE: can not register with master

©Copyright 2002, Mitel Networks Corporation 3

*** GL_QUE: invalid queue index %d

Description: An internal error exists.

*** GL_QUE: no memory available for global queues, abort

Description: The system is out of memory.

*** GL_QUE: res %d GL_SB %d differ

Description: An internal error exists.

HOLD queue is full. Reqs will be discarded.

Description: There is a problem manipulating the request queue.

*** NETQ: Unable to attach name!

Description: An attempt to register the NETQ process failed.

*** NETQ_AGENT: Unable to attach name!

Description: An attempt to find the named process used to establish communication

*** NTA_AGENT: Unable to attach name!

Description: An attempt to register the NTA_AGENT process failed.

*** QUE_RELAY: invalid queue index %d

Description: An internal error exists.

©Copyright 2002, Mitel Networks Corporation 4

*** QUE_RELAY: Out of queue %d space

Description: An internal error exists.

*** QUE_RL: rl_agent died, commit suicide

Description: An internal error exists.

*** RAM ***: could not register to master, abort

Description: An internal error exists.

*** ram at Node %d: Out of queue %d space

Description: An internal error exists.

*** RAM: agent is dead, commit suicide

*** RAM: Another ram is running in the system, Abort

Description: An internal error exists.

*** RAM: Could not attach RAM PORT %d, abort

Description: An internal error exists.

*** RAM: Could not spawn ram_agent, abort

Description: Ram is unable to start up agent task.

©Copyright 2002, Mitel Networks Corporation 5

*** RAM: get a unknown result %d

Description: An internal error exists.

*** RAM: No memory for directory buffer

Description: There is a shortage of memory within the system.

*** RAM: record %s

Description: An internal error exists.

*** RAM: relay to standby failed due to broken vc -1

Description: This message pertains to internal information keeping.

*** RAM: req %d, node %d, tid %04X

* RAM *: could not register to master, abort