3COM 900-0410-01 User Manual

IP Conferencing Module Installation Guide

3Com® Convergence Applications Suite VCX System Release 7.2

http://www.3com.com/

Part Number 900-0410-01 Published October 2006

3Com Corporation 350 Campus Drive Marlborough, MA 01752-3064

Copyright © 2006, 3Com Corporation. All rights reserved. No part of this documentation may be reproduced in any form or by any means or used to make any derivative work (such as translation, transformation, or adaptation) without written permission from 3Com Corporation.

3Com Corporation reserves the right to revise this documentation and to make changes in content from time to time without obligation on the part of 3Com Corporation to provide notification of such revision or change.

3Com Corporation provides this documentation without warranty of any kind, either implied or expressed, including, but not limited to, the implied warranties of merchantability and fitness for a particular purpose. 3Com may make improvements or changes in the product(s) and/or the program(s) described in this documentation at any time.

UNITED STATES GOVERNMENT LEGENDS:

If you are a United States government agency, then this documentation and the software described herein are provided to you subject to the following:

United States Government Legend: All technical data and computer software is commercial in nature and developed solely at private expense. Software is delivered as Commercial Computer Software as defined in DFARS 252.227-7014 (June 1995) or as a commercial item as defined in FAR such is provided with only such rights as are provided in 3Com’s standard commercial license for the Software. Technical data is provided with limited rights only as provided in DFAR 252.227-7015 (Nov

1995) or FAR portion of any legend provided on any licensed program or documentation contained in, or delivered to you in conjunction with guide.

Unless otherwise indicated, 3Com registered trademarks are registered in the United States and may or may not be registered in other countries.

3Com and the 3Com logo are registered trademarks of 3Com Corporation. VCX is a trademark of 3Com Corporation.

Other brand and product names may be registered trademarks or trademarks of their respective holders.

52.227-14 (June 1987), whichever is applicable. You agree not to remove or deface any

2.101(a) and as

CONTENTS

ABOUT THIS GUIDE

Conventions 5

Notices 5

Text 6 Related Documentation 6 Comments 7

1 PRE-INSTALLATION

Configuration Options 9

Option 1: Single Server 9

Option 2: Dual Server 10

Option 3: Multiple Servers (Four to Twelve) 11

Post-installation Setup 12 Gathering Site Information 13

Using DNS 13

Single Server 14

Dual Servers 14

Multiple Servers (Four to Twelve) 14 Worksheet 15

2 INSTALLATION SCRIPTS

Overview of Components 17 Initial Installation - Services Installed 18 Initial Installation - Configuration Guidelines 19 Single Server Initial Installation 22

Sample vcx-setup Script (All-in-one server) 22 Dual Server Initial Installation 38

Sample vcx-setup Script (Primary server) 38

Sample vcx-setup Script (Secondary server) 53 Multiple Server Initial Installation 65

Sample vcx-setup Script (Primary server) 65

Sample vcx-setup Script (Secondary server) 80 Sample vcx-setup Script (Conference server) 92

Post Installation Configuration 104

Set up Conference Server Routes 104 Set up Conference Attendant Routes 105 Trusted Host Configuration 106 Test E-Mail Notification Setup 108

Upgrade Installation 109

Distributed Implementation Upgrade Guidelines 109 Sample install-upgrade Script 109 Sample vcx-switchversion Script 112

Managing the Activation Keys 113

3 OBTAINING SUPPORT FOR YOUR PRODUCT

Register Your Product 115 Purchase Value-Added Services 115 Troubleshoot Online 116 Access Software Downloads 116 Telephone Technical Support and Repair 116 Contact Us 117

INDEX

ABOUT THIS GUIDE

This section contains an overview of this guide, lists guide conventions, related documentation, and product compatibility.

This guide describes how to answer the questions in the installation scripts, which run when you first start a 3Com Server. By providing the correct answers to the script questions, you configure the system for initial operation.

This guide is intended for equipment installers who have a thorough understanding of telecommunications, VoIP technology, Linux operating systems, databases, networks, and system administrator privileges.

Release Notes are issued with some products. If the information in the release notes differs from the information in this guide, follow the instructions in the release notes.

Conventions This section describes notice, text, and figure conventions.

Notices Tab le 1 lists notice icons.

Ta bl e 1 Notice Icon Descriptions

Icon Notice Type Description

