cc/td/doc/product/voice/uone/srvprov/r41s
hometocprevnextglossaryfeedbacksearchhelp
PDF

Table of Contents

Notes on 4.x Upgrade
Removing Packages From Previous Releases
Installation Overview
The Installation Script
Quick Configuration Tool

The Installation Script and Quick Configuration Tool

The installation script automates loading of uOne software packages, to include the Quick Configuration tool.

The Quick Configuration (quickconfig) tool automates configuration of the platform and initial database setup, as well as the uOne application environment. This tool assists in ensuring that all necessary areas are not overlooked. However, in many deployment scenarios, the final operational configuration may involve further editing of certain files. Refer to the later chapters of this document and the Backend Servers Reference Manual, as needed.


Note Within the Quick Configuration tool, the term Unified Communications (UC) refers to the uOne application and associated required and/or optional components.

Notes on 4.x Upgrade

If this is part of an upgrade of 4.x software, please perform the following steps.

Step 1 Read the Release Notes for any updated information concerning upgrade and/or configuration procedures.

Step 2 Ensure that agents and processes associated with uOne have been stopped. This information is available in the uOne Gateserver Installation and Configuration Manual.

Step 3 Remove all software packages that are currently on the Gateserver. See "Removing Packages From Previous Releases".

Step 4 Run the Installation Script to install packages on the Gateserver.

Step 5 There is no need to run the Quick Configuration tool again. However, you may need to add to or change your configuration as directed by the Release Notes.

Removing Packages From Previous Releases

Step 1 Access the Gateserver that will be upgraded.

Step 2 Use umcli to stop system software.

Step 3 Login as superuser.

Step 4 Determine which software packages are currently installed.

      pkginfo | grep DAP
      

Step 5 Remove each package using the following command:

      pkgrm <packagename>
      
Some dependency violations may appear when removing packages, however, they can be overridden. It is recommended that these be overridden only when all packages are being removed.

Installation Overview

The following is a summary of the installation/configuration process using the installation script and quick configuration tool.

Step 1 Set up supported Solaris 2.6 OS based on file system and package documentation in "Gateserver OS Configuration".

Step 2 Install/configure Backend servers (Directory and Messaging) based on uOne Gateserver Installation and Configuration Manual.

Step 3 Run the Installation Script on the Gateserver.

Step 4 Run the Quick Configuration tool for uOne (UM) and UMSA.

Step 5 Run the ldapsetup.sh script created via the Quick Configuration tool.

Step 6 Login to UMSA and start provisioning COS, administrators, and users.

Step 7 Call into system and start using uOne.

The Installation Script

The installation media or CCO contains a copy of the install script that enables installation of the various uOne packages. This tool provides the ability to install or re-install packages via a datastream file. It also creates the spmaster account as well as spgrp, if needed. The only requirement is to have the Solaris 2.6 operating system installed with the appropriate patches and that the Gateserver have the appropriate disk space allotments. See "Gateserver OS Configuration".

Step 1 The following will be available on the CD or in data stream format for downloading.

      um-41xxs-alaw-solaris26.pkg.Z 
      um-41xxs-alaw-solaris26.readme 
      um-41xxs-install-solaris26.readme 
      um-41xxs-install-solaris26.sh
      um-41xxs-mulaw-solaris26.pkg.Z
      um-41xxs-mulaw-solaris26.readme
      um-41xxs-plugins-solaris26.pkg.Z
      um-41xxs-plugins-solaris26.readme
       
      

Step 2 Issue the uncompress command on one of the following files (depending on which type of prompts need to be installed):

      uncompress um-41xxs-mulaw-solaris26.pkg.Z
      -OR- uncompress um-41xxs-alaw-solaris26.pkg.Z

Note Use the mulaw version of the prompts for T1 and the alaw version for E1.

Step 3 Then issue the following command as superuser:

      sh um-41xxs-install-solaris26.sh um-41xxs-<mulaw>-solaris26.pkg
       
      

Step 4 After confirming that you would like to continue with the installation process, the system will specify the locations where it will search for the software.

      1. Local $REL bundle
      2. CDROM bundle /mnt/$REL
      3. CDROM bundle /mnt/releases/$REL/$REL
      4. Local /var/spool/dist in pkg file system format
      

Note $REL is a variable that stores the name of the datastream file. In Step 3, $REL refers to um-41xxs-<encoding>-solaris26.pkg.

Step 5 After confirming, once again, that you would like to continue, answer the following questions:

      Do you wish to install Base Services plus UM? (yes/no):
      (If yes, answer the following)
      
      Which of the following applications do you wish to install
       
      1. Subscriber Web Administration Packages (UMSA/PMA)
      2. MWI Application
      3. SMS Application
      4. None of the above 
      

