The following are requirements for the Conferencing installation unless noted as optional.
Required packages: Before running the installer, you need to install the following packages:
neon
postgresql
postgresql-libs
postgresql-server
Emacs
apache2
php5
Installing the neon, postgresql, and postgresql-server packages: The PostgreSQL database server must be installed on one of the Conferencing hosts. A default Linux installation does not install the PostgreSQL database server. You must choose to install it explicitly. When installing the PostgreSQL software, select the postgresql server software. After you have installed the PostgreSQL software, the Conferencing installation initializes the database.
You need to install the libneon and libpq libraries before running the installer. On SUSE Linux Enterprise Server (SLES) 10, these libraries are not installed on the system by default. The libneon library is inside the neon RPM. If you are installing on a 64-bit server, you must use neon-32bit and postgresql-libs-32bit to complete the install. These are contained in the postgresql RPM.
The neon, postgresql, and postgresql-server packages should be available from the original installation media or from the online update. Install dependencies as required.
NOTE:Ensure that you do not have any existing PostgreSQL databases on any of the servers in the Conferencing cluster.
Time synchronization: All Conferencing hosts must be time-synchronized and the system time zones must all be consistent. To maintain accurate system time, you can configure reliable time servers inor manually with /etc/ntp.conf and /etc/ntp/step-tickers on SLES (see the ntpd(1) man page).
Emacs: During the installation, you have the opportunity to edit both the new user and invitation templates. You can do this by editing the templates and then importing them, or by using Emacs on an install host. If you are going to use Emacs on an install host, ensure that Emacs has been installed, because it might not be part of the default Linux installation and must be explicitly installed.
License key: The installation script asks you to provide a license key (license-key.xml) for the Conferencing Server. Make sure this file is in the sitescape-conferencing directory that contains install.sh (the directory files exist after you unpack the compressed tar archive). For more information, see Unpacking the Files.
You must define at least three static IP addresses that are used by Conferencing clients to connect to Conferencing services. The services that Conferencing clients connect to are the XML router, Web portal and desktop/application share server. The XML router and Web portal each require their own individual IP addresses. The desktop and application share services use the same IP address. If any of the Conferencing clients are outside your firewall, the IP addresses must be externally accessible.
For example:
192.168.1.1:80
:443 --> XML Router
:1270
192.168.1.2:80 --> Web portal
:443 (port 443 required if using SSL)
192.168.1.3:80
:443 --> Desktop and Application Share
:1270
VoIP requires two additional IP addresses. For more information, see VoIP Requirements.
XML router IPs: IP addresses have ports 1270, 443, and 80 open.
Desktop/Application Sharing IPs: IP addresses have ports 1270, 443, and 80 open.
Web portal IPs: You must have port 80 open.
NOTE:Port 443 must be open if you have enabled SSL/TLS. Then you can choose to block port 80 to disable unencrypted access.
(Optional) DMZ Configuration: If you run Conferencing services in the DMZ and you are concerned about database security, you can run the database inside the firewall. XML routers and Address Book and Web portal HTTP servers connect to the database through port 5432.
IMPORTANT:All hostnames currently need to be lowercase.
Three hostnames: The XML router, desktop/application sharing, and Web portal IP addresses each require a hostname resolvable by Conferencing clients.
A Conferencing server requires three IP addresses and hostnames for proper operation of all services:
Typically one address is given a friendly name and used for the XML router service. This is the service to which the Conferencing client initially connects.
The second address has “-share” appended to the base name and is used for the desktop sharing components.
The third address has “-portal” appended to the name and is used for Web services and client download.
Fully qualified domain name: The Web portal host requires a fully qualified domain name. For example, www.mycompany.com or webportal.conferenceinstall.com.
Unique hostnames (multiple machines): Multiple-machine Conferencing installations require each machine to have a distinct hostname. These hostnames do not need to be resolvable outside the local network.
To Add IP Addresses to a SUSE Enterprise Server:
Open select , and then select .
Click , select the desired network interface, then click .
Click , then select from the drop-down list.
Click , then specify the IP addresses and netmasks appropriate for your network.
Click .
The client connects to a gateway server by using the IAX protocol, and first attempts to use UDP over port 4569. If that fails, it tries a TCP connection on port 443. The VoIP client does not attempt to do HTTP tunneling. The gateway then uses SIP to communicate with the voice bridge itself. The SIP traffic is sent to the voice bridge server itself, and all voice data is streamed via RTP to the NMS board. See Section F.0, Installing the NMS Board for instructions on installing the NMS board and associated software to use VoIP with Conferencing.
To configure VoIP, you need to specify two additional IP addresses during server installation. One is for the gateway process and must be exposed to the external network; the second is assigned to the NMS board.
Multi-host installations only:
A load balancer is only required when either multiple Web portal hosts or multiple XML router hosts are used.
Conferencing clients need to maintain an open connection while a user is signed on.
Connections to the Web portal should be sticky. For example, if a host is assigned to a Web portal IP address, that host should continue to access the assigned Web portal IP address.