Information note Information that describes important features or

instructions

IP Conferencing Module

Caution Information that alerts you to potential loss of

data or potential damage to an application, system, or device

Warning

Information that alerts you to potential personal injury

6 ABOUT THIS GUIDE

Te xt Ta bl e 2 lists text conventions.

Ta bl e 2 Text Convention Descriptions

Convention Description

Screen displays This typeface represents information as it appears on the

screen.

Commands The word “command” means that you must enter the

command exactly as shown and then press Return or Enter. Commands appear in bold. Example:

To remove the IP address, enter the following command:

SETDefault !0 -IP NETaddr = 0.0.0.0

Words in italics Italics are used to:

n Emphasize a point.

n Denote a new term at the place where it is defined in

the text.

n Identify menu names, menu commands, and software

button names. Examples:

From the Help menu, select Contents.

Click OK.

Comments 7

The following documents are a part of the IP Messaging Module:

n IP Messaging Module Product Overview

n IP Messaging Module Quick Reference Guide - 3Com Native Interface

n IP Messaging Module User Guide - 3Com Native Interface

n IP Messaging Module Quick Reference Guide - Traditional Interface

n IP Messaging Module User Guide - Traditional Interface

n IP Messaging Module Operations and System Administration Guide

n E-Mail Reader Application Quick Start Guide

The following documents are a part of the IP Conferencing Module:

n IP Conferencing Module Installation Guide

n IP Conferencing Module User Guide

n IP Conferencing Module Administration Guide

The following documents provide information on products that support this release:

n Enterprise Management Suite User Guide

n Enterprise Management Suite Getting Started Guide

n V7111 Analog Media Gateway Fast Track Installation Guide

n V7111 Analog Media Gateway User Guide

n V6000 Analog Media Gateway Fast Track Installation Guide

n V6000 Analog Media Gateway User Guide

n V7122 Digital Media Gateway Fast Track Installation Guide

n V6100 Digital Media Gateway Fast Track Installation Guide

n V7122 and V6100 Digital Media Gateway User Guide

Comments Send e-mail comments about this guide or about any Voice product

documentation to:

VOICE_Techcomm_comments@3com.com

Include the following information with your comments:

n Document title

n Document part number (found on the front page)

8 ABOUT THIS GUIDE

n Page number

n Your name and organization (optional)

Example:

IP Conferencing Module Installation Guide System Release 7.1

Part Number 900-0353-01 Page 25

Please address all questions regarding 3Com software to your authorized 3Com representative.

PRE-INSTALLATION

This chapter provides pre-installation guidelines for the 3Com IP Conferencing Module, which is an optional component of the 3Com

™

V7000 IP Telephony System.

VCX

n Configuration Options

n Gathering Site Information

n Worksheet

Configuration Options

Option 1: Single

Server

This section describes sample hardware/software configurations that support the 3Com IP Conferencing Module.

Three basic configurations are possible. The option you select depends on the number of hardware servers you have. A minimum of one and a maximum of twelve servers are supported.

All hardware servers run the 3Com VCX™ Linux operating system. Definitions of these servers are contained in the 3Com price list.

If you only have one server, then all software components must be installed on it.

Components installed on the single server:

n conference server/conference attendant server

n presence server (if purchased)

n VCX user database

n conferencing and presence database (master)

n web console server.

10 CHAPTER 1: PRE-INSTALLATION

Figure 1 Network diagram - single server

Conference server pool

Conference server Presence server Master database User database Web server

VCX or NBX server

Option 2: Dual Server If you have two servers, configure the primary server as a “provisioning”

server by installing the web console server, initial master database, VCX user database, presence server, and conference server on it. Configure the secondary server with the initial slave database and the conference server. The database pair (master and slave) provides redundancy, with the slave maintaining a copy of the master using MySQL database replication. In the event the slave cannot communicate with the master for ten minutes, switchover occurs. Note that both servers in a dual-server configuration can host conferences.

Components installed on the primary server:

n conference server/conference attendant server

n presence server (if purchased)

n VCX user database

n conferencing and presence database (initial master)

n web console server.

Components installed on the secondary server:

n conference server/conference attendant server

n conferencing and presence database (initial slave).

Figure 2 Network diagram - two servers

Conference server pool

Conference server Presence server Master database User database Web console

Conference server Slave database

Configuration Options 11