Note Answer YES to all Y/N prompts during the package installation phase of the install script for the uOne product, especially the setuid and/or setgid prompts. For example,
The following files are being installed with setuid and/or setgid permissions:
/home2/spmaster/r410/bin/SCHED <setuid root>
Do you want to install these as setuid/setgid files [y,n,?,q]
y

Step 6 Upon completion, a summary of the packages installed and their status will appear.


Note The Install Script will not re-install packages that are already present.

Quick Configuration Tool

The Quick Configuration (quickconfig) tool is an initial configuration tool. In addition, it may be run as often as needed, however, only the most recent configuration takes effect. The applications can be installed independently. In fact, they most likely will not be installed on the same server. The quickconfig tool will backup any configuration locally into a cpio file first before running. The main menu of the quickconfig tool has options to:

If a process can not be automated, the Quick Configuration tool echoes a note to the user that a manual change must be done in order for this feature to work. The Quick Configuration tool configures all the software components as a whole and not just a subset of them. For example, the tool assumes CMA must be configured every time when setting up a uOne host. When software is optional (for example, MWI), the user will be prompted. In addition, the tool also configures an NTP client.

The quickconfig tool sets up UMSA separately if requested. The tool asks all questions necessary as they relate to the Directory and Messaging servers. In addition, the Directory Server still needs to be setup with the appropriate schema and indexing attributes.

The quickconfig tool confirms that the certified platform and application releases are valid. It also provides a script - ldapsetup.sh - to provision the database with the proper groups, communities, permissions, and users in order for uOne and UMSA to function properly.


Note It is required that the Directory and Messaging servers are already installed and configured according to the uOne Gateserver Installation and Configuration Manual prior to running the Quick Configuration tool. Information related to these servers is required to successfully complete configuration.

Prerequisites

On the Gateserver where the quick configuration tool is to be run, ensure that all the required platform and application packages have been installed.


Note Depending on which option you choose, the corresponding table (Table 6-2) should be filled out prior to using the Quick Configuration tool. The Notes column is available for this purpose and will greatly facilitate the process. However, note that information presented in the tables will not always correspond to the order in which the questions are presented on the screen.

Steps

Step 1 This tool must be run as superuser.

Step 2 The dapqcfgxx package installs the executable in the $HOME/quickconf/scripts directory.

Step 3 Once in this directory, issue the following command:
./quickconfig

Overview


Table 6-1: Capabilities of Quick Configuration tool
DOES DOES NOT

  • Initial installation only - not reconfiguration. If it is run multiple times, only the most recent configuration is used. The location of previous configuration files is displayed when the tool is executed.

  • Checks and validates that the certified platform and application releases are installed. It does not install interim patches. Check the Release Notes for further instructions about these.

  • Setup Backend Servers (i.e., Messaging, Directory, Paging, etc.). These servers should be setup prior to running this tool, as information from these servers will be needed during configuration.

  • Configure complex installations to include sophisticated dial plans.

The main menu has three options:

    1. Configure Unified Communication System from Scratch

    2. Setup UMSA tool for Subscriber Administration (Netscape 4.1)

    3. Setup UMSA tool for Subscriber Administration (InterMail Mx 5.0)

    4. Exit - You may run quickconfig later


Note If the uOne software is already installed and running, please ensure it is stopped before continuing with the Quick Configuration tool.

After the uOne software has been shutdown—

Currently, answering yes to this will only setup the NTP daemon. Eventually it will tune the kernel and perhaps provide other services.

Option 1 - Configure DAP/Unified Communication Software from Scratch

The following table concerns entries necessary for configuring DAP/uOne System from scratch.


Table 6-2: Information needed for Quick Configuration tool
ITEM DETAIL AVAILABLE ENTRIES NOTES

SNMP & ACB (Step 1 of 7)

Configure Autorestart

This will enable the ACB (BASE) agent and static applications to restart without manual intervention. Also, the agent/applications will be restarted after a reboot.

On, Off

SNMP traps

Send traps for ACB and agent transitions, or application events.

Yes, No

Note If Yes, you will be prompted for the following parameter (SNMP Manager).

SNMP Manager

The name of the SNMP Manager where traps are directed.

Valid SNMP Manager name.

ACB (APP) Object (Step 2 of 7)

MWI Token Routing

Allows the system to send MWI_Off toggles to the actual system with the SMSI link.

Yes, No

If yes, must answer the the next two entries.

MWI Route Token

Defined by mapping the first part of a telephone number to a system that has an SMDI link.

Valid telephone number prefix.

MWI host

Host that will receive the MWI signal.

Valid host name.

CMA (TNT) (Step 3 of 7)

Gatekeeper registration

