NEC Sentry Installation Guide

							NDA-30080   Revision 1.0Page 11
Sentry Installation Guide Sentry Alarm Control Terminal
11. Press Enter to continue the installation.
12. Press Enter to continue.
The following screen displays when the installation is complete.
13. Press Enter.
Installing the Sentry Terminal Binary . . .
NEC America Inc   Sentry Terminal Installation   Wed - Apr 29, 1998
Installing the Sentry Database Files . . .Installing the Default Terminal Configuration Files . . .Installing the ansi_sat terminal information . . .Installing the Sentry Platform Maintenance Utilities . . .Installing /etc/mygetty . . .Updating /etc/gettydefs . . .
Press Enter to continue. [ ]
Sentry Terminal Installation Complete.
The following configuration tasks must be completed before
NEC America Inc   Sentry Terminal Installation   Wed - Apr 29, 1998
1. Build, process, and install the sentry_m database.
starting Sentry Terminal application
2. Build a window configuration file for each entry in the   sentry_m database
See the Sentry Terminal Installation guide for more information.
Press Enter to continue. [ ] 
						

							Page 12NDA-30080   Revision 1.0
Sentry Alarm Control Terminal Sentry Installation Guide
UNIX Subsystem 
Database UpdateThe SCO UNIX Subsystem database must be updated for the Sentry Alarm Control 
Terminal.  
At the UNIX prompt, login as the superuser (root) and execute the SCO UNIX 
Subsystem Database authorization checking program (/tcb/bin/authck -s) and 
password deletion program (passwd -d) as shown below.
Answer yes when asked to fix the subsystem databases.  This ensures that the SCO 
UNIX Subsystem Databases are left in a proper state.
  login:  root
                                          .
# passwd -d sentry 
                                            .
                                            .
                                            .
Password: 
# /tcb/bin/authck -s
The following users have Protected Password Database entries
that do not match their Subsystem Database entries:
 
       sentry   sntryadm
There are errors in the database.
fix them (y/n)>  Y  
Deleting password for user sentry
# passwd  -d sntryadm
Deleting password for user sntryadm 
						

							NDA-30080   Revision 1.0Page 13
Sentry Installation Guide Sentry Alarm Control Terminal
Database Creation
The Sentry Master Database contains information used by the Emergency 
Conference, Annoyance Trap, and Sentry Alarm Control Terminal applications. 
The Feature Application Database contains a sub set of the Sentry Master Database 
and is used by the Sentry Alarm Control Terminal program. Each feature database 
record contains an entry for each Sentry feature (Emergency Conference or 
Annoyance Trap) used by the system.  Refer to the APM Configuration Manual for 
more information.
Each sentry master database record contains the following fields:
Monitored Number
The monitored number used by the caller to access the Emergency Conference or 
Annoyance Trap.
Category
An ASCII string containing the record category, which is set to “conference” for 
Emergency Conference records or “annoyance” for Annoyance Trap records.
Name
An ASCII string containing the Emergency Conference or Annoyance Trap name.
Minimum Lines Used
The minimum number of lines required by an Emergency Conference. This field is 
not used by the Sentry Alarm Control Terminal.
First Line Number
The first line number of the dedicated conference card set used by an Emergency 
Conference. This field is not used by the Sentry Alarm Control Terminal.
Override Allowed
A simple Y/N character that determines whether or not an emergency conference 
will override busy destinations. This field is not used by the Sentry Alarm Control 
Terminal.
Warning Tone Issued
A simple Y/N character that determines whether or not an Emergency Conference 
will issue a warning tone when a caller joins a conference. This field is not used by 
the Sentry Alarm Control Terminal.
Window Symbol
The name of the window symbol associated with an Emergency Conference or 
Annoyance Trap.
Contact Database
The name of the contacts database file used by an Emergency Conference. This 
field is not used by the Sentry Alarm Control Terminal.
Authorized Database
The name of the authorized caller database file used by an Emergency Conference. 
This field is not used by the Sentry Alarm Control Terminal. 
						

							Page 14NDA-30080   Revision 1.0