Option 3: Multiple

Servers (Four to

Twelve)

Primary

Server

VCX or NBX server

Secondary

Server

Both servers in the conference pool use their eth0 interface to connect to the network.

If you have between four and twelve servers, configure the primary server as a “provisioning” server by installing the web console server, presence server, master database, and VCX user database on it. Configure the secondary server with the initial slave database. The database pair (master and slave) provides redundancy. Configure all other servers in the pool with the conference server. Note that up to ten servers in a multi-server configuration can host conferences.

Components installed on primary server:

n presence server (if purchased)

n VCX user database

n conferencing and presence database (initial master).

n web console server.

Components installed on secondary server:

n conferencing and presence database (initial slave).

Components installed on all other servers:

n conference server/conference attendant server.

12 CHAPTER 1: PRE-INSTALLATION

Figure 3 Network diagram - multiple servers

Conference

server

Presence server Master database User database Web server

Conference server pool

Conference

server

Slave database

Conference

server

Conference

server

Conference

server

Post-installation

Setup

Primary

Server

Secondary

Server

VCX or NBX server

All servers in the pool use their eth0 interface to connect to the network.

Upgrades

Following the initial implementation, the system can be upgraded in order to increase system capacity or provide database redundancy. For example, adding a second server to a single-server implementation will provide database redundancy.

Upgrades can be performed at any time on fully operational systems. There is no need to disable any applications that are currently running when you add a new server.

After you run the installation script and assign a role to the servers in your network, you need to configure the following:

Setting up a Route to the Conference Servers

You must configure the VCX dial plan with a route to your conference server pool. If your implementation has only one server, then a route to a single endpoint is required. If your implementation has multiple servers, then a route to multiple endpoints are required in order to provide redundancy.

Gathering Site Information 13

Once the route is set up, the VCX system will forward conference calls to the designated endpoints—conference servers that provide a “routing” function by redirecting calls to ”hosting” conference servers. A single conference server can provide both routing and hosting functionality.

Setting up a Route to the Conference Attendant Servers

As with conference servers, it is necessary to configure a route for conference attendant servers. The VCX dial plan is used for this purpose. If you have only one server, then a route to a single endpoint is required. If you have multiple servers, then a route to at least two endpoints are required for redundancy.

Test E-Mail Notification Setup

You must test the e-mail setup by logging in to the system and sending an e-mail message using Send-only Simple Mail Transfer Protocol (sSMTP). If you fail to receive the test e-mail message, you can check for errors in /opt/logs/vcx-linux/maillog.

Adding the Presence Server as a Trusted Host

Gathering Site Information

Using DNS 3Com recommends that you configure your DNS servers so that they

To enable presence to function properly, you must add the presence server to the VCX system as a trusted host.

The 3Com VCX V7000 hardware servers communicate with each other using IP addresses. These addresses must be dedicated (static) and must be compatible with your network design.

One or more 3Com IP Conferencing Module servers may be added to a VCX system.

know the IP addresses of all VCX servers and gateways. If you prefer to not use DNS, you can edit the /etc/hosts files on the IP Conferencing Module and all of the VCX servers.

3Com does not support NIS or WINS as domain name resolution methods for VCX products.

14 CHAPTER 1: PRE-INSTALLATION

Single Server If your network contains a single server, you require the following:

n You must dedicate one IP address to the 3Com IP Conferencing

n You must assign a host name to the 3Com IP Conferencing Module.

n You must know the IP address of the network gateway.

n You must know the IP addresses of the primary and secondary DNS

n You must know the IP addresses of the primary and secondary NTP

Dual Servers If your network contains two servers, you require the following:

n You must dedicate an IP address to each of the two 3Com IP

n You must assign a unique host name to each of the two 3Com IP

Both servers must belong to the same domain.

Module.

servers.

Conferencing Modules.

Multiple Servers (Four to Twelve)

n You must know the IP address of the network gateway.

n You must know the IP addresses of the primary and secondary DNS

servers.

n You must know the IP addresses of the primary and secondary NTP

servers.

If your network contains four to twelve servers, you require the following:

n You must dedicate an IP address to each 3Com IP Conferencing

Module in the network.

n You must assign a unique host name to each 3Com IP Conferencing

Module in the network.

All servers must belong to the same domain.

n You must know the IP address of the network gateway.

