NEC Attendant Management System Operations Manual

							NDA-30046 Revision 4.0Page 27
Attendant Management System Operations Manual Installation And Setup
Database Requirements
AMS requires three APM-based databases that were installed with default values 
when the software was loaded from the release media. One (amscfg) can be 
modified to meet site requirements using the APM Database Administration option 
on the APM System Administration Menu. The amsfile default database should not 
be modified at all without first consulting with an NEC representative; it needs 
only to be configured as a database name. (See “Software Installation” on page 14 
for more information.) The only field entry that may be changed without first 
contacting an NEC representative is the One-Key-Stroke Commands field. This 
field can be changed from Yes to No.
Note:Remember to process and install any database in which any of the following field 
information has been modified through the Build Master Database option.
amscfg Database 
Information
The amscfg database structure and contents are described below. If this database 
must be modified or another one created for another Server component, follow the 
instructions provided in the APM Operations Manual to access the Database 
Administration option on the APM System Administration Menu. Any messages 
displayed during these steps are addressed in the “Process and Error Messages” 
section of the APM Operations Manual.
Field NameMaster File Definition
(amscfg) App. File 
Definition
(Amscfg)Master Database
(amscfg)
Ty p e S i z eMin. 
Va l u eMax. 
Va l u e
Server Base Name A 24 ASCII Ams_Server#
Park Manager Name A 24 ASCII Ams_Parkmgr
Max Number of Operators N 3 0 255 Integer 12
OMP Queue Maximum N 3 0 255 Integer 10
OMP Queue Load N 3 0 255 Integer 5
OMP Queue Key N 5 0 32767 Integer 2766
Shared Memory Key N 5 0 32767 Integer 2766
Semaphore Key N 5 0 32767 Integer 2766
Logging Level [1-5] N109Integer 5 
						

							Page 28NDA-30046 Revision 4.0
Installation And Setup Attendant Management System Operations Manual
Field Definitions
Server Base Name–The application name of the Server component 
as set up in Software Installation on page 14. 
The # (pound symbol) is replaced by the actual 
number of the Server process.
Park Manager Name–The application name of the ParkMgr 
component as set up in Software Installation 
on page 14.
Max Number of Operators–The maximum number of attendants in the 
system. The absolute maximum is 50, but you 
should only configure for the maximum number 
of attendants needed due to speed 
considerations.
OMP Queue Maximum–The maximum number of messages allowed on 
the AMS IPC queue at any given time. Do not 
modify this value without first consulting an 
NEC representative.
OMP Queue Load –The maximum number of messages that can be 
outstanding for an attendant process at any 
given time.
OMP Queue Key–The number of the queue key assigned to the 
attendant menuing process.
Shared Memory Key–The number of the shared memory key used by 
this AMS process.
Semaphore Key–The number of the semaphore key used by AMS 
process.
Logging Level [1-5]–The level at which system process and error 
messages are logged, ranging from 1 (least) to 5 
(greatest detail). 
						

							NDA-30046 Revision 4.0Page 29
Attendant Management System Operations Manual Installation And Setup
amsfile DatabaseThe amsfile database structure and contents are described below. These are path 
and filenames required by the AMS software. Do not make any changes to this 
database without first contacting an NEC representative.
attcfg DatabaseThe attcfg database structure and contents are described below. These are path and 
filenames required by the AMS software. The only field entry that may be changed 
without first contacting an NEC representative is the One-Key-Stroke Commands 
field. This field can be changed from Yes to No.
This completes the database support in the APM. Proceed to MAT Assignments 
on page 30 to learn how to make the necessary MAT assignments.
Field NameMaster File Definition
(amsfile)Appli File Definition
(Amsfile)Master Database
(amsfile)
Type Size Data Type Default Entry
Configuration File A 25 ASCII /oai/app/ams/cfg/ompcfg
Shared Statistics File A 25 ASCII /oai/db/cur/Attcfg
Daemon Name File A 25 ASCII /oai/app/ams/cfg/daemfile
Screen Definition File A 25 ASCII /oai/app/ams/cfg/isdcfg
Field NameMaster File
Definition
(attcfg)Appli File
Definition
(Attcfg)Master Database
(attcfg)
Type Size Data Type    Default Entry      
Att. Activity Rpts.Dir. A 25 ASCII /oai/app/ams/log
Color File A 25 ASCII /oai/app/ams/cfg/colors
Attendant File A 25 ASCII /oai/app/ams/cfg/passwd
Multiscreen Directory A 25 ASCII /oai/app/ams/cfg/scrn
Temporary Directory A 25 ASCII /oai/app/ams/tmp
Statistics Logger Name A 25 ASCII Stat
_Logger
One Key-Stroke Commands A 1 ASCII Y 
						

							Page 30NDA-30046 Revision 4.0