Registration is needed if the system is engineered to have calls coming through a Gateway.

Yes, No

Silence Compression Setting

If enabled, then the DialPeer must be configured to enable silence compression (vad).

On, Off

DTMF detection

Type of detection required by the node.

RTP, FFT, H245, DEFAULT

If RTP is selected, then the DialPeer must be enabled to allow RTPDTMFRelay.

Gatekeeper

IP address for the Gatekeeper.

Valid IP address.

Note If Gatekeeper is present, you will be prompted for the following two parameters (Tech-Prefix and H323 node).

Tech-Prefix

The prefix that identifies the Gateserver to the Gatekeeper.

Usually in the format of 2#.

H323 node id

The name that will identify this server to the Gatekeeper.

Valid server name.

Send Outbound fax(es)

Enables this system to send outbound fax(es).

Yes, No

Note If Yes, you will be prompted for the following parameter (Gateway), as well as all FAX admin parameters.

Fax Gateway

Name of the Gateway server that will send outbound faxes.

Valid Gateway server.

Switch/Voice Bridge

System connected to either of these devices for the purpose of sending MWI.

Yes, No

Note If Yes, the following four parameters must be addressed.

Baud Rate

19200, 9600, 1200

Data Bits

8,7,6

Stop bits

1,2

Hardware Flow Control

Off, On

UNIFIED MESSAGING

Directory Server
(LDAPhost)

The name of the LDAP host.

Valid Directory Server name.

Bind DN
(LDAPBindDn)

Authority to bind to the Directory Server.

Valid bind entry.

Directory Manager Password
(LDAPDnPassword)

The e-mail password of the above authority.

Valid e-mail (IMAP) password.

Directory Search Base
(LDAPSearchBase)

The DN of the organizational community entry from which uOne can see all the entries that are to be accessed.

Valid search base:

o=
or
ou= ,o=

Activate Personal Access Support (SNAMode)

Allows Personal Access to be available to subscribers.

Enabled/Disabled

Initial Application

Scheduled application to be launched.

UM

Note TELdemo is available for test purposes only.

DNIS/RDNIS

This is the number (token) needed to launch UM or TNTdemo agent.

Valid 1-10 digit number.

FAX admin

Fax admin account name.

Valid FaxAdmin account.

Mail Server of the Fax admin account.

Valid Messaging Server.

Fax admin account password.

Password for FaxAdmin account.

Name of the FaxPrint IMAP retry folder.

Postmaster address for FaxPrint errors.

Note Faxes will not print unless Fax Services are enabled via the COS and the DialMap.ini file is configured correctly.

Notification entries

SMS services

Yes/No

Note If yes, the following two parameters must be addressed.

SMS administration account

Valid account name.

Messaging Server

Valid host name.

Notification requests

Yes, No

If Yes, run MWI_OnOff (which receives request from MWI_PassOff)


Note Reboot for all changes to take effect.

Options 2 and 3 - Setup UMSA tool for Subscriber Administration

The following table concerns entries necessary for setting up the UMSA tool for Subscriber Administration.


Table 6-3: Setup UMSA tool for subscriber administration
ITEM DETAIL AVAILABLE ENTRIES NOTES

Netscape Directory Server

Name

Root Bind DN

Designated during Directory Server installation.

Root Bind DN Password

Designated during Directory Server installation.

Root Search Base

Designated during Directory Server installation.

UMSA authority name

Reference unique name.

Database Root Organization Name

Designated during Directory Server installation.

Community Search Base

Reference ou=

Community group

Reference unique location of UMSA users.

Community UMSA login name

Login used to access UMSA.

Netscape Messaging Server

Name

Supported Mail Domain Name

Designated during Messaging Server installation

Postmaster account

Designated during Messaging Server installation

UMSA Login Name

UMSA login


Table 6-4: Installation summary
Required Optional

  • Install and administer Unified Messaging Web Administration (UMSA)

  • Install and configure Cisco software on the directory server

  • Install and configure Gateserver, to include

    • ACB

    • uOne agent

    • other agents

  • Administer uOne application

  • UMSA Group Administration

  • Administer Communities of Interest

  • Administer Classes of Service

  • Administer Addressing Rules

  • Administer Users

  • Personal Messaging Administrator (PMA)

  • Install and configure optional software on the Gateserver

    • TTS libraries

    • FaxPrint application

  • Administer

    • inbound and outbound fax

    • Email/Text-to-Speech

    • Paging

  • Install and Administer Notification Services

  • Install and Administer Streaming Services


hometocprevnextglossaryfeedbacksearchhelp
Posted: Mon Sep 25 19:21:53 PDT 2000
Copyright 1989-2000©Cisco Systems Inc.