n You must know the IP addresses of the primary and secondary DNS

servers.

n You must know the IP addresses of the primary and secondary NTP

servers.

Worksheet 15

Worksheet To make it easier to configure your system, you may want to have the

necessary information in front of you before you begin to install any server.

Ta bl e 3 Network Configuration Parameters

Configuration Parameter Value

3Com IP Conferencing Module IP address (eth0)

3Com IP Conferencing Module host name

Subnetwork mask

Gateway IP address

Primary DNS server IP address

Secondary DNS server IP address

DNS search path

Primary NTP server IP address

Secondary NTP server IP address

Continent

Country

Time Zone

Ta bl e 4 System Configuration Parameters

Configuration Parameter Value

Services:

1. Presence and Conference - all in one

2. Conferencing server

3. Conferencing and database server

4. Data server for presence and conferencing

5. Presence server (with database)

16 CHAPTER 1: PRE-INSTALLATION

Ta bl e 5 E-Mail Notification Parameters

Configuration Parameter Value

Mailhub (computer that handles mail)

Hostname of your computer

Mail name of your system

System user e-mail address

Ta bl e 6 Database Configuration Parameters

Configuration Parameter Value

Database:

1. Local Master: this server will have the master db

2. Local Slave: this server will have the slave db

3. Remote database: db is on another server

Ta bl e 7 Initial Configuration Parameters

Configuration Parameter Value

Domain name of organization

Administrator’s e-mail address

Activation key(s)

Minimum value for numeric conference names

Maximum value for numeric conference names

Prefix for Ad Hoc conference names

IP address of the primary dialout proxy

IP address of the secondary dialout proxy

Digit Map for DTMF dialout

VCX server Site ID (enter on master only)

VCX Server IP address (primary server: eth0)

Username for VCX database synchronization

Password for VCX database synchronization

INSTALLATION SCRIPTS

This chapter describes the initial configuration of each 3Com IP Conferencing Module server in a VCX system. All software components run on each server.

The installation scripts are run on command. Each time a script prompts you for a response, you can accept the default (preconfigured) value by pressing the Return or Enter key, or you can manually enter a different value.

If necessary, you can re-run the scripts and enter new values.

Verify that all the procedures outlined in Chapter 1, “Pre-Installation” have been completed before continuing with this chapter.

This chapter contains information on the following:

Overview of Components

n Overview of Components

n Initial Installation - Services Installed

n Initial Installation - Configuration Guidelines

n Single Server Initial Installation

n Dual Server Initial Installation

n Multiple Server Initial Installation

n Post Installation Configuration

n Upgrade Installation

n Managing the Activation Keys

This section provides a general description of the various components of the IP Conferencing Module.

18 CHAPTER 2: INSTALLATION SCRIPTS

n Web Provisioning Server — Allows for the creation of conferences and

maintenance of the server.

n Conference Server — Allows SIP devices to join conferences that

support any or all of audio, video, and desktop sharing communication modes.

n Conference Attendant — Allows users to join conferences by dialing a

single access number independent of conference ID. The attendant prompts the user for the conference ID, and if required, the conference passcode.

n Presence Server — Collects and distributes the online status

information of users.

n Conference and Presence Server Database — Database of IP

Conferencing Module activity. On systems with two or more servers, a single database pair (master and slave) is supported.

n VCX user database — Database of VCX system users.

Initial Installation Services Installed

When you perform an initial software installation (a “fresh” install), you must run the setup script for each hardware server in your conference server pool. The script provisions the following services on the hardware server:

Network Configuration — For the initial installation, you are prompted to enter general networking settings.

System Configuration — The script prompts you to select the configuration that matches the services you have purchased. Select one of the following:

n Presence and Conference (All-in-one): Installs all components,

including the conference server, conference attendant server, web server, VCX user database, and conference & presence database.

n Conferencing server: Installs the conference server and conference

attendant server.

n Conferencing and database server: Installs the conference server,

conference attendant server, and conference & presence database.

n Data server for presence and conferencing: Installs the conference &

presence database.

Initial Installation - Configuration Guidelines 19

n Presence server (with database): Presence server, web server, VCX user

database, and conference & presence database.

E-Mail (sSMTP) Configuration — This portion of the script configures the Send-only Simple Mail Transfer Protocol (sSMTP) that enables the system to send e-mail notifications when conferences are created or modified, or when users add contacts to their buddy lists.