Installation And Setup Attendant Management System Operations Manual
MAT Assignments
This guide assumes that the data settings that affect the operation of all OAI 
software on a system-wide basis have already been assigned on the NEAX 
Maintenance Administration Terminal (MAT). Such settings include system index 
values and assignment of Interface I/O port data in the Interface Processor (IP). For 
more information about these system data settings and the MAT commands 
described below for AMS, refer to the OAI System Manual.
ACNO – Assignment of Conversion Number Data
Use this command to make ring-down trunks go to the monitor number 
assigned to the operator.
ACSA – Assignment of Connection Service Index A
Use this assignment with the ACNO command. If the monitored number used 
in ACNO for ring-down trunks is not monitored by AMS, the ring-down trunks 
are not downgraded. The ACSA must be used to assign the downgrade number 
for ring-down trunks. This is usually the pilot number of the attendant UCD 
group.
AMNO – Assignment of Monitored Number
Use AMNO to assign the monitored numbers tied to incoming call types, orbit 
numbers, and the attendant logical extensions. (The AMS queues require 
monitored numbers.) Monitored numbers must fit into the numbering plan, but 
cannot be defined as stations. The following conditions apply:
0 (zero) must be set up as a monitored number. The main incoming num-
ber(s) and 800 number(s) must then be routed to 0. The 800 numbers must 
allow both incoming and outgoing calls.
The monitored number index (MNI) must be unique. Usually, the last three 
digits of the monitored number are used as the value for the MNI.
The downgrade number is the number called when the AMS is not initialized 
and a call is made to the matching monitored number. When a call from a 
ring-down trunk is sent to a monitor number and the AMS is not initialized, 
the call will not go to the downgrade number assigned in AMNO. Instead, it 
will go to the downgrade number set up when the ACSA command is used.
Usually, the downgrade number used for the operator monitored number is 
the pilot number of the attendant universal call distribution (UCD) group.
ASHU – Assignment of Station Hunting (UCD)
Use this command to assign the attendant’s physical extensions to a UCD 
group.
ASDT – Assignment of Station Data
AKYD – Assignment of Key Data for D
term
Use these commands to make station assignments for attendants, the night 
station, and the Meet-me Paging station. The HDAC or Dterm Series II or III part 
of the AMS attendant workstation must be assigned a unique station number 
and a virtual line set in off-hook suppress. The Meet-me Paging station must be 
set in off-hook suppress with the handset off-hook and assigned as tenant 1.
This completes the MAT assignments. Proceed to Preparing Attendant Stations 
on page 31 to learn how to prepare attendant stations. 
						

							NDA-30046 Revision 4.0Page 31
Attendant Management System Operations Manual Installation And Setup
Preparing Attendant Stations
Using an attendant station that is connected as an attendant workstation, log in 
to the AMS menus by typing the login name ams at the SCO UNIX login 
prompt and pressing Enter. The Attendant Station Configuration screen 
appears for entry of an initial attendant station configuration, using the 
definitions below:
Figure 2-11   Attendant Station Configuration
Field Definitions
Attendant ID –The ID number of an attendant.
Logical Ext  –The monitored number set up in the PBX for this individual 
attendant.
Vi r t u a l  E x t  –The extension number that is set in off-hook suppress.
Station Type  –The type of station associated with the physical extension.
Tenant  –The number of the tenant served by this physical extension. 
This must match the PBX tenant and fall in the range from 1 
to 255.
Default RSC  –The default restriction class index. This must match an index 
between 0 and 15 that is defined in the PBX. (This value is no 
longer used.)
CCIS Index  –The unique prefix for the extension in a CCIS network. If not 
in a network, leave this field blank. (This value is no longer 
used.)
Physical Ext  –The real extension of the HDAC–my line vs. Prime Line. If 
one is not assigned, leave this field blank.
Device  –The tty on which this attendant will log in. Type /dev/null for 
network attendant stations.
Server Number –The “Server #” must match the number entered for one of the 
OAI Server application components that were set up in the 
APM.
Attendant ID:
Logical Ext:
Virtual Ext:
Station Type:
Tenant:
Default RSC:
CCIS Index:
Physical Ext:
Device:
Server Number:
Attendant Management System Mon Aug 19 0237 pm
*** Attendant Stations ***
Enter  to Return to Command Line 
						

							Page 32NDA-30046 Revision 4.0
