NEC Call Forward Control Installation And Operations Manual

							NDA-30030-003   Revision 3Page 11
Call Forward Control - Installation & Operations Manual INSTALLATION INTRODUCTION
SOFTWARE INSTALLATION (Cont)
If the current database format is not compatible with the new installation, it is converted to 
the new database format and the following status screen is displayed. Press the 
 key at the prompt to continue to the next step.
If the database conversion fails, the following status screen is displayed. Press the 
 key at the prompt to continue to the next step.
If a previous version of CFC is not installed on the system, then the following 
screen is displayed. Press the 
 key at the prompt to continue to the next 
step
STEP 6:   CFC Login Names
The cfc and cfcadm login names are installed with the same user ID (default is 4010). Any 
change in the user ID value must be made for both login names since they both use the same 
user ID value. The following screen is displayed while installing the cfc user. Just press 
ENTER at the user id prompt to accept the default value.
Creating CFC directories...
An existing /oai/app/cfc/data directory was found, and
the contents will be saved in /oai/app/cfc.s1/data.
A new /oai/app/cfc/data directory has been created, and
the original database has been successfully converted.
to the new data format and placed in the new directory.
Press Enter to continue. [ ] 
Creating CFC directories...
An existing /oai/app/cfc/data directory was found, and
the contents will be saved in /oai/app/cfc.s1/data.
A new /oai/app/cfc/data directory has been created, but
the original database could not be converted to the new
data format.
Press Enter to continue. [ ] 
Creating CFC directories...
Press Enter to continue. [ ] 
Installing cfc user on SCO UNIX
Enter (cfc) user id [4010]: 
User (cfc) installed.
Press Enter to continue. [ ]   
						

							Page 12NDA-30030-003   Revision 3
INSTALLATION INTRODUCTION Call Forward Control - Installation & Operations Manual
SOFTWARE INSTALLATION (Cont)
The following screen is displayed while installing the cfcadm user. Just press 
ENTER at the user id prompt to accept the default value. Note that a warning 
message is given when installing the cfcadm user, since it has the same user id as 
the cfc user. Enter y  at the warning prompt and continue.
STEP 7:   CFC Auto-Config
The installation script can load default HFC, CRC, and MCI_Server application 
configurations (see the Application Configuration section for additional details) if 
desired. The script will display the following screen:
Type n  to skip the “auto-config” step, or y  to load the 
default configurations. During the CRC configuration load the following screen is 
displayed:
At the prompt, type  to continue.
Installing cfcadm user on SCO UNIX
Enter (cfcadm) user id [4010]: 
Warning: The user id [4010] is already assigned on this system.
Install (cfcadm) with user id [4010]? (y/n) y 
User (cfcadm) installed.
Press Enter to continue. [ ] 
Would you like this script to ’auto-config’
the CFC applications into the APM Platform?
You can skip applications within
’auto-config’ if already configured.
Enter Yes [y] to ’auto-config’. (y/n) [y] 
/oai/utils/autocfg: running...
/oai/utils/autocfg: CRC
/oai/utils/autocfg: terminated normally
Press any key to continue.  
						

							NDA-30030-003   Revision 3Page 13
Call Forward Control - Installation & Operations Manual INSTALLATION INTRODUCTION
SOFTWARE INSTALLATION (Cont)
During the HFC configuration load the following screen is displayed:
At the prompt, type  to continue.
During the MCI_Server configuration load the following screen is displayed:
At the prompt, type  to continue.
STEP 8:   CFC Installation Processing (No input required.)
The installation script performs several tasks following the auto configuration and 
displays the results. Note that none
 of these actions require input. This process may 
include one or more of the following actions:
Installing the Tenant Database files.
Enter boot-up commands into UNIX boot-up sequence.
Install all remaining CFC files and directories as well as CFC host directories 
and executables.
Enter CFC crontab information.
Saving old CFC files from previous installations.
After these tasks have been completed, installation continues to the next step.
/oai/utils/autocfg: running...
/oai/utils/autocfg: HFC
/oai/utils/autocfg: terminated normally
Press any key to continue. 
/oai/utils/autocfg: running...
/oai/utils/autocfg: MCI_Server
/oai/utils/autocfg: terminated normally
Press any key to continue.  
						

							Page 14NDA-30030-003   Revision 3