Database Configuration — Select a database configuration for this server. Select “Local Master” if the server is going to host the master database (All-in-one server, or primary server in a distributed system). Select “Local Slave” if the server is going to host the slave database (secondary server in a distributed system). Select “Remote database” if the server is not going to host a database (all servers except the primary and secondary servers in a distributed system).

IP Conferencing Module Configuration — Contains parameters for the VCX system software components, including the IP Conferencing Module. Activation keys are entered in this portion of the script.

Initial Installation Configuration Guidelines

Follow these general guidelines when you perform an initial software installation. The installation varies depending on the number of servers you have (one, two, or more).

Single Server Configuration

General installation steps:

1 On the single server, run the vcx-setup script:

a When prompted to select the services the system will provide, select 1

(presence and conference - all in one).

b When prompted to select a database configuration, select 1 (Local

Master: this server will have the master database).

c When prompted to start the 3Com IP Conferencing Services, enter Y.

2 Complete the post-installation configuration (see Post Installation

Configuration).

20 CHAPTER 2: INSTALLATION SCRIPTS

Dual Server Configuration

General installation steps:

1 On the primary server, run the vcx-setup script:

a When prompted to select the services the system will provide, select 1

(presence and conference - all in one).

b When prompted to select a database configuration, select 1 (Local

Master).

c When prompted to start the 3Com IP Conferencing Services, enter Y.

All services will start except DB_watchdog. It starts after the secondary server is installed and the database replication process is initiated.

2 On the secondary server, run the vcx-setup script:

a When prompted to select the services the system will provide, select 3

(Conferencing and database server).

b When prompted to select a database configuration, select 2 (Local

Slave).

c When the script asks whether you have run remote_access.sh, do the

following:

n On the primary server, run remote_access.sh <secondary-server

hostname | IP>

d Return to the secondary server and enter Y at the prompt.

e When prompted, enter the password of the primary (master) server.

f When prompted to start the 3Com IP Conferencing Services, enter Y.

3 Complete the post-installation configuration (see Post Installation

Configuration).

Multiple Server Configuration (Four to Twelve Servers)

General installation steps:

1 On the primary server, run the vcx-setup script:

a When prompted to select the services the system will provide, select 5

(Presence server with database).

b When prompted to select a database configuration, select 1 (Local

Master).

c When prompted to start the 3Com IP Conferencing Services, enter Y.

Initial Installation - Configuration Guidelines 21

All services will start except DB_watchdog. It starts after the secondary server is installed and the database replication process is initiated.

2 On the secondary server, run the vcx-setup script:

a When prompted to select the services the system will provide, select 4

(Data server for presence and conferencing).

b When prompted to select a database configuration, select 2 (Local

Slave: this server will have a slave database).

c When prompted, enter the hostname of the primary (master) server.

d When the script asks whether you have run remote_access.sh, do the

following:

n On the primary server, run remote_access.sh <secondary-server

hostname | IP>

e Return to the secondary server and enter Y at the prompt.

f When prompted, enter the password of the primary (master) server.

g When prompted to start the 3Com IP Conferencing Services, enter Y.

3 On each of the conference servers (up to ten), run the vcx-setup script:

a When prompted to select the services the system will provide, select 2

(Conferencing server).

b When prompted to select a database configuration, select 3 (Remote

database: database is on another server).

c When prompted, enter the hostname of the primary (master) server.

d When the script asks whether you have run remote_access.sh, do the

following:

n On the primary (master) server, run remote_access.sh

<conference-server hostname | IP>

n On the secondary (slave) server, run remote_access.sh

<conference-server hostname | IP>

e Return to the conference server and enter Y at the prompt.

f When prompted to start the 3Com IP Conferencing Services, enter Y.

4 Complete the post-installation configuration (see Post Installation

Configuration).

Run the vcx-setup script only for “fresh” software installations where the VCX Linux server is not already running the IP Conferencing Module.

22 CHAPTER 2: INSTALLATION SCRIPTS

When configuring the network parameters on the VCX Linux server, make sure you specify the fully qualified domain name for your system, not just the hostname. For example, use conf01.yourcompany.com not conf01.

Use a local connection to the server to complete the initial software installation.

The vcx-setup script is divided into five sections:

n network configuration

n system configuration

n e-mail configuration

n database configuration

n initial configuration.

