NEC Ucd-Xl User Guide

							NDA-24169   Revision 2.0Page 25
UCD - XL User Guide Administration
Stop TraceThis command terminates the trace of incoming calls. The contents of the trace file 
can be viewed (using the View Trace command) until the UCD-XL Administrator 
is terminated, or until another trace is initiated.  Anytime a trace is initiated, it 
overwrites the previous trace file, destroying it.
Procedure
1. Select Stop Trace from the Trace Functions menu.
The TRACE ON message is removed from the bottom of the screen.
2. UCD-XL returns to the Trace Functions menu.
Note:
The Administrator cannot stop the trace if UCD-XL Monitor has been ter-
minated. Once Monitor has been restarted, you must reissue the command 
to stop the trace before you can initiate a new one.
End of procedure.
View TraceNote:
The View Trace command executes an OAI utility called viewa.
At any time during or after a trace, you may view the results, as shown in Figure 2-
11. You should use the AutoScroll subcommand to observe an active trace. The 
TRACE ON message, or any other information in the status window, is not 
displayed while the trace is viewed.
Figure 2-11   View of a Trace
UCD-XL TraceFri Dec 31 11:58
Search Top Command AutoScroll QuitBottom
Beginning of Data
Wed Dec 01 07:12 1995 Extn  2604 INCOMING  to  3991
Wed Dec 01 07:12 1995 Rt 15 Tk 3 INCOMING  to  3995
Wed Dec 01 07:12 1995 Extn  2604 CONNECTED to  3002
Wed Dec 01 07:13 1995 Rt 15 Tk 3 CONNECTED to  3347
Wed Dec 01 07:17 1995 Extn  2559 INCOMING  to  3995 by 2645 FORWD
Wed Dec 01 07:17 1995 Extn  2559 QUEUED
Wed Dec 01 07:20 1995 Rt 14 Tk 1 INCOMING  to  3991 by 2620 BUSY
Wed Dec 01 07:20 1995 Rt 14 Tk 1 CONNECTED to  3003
Wed Dec 01 07:21 1995 Extn  2688 INCOMING  to  3995 by 2633 NOANS
Wed Dec 01 07:22 1995 Extn  2617 INCOMING  to  3991
Wed Dec 01 07:22 1995 Extn  2604 RELEASED 
Wed Dec 01 07:23 1995 Extn  2617 CONNECTED to  3004
Wed Dec 01 07:27 1995 Rt 14 Tk 1 RELEASED from 3003
Wed Dec 01 07:30 1995 Rt 15 Tk 2 INCOMING  to  3991 by Att 3 XFER
End of Data Wed Dec 01 07:21 1995 Extn  2688 QUEUED
Wed Dec 01 07:28 1995 Extn  2559 ABANDONED 
						

							Page 26NDA-24169   Revision 2.0
Administration UCD - XL User Guide
Procedure
1. Select View Trace from the Trace Functions menu.
Seven subcommands are displayed at the bottom of the View Trace screen:
Search - Perform a case-sensitive search for a text string. When you select 
this command, UCD-XL issues the prompt 
CUQbSX*
Type the text string (maximum of 8 characters) and press Enter. The search 
will start at the top of the next screen of the report and proceed forward. The 
first occurrence of the text string on that screen will be highlighted, as well 
as any other occurrence on that screen. To see the next screen with occur-
rences of the string, repeat the search procedure. You can press Esc instead 
of Enter to abort the search.
If the text string is not found, UCD-XL displays the message
@QddUb^ ^_d V_e^T
To p - Go to the first line of the trace file. Pressing the Home key has the 
same effect.
Bottom - Go to the last line of the trace file. Pressing the End key has the 
same effect.
Command - Execute a UNIX command. UCD-XL issues the prompt 
5^dUb E>9H S_]]Q^T Q^T `bUcc B5DEB>
Type the command and press Enter.   The command will execute, but any 
output from the command does not display.  For this reason, use this sub-
command sparingly.
Print - Send a snapshot of the current trace file to the default printer. Use the 
Print Trace command from the Trace Functions menu instead of this sub-
command.
Au t o Sc ro ll - Toggle the AutoScroll mode. When AutoScroll is on, the trace 
information on the display is scrolled as new information is written to the 
trace file. When AutoScroll is off, the displayed information will not change, 
even if activity is occurring. The activity information will be written to the 
trace file, but it will not display on screen. If AutoScroll is on, A-S displays 
on the right side of the screen.
Quit - Exit the view screen, and return to the Trace Functions menu.
Note:
 If, after selecting the Quit subcommand, you do not return to the Trace Functions 
screen, then the UCD-XL Administrator has been terminated by APM. To correct 
this, the UCD-XL  Administrator must be reinitialized from the APM.
Use the left arrow and right arrow keys to scroll the cursor through the sub-
command list. When a subcommand is highlighted, press Enter to execute 
that subcommand. Alternatively, you may execute a subcommand by press-
ing the first letter of the subcommand and then pressing Enter. 
						

							NDA-24169   Revision 2.0Page 27
UCD - XL User Guide Administration
2. After viewing a trace, execute the Quit subcommand. 
3. UCD-XL returns to the Trace Functions menu.
End of procedure.
Print TraceAfter initiating a trace, a snapshot of the trace file may be sent to a printer. The 
snapshot will only include data recorded up to the time the print command is 
selected.   The method of printing is configured for the UCD-XL Administrator via 
APM. The UNIX system printer is the default.
Procedure
1. Select Print Trace from the Trace Functions menu.
If the Trace file exists, it is sent to the specified printer.
2. UCD-XL returns to the Trace Functions menu.
End of procedure.
Transfer to MediaAfter initiating a trace, a snapshot of it may be written as a UNIX-formatted file to 
an external device, such as a floppy disk or a cartridge tape. The snapshot only 
includes trace data recorded up to the time you select the transfer command.
Note:
The UNIX tar command is used to implement the Transfer to Media command. 
The tar command may generate an error message that overwrites part of the 
Trace Functions menu.
Procedure
1. Select Transfer to Media from the Trace Functions menu.
UCD-XL issues the prompt 
>Q]U _V TUfYSU*
2. Type the name of the device and press Enter. (Be sure there is something in the 
device.)
You may cancel the transfer by pressing Esc instead of Enter. 
While the transfer is taking place, UCD-XL displays the following messages:
1ddU]`dY^W d_ dbQ^cVUb dXU VY\U
and
>Q]U _V TUfYSU*,TUfYSU ^Q]U.
Note:
The last message displays on the left side of the screen (where  is 
the name of the specified device). 
						

							Page 28NDA-24169   Revision 2.0
