NEC Ucd-Xl Installation Guide

							NDA-30078   Revision 1.0Page 59
UCD-XL Installation Guide Error Messages
8. Too many Messengers! Terminating.
During an attempt to start a Messenger, the absolute limit of 10 running Mes-
senger applications was exceeded. This Messenger is terminated, but the others
are not affected.
9. Unable to check tenant  number 
The Messenger was unable to check the status of the specified extension in the
PBX. Possible reasons include: (1) the port is not defined in the PBX; (2) the
PBX is slow or unable to respond via OAI.
10. Failed to connect to announcement message 
The Messenger was unable to connect a call to the announcement package as-
sociated with the specified announcement message number. Possible reasons
include: (1) maximum of 8 callers are already connected (limitation of the
PBX); (2) the announcement message is being played for other callers; (3) the
caller has released. This error message does not identify the caller.
11. Failed to connect to extension 
The Messenger was unable to connect a call to the specified extension in the
PBX. Possible reasons include: (1) the port is not idle; (2) the caller has re-
leased. This error message does not identify the caller. 
						

							Page 60NDA-30078   Revision 1.0
Error Messages UCD-XL Installation Guide
Error Messages from UCD-XL Mediator
The following are the error messages from the UCD-XL Mediator which you might 
encounter in the APM log and/or on the APM screen.  Immediately following each 
error message is a brief explanation and a possible solution to the problem.
Note:
“UDP” means User-defined Parameter.
1. Invalid option: 
The given input is not an acceptable option for UDP #2 -- MCI message set.
Refer to the Mediator User-defined Parameters section on 
page 38 for a list of
valid options for this parameter.
2. Incomplete characteristics for port 
UDPs #3 and #4 must define 5 characteristics of the PBX and VMS ports -- de-
vice name, baud rate, parity, data bits, and stop bits -- each separated by a
space. If any of these values are missing, this error message is displayed. Refer
to the Mediator User-defined Parameters section on 
page 38 for further infor-
mation.
3. Device unknown or inaccessible: /dev/
The specified device name does not exist in the UNIX system or cannot be ac-
cessed by the Mediator. Check the list of UNIX devices under /dev and modify
UDP #3 or #4 accordingly. Also, as superuser, check the ownership and per-
missions of the desired device file. It should either be owned by “apm” or have
“rw” permission for the world (other). 
4. Invalid baud rate: 
The specified baud rate (bits per second) in UDP #3 or #4 is wrong. Acceptable
values for baud rate are 1200, 2400, 4800, 9600, and 19200. 
5. Invalid parity: 
The specified parity type in UDP #3 or #4 is wrong. Acceptable values for par-
ity type are “none”, “even”, and “odd”. 
6. Invalid # of data/stop bits: /
The specified quantity of data bits or stop bits in UDP #3 or #4 is wrong. Ac-
ceptable values for data bits are 7 and 8. Acceptable values for stop bits are 1
and 2.
7. Error while opening device /dev/:  (open)
Error while opening device /dev/:  (ioctl)
The Mediator could not open or set characteristics of the specified device due
to a UNIX system error (errno) or device driver error. As superuser, check the
ownership and permissions of the desired device file. It should either be owned
by “apm” or have “rw” permission for the world (other). Terminate the Medi-
ator and restart. If the problem persists, contact your NEC distributor or an
NEC representative. 
						

							NDA-30078   Revision 1.0Page 61
UCD-XL Installation Guide Error Messages
8. Unable to spawn Reader for PBX
Unable to spawn Reader for VMS
The Mediator could not start a Reader program (child process) for reading MCI
messages from the specified source (PBX or VMS). Verify that UDP #5 con-
tains the correct filename of the Reader as described in the Mediator User-de-
fined Parameters section on 
page 38. Terminate the Mediator and restart. If the
problem persists, contact your NEC distributor or an NEC representative.
9. Detected death of Reader for PBX (errno )
Detected death of Reader for PBX (signal )
Detected death of Reader for VMS (errno )
Detected death of Reader for VMS (signal )
One of the two Reader processes terminated unexpectedly due to a UNIX sys-
tem error (errno) or the receipt of a UNIX signal (signum). Terminate the Me-
diator and restart. If the problem persists, contact your NEC distributor or an
NEC representative. 
10. Unable to send message  -- apmsend error  
(errno = )
The Mediator could not send a message to the Monitor. Verify that the Monitor
is an active application under the APM and is specified in UDP #6. Terminate
the Mediator and restart. If necessary, also terminate the Monitor and restart
both. If the problem persists, contact your NEC distributor or an NEC repre-
sentative.
Note:
 identifies a UCD-XL specific message;  is an error code 