These sections run automatically after the command “vcx-setup” is entered.

Single Server Initial Installation

Sample vcx-setup

Script (All-in-one

server)

1 Log in to the server as root.

2 Enter a password (default is pvadmin).

3 Press Enter (or Return).

-bash-2.05b# vcx-setup

The section contains a sample script of the vcx-setup script for the single server (all-in-one) configuration).

The following options are selected in this sample script:

n All-in-one system configuration (installs the conference server,

conference attendant server, web server, VCX user database, and conference & presence database)

n Master database configuration.

The vcx-setup script displays the current settings and then asks you if you want to accept or update them. Sample answers are provided in bold type along with explanations of those answers. Explanations are in italics.

To run the vcx-setup script:

Single Server Initial Installation 23

Enter vcx-setup at the command prompt.

---------------------------------------------------------------------------

---------- Welcome to the VCX Linux Network Configuration Wizard ----------

--------------------------------------------------------------------------This wizard sets up networking and related services.

Start of Network Configuration

Configure networking now? [yes] :

Press the Enter or Return key to accept yes as the suggested answer.

--------- Configuring Dynamic Host Configuration Protocol (DHCP) ----------

VCX servers can use DHCP for automated configuration, but this requires that the DHCP server is configured to provide the proper options. Unless you know that your environment is set up in this way, you should say 'no' here and configure static network parameters.

Use DHCP on eth0 to configure network parameters? [no] :

---------- Configuring Hostname ---------Enter system hostname [localhost] : conf01.yourcompany.com

---------- Configuring IP Interface 'eth0' ---------Enter IP Address [192.168.1.100 ] : 10.20.30.60 Enter Network Subnet Mask [255.255.255.0 ] : 255.255.255.0 Enter Default Gateway Address [10.20.30.254 ] : 10.20.30.254

---------- Configuring IP Interface 'eth1' ---------Interface State : disabled

Note that ‘eth1’ is not used for the 3Com IP Conferencing Module.

---------- Configuring DNS Servers ---------Enter DNS servers one at a time. When done, enter 0.0.0.0 to stop. Primary DNS Server [192.168.1.1] : 10.25.10.31 Secondary DNS Server [192.168.1.2] : 10.26.10.31 Tertiary DNS Server [0.0.0.0] : 0.0.0.0

---------- Configuring DNS Search Path ---------Press Enter to leave the current path unchanged, or specify a new search path, with spaces separating each entry.

DNS Search Path []: yourcompany.com

24 CHAPTER 2: INSTALLATION SCRIPTS

---------- Configuring Network Time Protocol ---------Enter NTP servers one at a time. When done, enter 0.0.0.0 to stop.

Primary NTP Server [192.168.1.253] : 10.35.10.51 Secondary NTP Server [192.168.1.252] : 10.36.10.51 Additional NTP Server : 10.1.0.3

-------------------------- Configuring Time Zone --------------------------

Please select a geographic location from the following list:

1. Africa

2. Americas

3. Antarctica

4. Arctic Ocean

5. Asia

6. Atlantic Ocean

7. Australia

8. Europe

9. Indian Ocean

10. Pacific Ocean Enter continent [2] :

Press the Enter or Return key to accept 2 as the suggested answer.

Please select a country from the following list:

1. Antigua & Barbuda 18. Ecuador 35. Panama

2. Anguilla 19. Grenada 36. Peru

3. Netherlands Antilles 20. French Guiana 37. St Pierre & Miquelon

4. Argentina 21. Greenland 38. Puerto Rico

5. Aruba 22. Guadeloupe 39. Paraguay

6. Barbados 23. Guatemala 40. Suriname

7. Bolivia 24. Guyana 41. El Salvador

8. Brazil 25. Honduras 42. Turks & Caicos Is

9. Bahamas 26. Haiti 43. Trinidad & Tobago

10. Belize 27. Jamaica 44. United States

11. Canada 28. St Kitts & Nevis 45. Uruguay

12. Chile 29. Cayman Islands 46. St Vincent

13. Colombia 30. St Lucia 47. Venezuela

14. Costa Rica 31. Martinique 48. Virgin Islands (UK)

15. Cuba 32. Montserrat 49. Virgin Islands (US)

16. Dominica 33. Mexico

17. Dominican Republic 34. Nicaragua Enter country [44] :