Administration UCD - XL User Guide
If the transfer is successful, UCD-XL displays the message 
DbQ^cVUb S_]`\UdUT
If the transfer is not successful, UCD-XL displays the message 
DbQ^cVUb VQY\UT
3. UCD-XL returns to the Trace Functions menu.
End of procedure.
Copy to DOS 
DisketteYou may save a trace on a DOS-formatted diskette (or other media).
Procedure
1.  Select Copy to DOS Diskette from the Trace Functions menu.
UCD-XL issues the prompt:
4?C TbYfU \QRU\ 1 _b 2*
2. Enter the letter representing the DOS label for the diskette drive (usually A or 
B). If you want to provide a name for the file other than “UCDTRC”, follow the 
label with a colon and new name (e.g.: “A:UCDTRACE”). You may cancel by 
pressing Esc instead of Enter.
Note:
Be sure there is a diskette in the drive before you press Enter
.
While the file is being copied, UCD-XL displays the following message:
1ddU]`dY^W d_ S_`i _^d_ 4?C TYc[UddU
If the trace was copied successfully, UCD-XL displays the message:
4?C S_`i S_]`\UdUT
If the trace was not copied, UCD-XL displays the message:
4?C S_`i VQY\UT
3. UCD-XL returns to the Trace Functions menu.
End of procedure.
QuitExit the Trace Functions menu and return to the UCD-XL Main Menu. 
						

							NDA-24169   Revision 2.0Page 29
UCD - XL User Guide Administration
Quit (Log Off)
This selection from the UCD-XL Main Menu terminates any active trace and 
returns you to the UCD-XL Administrator Log On screen (Figure 2-1). 
						

							Administration UCD - XL User Guide
Page 30NDA-24169   Revision 2.0
This Page Left Blank. 
						

							NDA-24169   Revision 2.0Page 31
UCD - XL User GuideLimitations
Chapter 3 Limitations
Limitations of UCD-XL:
The UCD-XL ports/lines must be connected to the same PBX as the OAI User 
Application Processor.
All ports in a group must belong to the same tenant, but groups may be 
associated with different tenants.
For a call transferred across CCIS, the PBX identifies the call as if the 
transferring party dialed direct. Hence, UCD-XL will use MCI call type 43 
(Direct Call) to inform the VMS; the calling party is the transferring extension, 
not the original caller.
If UCD-XL attempts to connect a call to a port that is also the pilot number of 
a UCD group defined in the PBX, the final destination of the call is determined 
by the PBX and may not be the port that UCD-XL requested.
For a call forwarded across CCIS, UCD-XL will not know the tenant number of 
the forwarding party. Therefore, UCD-XL will specify tenant 0 in the called 
party field of the MCI message to the VMS.
Groups must be in operation 24 hours a day, 7 days a week. All ports must be 
available for answering calls (unless made busy), and should not be used for 
outgoing calls.
A port (especially a D
term) in a UCD-XL group must not be call-forwarded to 
another extension at any time for any reason.
A transferred call cannot be connected to an announcement message until the 
intermediate party releases.
You can generate and examine only one report at a time
All office codes in a PBX network must be the same size.
UCD-XL can communicate (via a single MCI link) with only one VMS.
You can initiate and examine only one trace at any time.
An ANI number must consist of 10 digits: 3-digit area code, 3-digit exchange, 
and a 4-digit extension. Any value longer than that will only match the special 
ANI pattern “FOREIGN” or “DEFAULT”.
UCD-XL does not receive ANI data across CCIS.
The UCD-XL option to use a caller’s my line (physical extension) instead of 
actual line as mailbox number applies to all
 phones in the local PBX (the one 
having OAI). This option does not apply to calls across CCIS; a remote PBX 
must be configured on the MAT (ASYD index 240, bit 5) to pass along the my 
line of a remote caller. 
						

							LimitationsUCD - XL User Guide