Sentry Alarm Control Terminal Sentry Installation Guide
Sentry Master 
DatabaseThe Sentry master database is named “sentry_m” by default and contains the 
following fields.
Table 2-1  Sentry Master Database Fields
Feature 
Application 
DatabaseThe feature application database uses data contained in the sentry master database.   
It is called “features” by default and contains the following fields.
Table 2-2  Feature Application Database Fields Field Description Type SizeMinimum 
Va l u eMaximum 
Va l u eExample
Va l u e
Monitored Number ASCII 10 5776
Category ASCII 25 conference
Name ASCII 25 conference1
Minimum Lines Used Numeric 2 0 42 0
First Line Number Numeric 5 0 99999 0
Override Allowed ASCII 1 n y
Warning Tone Issued ASCII 1 y y
Window Symbol ASCII 25 ALARM_WIN
Contact Database ASCII 25 /oai/db/cur/conf1
Authorized Database ASCII 25 /oai/db/cur/caller1
Field Description Data Type
Monitored Number ASCII
Name ASCII
Window Symbol ASCII
Category ASCII 
						

							NDA-30080   Revision 1.0Page 15
Sentry Installation Guide Sentry Alarm Control Terminal
Window Configuration Files
To create window configuration files:
1. Log in as apmadm to access the APM Administration Main Menu.
2. At the APM Administration Main Menu, type U to exit to UNIX.
3. At the UNIX prompt, type the following to change to the Sentry Alarm 
Control Terminal default configuration directory:
cd /oai/app/sentry/cfg/terminals/default
4. Make a feature configuration file for each Sentry Feature by copying the 
“feature.def” file using the following command:
cp feature.def 
where  is a unique name assigned by you.  For example,
 cp  feature.def fire.cfg
5. Use a UNIX editor (such as vi) to edit each feature configuration file, 
following the instructions contained in the file’s header.  For example,
vi fire.cfg
6. After the feature configuration files have been created and edited, use the 
following command to change to the Sentry Alarm Control Terminal 
configuration directory:
cd /oai/app/sentry/cfg/terminals
7. Use a UNIX editor (such as vi) to edit the Default Master Configuration file 
(Mdefault.cfg). Add the full path of each feature configuration file to the list 
within the Master Configuration file.  For example,
vi Mdefault.cfg
Note:
Refer to the next section, Configuration Parameters on page 16  and Feature 
Window Configuration on page 29 for more information about configuration 
parameters.   
						

							Page 16NDA-30080   Revision 1.0
Sentry Alarm Control Terminal Sentry Installation Guide
Configuration Parameters
The Sentry Alarm Control Terminal application uses configuration parameters 
defined in configuration files found in the “/oai/app/sentry/cfg/terminals” 
directory. The following sections describe the formats and functionality of these 
files.
Master 
Configuration FileWhen a Sentry Alarm Control Terminal is started it will determine which UNIX tty 
device it is using (tty01, tty02, etc.). It will then look for a master configuration file 
in the “/oai/app/sentry/cfg/terminals” directory that is associated with the tty 
device (“/oai/app/sentry/cfg/terminals/Mtty01.cfg”, “/oai/app/sentry/cfg/
terminals/Mtty02.cfg”, etc.). 
If a master configuration file has not been created for this tty then the file 
“Mdefault.cfg” is used by default. Each master configuration file contains a list of 
configuration file paths. A subdirectory is normally created to hold the 
configuration files associated with the default configuration and each tty (“oai/app/
sentry/cfg/terminals/default/”, “/oai/app/sentry/cfg/terminals/tty01/”, etc.). 
The master configuration file can list files that are located in different directories, 
allowing different tty devices to share configuration files.  Each master 
configuration file contains a complete path for the following configuration files:
db.cfg
The data buffer configuration file (
See, Data Buffer Configuration File on page 17).
init.cfg
The initialization configuration file (
See, Initialization Configuration File on page 21).
logos.cfg
The screen save configuration file (
See, Screen Saver Configuration File on page 22).
keys.cfg
The function keys configuration file (
See, Function Keys Configuration File on page 
23
).
dialogs.cfg
The dialogs configuration file (
See, Dialogs Configuration File on page 25).
titleBar.cfg
The title bar configuration file (
See, Title Bar Configuration on page 27).
msgBar.cfg
The message bar configuration file (
See, Message Bar Configuration on page 28).
login.cfg
The login screen configuration file (
See, Login Screen Configuration on page 28).
status.cfg
The status window configuration file (
See, Status Window Configuration on page 28).
xxxxxx.cfg
One or more feature window configuration files (
See, Feature Window Configuration 
on page 29
). 
						

							NDA-30080   Revision 1.0Page 17