that originates from the APM; and  originates from UNIX.
11. Error while writing MCI port for PBX: 
The Mediator could not send an MCI message to the PBX due to a UNIX sys-
tem error (errno).  As superuser, check the ownership and permissions of the
device file for the MCI port for the PBX. It should either be owned by “apm”
or have “rw” permission for the world (other). Terminate the Mediator and re-
start. If the problem persists, contact your NEC distributor or an NEC represen-
tative. 
12. Error while writing MCI port for VMS: 
The Mediator could not send an MCI message to the VMS due to a UNIX sys-
tem error (errno). As superuser, check the ownership and permissions of the de-
vice file for the MCI port for the VMS. It should either be owned by “apm” or
have “rw” permission for the world (other). Terminate the Mediator and restart.
If the problem persists, contact your NEC distributor or an NEC representative.
organizing
13. Invalid office code length. Maximum size is 4.
UDP #7, if not blank, must specify a value from 0 to 4 that represents the length
of an office code assigned to the PBX. 
						

							Page 62NDA-30078   Revision 1.0
Error Messages UCD-XL Installation Guide
Error Messages from UCD-XL Administrator
The following are the error messages from the UCD-XL Administrator which you 
might encounter in the APM log and/or on the APM screen. Immediately following 
each error message is a brief explanation and a possible solution to the problem.
Note 1:
 is the UNIX error code.
Note 2:
“UDP” means User-defined Parameter.
1. Unable to access terminal  (errno ).
The specified device name does not exist in the UNIX system or cannot be ac-
cessed by the Administrator. Check the list of UNIX devices under /dev and
modify UDP #2. Also, as superuser, check the ownership and permissions of
the device file. It should either be owned by “apm” or have “rw” permission for
the world (other).
2. Unable to receive a message - error  (errno ).
The Administrator could not receive a message due to an APM or UNIX sys-
tem error. Contact your NEC distributor or an NEC representative.
3. No memory available.
The UNIX system was unable to allocate sufficient memory to satisfy the ap-
plication’s requirements. Additional RAM may be needed. Contact your NEC
distributor or an NEC representative.
4. Cannot open Group Identification Database. (errno )
Verify that the Group Identification Database named 
ucdgrps_m exists by se-
lecting the “Build Master Database” option under the APM’s Database Admin-
istration Menu. If it does exist, use the “Process Application Database” and
“Install Application Database” options in order to process and install the data-
base. If not, create 
ucdgrps_m by following the instructions in the Database Re-
quirements section on page 41. Also verify that UCD-XL Administrator’s UDP
#7 is correct via the APM’s Application Configuration Menu (see page 40).
5. Cannot open ANI Pattern Database. (errno )
Verify that the ANI Pattern Database named 
ucdani_m exists by selecting the
“Build Master Database” option under the APM’s Database Administration
Menu. If it does exist, use the “Process Application Database” and “Install Ap-
plication Database” options in order to process and install the database. If not,
create 
ucdani_m by following the instructions in the Database Requirements
section on page 41. Also verify that UCD-XL Administrator’s UDP #10 is cor-
rect via the APM’s Application Configuration Menu (see page 40). 
						

							NDA-30078   Revision 1.0Page 63
UCD-XL Installation Guide Error Messages
Informational Messages from UCD-XL
The following are the informational messages you might encounter when running 
UCD-XL.  Immediately following each message is a brief explanation.
Note:
“UDP” means User-defined Parameter.
 calls are currently queued.