Page 32NDA-24169   Revision 2.0
This Page Left Blank. 
						

							Error Messages UCD - XL User Guide
Page 33NDA-24169   Revision 2.0
Appendix A Error Messages
Error Messages on Administrator Screen
The following are error messages you might encounter on the UCD-XL 
Administrator’s screen when running UCD-XL. None of these messages will 
appear in the log file. Many of these error messages are the result of incorrect data 
entry. Immediately following each error message is a brief explanation and a 
possible solution to the problem.
Note:
“UDP” means User-defined Parameter. Refer to instructions for the Administra-
tor’s configuration in the UCD-XL Installation Guide.
Cannot communicate with UCDXL Monitor.
The Administrator could not send a message to the Monitor. Without the Monitor,
the Administrator cannot perform tracing functions but can still generate reports.
Verify that the Monitor is an active application under the APM and is specified in
UDP #5. 
Cannot create trace file -- error 
The Administrator could not create the trace file named 
ucdtrace in the statistics
directory specified in UDP #6. Verify that UDP #6 contains a directory pathname.
If necessary, create the directory using the UNIX command mkdir.
Note:
 is the UNIX error code.
Cannot lock statistics file.
The Administrator could not lock the statistics file, probably because the Monitor
was accessing the file while performing statistics collection. Wait for the Monitor
to complete its task (check the APM log), then select the function again.
Cannot open statistics file 
The Administrator could not open the file named  in the statistics direc-
tory specified in UDP #6. Verify that UDP #6 contains a directory pathname. If nec-
essary, create the directory using the UNIX command mkdir.
DANGER! Disk nearly full. Erase statistics immediately! 
In addition to this message being displayed, the file size specified at the bottom of
the screen is flashing. There is insufficient space (2% or less) in the /oai filesystem
on disk to permit further growth of the statistics file. Select the “Erase Statistics”
option in the Report Generation menu and delete a set of obsolete statistics in order
to reduce the size of this file.
DOS copy failed.
The Administrator could not copy a file to a DOS-formatted diskette. The reason
may be stated in file 
/tmp/ucderr; use the UNIX command cat or more to view the
file. Possible reasons include: (1) the specified drive does not exist or is not acces-
sible; (2) the drive does not contain a writeable DOS-formatted diskette.This Page Left Blank. 
						

							Error Messages UCD - XL User Guide
Page 34NDA-24169   Revision 2.0
Future date not permitted.
When the reporting period is being specified, the Administrator does not accept any
date in the future. Enter a date in month/day/year format that is less than or equal
to todays date, or press Esc to return to the menu.
Invalid format or value.
The starting and ending dates of a reporting period must be specified in the format
“month/day/year”, or “month/day” where the current year is assumed. The month
must range from 1 to 12 and the day must range from 1 to 31. (There is no valida-
tion of the day combined with month.) A two-digit year value is converted to a four-
digit year like so: 60-99 represents 20th century (1960-1999), 0-59 represents 21st
century (2000-2059). Enter a different set of values or press Esc to return to the
menu.
Must equal or exceed starting date.
The ending date of a reporting period cannot be less than the starting date. Enter a
different set of values or press Esc to return to the menu.
Print failed.
The Administrator could not print a file as requested using the command specified
in UDP #8. (If no command is given, lp is used.) The reason may be stated in file /
tmp/ucderr; use the UNIX command cat or more to view that file. Possible reasons
include: (1) the system printer is not enabled or on-line; (2) the specified command
is invalid. 
Report file does not exist.
A report must be created before any other reporting function can be accomplished.
Select the option “Create a Report” first. Refer to page 6 for further instruction. 
Trace file does not exist.
A trace must be initiated before any other tracing function can be accomplished.
Select the option Initiate Trace first. Refer to page 20 for further instruction.
Transfer failed.
The Administrator could not transfer a file as requested using the UNIX command
tar. The reason may be stated in file /tmp/ucderr; use the UNIX command cat or
more to view that file. Possible reasons include: (1) the specified destination device
does not exist or is not accessible; (2) the specified device does not contain a write-
able UNIX-formatted diskette or cartridge. 
Unable to generate report.
The Administrator could not create the report file named ucdreport in the statistics
directory specified in UDP #6. Verify that UDP #6 contains a directory pathname.
If necessary, create the directory using the UNIX command mkdir.  This Page Left Blank.