Sentry Installation Guide Sentry Alarm Control Terminal
Data Buffer 
Configuration FileThe data buffer configuration file, “db.cfg”, contains constants and data buffer 
field definitions. Data buffers are used to store fields of ASCII character 
information contained in messages or read from a terminal. The fields within a data 
buffer may be used to build configurable display strings. 
The data buffer configuration file contains field definitions consisting of a field 
symbol, the number of characters in the field, and the offset of the field (offsets 
start with 0). Data buffer configurations will not require modifications unless the 
Sentry Alarm Control Terminal application is changed. The following data buffers 
are defined below.
Dynamic Window Area Configuration
The dynamic window area is the portion of the screen that is used to display 
dynamic windows. Usually, this area is located between the title and message bars. 
The following constants define the dynamic window area:
DYNAMIC_START
The screen position of the first row of the dynamic window area (row 0 = the first 
row of the screen, row 23 = the last row of the screen).
DYNAMIC_END
The screen position of the last row of the dynamic window.
Feature Window Sorting Methods
Each feature window can have a unique sorting method which controls the order of 
stations in the window. (See, Feature Window Configuration on page 29.) The 
sorting method is selected from one of the following:
SORT_NONE
Stations are not sorted.
SORT_BY_TIME
Stations are sorted by event time, with the newest events at the top of the window 
and the oldest events at the bottom.
Feature Window Filtering Methods
Each feature window can have a unique filtering method which limits station 
updates to a particular class of station including caller, operator, and source. (See, 
Feature Window Configuration on page 29.) 
The filtering method is selected from one of the following:
PASS_CALLER
Stations are not sorted.
PASS_OP
Stations with a classification of operator are passed.  All other stations are ignored.
PASS_SRC
Stations with a classification of source are passed.  All other stations are ignored. 
						

							Page 18NDA-30080   Revision 1.0
Sentry Alarm Control Terminal Sentry Installation Guide
PASS_OP_CALLER
Stations with a classification of operator or caller are passed.  All other stations are 
ignored.
PASS_SRC_CALLER
Stations with a classification of source or caller are passed.  All other stations are 
ignored.
PASS_SRC_OP
Stations with a classification of source or operator are passed.  All other stations 
are ignored.
PASS_ALL
All stations are passed.  
Login Screen User Name and Password Data Buffer 
Configuration
The user name and password data buffer is used by the login screen to contain the 
user name and password. It contains the following fields.
U_NAME  The user name field.
U_PASSWORDThe user password field.
Feature Title Data Buffer Configuration
The feature title data buffer is used to build a feature title string. It contains the 
following fields:
FEAT_TITLEThe feature title field.
Feature Statistics Data Buffer Configuration
The feature statistics data buffer contains feature statistics. The following fields are 
defined:
FEAT_NAMEThe feature name field.
FEAT_EXTThe feature monitored number extension field.
FEAT_RING  The ringing caller count field.
FEAT_ANSThe answered caller count field.
FEAT_RELThe released caller count field.
FEAT_QUEUEDThe queued caller count field.
FEAT_ABANDONThe abandoned caller count field.
FEAT_ACTIVEThe active caller count field.
FEAT_IDLEThe idle caller count field.
FEAT_TOTALThe total caller count field.
FEAT_RECORDThe recording flag field.
FEAT_OFFLINEThe monitor off line flag field. 
						

							NDA-30080   Revision 1.0Page 19