This message from the Monitor may appear after an inspection of all ports in a
group. It specifies the quantity of incoming calls waiting to be connected to a port
as the inspection concludes.
Caller has abandoned. Freeing port . 
This message from the Monitor is displayed to explain certain SCF errors that may
occur during an attempt to connect a call to the specified port. (Also see Messenger
error #11 on page A-6.) In this case, the caller has apparently abandoned before the
connection could be completed. As a result, the specified port is considered free
again.
Caught termination signal.
This message indicates that the Monitor did receive the signal to terminate from the
APM.
Communicating with Mediator again.
This message from the Monitor indicates that Monitor has re-established commu-
nication with the Mediator, allowing it to again provide information about connect-
ed calls so that the Mediator can inform the VMS via MCI.
DANGER! All request bins utilized. Need more shared memory.
This message from the Monitor is a warning that the UCD-XL system is overload-
ed. More request bins are needed in order to satisfy the influx of UCD calls. With-
out available bins, the Monitor and Messengers cannot promptly connect calls to
the ports or inspect those ports. If this message appears, it is strongly recommended
that the number of request bins (UDP #7) be increased by 10 or more in Monitors
configuration. The application must be terminated first.
DANGER! Disk is full. Unable to save statistics for . 
The Reporter issues this message when there is no more space available in the /oai
filesystem for the growth of the statistics file. The statistics from the concluding
collection period for the specified group are not saved. You should erase obsolete
statistics via UCD-XL Administrator immediately.
DANGER! Disk is nearly full. Will not save statistics for . 
The Reporter issues this message when there is 2% or less space available in the /
oai filesystem for the growth of the statistics file. The statistics from the concluding
collection period for the specified group are not saved. You should erase obsolete
statistics via UCD-XL Administrator immediately. 
						

							Page 64NDA-30078   Revision 1.0
Error Messages UCD-XL Installation Guide
Database update completed.
This message from the Monitor concludes an update (reloading) of one of UCD-
XL’s databases. Such an update occurs when the APM Administrator installs the
database while the Monitor is running.
Group ():ports.
Once the Group Identification Database and Port Assignment Database are loaded,
this message from the Monitor displays to show the quantity of ports associated
with each group.
Halting Messengers.
Prior to termination, the Monitor displays this message when it tells the APM to
terminate all Messengers.
Initialization failed - terminating.
A significant error has occurred during initialization, preventing the Monitor from
proceeding. The APM logfile contains a specific message about the error. See “Er-
ror Messages from UCD-XL Monitor” on page 51.
Keeping original ANI Database.
This message from the Monitor will appear if, during a reloading of the ANI Pat-
tern Database, there is an error in the data of one of the records. The original set of
database records is restored as the application abruptly concludes the update pro-
cedure.
Keeping original Group Database.
This message from the Monitor will appear if, during a reloading of the Group
Identification Database, there is an error in the data of one of the records. The orig-
inal set of database records is restored as the application abruptly concludes the up-
date procedure.
Keeping original Port Database.
This message from the Monitor will appear if, during a reloading of the Port As-
signment Database, there is an error in the data of one of the records. The original
set of database records is restored as the application abruptly concludes the update
procedure.
Loading ANI patterns ...
This message from the Monitor indicates that, during initialization, the Monitor is
loading the ANI Pattern Database into memory. There may be a noticeable delay
while this action occurs.
Loading groups and ports...
This message from the Monitor indicates that, during initialization, the Monitor is
loading the Group Identification Database and Port Assignment Database into
memory. There may be a noticeable delay while this action occurs. 
						

							NDA-30078   Revision 1.0Page 65
UCD-XL Installation Guide Error Messages
Logged stats for . 
The Reporter issues this message after saving on disk the statistics from the con-
cluding collection period for the specified group.
Lost OAI communication. Now PASSIVE.
This message from the Monitor indicates that the Monitor has entered the passive
state because it cannot communicate with the PBX any more. In this state, no calls
can be processed, but the Monitor repeatedly attempts to re-establish the OAI link
in order to become active again. The application may be terminated if desired.
Port  busy. Connecting caller to .
Port  busy. Putting caller on a queue.
The Monitor issues one of these two messages if the Monitor has failed to connect
a call to the specified port (extn1) because it was unexpectedly busy. The first mes-
sage indicates that the call is being redirected to another available port (extn2). The
second message indicates that no other ports are free so the call is being held in a
queue (perhaps hearing an announcement message). These messages do not iden-
tify the caller.
Port  locked out. Connecting caller to .
Port  locked out. Putting caller on a queue.
The Monitor issues one of these two messages if the Monitor has failed to connect
a call to the specified port (extn1) because it was unexpectedly locked out. The first
message indicates that the call is being redirected to another available port (extn2).
The second message indicates that no other ports are free so the call is being held
in a queue (perhaps hearing an announcement message). These messages do not
identify the caller.
Port inspection aborted for group .
This message from the Monitor indicates that the Monitor has aborted an inspec-
tion of the specified group due to an OAI error. It has scheduled another inspection
for that group, however, according to the interval stated in the corresponding record
of the Group Identification Database.
Port inspection begins for group .
This message from the Monitor indicates that the Monitor has started an inspection
of the specified group’s ports, as assigned in the Port Assignment Databse.
Port inspection ends for group .
This message from the Monitor indicates that the Monitor has concluded an inspec-
tion of the specified group’s ports.
Processing error. Freeing port .
This message from the Monitor is displayed to explain certain SCF errors that may
occur during an attempt to connect a call to the specified port. (Also see Messenger
error #11 on page 59.) In this case, UCD-XL has provided the PBX with incorrect
data to identify the call. As a result, the caller (hearing ringing) remains attached to
the monitored number indefinitely, while the specified port is considered free
again. If this error occurs repeatedly, contact your NEC distributor or an NEC rep-
resentative. 
						

							Page 66NDA-30078   Revision 1.0
Error Messages UCD-XL Installation Guide
Ready for MCI communication.
This message from the Mediator indicates that the Mediator is ready to receive
MCI messages from the PBX or VMS and pass them to the other system. It will
also convert information about incoming calls from the Monitor into MCI messag-
es (“J” records) and send them to the VMS.
Ready for requests.
This message from the Messenger indicates that the Messenger is ready to process
requests from the Monitor for performing OAI functions, specifically the connec-
tion of a call to a VMS port and the determination of the status of a port. These re-
quests are read from request bins in shared memory.
Ready to log statistics and/or trace. 
This message indicates that the Reporter process, spawned by the Monitor, is alive
and ready to perform its duties. The Reporter is needed for the preservation of sta-
tistics and trace data on the hard disk.
Reloading the ANI Database.
If the APM Administrator has processed and installed the ANI Pattern Database
while the Monitor is running, the application displays this message. There may be
a noticeable delay while the Monitor loads the database into memory. During this
time, no calls can be processed.
Reloading the Group Database.
If the APM Administrator has processed and installed the Group Identification Da-
tabase while the Monitor is running, the application displays this message. There
may be a noticeable delay while the Monitor loads the database into memory. Dur-
ing this time, no calls can be processed.
Reloading the Port Database.
If the APM Administrator has processed and installed the Port Assignment Data-
base while the Monitor is running, the application displays this message. There
may be a noticeable delay while the Monitor loads the database into memory. Dur-
ing this time, no calls can be processed.
Request bins are at normal level of usage.
This message indicates that the burst of call traffic has subsided sufficiently to re-
duce Monitors usage of request bins to below 75%. If this message does not occur
soon after a “75% used” warning (see below), it is recommended that the number
of request bins (UDP #7) be increased by 5 or more in Monitors configuration. The
application must be terminated first.
SHUTDOWN in progress.
This message from the Monitor indicates that the Monitor has entered the shut-
down state because the APM has signaled termination or all Messengers have ter-
minated. The Monitor will wait for running Messengers to complete call
connections to ports, but no new calls will be processed since the application stops
monitoring all pilot numbers. No further port inspections will occur, either.
Statistics collection begins. 
						

							NDA-30078   Revision 1.0Page 67
UCD-XL Installation Guide Error Messages
This message from the Monitor indicates that the Monitor, in conjunction with the
Reporter process, has begun to compile statistics about the call activity that has oc-
curred during the current collection period (an hour or a day). It appends the data
to a file on disk (named /oai/app/data/ucdxl/ucdstats) so that the Administrator
may generate reports. During collection, the Monitor is unable to process any calls.
Statistics collection ends.
This message from the Monitor indicates that the Monitor has concluded the task
of compiling call statistics. (The Reporter may still be updating the statistics file,
though.) A new collection period commences.
Stopped monitoring groups.
This message indicates that the Monitor has informed the PBX to cease monitoring
of the pilot numbers for every group in the Group Identification Database.
Stopped monitoring ports.
This message indicates that the Monitor has informed the PBX to cease monitoring
of every extension in the Port Assignment Database.
UCD processing commences. ACTIVE.
This message from the Monitor indicates that the Monitor has entered the active
state. It is able to process any calls placed to the pilot numbers of UCD-XL groups.
Port inspections and statistics collections are also performed periodically, based
upon the Monitors configuration.
Waiting for a Messenger. STAND-BY.
This message from the Monitor indicates that the Monitor has entered the stand-by
state. It waits either for a Messenger to initialize or for the APM to signal termina-
tion. No incoming calls are processed, and no port inspections are performed.
Waiting for completion of outstanding requests.
During shutdown, this message from the Monitor appears if the Monitor needs to
wait for one or more Messengers to complete their tasks -- connecting a call to a
port or determining the status of a port. If a problem has occurred, the Monitor may
remain in this state until the APM recognizes it as a hung application and termi-
nates it. If this situation occurs repeatedly, contact your NEC distributor or an NEC
representative.
Waiting for Monitor...
This message from the Messenger indicates that the Messenger is waiting for the
Monitor to establish an OAI association after being initialized by the APM. The
Messenger cannot perform any tasks while in this state. 
						

							Page 68NDA-30078   Revision 1.0
Error Messages UCD-XL Installation Guide
WARNING! 75% of request bins are used.
This message from the Monitor indicates that a burst of call traffic has caused the
Monitor to use 75% or more of the request bins in shared memory. If this message
occurs frequently, it is recommended that the number of request bins (UDP #7) be
increased by 5 or more in Monitors configuration. The application must be termi-
nated first.
WARNING! 90% of request bins are used.
This message from the Monitor indicates that a burst of call traffic has caused the
Monitor to use 90% or more of the request bins in shared memory. If this message
occurs, it is recommended that the number of request bins (UDP #7) be increased
by 5 or more in Monitors configuration. The application must be terminated first.
WARNING! Disk is 75% full. Please erase old statistics. 
The Reporter issues this message when there is 25% or less space available in the
/oai filesystem for the growth of the statistics file. Although the statistics from the
concluding collection period for the specified group are saved, it is recommended
that you erase obsolete statistics via UCD-XL Administrator immediately.