NEC Second Party Alert User And Installation Guide

							NDA-30041   Revision 5Page 5
Second Party Alert User and Installation Guide OPERATING PROCEDURES
Return Call to an 
Internal CallerTo return an internal call:
1. Browse the list of callers to find the call you want to return. For more 
information on browsing calls and information displayed on the LCD, see 
“Browse List of Callers” on page 3 and “Internal Call Display Format” on page 
7.
2. When information for the call you want to return is displayed, press the 
Dterm 
key assigned for returning a call (1 or #).
3.“Calling” or one of the following messages appears:
“Phone Busy” — Indicates that the phone you are calling is busy.
“Bad Number” — Indicates that the number is invalid.
“Call Failed” — Indicates that an error occurred when the call was placed.
“DB Error” — Indicates that a database error occured.
Figure 1-5   Placing an Internal Call
4. When you browse the list of callers after returning a call (see “Browse List of 
Callers” on page 3), one of the following symbols appears before the party’s 
name and number:
-> 
Displays when the number is called and no answer is received

						

							Page 6NDA-30041   Revision 5
OPERATING PROCEDURES Second Party Alert User and Installation Guide
Return Call to an 
Outside CallerTo return an outside call:
1. Browse the list of callers to find the call you want to place. (See “Browse List 
of Callers” on page 3 and “External Call Display Format” on page 8 for more 
information.) 
2. When information for the call you want to place is displayed, press the 
Dterm key 
assigned for returning a displayed call:
For local and metro calls, Press #.
For long distance calls, Press 1.
3.“Calling” or one of the following messages appears. 
You might also see one of the following messages:
“Phone Busy” — Indicates that the phone you are calling is busy.
“Bad Number” — Indicates that the number is invalid.
“Call Failed” — Indicates that an error occurred when the call was placed.
“DB Error” — Indicates that a database error occured.
Figure 1-6   Placing an Outside Call
4. When you browse the list of callers after returning a call, the “->” symbol 
appears before the party’s name and number. (See “Browse List of Callers” on 
page 3 for more information on browsing a list.)
Quit Second Party 
AlertTo quit using SPA, press the Dterm key assigned to SPA. If you are not sure which 
key to use, see your system administrator. The Dterm returns to its standard display.
Figure 1-7   Dterm Telephone Set
CALLING
123
456
789
*0#
Dterm 8DC
To quit SPA, press the assigned 
Dterm key at any time. 
						

							NDA-30041   Revision 5Page 7
Second Party Alert User and Installation Guide OPERATING PROCEDURES
Display Formats
Internal Call 
Display FormatInternal call information displayed on the LCD is shown in the following table and 
described below:
The line number represents the line number of an incoming call. A station can 
have up to five secondary lines.
1 - Prime number
2 - first secondary line
3 - next secondary line
(A blank character follows the line number.)
The call signal is a single character indicating what actions the user performs 
on a call. 
This character is a blank if no action is performed.
The “*” character displays when a chime tone is issued at the caller’s station.
Note:Only internal PBX callers can be notified with a chime tone.
The “->” character displays when a number is called and no answer is 
received.
Note:The “”,
“
						

							Page 8NDA-30041   Revision 5
OPERATING PROCEDURES Second Party Alert User and Installation Guide
External Call 
Display FormatExternal calls with Automatic Number Identification (ANI) display different 
information than internal calls. The information displayed on the LCD is shown in 
the following table and described below:
The line number represents the line number of an incoming call. A station can 
have up to five secondary lines.
1 - Prime number
2 - first secondary line
3 - next secondary line
The call signal is a single character indicating what actions the user performs 
on a call. 
This character is a blank if no action is performed.
The “->” character displays when a number is called.
If an outside call has no ANI data, the line number and “OUTSIDE” display 
on the D
term.
The area code contains the three-digit area code of the caller.
The phone prefix contains the three-digit phone number prefix of the caller.
The phone suffix contains the four-digit phone number suffix of the caller.
Figure 1-9   Dterm Display (External Call)
1 Character 1 Character 1 Character 3 Characters 1 Character 3 Characters 1 Character 4 Characters
Field
Line
Number  Call Signal Parenthesis Area Code Parenthesis Extension HyphenPhone
Suffix
Va l u e s“1” - “6”“”, “->”“(““000” - “999”“)““ 000” - “999”“-““ 0000” - “9999”
1 (903) 555-1234
10:00 AM WED 30 
						

							NDA-30041   Revision 5Page 9
Second Party Alert User and Installation Guide OPERATING PROCEDURES
CCIS Call Display 
FormatCCIS calls use Automatic Number Identification (ANI) and consists of a PBX 
Office Code and extension. The PBX Office Code is configured at the NEAX and 
may contain either integer or non-integer characters. If the PBX Office Code and 
extension both contain integer characters only, then CCIS extensions (without the 
PBX Office Code) and associated user names can be entered in the database. Calls 
display using the same format as internal calls. Other CCIS calls display using the 
information displayed on the LCD shown in the following table and described 
below:
The line number represents the line number of an incoming call. A station can 
have up to five secondary lines.
1 - Prime number
2 - first secondary line
3 - next secondary line
The call signal is a single character indicating what actions the user performs 
on a call. 
This character is a blank if no action is performed.
The “->” character displays when a number is called.
The CCIS number contains the PBX office code and extension.
Figure 1-10   Dterm Display (CCIS Call)
1 Character 1 Character 4 Characters 1 Character 9 Characters
Field
Line
Number  Call Signal CCIS Label Blank CCIS Number
Va l u e s“1” - “6”“”, “->”CCIS“ ”Any ASCII characters
1 CCIS #49234
10:00 AM WED 30 
						

							Page 10NDA-30041   Revision 5
OPERATING PROCEDURES Second Party Alert User and Installation Guide
Function Key 
AssignmentsThe Dterm keypad is assigned the functions found in Figure 1-11. These functions 
are valid when Second Party Alert is enabled. SPA does not use the keys shown 
with a white background.
Figure 1-11   Dterm Keypad Layout
Previous Caller
ABC 
 2
3
DEF
 4
GHI
 
 5
JKL
6
MNO
8
TUV
9
WXY
 0
        OPER   
7
PRS
 * #
Next Caller
Signal Caller /
Place Call
 1Signal Caller/
Place Call
Previous Caller
Next Caller 
						

							NDA-30041   Revision 5Page 11
Second Party Alert User and Installation Guide INSTALLATION AND CONFIGURATION
Chapter 2 INSTALLATION AND CONFIGURATION
Installation
This guide provides specific field entries that need to be made during the 
installation and configuration of SPA. In addition to this guide, use instructions in 
the following manuals for this installation:
Applications Manager (APM) Installation Manual - Contains step-by-step 
instructions for installing the software from the release media.
Applications Manager (APM) Operations Manual - Explains how applications 
like SPA are configured in the APM environment and how the SPA database is 
created, using the entries and values provided in this chapter.
NEAX2400 System Manuals - Give very detailed explanations about the 
assignments that need to be made through the Maintenance Administration 
Terminal (MAT) commands on the NEAX2400.
The installation and set up of SPA involves the following sequence of steps:
Software Installation — SPA software must first be loaded from the release 
media. Log in to the APM Platform Management Menu, select the Installation 
of Applications/Packages option, and follow the instructions provided in the 
APM Installation Manual to complete this part of the installation. 
Application Configuration — SPA is internally supported by the APM and 
must be configured in the APM environment. Chapter 2, “INSTALLATION 
AND CONFIGURATION” in this manual provides the information that must 
be entered into this APM configuration file. Use the instructions provided in the 
APM Operations Manual to make the entries contained in this section.
Database Requirements — SPA requires a database that is constructed and 
maintained through the APM Database Administration option. The process 
begins with the creation of a master definition file and its related master 
database. Then, an application definition file is constructed which enables the 
processing of the master file into an application database. Chapter 3, 
“DATABASE REQUIREMENTS” of this manual defines the information 
which must be included in these definition and database files. Use the 
instructions provided in the APM Operations Manual to make the entries 
contained in this section.
MAT Assignments — There are data settings that must be assigned at the 
NEAX2400 Maintenance Administration Terminal (MAT) before SPA will 
function. Chapter 4, “MAT ASSIGNMENTS” specifies the necessary 
commands and the values at which they are to be set. Use the instructions 
provided in the NEAX2400 IMS System Manuals to make the entries contained 
in this section. 
						

							Page 12NDA-30041   Revision 5
INSTALLATION AND CONFIGURATION Second Party Alert User and Installation Guide
Installation (Continued)
The installation process, including its presentation in this and other manuals, is 
illustrated below:
SECOND PARTY ALERT
INSTALLATION REQUIREMENTS
Discussed in:Instructions in:
Chapter 2 Software Installation
SoftwareAPM Installation 
Manual
Chapter 2 Application Configuration
Application Characteristics
Primary Parameter Configuration
OAI Facilities (Optional)
OAI Configuration Parameters (Optional)
User-Defined ParametersAPM Operations 
Manual
Chapter 3 Database Requirements
Master Field Definitions
Master Database
SPA Application Field Formats
Process and Install SPA DatabaseAPM Operations 
Manual
Chapter 4 NEAX2400 IMS
Maintenance Administration Terminal (MAT)
Assignments
AIPT 
(Assignment of Interface I/O Port Data in IP)
ASYD
 (Assignment of System-wide Data)
ASDT
 (Assignment of Station Data)
AOKC
 (Assignment of OAI Key Codes)
AKYD
 (Assignment of Dterm Function Key)
ASHU
 (Assignment of Station Hunting-Group Data)NEAX2400 IMS
System Manuals 
						

							NDA-30041   Revision 5Page 13
Second Party Alert User and Installation Guide INSTALLATION AND CONFIGURATION
Software 
InstallationInstallation of the Second Party Alert software is initiated from the Applications 
Manager (APM) Platform Administration Main Menu. To display this menu, type 
apmadm at the UNIX prompt and press Enter. Using instructions in the APM 
Operations Manual, select the Installation of Applications/Packages option from 
this menu and load the SPA software from release media. As the installation 
process executes, follow the steps described below, entering the necessary 
information. 
Step 1: 
Active Second Party Alert Application Check
In order to install the SPA software, no SPA applications can be running on the 
system. 
-  If SPA applications are running, the error screen illustrated in Figure 2-1 is 
displayed and installation is terminated. Use the APM to terminate all active 
SPA programs before attempting another SPA installation.
Figure 2-1   Active Application Error
-  If there are no active SPA programs, continue installation with “Step 2: 
Superuser (Root) Password”. 
Step 2: 
Superuser (Root) Password
-  If no SPA applications are running on the system, the following password 
screen displays. Use the instructions below to enter the superuser (root) 
password:
Figure 2-2   Password Screen
Type the correct password for the root login and press Enter to continue. If you 
enter an invalid password, the following message displays: “Invalid root 
password. Do you wish to continue? (Y/N) [ ]”. 
Ty p e  y and press Enter to try again, or type n and press Enter to cancel the 
installation.
The Second Party Alert Application is currently active.
Installation cannot continue until Second Party Alert has
been terminated through the Applications Manager.
Press Enter to continue. [ ] 
Super User (root) privileges are required.
Please enter the Super User Password: su/root password  
						

							Page 14NDA-30041   Revision 5
INSTALLATION AND CONFIGURATION Second Party Alert User and Installation Guide
Step 3: 
Existing SPA Installation Check
During this portion of the installation, the system determines if a previous version 
of SPA is installed. 
-  If SPA is not installed, the installation continues with “Step 4: Existing OAI 
Name Display Database Check” on page 15. 
-  If SPA is installed, then a warning screen is displayed, indicating that the 
current installation will be saved if installation is continued. Type y and 
press Enter to continue, or type n and press Enter to terminate.
Figure 2-3   Previous Version Detected
-  If you chose to continue the installation after a previous version of SPA was 
detected, the following screen will be displayed. Type y and press Enter to 
delete this previously saved installation, or type n and press Enter to 
terminate.
Figure 2-4   Delete Previous Version
-  If you chose to save the previous version, the following message is displayed 
after the existing SPA installation has been saved. Press Enter to continue 
with “Step 4: Existing OAI Name Display Database Check” on page 15.
Figure 2-5   Saved Previous Version Confirmation Message
Second Party Alert is currently installed on this
machine.  If you choose to continue, the current
installation will be saved and all executable files
will be upgraded.  Database files will not be altered
since this version uses the same database formats as
previous versions.
Do you wish to continue? (y/n) [y
] 
A copy of /oai/app/party.old already exists on your system.
This copy must be removed before the current system can be
saved.  If it is not removed, installation will be aborted.
Do you wish to remove /oai/app/party.old? (y/n) [y
] 
The current installation of Second Party Alert is now
saved in /oai/app/party.old.
Press Enter to continue. [ ]