Press the Enter or Return key to accept 44 as the suggested answer.

Please select a time zone from the following list:

1. Alaska Time

2. Alaska Time - Alaska panhandle

3. Alaska Time - Alaska panhandle neck

4. Alaska Time - west Alaska

5. Aleutian Islands

6. Central Time

7. Central Time - Michigan - Wisconsin border

8. Central Time - North Dakota - Oliver County

9. Eastern Standard Time - Indiana - Crawford County

10. Eastern Standard Time - Indiana - Starke County

11. Eastern Standard Time - Indiana - Switzerland County

12. Eastern Standard Time - Indiana - most locations

13. Eastern Time

14. Eastern Time - Kentucky - Louisville area

15. Eastern Time - Kentucky - Wayne County

16. Eastern Time - Michigan - most locations

17. Hawaii

18. Mountain Standard Time - Arizona

19. Mountain Time

20. Mountain Time - Navajo

21. Mountain Time - south Idaho & east Oregon

22. Pacific Time Enter zone [13] : Selected Time Zone: America/New_York

Single Server Initial Installation 25

-------------------------- CONFIGURATION SUMMARY -------------------------DHCP state: disabled

Hostname: conf01.yourcompany.com

IP Interfaces: Device IP Address Network Mask Default Gateway

eth0 10.20.30.60 255.255.0.0 10.20.30.254 eth1 (interface is disabled)

DNS Servers: 10.25.10.31

10.26.10.31

Search Domains:yourcompany.com

NTP Servers: 10.35.10.51

10.36.10.51

10.1.0.3

Time Zone: America/New_York

---------------------------------------------------------------------------

26 CHAPTER 2: INSTALLATION SCRIPTS

Is all of the above information correct? [yes] :

---------------------------------------------------------------------------

--------------------------------------------------------------------------Please wait while the wizard completes. Saving configuration...Done.

End of Network Configuration

The network configuration is complete. If necessary, you can re-run this portion of the script by entering vcx-config-network -wizard.

Start of System Configuration

After successful completion of the network configuration, the script will prompt you to select a set of services.

----------------------- Select System Configuration -----------------------

Individual systems may provide various services in a VCX installation.You must select the appropriate set of services which this system is to provide. Be certain that the selection corresponds to the functionality you have purchased.

Which services will this system provide?

1. Presence and Conference - all in one

2. Conferencing server

3. Conferencing and database server

4. Data server for presence and conferencing

5. Presence server (with database)

Enter your choice (1-5) : 1

Select “1” to install the following components:

- conference server

- conference attendant server

- presence server

- web server

- VCX user database

- conference & presence database.

Single Server Initial Installation 27

You have chosen to configure this system to provide:

Presence and Conference - all in one

Note that in order for these services to work, you must have purchased an appropriate license and installed the corresponding license activation key on this system.

*** WARNING *** Once you confirm your selection, you cannot change it.

Are you absolutely certain that you wish to configure this system as an 'Presence and Conference - all in one' server?If you answer 'no' here you can choose an alternative configuration.

Confirm selection? [no] : y

Confirm your selection by typing “y.”

Selection confirmed.

*** Assembling VCX.2.9.3 using 'VSBOM.xml' *** *** Processing components *** *** Executing assembly commands *** *** Assembly complete ***

The VCX assembly has been created. Preparing system for use:

Performing early startup tasks: [ OK ]

Starting VCX-Firewall: [ OK ]

Starting httpd:

Removing unneeded application components from the system. This may take several minutes. Please wait while the operation completes.

Determining which packages are not used by any VCX version:

oem.7.0.1 : [keep; used in 2.9.3] presconf.2.5.3 : [keep; used in 2.9.3] presconf-conf.2.5.3 : [keep; used in 2.9.3] presconf-presence.2.5.3 : [keep; used in 2.9.3] presconf-vcxdb.2.5.3 : [keep; used in 2.9.3] presconf-web.2.5.3 : [keep; used in 2.9.3]

28 CHAPTER 2: INSTALLATION SCRIPTS

vcx-firewall.1.5.5 : [keep; used in 2.9.3] mysql.3.23.58 : [keep; used in 2.9.3]

No extra packages were found.

End of System Configuration

The system configuration is complete. If necessary, you can re-run this portion of the script by entering vcx-setconfigtype.

Start of E-mail (sSMTP) Configuration

