NEC Second Party Alert User And Installation Guide

							NDA-30041   Revision 5Page 25
Second Party Alert User and Installation Guide INSTALLATION AND CONFIGURATION
Step 3: OAI Facilities
According to instructions in the APM Operations Manual, designate the following 
NEAX2400 facilities for SPA using the Facilities command on the Configuration 
Entry screen. These facilities are automatically set up when you run autoconfig 
during installation.
Note:The same MSF Op-Code that is specified here must be assigned to SPA at the 
NEAX MAT. For more information, see Chapter 4, “MAT ASSIGNMENTS”. Only 
one MSF can be specified or the application terminates immediately.
MRFI Mode Release (I) MRFR Mode Release (R)
MSF  OAI Mode Set  NTF Number Transfer
SMFR Status Request (R) SMFN Status Notification (N)
TCFD Terminal Control (D)  TCFI Terminal Control (I)
SCF Switch Control 
						

							Page 26NDA-30041   Revision 5
INSTALLATION AND CONFIGURATION Second Party Alert User and Installation Guide
Step 4: Secondary OAI Configuration Parameters 
Using the OAI-Conf command on the APM Configuration Entry screen, make an 
for each of the following parameters. If the parameter is followed by an asterisks 
(*) in the table, you must make the entry exactly as shown. Other entries serve only 
as examples — actual entries are site-dependent. Use the instructions provided for 
this option in the APM Operations Manual. These parameters are automatically set 
up when you run autoconfig during installation.
Parameter Default Entry Description
Database Name #1* /oai/db/cur/nmdsp Indicates the path name of the 
database containing the names and 
extensions of everyone in the 
organization.
Note:
This entry refers either to the 
name of the SPA database 
created through the APM (see 
Chapter 3, “DATABASE 
REQUIREMENTS”) or to the 
Name Display database that is 
to  b e us ed b y SPA. If  the N a me 
Display database is to be used, 
enter its name here.
Database Name #2* /oai/db/cur/phonline Indicates the path name of the 
database containing primary 
extensions and the secondary 
(virtual) lines associated to them.
Timeout Value #1 60 Designates the number of seconds 
that SPA waits before clearing 
information from the D
term LCD 
panel.
Timeout Value #2 0 Indicates that there is not a timeout 
period for the second timeout value.
Tenant Number 1 Specifies the number of the tenant 
that SPA serves.
Source Link Name OAI1TCP Identifies the port on the source side 
of the communication link.
Destination Link Name PBX1TCP Identifies the port on the destination 
side of the communication link. 
Association Recovery 30 Designates the number of seconds 
SPA waits before trying to 
re-establish an association with the 
NEAX that has been released. 
						

							NDA-30041   Revision 5Page 27
Second Party Alert User and Installation Guide INSTALLATION AND CONFIGURATION
Step 5: User-Defined Parameters 
Make the following additional parameter entry through the UserDefined command 
on the OAI Configuration screen. These parameters are automatically set up when 
you run autoconfig during installation.
Parameter Typical Entry Description
User Defined #1  7 The OAI key code assigned on the 
MAT via the AOKC command.
User Defined #2 2 This is the chime tone value 
(assigned at installation) that is 
heard by the caller and called party. 
The tones are:
0Connected tone*
1Release tone
2Request tone
3Warning tone*
4Special tone*
5Acknowledgment tone
6Non-acknowledgment tone
7Confirmation tone
Note:
For 4200 V6 or earlier 
version of the PBX software, 
the connect tone, warning 
tone, and special tone do not 
produce any audio tones.
User Defined #3 (no entry) This allows the station to chime 
when a call is received on a 
secondary line. If the value is set to 
Y, a chime sounds. If it is set to 
N, 
no chime sounds. the default is 
N.
User Defined #4 8 This value describes the size of the 
display name used by the name 
display database defined in Second 
Party Alert. Valid values for this 
field are 
8 and 
16. The default is 
8.
User Defined #5 Enter the local area code in this 
field (assigned at installation).
User Defined #6 Enter the NEAX trunk access 
prefix (assigned at installation).
User Defined #7 /oai/db/cur/tenants Indicates the path name of the 
tenant number database. 
						

							INSTALLATION AND CONFIGURATION Second Party Alert User and Installation Guide
Page 28NDA-30041   Revision 5
Step 5: User-Defined Parameters (Cont)
This completes the configuration of SPA in the APM. Now go to Chapter 3, 
“DATABASE REQUIREMENTS” to create its database support.
Parameter Typical Entry Description
User Defined #8 7 This field specifies the number of 
digits used to place a local call. 
Valid values for this field are 7 (7 
digit phone number only) and 10 
(area code + 7 digit phone number). 
If this field is blank or an invalid 
value is specified, the default value 
of 7 is used by the program.
User  Defined  #14 /T L1  U9  D/oai/log/dbg/party.out This is not part of the default setup. 
Enter the value listed to enable 
debug logging.
Caution:
This file grows very quickly. 
Please monitor the file size 
to ensure the hard drive does 
not run out of space. 
						

							NDA-30041   Revision 5Page 29