Installation And Setup Attendant Management System Operations Manual
Constantly Display 
The Login ScreenYou can set up certain terminals to always display the AMS login screen rather 
than return the display to the SCO UNIX login prompt. To do so:
1. Log in as root at the UNIX login prompt.
2. Enter single user mode by typing shutdown -g0 -i1. 
3. Once the system is down, mount the oai partition. Type mount /oai and press 
Enter. 
4. Type ksh and press Enter.
5. Type . /oai/app/ams /.kprofile and press Enter.
6. From the AMS Platform Maintenance menu, shown below in Figure 2-12, type 
T and press Enter to choose the Terminal Maintenance option.
Figure 2-12   AMS Platform Management
7. At the prompt “Install, De-install or Restart an attendant terminal (i,d,r,q)”, 
type i and press Enter.
8. At the prompt “Enter name of terminal”, type the name of the device, 
beginning with tty, and press Enter.
9. From the AMS Main Menu, type L (logout) and press Enter.
10. At the UNIX prompt, type exit twice to log out.
11. Bring the system back up in multiuser mode. The new AMS terminal will then 
automatically be brought up displaying the AMS login screen.
If this arrangement is used to allow access to the APM Platform Maintenance menu 
and the UNIX system from an attendant console, a special attendant login is 
required. The default login data file contains an entry to allow UNIX access–the 
login entry name is unix and the password is unix. If UNIX access from the 
attendant console is not required, delete the login name unix through the Login 
Name Maintenance option on the Main Menu.
NEC America Inc.                     Sat - Nov 13, 1993
                AMS Platform Maintenance
AMS
Install Database
Remove Database
Build Database Indices
Erase Database Indices
Cluster Database Tables
Set Menu Colors
Display Table Count
Key Pad Value Test
Terminal Maintenance
InformiX dbaccess Utility
UNIX
Logout
Enter option: [ ] 
						

							NDA-30046 Revision 4.0Page 33
Attendant Management System Operations Manual Installation And Setup
Change Hot Key 
Access To 
Enhancement 
ApplicationsEach terminal in the AMS has a file in the directory /oai/app/ams/cfg/scrn. Each 
screencap file is used by OAI applications for switching among applications on the 
same terminal using a configured “hot key” for each application. This file may be 
edited to change the hot key. Its format for each key/application combination is:
:label,flags,key_label,key_select,executable,args,dum,sig,pid,status:
where
label–Name of the application. The application uses this to identify 
the record while reading a single character (getch()). 
flags–Bit-mapped flags:
0x1 = This application will automatically be started in 
background.
0x2 = This application is to have a pipe opened for it so 
that the primary application can communicate with 
it.
key_label–Key label selection for this application.
key_select–Curses keypad value corresponding to the application in 
decimal notation.
executable–Excutable path name of the application.
args–List of arguments with items separated by spaces. They are 
passed to the application when executed.
dum–Place holder for new version of AMS. This used to be esig.
sig–Switch signal used by the application.
pid–Application’s process ID. This should not be altered manually.
status–Application status, which is updated by the screen libraries:
0 = Inactive
1 = Active
2 = Background
3 = Primary is to start this application.
Example:
:Scap,0,F1,109,/oai/bin/apm,@,@,16,0,0:
:APM,2,Shift-F1,109,/oai/bin/apm,@,@,16,0,0:
:Aac,0,F2,112,/oai/app/aac/bin/aamp,@,$,17,0,0:
:CFC,0,Shift-F2,110,/oai/app/cfc,arg1 arg2 arg3,@,2,0,0:
:Exit,0,F10,111,/oai/app/cfc,arg1 arg2 arg3,@,2,0,0:
To configure the F2 key with access to the Att Statistics application, the file should 
look like this: 
: ams,F1,265,@,@,3,16,0:
: stats,F2,266,/oai/app/ams/bin/statmenu,Stats,17,16,0,0: 
						

							Page 34NDA-30046 Revision 4.0