Sentry Installation Guide Sentry Alarm Control Terminal
Clock and Caller Information Data Buffer Configuration
The clock and caller information data buffer contains date and time fields which 
may be used to create date and time display strings. The optional caller status fields 
(along with the date and time fields) are used to display caller status. The following 
fields are defined:
MONTH_NUMThe numeric month (1...12, where 1 = January, 2 = 
February, etc.)
MONTH_ABRVThe three character month name (Jan, Feb, etc.).
MONTH_FULLThe full month name (January, February, etc.)
DAY_NUMThe numeric date (1...31).
WEEK_DAY_ABRVThe three character week day (Mon, Tue, etc.).
WEEK_DAY_FULLThe full week day (Monday, Tuesday, etc.).
YEAR_ABRVThe last two digits of the current year (95 for 1995, 96 
for 1996, etc.)
YEAR_FULLThe full current year (1995, 1996, etc.).
HOURS_24The 24 hour value (0...23, where 0 = midnight, 1...11 
= 1:00 AM to 11:00 AM, 12 = noon, and 13...23 = 
1:00 PM to 11:00 PM).
HOURS_12The 12 hour value (1...12).
MINUTESThe minutes value (0...59).
SECONDSThe seconds value (0...59).
AM_PMThe AM/PM string (“AM” or “PM”).
CALLER_ROWThe caller window row.
CALLER_EXTThe caller’s extension.
CALLER_LOCThe location of the caller’s extension.
CALLER_STATThe caller’s status (“Released”, “Ringing”, 
“Answered”, “Queued”, or “Abandoned”).
CALLER_CLASSThe caller’s class (“Operator”, “Caller”, or “Source”).
CALLER_CONNECTContains the extension of the party connected to the 
caller. This data is available for Annoyance Trap calls 
only 
						

							Page 20NDA-30080   Revision 1.0
Sentry Alarm Control Terminal Sentry Installation Guide
Function Key Assignments Data Buffer Configuration
The function key assignments data buffer contains the function key assignment 
descriptions which are displayed in the function key help dialog (see Function Key 
Help Dialog Configuration on page 25). A function key assignment description 
field corresponding to the respective function key may be defined in the function 
key assignment data buffer.  The following function key assignment description 
fields and the corresponding function keys are defined below.
F1_DESCF1
F2_DESCF2 
F3_DESCF3 
F4_DESCF4
F5_DESCF5
F6_DESCF6 
F7_DESCF7 
F8_DESCF8 
F9_DESCF9 
F10_DESCF10
F11_DESCF11 
F12_DESCF12 
SHIFT_F1_DESCShift-F1 
SHIFT_F2_DESCShift-F2 
SHIFT_F3_DESCShift-F3 
SHIFT_F4_DESCShift-F4
SHIFT_F5_DESCShift-F5 
SHIFT_F6_DESCShift-F6 
SHIFT_F7_DESCShift-F7 
SHIFT_F8_DESCShift-F8 
SHIFT_F9_DESCShift-F9 
SHIFT_F10_DESCShift-F10 
SHIFT_F11_DESCShift-F11 
SHIFT_F12_DESCShift-F12 
Title Bar Terminal Name Data Buffer Configuration
The title bar terminal name data buffer contains the tty terminal name used by the 
title bar window (see Title Bar Configuration on page 27). It contains the following 
fields:
TITLE_TERM The tty terminal name field.