This manual provides the information needed to configure and operate the
Attendant Monitor software application.
How To Use This Manual
This manual describes the various screens, windows and functions for the
installation, configuration and operation of Attendant Monitor. Examples of
displayed scree ns and step-by-s tep procedures a re shown in the following chap ters.
The procedural steps to per form a given tas k are give n in seque nce and ma rked as
shown below:
Step 1: From the Main Menu, select...
Manual
Organization
Chapter 1 - Introduction
This chapter details how to use this manual, t he actual manual org anization, and an
overview of the Attendant Monitor application.
Chapter 2 - Installation and Configuration
Chapter 2 describe s how to install an d configure the applic ation, along wit h the key
usage conventions, main menu screen, and an overview of the main menu
functions.
Chapter 3 - Administrator Tasks
This chapter describes the various functions and tasks available to maintain the
Attendant Monitor databases.
Chapter 4 - Attendant Tasks
Chapter 4 describes the basic attendant functions and tasks.
NDA-30135 Revision 1Page 1
Page 6
INTRODUCTIONAttendant Monitor Operations Manual
What is Attendant Monitor?
OverviewAttendant Monitor is an ap pli cation that will accumulate attendant statistics when
attendant consoles ar e used in a stand alone environmen t. Attendant Monitor serves
as the event collector for the Attendant Console Statistics application, detecting
events generated by the attendants and the PBX, and sending messages to the
Attendant Console Stati st ic s Log ger component. The Logger parses the messages
and saves the statistic data in an In formix Data base. The da ta is then used to
generate attendant statistic reports.
Note:Attendant Monitor is not required if Attendant Console Statistics is used with the
Hospitality Center System (HCS) or the Medical Center System (MCS), since
these applications serve as event collectors.
The following diagram illustrates how Att end ant Mo nit or interfaces with the
Attendant Console Statistics application.
This chapter provides a step-by-step description of the installation, initial
configuration, and Main Menu functions for Atten dant Monitor. Before proceedi ng
with the configuration, ensure that the SCO UNIX operating system and the
Applicati ons Manager (APM) plat form software are installed on the system.
The Applications Manager Operations Manual provides detailed instructions for
using the APM menus and for compl eting the data entry scree ns illustrated in this
manual. NEAX2400 IMS system manuals provide the procedures for making the
data assignments at the NEAX MAT.
Installation Procedure
This section describes the procedures to install the Attendant Monitor application
software. Follow the procedure below to install the software.
login: apmadm
password:
Note:Some keyboar ds use a marked Return key for the carriage return function. Other
keyboards mark this function key as Enter. The installation procedure will iden-
tify this function as Return (Enter). When the procedur e indica tes, use the ap pr opriate marked key on your particular keyboard.
To begin the Attendant Monitor
software installation, type apmadm at
the UNIX login prompt and press
Enter.
(If your “apmadm” account requires a
password, enter the “apmadm”
password at the subsequent password
prompt.)
Continue with the installation on the following pages...
Insert OAI Application/Update Release Media #1
Enter <Return> to continue:
Install Procedure
Installing from /dev/fd0
Insert OAI Application/Update Release Media #1
Enter <Return> to continue:
Copying ........
tar: blocksize = 20
x oai/app/attMonitor/install/etc/updstats.Z, 112163 bytes, 220 tape blocks
x oai/app/attMonitor/install/etc/swpcall.Z, 115463 bytes, 226 tape blocks
x oai/app/attMonitor/install/etc/swpattl.Z, 114652 bytes, 224 tape blocks
x oai/app/attMonitor/install/bluebars1.Z, 562 bytes, 2 tape blocks
x oai/app/attMonitor/install/bluebars2.Z, 343 bytes, 1 tape blocks
.
x oai/app/attMonitor/install/stats_ins.Z, 5263 bytes, 11 tape blocks
.
x oai/app/attMonitor/install/createAccounts.Z, 947 bytes, 2 tape blocks
x oai/app/consoleStats.ins, 2050 bytes, 5 tape blocks
x oai/chksum_app, 5259 bytes, 11 tape blocks
Has all release media been loaded [y or n] ? y
Next, you are requested to insert the
Attendant Monitor installation diskette
in the Flop py Disk Device.
Insert the diskette and press Enter to
continue.
Note: The Attendant Monitor
installation diskette will be a 3.5 inch type.
The screen displays t he fi les as the y are
loaded from the media. Some f iles may
scroll off the screen, until all the files
from the diskette have been processed.
You are asked if all of the application
release media (diskettes) have been
processed. Type ’n’ for any additional
diskettes fo r Attendant Monitor. When
all diskettes have been loaded, type ’y’
(yes) and press Enter.
Note: The number of bytes, tape blocks,
and/or files may vary from this example.
APM installation beg ins, processi ng all
OAI Platform is at revision 6 for machine i386 (May 22 1996 Rel3.1.4)
Old files saved in /tmp/attMonitor0, the system deletes these after 7 days.
Apm should now be Terminated and then Re-Initialized and the appropriate
Attendant Monitor APM Database files should be modified.
Installation Complete.
Press Return
Status messages show the installation
and configuration of the first Attendant Monitor main component.
At the prompt, press Enter to continue
the install ation.
Status messages show the progress of
the Attendant Monitor installation.
When all files have been set-up by the
installer, the Attendant Monitor
installation is complete.
Press Enter to exit this screen and
return to the APM Main Menu.
Proceed to the next page to configure the APM and various components...
Since Attendant Monitor is internally supported by the APM, its compone nt must
be configured in the APM enviro nment. This sec tion provides the i nformation tha t
must be entered into the AP M configuration file.
Attendant Monitor is set-up in the APM sy stem using the Add function of the
Application Configuration option on the APM System Administration menu.
A Note on Se lecting Commands
In the following procedure s, a step may c all for pressi ng the Tab key to se lect
a command. It may be necessary to press the Tab key multiple times in order
to select the specific command. When reading a step, understand to press the
Tab key (as needed) to select the specified command.
APM System
Configuration
AttendantMonitor
Component
Follow the steps to configure the APM system for Attendant Monitor.
- Enter the APM option from the APM Platform Management menu.
- Enter the System Administrator password at the APM password screen.
- Select the Application Configuration option from the System
Administration menu.
Attendant Monitor has one component that must be configured through the APM.
AttendantMonitor – Detects events generated by attendants and the PBX, then
sends messages to the Attendant Console Statistics Logger
component.
Define the AttendantMonitor component Characteristics in the APM
environment exactly as shown in the table:
CharacteristicValueDescription
OAI ApplicationYWhether (Yes or No) the component
communicates with the NEAX2400 using OAI
processes.
CRT ApplicationNWhether (Yes or No) the component runs on
the same screen as the APM, rendering the
APM temporarily inaccessible.
Communication QueueNCommunication Queue whether (Yes or No)
the component needs an IPC queue to
communicate with other processes.
From the APM Configuration Entry screen, configure the AttendantMonitor
component as follows. All pa ramete rs marked wit h asterisks ( *) should be entered
exactly as shown. The rest of the entries in the table below are just examples.
ParameterEntry ValueDescription
Application NameAttendantMonitorThe name to be displayed in the APM menus.
This name is displayed as it is entered
here — i.e., capital letters, lowercase, etc.
Executable Filename*/oai/app/attMonitor/
bin/attMonitor
Group*The group that the component belongs to.
Response Mode*I(gnore)The action that the APM is to take with the
Initialization Batch N(o)Whether (Yes or No) the component is to be
Termination Mode*M(essage)How the APM is to notify the component to
Standard Output/dev/nullWhere any output is sent.
The path name of the executable file.
Make no entry.
component should a member of the group
terminate.
initialized automatically when the OAI system
is initialized.
terminate.
Number of Restarts0How many times the APM may restart the
component after it terminates in error.
OAI FacilitiesFollowing the instructions in the APM Operations Manual, name the following
NEAX2400 facilities for the AttendantMonitor component using the Facilities
command on the APM Configuration Entry screen:
- SCFSwitch Control
- SMFR Status Request (R)
- SMFNStatus Notification (N)
Continue to the next page for OAI-Conf settings...
OAI-Conf SettingsUse the OAI-Conf command on the APM Configuratio n Entr y screen to make the
necessary paramete r entri es. For paramete rs shown wit h an asteris k (*) in the t able
below, make entries exactly as shown. The other parameters are shown with
sample entries that may be cha nged to meet site re quirements. Use the instruct ions
provided for this option in the APM Operations Manual:
ParameterEntry ValueDescription
Database Name #1*/oai/db/ cur/te nantsThe path name of the tenant number
database.
Database Name #2*/oai/db/ cur/AttmonThe path name of the Attendant Monitor
database.
Timeout Value #10Unused
Timeout Value #20Unused
Tenant Number1Default Tenant Number
Source Link NameOAI1TCPPort on the source side of the
communication link. Entry sh ould match a
link name in the APM system
configuration file.
User-Defined
Parameters
Destination Link NamePBX1TCPPort on the destination side of the
communication link. Entry sh ould match a
link name in the APM system
configuration file.
Association Recovery30Number of seconds Attendant Monitor
waits before trying to reestablish an
association with the NEAX that has been
released.
No user defined parameters are used in Attenda nt Mon it or. Therefore, all user
defined parameters are blank.
Attendant Monitor requires two APM databases: the Attendant Monitor database
and the Tenant Numbe r Data base. These d atabas es ar e cre ated wit h defa ult values
during initial software installation, but specific records must be added before
Attendant Monitor is enabled.
Attendant Monitor
Database
The Attendant Monitor database (attmon) con sists of a Master Datab ase file
component and an Application Database file component.
Master Database File - filename ’attmon’.
The attmon master database structure and example entries are shown in the table
below.
- The Monitor Number field specifies the monitor number the attendant will
dial to log on and log off the system.
- The Attendant Name field specifies the attendant name that will be used in
attendant reports.
- The TTY field spe cifies t he unique TTY devi ce used by the att endant. Since
stand alone attendants do not use an actual TTY device, the monitored
number value ma y be entered ag ain in this f ield to ensur e that the TTY v alue
is unique.
- The Supervisor Flag fields speci f ies if the atten dant is a supe rviso r. It may
be set to ‘Y’ or ‘y’ to indicate the attendant is a supervisor, or to ‘N’ or ‘n’
to indicate the attendant is not a supervisor.
Max.
Value
Example
Entry
Application Database File - filename ’Attmon’.
The Attmon application database structure is shown in the table below:
Field DescriptionData Type
Monitored Number
Attendant Name
TTY
Supervisor Flag
The database is initi ally b lank. It must be configu red be fore t he Atten dant Monitor
application can operate. The database values are set using the APM Applications
Manager Main Menu-- Selecting the Application Configuration option. The
general sequence is the following:
1.Build a Master Database File
Enter data into the master database fields to add the necessary Monitored
Number, Attendant Name, T TY, and Supervisor Flag values for Attendant Monitor.
2.Process the Application Database
Use the Process Application Databases option on the APM Database
Administration menu to create the application database file.
(When the Process o ption is act iv ated, data is drawn from th e master databas e
and converted to the formats specified in the application definition file.)
3.Install the Application Database
Use the Install Application Databases option on the APM Database
Administration menu to enable Attendant Monitor to copy its database.
Note:Refer to the APM Operations Manual for more detailed instructions on adding a
database.
AMNO: PBX assignment of Monitored Number
Each monitored number that is specified in the Attendant Monitor database must
be created on the PBX using the AMNO command.
Note:Refer to the NEAX2400 IMS system manuals for detailed pr o cedur es for making
the data assignments at the NEAX MAT.
Continue to the Tenant Number database on the next page...
The Tenant Database is an APM database used by the Attendant Monitor
application and other OAI applicati ons. It provi des a mechani sm for retri eving the
tenant number of an extension.
The Tenant Number databas e consists o f a Master Dat abase file component and a n
Application Database file compon ent:
Master Database File - filename ’tenant_m’.
The tenant_m master database structure and example e ntries are shown in the t able
below:
Field Name
TypeSizeMin.
Value
First ExtensionASCII10
Last ExtensionASCII10
Tenant NumberNumeric31255
Field Definitions
- The Tenant Number field contains the Tenant Number that is used by one
or more extensions. Tenant Numbers are associated with extensions using
the following me thods:
Max.
Value
Example
Entry
0
99999
1
- A Tenant Number may be associat ed with a set of extens ions def ined b y the
First and Last Extension fields. The First Extension field contains the
smallest extension number in the set, and the Last Extension field contains
the largest extension number in the set.
- A Tenant Number may be associated with a single extension by setting the
First and Last Extension fields to the same extension value.
- A Tena nt Nu mber may be as socia ted wit h a si ngle e xt ension that contai ns a
non-numeric charact er suc h as ’*’ or ’#’. The Fir st Exte nsion field contains
the extension value, and the Last Extension field is left blank.
Application Database File - filename ’tenants’.
The tenants application database structure is shown in the table below:
Field DescriptionData Type
First ExtensionASCII
Last ExtensionASCII
Tenant NumberShort Integer
This database must be configured before the Attendant Monitor application can
operate. The database values are set using the APM Applications Manager Main
Menu-- Selecting the Appli cation Conf iguration option. The gene ral sequenc e is
the followin g:
1.Build a Master Database File
Enter data into the master database fields to add the necessary phone line
numbers.
2.Process the Application Database
Use the Process Application Databases option on the APM Database
Administration menu to create the application database file.
(When the Process o ption is act iv ated, data is drawn from th e master databas e
and converted to the formats specified in the application definition file.)
3.Install the Application Database
Use the Install Application Databases option on the APM Database
Administration menu to enable Attendant Monitor to copy its database.
Note:Refer to the APM Operations Manual for more detailed instructions on adding a
database.
Initialize
Component
The Attendant Monitor component must be initialized from the APM. Follow the
steps below to initialize the AttendantMonitor component:
- On the APM System Operations Menu, select the Non-CRT Application Control option.
- Use the Initialize command to start up the “AttendantMonitor” component.
This completes the Atendant Monitor a pplication in stallation and
configuration...
A change of attendan t personne l or change s to monito red numbers wi ll requi re the
databases used by Attendant Monitor to be modified. Specific database records
must be modified to reflect these changes. The following must be changed:
•Attendant Monitor Database to reflect changes to attendant names, num-
bers, or other values.
•AMNO command to make changes on the PBX.
•Tenant Number Database for any changes to numbers.
Perform the following procedures to make changes to the Attendant Monitor
databases:
Note:Refer to the procedural instructions in the APM Operations Manual. If you en-
counter messages during this process, refer to the “Process” an d “Error Messages” chapters of t he APM Operations Manual.
Attendant Monitor Database Records
Perform the following steps to add, modify, o r delete records:
1.Build a Master Database File
Enter data into the master database fields to chan ge the Monitored Number,
Attendant Name, TTY, or Supervisor Flag values.
2.Process the Application Database
Use the Process Application Databases option on the APM Database
Administration menu to create the application database file.
(When the Process option is acti vate d, data is dra wn from the mas ter database
and converted to the formats specified in the application definition file.)
3.Install the Application Database
Use the Install Application Databases option on the APM Database
Administration menu to enable Attendant Monitor to copy its database.
AMNO: PBX assignment of Monitored Number
Any monitored number that is added, chan ged, or del eted in t he Attendant Monitor
database must be so modified on the PBX using the AMNO command.
Note:Refer to the NEAX2400 IMS system manuals for detailed pr ocedu r es for ma king
Any changes to monitored numbers will also require a change to the Tenants
database. Perform the following steps to add, modify, or delete records:
1.Build a Master Database File
Enter data into the master database fields to change the necessary extension
numbers.
2.Process and Tenant the Application Database
Use the Process Application Databases option on the APM Database
Administration menu to create the application database file.
(When the Process o ption is act iv ated, data is drawn from th e master databas e
and converted to the formats specified in the application definition file.)
3.Install the Application Database
Use the Install Application Databases option on the APM Database
Administration menu to enable Attendant Monitor to copy its database.