Installation And Setup Attendant Management System Operations Manual
Change Hot Key 
Access To 
Enhancement 
Applications 
(continued)Use the F1 key to return to AMS from Attendant Statistics.
Configure a hot key in this format using these guidelines:
Maximum limits for each file are 15 records, record fields of no more than 50 
bytes, 20 arguments per application.
NULL fields are identified with an “@” character or a “0”. No fields may be 
blank.
Each record begins on a new line.
The first record (Scap) is the primary application and should always be the first 
application record in this file. This application must be initialized first.
If an application has an invalid signal value set for its switch signal or exit 
signal, it will exit any time it switches. To turn off signals, enter a zero (“0”) for 
these fields.
“Scap” and “Exit” are predefined labels that must not be used by any other 
applications.
Finalizing Installation
After installing the system, perform the following steps to complete the setup.
Step 1: Checking 
System ConfigurationNow that at least one attendant station is configured, log into AMS from one of the 
configured stations. Use ams as both the login name and the password. The Main 
Menu for the AMS system administrator appears.
Figure 2-13   System Configuration
Display Configuration*** Main Menu ***
Database Administration
Extension Maintenance
Login Name Maintenance
Real-Time Screening
Quit
 Arrow keys to move cursor,  to select,  to quitCall Processing
System Configuration(1)
(2)
Calls Q’d    Attendant Status Attendant Management System
   Call StatusTrnfr
S      
SupervisorTue Aug 17 09:02 am
D   
      *** System Configuration ***
Basic Configuration
Announcement Configuration 
Timer Configuration
Queue Assignment
Orbit Numbers
Quit
Arrow keys to move cursor,  to select,  to  
						

							NDA-30046 Revision 4.0Page 35
Attendant Management System Operations Manual Installation And Setup
Step 1: Checking 
System Configuration 
(continued)Enter each sub-menu of the System Configuration screen. Pay special attention to 
Timer Configuration and Queue Assignment. Each of these fields must be filled in 
before the system will come up.
Remember to program the new assignments in the MAT using AMNO. 
Additionally, you must program the orbit numbers just entered if the Meet-me 
Paging feature of AMS is going to be used. Change any defaults in Basic 
Configuration and decide if the site will use announcement trunks.
Step 2: Checking 
Display Configuration You may perform this step now or after the system is brought up.
Choose the Display Configuration option from the Main Menu. Change the input 
fields as desired for each type of database record. The information displayed here 
will be the prompts for later data input. They will also serve as choices for source 
caller and directory lookup display.
Step 3: Checking 
Extension 
MaintenanceIf the existing extensions on the PBX have not been loaded into the system already, 
enter them using the Extension Maintenance option from the Main Menu.
Step 4: Entering 
EmployeesEnter employees using the Database Administration option from the Main Menu.
If desired, add attendant login names via the Login Name Maintenance option from 
the Main Menu.
Step 5: Initializing the 
AMS DaemonFrom the APM Operations Menu, choose the Non-CRT Application Control 
option. If the Ams_Daemon correctly comes on-line, an asterisk (*) will appear 
next to the Ams_Daemon, Ams_Server1, and Ams_Prkmgr, indicating they are 
running. Any other application specified in the Ams_Daemon’s user definable 
field will also be initialized.
If error messages appear, use the Log Files option from the APM Operations Menu 
to look at the apmlog file. This file shows all messages that scroll in the bottom 
APM window.
Step 6: Logging On When on-line, try to log into a preconfigured attendant station and enter Call 
Processing. A message should appear in the bottom left corner after a few seconds. 
If the message does not appear, look at apmlog and make sure that the extensions 
and logical number programmed for this attendant are valid. Otherwise, dial the 
queue number set up for the attendant and answer the call using the space bar on 
the console. Use Cancel to disconnect.  
						

							Installation And Setup Attendant Management System Operations Manual
Page 36NDA-30046 Revision 4.0
This Page Left Blank.