Installation on an SS7 Server

This section tells you how to install the SS7 Support for Blueworx Voice Response onto an AIX SS7 Server. There are five stages to installing and configuring the SS7 Server:

Pre-installation
Installing the D7 and the D7 Enablement packages
Configuring the SS7 Cluster
Configuring the AIX machine for SS7 Server usage
Installation and configuration complete

Pre-installation

Before installing these software packages read the README.TXT file on the CD-ROM to see if there are any special instructions.

Installing the D7 and the D7 Enablement packages

Use the following procedure to install the D7 and the D7 Enablement packages onto your SS7 Server.

Logon to the computer with a userid of root.
Using smitty, install the following file sets:
- dirTalk.SS7_D7_Enablement (D7 Enablement, from the base Blueworx Voice Response package)
- D7.isup (D7, from the SS7 Support for Blueworx Voice Response CD). Refer to the readme file located in /usr/lpp/dirTalk/readme/SS7README, as this stipulates which level of D7 is required. If more than one level is required, install the packages in chronological order, then refer to D7 software release to select the relevant package, before proceeding.
Now copy the relevant Distributed7 license for this machine (see Licensing the Distributed7 package) into /usr/ss8/d7/access/etc/license.dat .

The D7 package is installed into the directory /usr/ss8/d7. The D7 Enablement package is installed into /usr/lpp/dirTalk, and creates a dtuser userid if one does not already exist. This userid has not yet been assigned a password and therefore can only be accessed via the root userid.

Configuring the SS7 cluster

If this is the first SS7 Server, refer to Configuration using SS7itty, and then continue to the next section. Otherwise use the following instructions:

Logon as dtuser.
Change directory to /usr/lpp/dirTalk/db/current_dir/ca/SS7_D7_cfg. Using mkdir, create a directory of the same name as this machine (the name returned if you enter the hostname –s command).
Note: If the /usr/lpp/dirTalk/db/current_dir/ca/SS7_D7_cfg directory does not exist, create it by running the ss7itty command, followed by exit.
Using ftp, connect to the original SS7 Server on which SS7itty was run.
Change both the local and remote directories to /usr/lpp/dirTalk/db/current_dir/ca/SS7_D7_cfg/AnyMachine, by using the ftp commands cd and lcd.
Using the ftp command mget *, copy all the files that are in this directory.
Change both local and remote directories to /usr/lpp/dirTalk/db/current_dir/ca/SS7_D7_cfg/hostname
Using the ftp command mget *, copy all the files that are in this directory
Exit from ftp

Configuring the AIX machine for SS7 Server Usage

This section describes how to configure the machine for SS7 Server operation.

Logon as dtuser.

Enter the command SS7_MAINT and select the following options:

S

SS7 Server/Blueworx Voice Response client

S

Configure machine as an SS7 Server.

Once completed the AIX machine is configured for SS7 Server operation. The status line shown just before the prompt should show:

<name> is configured for D7 Server usage

R

Return to top level menu

D

D7 Operation (Start/Stop)

M

Start the D7 package with Alarm Message to screen. The following text appears:

Starting D7 package
Application Process Manager - Version v1.3.1
Copyright (c) 1991-2004, SS8 Networks, Inc.
All Rights Reserved
D7 Status - [init] : D7 core starting
Select an option :
Master Event Log Daemon - Version v1.3.1
Copyright (c) 1991-2004, SS8 Networks, Inc.
All Rights Reserved	
Signalling Point Manager - Version v1.3.1
Copyright (c) 1991-2004, SS8 Networks, Inc.
All Rights Reserved
Network Manager - Version v1.3.1
Copyright (c) 1991-2004, SS8 Networks, Inc.
All Rights Reserved
+++++++++++++++++++++++++++++++++++++++++++++++++++
+                                                 +
+              <<< IMPORTANT NOTE >>>             +
+                                                 +
+  Operations of the Application Process Manager  +
+  are now suspended indefinitely !!!             +
+                                                 +
+  To continue, use either MMI/MML or AccessMOB   +
+  interface to set the product operation mode    +
+  (i.e., stand-alone vs. distributed) and        +
+  introduce any remote host machines involved.   +
+                                                 +
+  It is only after you perform these tasks,      +
+  Application Process Manager will resume its    +
+  normal operations & proceed with its routine   +
+  system software initialization/start-up ...    +
+                                                 +
+++++++++++++++++++++++++++++++++++++++++++++++++++

Ignore the message in the "Important Note" and press Enter to recover the command prompt.

R

Return to top level menu

C

MML configuration loader

H

Load Host MML configuration for this machine. The following text appears:

*** Script loading operation - completed
Loading the script has been successful
The log output can be reviewed in /usr/lpp/dirTalk/sw/ss7/log/mml-host.log

After about 30-60 seconds the following text appears:

Alarm Daemon - Version v1.3.1
Copyright (c) 1991-2004, SS8 Networks, Inc.
All Rights Reserved
Distributed Shared Memory Manager - Version v1.3.1
Copyright (c) 1991-2004, SS8 Networks, Inc.
All Rights Reserved
Distributed Kernel Memory Manager - Version v1.3.1
Copyright (c) 1991-2004, SS8 Networks, Inc.
All Rights Reserved
User Part Manager - Version v1.3.1
Copyright (c) 1991-2004, SS8 Networks, Inc.
All Rights Reserved
ISDN User Part - Version v1.3.1
Copyright (c) 1991-2004, SS8 Networks, Inc.
All Rights Reserved

If this is the first of two SS7 Servers, you should now suspend installation on this server, and repeat on the second server the instructions that you have completed up to this point. Once you have completed that activity on the second server, return to this server and complete the rest of the instructions in this section (note that there is no further action required on the second server).

S

Load SS7 MML configuration. This loads the SS7–specific information, such as card configuration, Link, Link Sets and circuit configuration. The following text appears:

Waiting for MTP to be ready ...
Installing MTP components ...
NOTICE: spmd: pci3xapq[0] configured.
Waiting for ISUP to be ready ...
NOTICE: isup0: configuration started
NOTICE: isup0: database sync in progress ...
NOTICE: isup0: ready
Installing ISUP components ...
*** Script loading operation - completed
Loading the script has been successful
Review the log output in /usr/lpp/dirTalk/db/current_dir/ca/SS7_D7_cfg/log/mml.log

Note: The action of loading this configuration automatically enables other functions, such as activating Links etc. Therefore the text may be interspersed with D7 error messages. This is normal if the remote end of the SS7 links has not yet been configured.

Installation and configuration complete

All the necessary actions to install and configure the SS7 Server have now been completed. Continue the installation and configuration for the other machines in this SS7 cluster. If error messages are still being generated once all the machines have been configured, refer to Problem determination for assistance. Once the complete installation of the SS7 cluster has been validated, refer to Putting into production to ensure that all operations have been set to automatic mode.