Second Party Alert User and Installation Guide DATABASE REQUIREMENTS
Chapter 3 DATABASE REQUIREMENTS
This chapter assumes that SPA is not going to use the OAI Name Display 
application database and must have one built. In this case, SPA requires two 
databases that are created through the Database Administration option on the APM 
System Administration Menu.
Database creation in the APM involves the following 4-step process:
Step 1 - Create a Master Definition File: This step involves creating the 
master definition file that defines the fields in the master database file. 
Step 2 - Build a Master Database File: This step involves entering data (e.g., 
actual phone lines) into the master database fields that were just defined in the 
master definition file in Step 1. 
Step 3 - Create an Application Definition File: In this step, a definition file is 
created for the SPA database. This file defines the formats by which data from 
the master file is to be converted to meet the needs of SPA.
Step 4 - Process and Install the Application Database: In this step, the 
Process and Install Application Databases options on the APM Database 
Administration menu creates the file that will be used by SPA. When the 
Process option is activated, data is drawn from the master database and 
converted to the formats specified in the application definition file. The Install 
option is then activated to enable SPA to copy its database. 
Instructions 
The information required for the SPA database is provided in the table on the 
following page. Using this information with the procedural instructions provided 
in the APM Operations Manual, enter the Database Administration option on the 
APM System Administration Menu and build the SPA database. Any messages 
displayed during these steps are addressed in the Process and Error Messages 
chapter of the APM Operations Manual.
Note:Remember to complete Step 4, Process and Install the Application Database, for 
each database after you enter the following information.
Step 1
 - Create
Master Definition FileStep 2 
- Build
Master Database FileStep 3
 - Specify
Application FormatsStep 4
 - Process
Application Database 
						

							Page 30NDA-30041   Revision 5
DATABASE REQUIREMENTS Second Party Alert User and Installation Guide
Name Display 
Database 
InformationThe Name Display database field entries are shown in the following table and 
defined below the table. Name the Master Definition File name_m and the 
Application Definition File nmdsp.
Note 1:
You do not have to create this database if the Name Display application is 
installed, and its database is going to be used.
Note 2:
Name the name_m
 file in the Define Master Database Fields option, chosen from 
the Build Master Database option on the Database Administration menu. Name 
the nmdsp
 file in the Specify Application Database Fields option.
Field Definitions
Extension - The five-digit primary extension number. This is the 
number that is displayed with the caller’s name when this 
phone is used to place the call. 
Display Name - The name that is to be displayed on the D
term LCD panel. 
The name must be entered in the format, F.Lucas, with the 
first name initial separated from the last name by either a 
period (.) or a blank space.
Field DescriptionMaster Definition FileApplication
Definition FileMaster Database
Ty p e S i z eMin.
Va l u eMax.
Va l u eD a t a  Ty p e Ty p i c a l  E n t r y
Extension N 5 0 99999 ASCII 4290
Display Name A 8 ASCII F. Smith 
						

							NDA-30041   Revision 5Page 31
Second Party Alert User and Installation Guide DATABASE REQUIREMENTS
Phone Line 
Database 
InformationThe Phone Line database field entries are shown below in the table and defined 
below the table. Name the Master Definition File phone_m and the Application 
Definition File phonline.
Note:
Name the phone_m
 file in the Define Master Database Fields option, chosen 
from the Build Master Database option on the Database Administration menu. 
Name the phonline
 file in the Specify Application Database Fields option.
Field Definitions
Phone Line 1 - The five-digit primary extension number. This is the 
number that is displayed with the caller’s name when this 
phone is used to place the call. 
Phone Line 2 - 6 - The five-digit secondary, or virtual, lines that are 
associated with the primary extension that was entered in 
the first field. These virtual lines must be assigned to this 
primary line and to a hunt group through the NEAX 
Maintenance Administration Terminal (see MAT 
Assignments). 
Field DescriptionMaster Definition FileApplication
Definition FileMaster Database
Ty p e S i z eMin.
Va l u eMax.
Va l u eD a t a  Ty p e Ty p i c a l  E n t r y
Phone Line 1 N 5 0 99999 Long Integer 4290
Phone Line 2 N 5 0 99999 Long Integer 4291
Phone Line 3 N 5 0 99999 Long Integer 4292
Phone Line 4 N 5 0 99999 Long Integer 4293
Phone Line 5 N 5 0 99999 Long Integer 4294
Phone Line 6 N 5 0 99999 Long Integer 4295 
						

							Page 32NDA-30041   Revision 5
DATABASE REQUIREMENTS Second Party Alert User and Installation Guide
Tenant Number 
Database 
InformationThe Tenant Number database field entries are shown below in the table and defined 
below the table. The database contains a list of extensions and associated tenant 
numbers used by the PBX. A tenant number can be associated with an individual 
numeric extension or a range of numeric extensions. A given tenant number can 
have more than one record if all of the extensions associated with it are not 
consecutive. Tenant numbers can also be associated with individual extensions that 
contain non-numeric characters such as ‘*’ or ‘#’. Make the Master Definition File 
tenant_m and the Application Definition File tenants.
Note:
Name the tenant_m
 file in the Define Master Database Fields option, chosen 