INSTALLATION INTRODUCTION Call Forward Control - Installation & Operations Manual
SOFTWARE INSTALLATION (Cont)
STEP 9:   CFC Installation Complete
When the installation script has completed the following screen is displayed.
Press  to return the APM Administration Main Menu, then either exit 
the APM Administration program or use an Alt F(#) key combination to switch to 
another screen to perform Step 10.
STEP 10: SCO UNIX Subsystem Database
In this step, the SCO UNIX Subsystem Databases are updated to accept the new 
CFC information. Following this update, the passwords for the cfc and cfcadm 
login names are deleted, as follows:
At the SCO UNIX prompt, enter 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.  Deleting passwords for the 
cfc and cfcadm login names causes the system to ask for new passwords when first 
logging on using these names.
CFC Installation Complete
Press Enter to continue. [ ] 
Sysname
Welcome to SCO System V/386
sysname!login: root
Password: 
# /tcb/bin/authck -s
The following users have Protected Password Database entries
that do not match their Subsystem Database entries:
cfc cfcadm
There are errors in the databases.
Fix them (y/n)? y 
# passwd -d   cfc
Deleting password for user: cfc
Last Unsuccessful password change for cfc: Mon Mar 31 11:36:48 1997
# passwd -d cfcadm
Last successful password change for cfcadm: xxxxxxxxxxxx
Last Unsuccessful password change for cfcadm: NEVER
# 
						

							NDA-30030-003   Revision 3Page 15
Call Forward Control - Installation & Operations Manual INSTALLATION INTRODUCTION
SOFTWARE INSTALLATION (Cont)
If the MCI_Server component is used, two tty devices must be created in the SCO 
Subsystem database. This can be done by entering the SCO UNIX administration shell 
(sysadmsh), selecting Account –
>Terminal –>Create and then creating each tty device 
(ttyn1a, ttyn1b, etc.).   Refer to the SCO UNIX Administration Manual.
STEP 11:   Reboot
When finished, the entire system should be rebooted. At the “#” prompt, enter the follow-
ing command:
shutdown -g0 -i0 -y
When the message Safe to Power Off
 or Press Any Key to Reboot
 is displayed, reset the
UAP by pressing a key and allowing it to reboot. Then continue with the installation.
This completes the loading of CFC software in the APM. Now go to 
Application Config-
uration to configure the CFC applications. 
						

							Page 16NDA-30030-003   Revision 3
INSTALLATION INTRODUCTION Call Forward Control - Installation & Operations Manual
APPLICATION CONFIGURATION
If the “auto-config” utility was used during installation then default APM 
configuration data was loaded for the CRC, HFC, and MCI_Server applications. 
These default settings may require modification using the Select function of the 
Application Configuration option on the APM System Administration menu. If the 
“auto-config” utility was skipped, then the CRC, HFC, and MCI_Server 
applications must be configured into the APM system using the Add function of 
the Application Configuration option on the APM System Administration menu.
–Enter the APM option from the APM Platform Management Menu.
–Enter the System Administrator password at the APM password screen.
–Enter the Application Configuration option from the System Administration 
menu.
–To add a new application type “A” and press . Fill out the 
configuration forms as described in the following steps.
–To modify an application installed by “auto-config” type “S” and press 
. Use the arrow keys to select the desired application (HFC or CRC) and 
then press . Fill out the configuration forms as described in the 
following steps.
This section contains the information that should be entered to the configuration file for
CRC and HFC. For specific instructions on what these parameters mean and how to make
these entries, use the APM Operations Manual.
STEP 1:   APPLICATION CHARACTERISTICS
When adding HFC and CRC configurations to the APM Application Configuration file,
characterize, use the following values (if “auto-config” was used, these values are already
set and cannot be changed):Note
: 
Entries for parameters that are marked with an asterisk (*) should be made exactly
as they are shown; all other entries in this section are the default values installed
the “auto-config” utility and may be modified if necessary.
Parameter  Entry Parameter Definition
OAI Application* YIndicates whether or not (Yes or No) the application com-
municates with the NEAX2400 using OAI processes.
CRT Application* NIndicates whether or not (Yes or No) the application dis-
plays on the same screen as the APM, rendering the APM 
temporarily inaccessible.
Communication Queue* NIndicates whether or not (Yes or No) the application needs 
an IPC queue to communicate with other processes. 
						

							NDA-30030-003   Revision 3Page 17
Call Forward Control - Installation & Operations Manual INSTALLATION INTRODUCTION
APPLICATION CONFIGURATION (CONT)
STEP 2:   PRIMARY CONFIGURATION PARAMETERS
On the APM Configuration Entry screen, make the entries shown below for CRC:
Make the entries shown below for HFC: Parameter Entry Parameter Definition
Application Name CRCSpecifies the name to be displayed in the APM menus.  
This name is displayed however it is entered here; lower 
case letters and punctuation are acceptable; spaces are 
not.
Executable Filename*/oai/app/cfc/
bin/CRCDefines the path name of the executable file.
Group* CFC Names the group to which CRC is associated.
Response Mode*N(otify)Indicates the action that the APM is to take with CRC 
should a member of the group terminate.
Initialization BatchN(o)Indicates whether or not (Yes or No) CRC is to be initial-
ized automatically when the OAI system is initialized.
Termination Mode*M(essage) Indicates how the APM is to notify CRC to terminate.
Standard Output/dev/null Designates the file into which CRC output is redirected.
Number of Restarts 0Indicates how many times the APM may restart CRC af-
ter it terminates erroneously.
Parameter Entry Parameter Definition
Application Name HFCSpecifies the name to be displayed in the APM menus.  
This name is displayed however it is entered here; lower 
case letters and punctuation are acceptable; spaces are 
not.
Executable Filename*/oai/app/cfc/
bin/HFCDefines the path name of the executable file.
Group* CFC Names the group to which HFC is associated.
Response Mode*N(otify)Indicates the action that the APM is to take with HFC 
should a member of the group terminate.
Initialization BatchN(o)Indicates whether or not (Yes or No) HFC is to be initial-
ized automatically when the OAI system is initialized.
Termination Mode*M(essage) Indicates how the APM is to notify HFC to terminate.
Standard Output/dev/null Designates the file into which HFC output is redirected.
Number of Restarts 0Indicates how many times the APM may restart HFC af-
ter it terminates erroneously. 
						

							Page 18NDA-30030-003   Revision 3
INSTALLATION INTRODUCTION Call Forward Control - Installation & Operations Manual
APPLICATION CONFIGURATION (CONT)
STEP 3:   FACILITIES
According to instructions in the APM Operations Manual, designate the 
following NEAX2400 facilities for CRC using the Facilities command on the APM 
Configuration Entry screen:
SCF– Switch Control Facility
SMFN– Status Notification Facility
SMFR– Status Request Facility
Designate the following NEAX2400 facilities for HFC using the Facilities 
command on the APM Configuration Entry screen:
SSFM– Service Set Facility Monitor
SSFR– Service Set Facility Request
STEP 4:   OAI CONFIGURATION
Using the OAI-Conf command on the APM Configuration Entry screen, make the 
entry shown for each of the following parameters for CRC and HFC:   (Note: Make 
no entries to parameters that are not shown.)
Parameter Entry Parameter Definition
Tenant Number 1Specifies the number of the tenant that the application 
serves.
Source Link Name OAI1TCPIdentifies the port on the source side of the communication 
link; entry should correspond to a link name in the APM 
system configuration file. 
Destination Link 
NamePBX1TCPIdentifies the port on the destination side of the communi-
cation link; entry should correspond to a link name in the 
APM system configuration file.
Association Recovery 30Designates the number of seconds the application waits be-
fore trying to re-establish an association with the NEAX 
that has been released. 
						

							NDA-30030-003   Revision 3Page 19
Call Forward Control - Installation & Operations Manual INSTALLATION INTRODUCTION
APPLICATION CONFIGURATION (CONT)
STEP 5:   USER-DEFINED PARAMETERS
Make the entries below through the UserDefined command on the OAI 
Configuration screen for CRC:.
Make the following OAI Configuration entries for HFC:. U-D # Entry Parameter Definition
 #1*/oai/app/cfc/
data/Names-
FileIdentifies the full path and filename of the file that contains 
the names of the databases used by CRC and listed on the 
CFC Administration Main Menu. 
 #2*MCI
_Server If CRC is to forward calls to an existing on-site voice mail 
system, indicates the name of the message center interface 
used to ensure correct delivery of calls to the voice mail box. 
If an on-site voice mail system exists and the MCI
_Server 
name is entered here, enter the MCI
_Server configuration informa-
tion provided below to the APM Application Configuration f ile.
#3 3Indicates the maximum number of times a call is forwarded 
before it is sent to the default extension that is designated for 
the group through the Main Menu.
#4 5Indicates the number of seconds CRC waits before trying to 
deliver a call to voice mail after a previous attempt has failed.
#5 0#Serves as a system default; that is, if all call forwarding 
assignments in CRC were to fail, all calls are forwarded to 
this entry; must be the actual digits dialed, even to indicate 
the operator (0#).
U-D # Entry Parameter Definition
 #1*/oai/app/cfc/
data/Names-
FileIdentifies the full path and filename of the file that contains 
the names of the databases used by HFC and listed on the 
CFC Administration Main Menu. 
#2*/oai/db/cur/
tenantsIdentifies the full path and filename of the Tenant Database 
file. 
						

							Page 20NDA-30030-003   Revision 3
INSTALLATION INTRODUCTION Call Forward Control - Installation & Operations Manual
APPLICATION CONFIGURATION (CONT)
MCI_SERVER
If there is an existing on-site voice mail system with which CRC is to communicate, the 
MCI
_Server application must be configured through the Application Configuration option 
on the APM Administration Menu. The name MCI
_Server
 must be entered as User-
Defined Parameter #2 in the CRC configuration (see Step 5 above). The information that 
should be entered to the configuration file for MCI
_Server is shown below.
STEP 1:   APPLICATION CHARACTERISTICS
Set the MCI_Server application characteristics as follows (if “auto-config” was used, these 
values are already set and cannot be changed):
STEP 2:   PRIMARY CONFIGURATION PARAMETERS
Set the MCI_Server primary configuration parameters as follows: Parameter  Entry Parameter Definition
OAI Application* NIndicates whether or not (Yes or No) the application com-
municates with the NEAX2400 using OAI processes.
CRT Application* NIndicates whether or not (Yes or No) the application dis-
plays on the same screen as the APM, rendering the APM 
temporarily inaccessible.
Communication Queue* YIndicates whether or not (Yes or No) the application needs 
an IPC queue to communicate with other processes.
Parameter Entry Parameter Definition
Application Name MCI_ServerSpecifies the name to be displayed in the APM menus.  
This name is displayed however it is entered here; lower 
case letters and punctuation are acceptable; spaces are 
not.
Executable Filename*/oai/app/cfc/
bin/
MCI_ServerDefines the path name of the executable file.
Group* CFC Names the group to which MCI_Server is associated.
Response Mode*
I(gnore)Indicates the action that the APM is to take with 
MCI_Server should a member of the group terminate.
Initialization Batch
N(o)Indicates whether or not (Yes or No) MCI_Server is to be 
initialized automatically when the OAI system is initial-
ized.
Termination Mode*
M(essage)Indicates how the APM is to notify MCI_Server to termi-
nate.
Standard Output
/dev/nullDesignates the file into which MCI_Server output is re-
directed.
Number of Restarts 0Indicates how many times the APM may restart 
MCI_Server after it terminates erroneously.
Communication 
Queue500UNIX Message Queue key used by MCI_Server to re-
ceive queue messages.