After successful completion of the system configuration, the script will prompt you to set up the e-mail notification utility. The utility sends e-mails when conferences are created and modified, and when users attempt to add contacts to their buddy lists. E-mail notification works once users have added their e-mail addresses to the 3Com IP Conferencing Module.

Configuration for sSMTP

(1) mailhub This is the computer responsible for handling your outgoing mail. It could be the SMTP server of your ISP, or a departmental mailhub. Use the fully-qualified domain name (foo.bar.baz) of the mailhub; if it uses an unusual SMTP port number, use the colon syntax foo.bar.baz:2525 Otherwise sSMTP will use the standard SMTP port number (25). (Note that sSMTP can support a user-dependent mailhub with the 'reverse aliases' feature, for which see the man page.)

Please enter your mailhub []: mail.yourcompany.com

Enter the fully qualified domain name of the computer handling outgoing mail.

(2) FromLineOverride This specifies how sSMTP handles the From: line of outgoing mail. If FromLineOverride=YES, sSMTP will leave the From: line alone if it already exists. If FromLineOverride has any other value, or there is no From: line, sSMTP creates the From: line using your username (or the -f command-line option), and the value of the rewriteDomain option (step (4), below). If you use a mail user agent (MUA; e.g. mutt, pine) I recommend using YES and having the MUA set the From: line. (Exception: the 'reverse aliases' feature can be used to set up a particular From:

Single Server Initial Installation 29

address for each user, in which case don't use FromLineOverride=YES. See the man page.)

FromLineOverride? [YES]:

Specify how sSMTP handles the From: line of outgoing mail.

(3) hostname sSMTP uses the hostname of your computer to identify itself to the mailhub, and in the Received: headers of the outgoing mail. This has relatively little effect on how the mail is handled. Use the fully-qualified domain name (FQDN) of your computer(foo.bar.baz). If it doesn't have a FQDN, use some name for your box.

Hostname of your box [conf01.yourcompany.com]:

Enter the host name of your computer handling outgoing mail.

(4) rewriteDomain Please enter the mail name of your system. sSMTP uses this value to add a domain to unqualified e-mail addresses(addresses without an @-sign). You probably want to use the domain from your own e-mail address.You probably want to set up your MUA to handle unqualified addresses itself, in which case sSMTP will never have to use this.

Mail name [conf01.yourcompany.com]:yourcompany.com

Enter the mail name of your system.

(5) root Last and least: if sSMTP finds an unqualified e-mail address among the recipients, and it corresponds to a username on your local machine with a userid less than 1000, then the e-mail is sent to this value instead. The idea is that mail sent to 'root' should probably go to 'postmaster' instead.

If you set up your MUA to do its own handling of unqualified addresses, this is irrelevant. Use the default value of 'postmaster' or your own e-mail address if you're paranoid.

System users receive mail at [postmaster]:postmaster

Enter the system user e-mail address.

Note: check with your e-mail administrator for the proper system user e-mail address.

Wrote configuration file /etc/ssmtp/ssmtp.conf

Starting mysqld daemon with databases from /opt/3comdata/mysql

30 CHAPTER 2: INSTALLATION SCRIPTS

Tcl is already installed Tcl version is 8.3 Please report any installation problem to "3Com Support" <support@3com.com>

End of E-mail (sSMTP) Configuration

The e-mail configuration is complete. If necessary, you can re-run this portion of the script by entering usr/sbin/smtp-configure.

Start of Database Configuration

After successful completion of the e-mail configuration, the script will prompt you to select a database configuration.

There are different ways to install and access the database. 1 Local Master: this server will have the master database. 2 Local Slave: this server will have a slave database. 3 Remote database: database is on another server. Please choose one of the above options: 1

Select “1” to specify that this server will initially host the master database (All-in-one server, or primary server in a distributed system).

Available applications: sipconf,sipvxml,gui,vcxdb,sippeng,

End of Database Configuration

The database configuration is complete. If necessary, you can re-run this portion of the script by entering presconf-setup.

Start of IP Conferencing Module Configuration

After successful completion of the database configuration, the script will prompt you to select an initial configuration.

Enter the fully qualified hostname for this installation. [host.yourcompany.com]:

Enter the fully qualified hostname of the machine you are installing on.

Assuming the userid of the administrator who will manage the applications for your domain is root

+ 90 hidden pages