from the Build Master Database option on the Database Administration menu. 
Name the tenant
 file in the Specify Application Database Fields option.
Field Definitions
First Extension- the first extension in the range of extensions.
Last Extension- the last extension in the range of extensions.
Tenant Number- this field contains the associated tenant number.
This completes creation of SPA database support. Now go to Chapter 4, “MAT 
ASSIGNMENTS” to make the necessary command assignments at the NEAX2400 
MAT.
Field DescriptionMaster Definition FileApplication 
Definition 
FileMaster Database
Type Size Min.
Va l u eMax.
Va l u eData Type Typical Entry
First Extension ASCII 10 ASCII 1000
Last Extension ASCII 10 ASCII 1099
Tenant Number Numeric 3 1 255 Short Integer 1 
						

							NDA-30041   Revision 5Page 33
Second Party Alert User and Installation Guide MAT ASSIGNMENTS
Chapter 4 MAT ASSIGNMENTS
This guide assumes that 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 SPA, refer to the OAI Module Installation Manual for the NEAX2400 
IMS, the NEAX2400 IMS Command Manual, the NEAX2400 IMS Job Specification 
Manual, and the NEAX2400 IMS Programming Manual.
The user-defined parameter #1 assigned during the application configuration on 
page 27 identifies the function key that the phone user presses to display call 
information. You must now assign this key at the MAT to the Mode Set Facility 
(MSF) for all D
terms that will be able to display calling party information.
Using the AOKC command, assign the MSF facility and its Op-Code to one of the 
14 OAI Key Codes in the MAT. Each of these OAI Key Codes corresponds to an 
AKYD Function Key Index (FKI) value that is then assigned to the specific D
term 
function key. This process is illustrated below.
Figure 4-1   OAI Function Key Assignment
A knowledge of the Dterm stations in the NEAX system and which ones will be set 
up to access SPA is necessary for using the following commands.
APM
Application
Configuration
Designation of
 Facility 
(Type)
 and its Op-
Code
 for Use by 
Application
MAT
AOKC
Command
Assignment of
 an OAI 
Key Code
 (between 1 
and 14)
 to the Same 
Facility Type and Op-
Code
MAT
AKYD
Command
Assignment of 
Corresponding MAT 
Function Key Index to 
a
 specific Dterm 
Function Key
. . . . .. . . . .
. . .
. . .
  
PBX Correspondence of
 AOKC AKYD
  OAI Function
 Key Codes
Key Indices
  1 < . . . .> 34
  2 < . . . .> 35
  3 < . . . .> 36
  4 < . . . .> 37
  5 < . . . .> 38
  6 < . . . .> 39
  7 < . . . .> 40
  8 < . . . .> 41
  9 < . . . .> 42
 10 < . . . .> 43
 11 < . . . .> 44
 12 < . . . .> 45
 13 < . . . .> 46
 14 < . . . .> 47 
						

							Page 34NDA-30041   Revision 5
MAT ASSIGNMENTS Second Party Alert User and Installation Guide
AIPT Command: (Assignment of Interface I/O Port Data in IP)
This command can be used to assign TCP/IP address of the system’s IP. Let system 
and UAP both in ethernet.
IP-NO: Assign face Processor Number.
Port Number
PNI: Assign 1
KIND: Assign 3 for choose TCP/IP protocol.
Assign ETHER-PKGNO
Assign TCP/IP address
ASYD Command: Assignment of System Data
If the Name Display application is not installed and a Name Display Database has 
been created through the APM for SPA use, the Name Display feature on the 
NEAX2400 does not need to be enabled, and this MAT assignment does not have 
to be made. If the Name Display application is installed and its database is going 
to be used by SPA, the Name Display feature on the NEAX2400 must be enabled. 
This feature allows SPA to access the Name Display database and retrieve the 
name associated with the calling extension. Use the ASYD command to enable this 
feature if necessary:
System 1, Index 78, bit 3
Enter either of the following two values:
0: Display name only.
1: Display calling/called number with name.
System 1, Index 78, bit 5
Enter 1 (yes) to set name display feature into service.
ASDT Command: Assignment of Station Data
Each Dterm that is to carry SPA must be set up to handle multiple incoming calls in 
a manner that is supportive of the SPA function. In addition to its primary incoming 
line, each supported D
term must have a user-defined number of virtual lines 
assigned to it, and those primary/virtual lines assigned into a pilot hunt group. 
Then, when the D
term user is on the primary line, any incoming call is wrapped to 
the next virtual line in that hunt group. Use the ASDT and ASHU commands to 
complete these assignments for each supported D
term:
1. Enter the same tenant number that is configured for the application in the APM 
Application Configuration option (Tenant #1, page 26).
2. Identify virtual lines for each supported D
term. These lines should agree with the 
secondary, or virtual, lines entered for each Dterm station in the database.