Version 5.2

Installation
Introduction
SysAdmin
Network
Objects
E-mail
Signals
Access
Services
Directory
Clusters
Applications
Miscellaneous
Licensing

WebMail
Pronto!
PBX

Installation	QuickStart	Migration

Installation

You should download the CommuniGate Pro software either from the CommuniGate Systems Web/FTP site, or from any authorized mirror site. Make sure you have the latest version of the software, and that the downloaded version is designed to work on the selected platform.

Install the Server following the instructions below, and then proceed with Initial Configuration.

Installation

On all systems, the CommuniGate Pro uses 2 directories (folders):

the application directory containing the Server application and supplementary files (as Web Interface page templates). Files in this folder are not modified when the system runs.
the base directory containing Account data, Settings, Queued messages, Logs, and other Server data.

Installing on a Sun Solaris System.

Make sure you are running Solaris version 8 or better.

Unpack the CommuniGate Pro archive with the gtar command (or with the gunzip and tar commands): gunzip CGatePro-Solaris-version.tar.gz tar -xpf CGatePro-Solaris-version.tar

Install the CommuniGate Pro package:
pkgadd -d .
The CommuniGate Pro software will be installed in the /opt directory.

If your system was running sendmail or any other SMTP server, stop that server and remove that server start-up script from the /etc/rcn/ directory, so the system will not start that other SMTP server automatically.

If your system was running POP, IMAP, or poppwd servers, remove the lines describing those servers from the /etc/inetd.conf file.

The Installer creates a symbolic link /bin/cgmail for the command line mode mail program to use with the CommuniGate Pro system.

The Installer creates a startup script /etc/init.d/STLKCGPro.init, and the symbolic link /etc/rc2.d/S88CommuniGate for that script.

The Installer creates the "base directory" /var/CommuniGate and the Server uses it by default. You can move the "base directory" to any other location. In this case, open the /etc/init.d/STLKCGPro.init file and update it.

Restart the system or launch the start-up script manually:
/etc/init.d/STLKCGPro.init start

Proceed with Initial Configuration.

Installing on a Linux System.

Using the Red Hat Package Manager (the .rpm file):
rpm -i CGatePro-Linux-version.rpm
Using other systems (the .tgz file):
  tar -xzf CGatePro-Linux-version.tgz
  cd CGateProSoftware
  sh install.sh

The CommuniGate Pro software will be installed in the /opt directory.

The installer will create the /etc/rc.d/init.d/CommuniGate startup script. To make the CommuniGate Pro Server start and stop automatically when the system starts up and shuts down, the installer adds the startup file links to the /etc/rc.d/rcn.d directories.

If your system was running some standalone SMTP server/MTA (such as sendmail), stop that server (for example, you can use the
/sbin/chkconfig sendmail off
command and then restart the server computer).

If your system was running POP, IMAP, or poppwd servers, remove the lines describing those servers from the /etc/inetd.conf file (or put the hash #) symbol into the first position of those lines).

The Installer renames the /bin/mail program into the /bin/LegacyMail. If you decide to uninstall the CommuniGate Pro system, the legacy mail program will be renamed back to /bin/mail.

The Installer creates the new /bin/mail application - a drop-in substitution for the legacy mail program.

Restart the system or launch the start-up script manually:
/etc/rc.d/init.d/CommuniGate start

Proceed with Initial Configuration.

Note: some older versions of Linux (such as RedHat 9.0, SuSE 9.1 and some other distributions) used a very unstable version on the NPTL p-threads library.
To provide a workaround for these versions of the Linux OS, the CommuniGate Pro startup script uses the LD_ASSUME_KERNEL=2.4.1 command to make the Linux linker use the old, more stable version of the p-threads library.

Note: When the old p-threads library is used, each CommuniGate Pro thread is seen as a separate process when you use the ps and top system utilities. This is normal: all those "processes" are actually CommuniGate Pro Server threads, and they share all their resources - VRAM, file descriptors, etc.

Note: Linux kernels prior to 2.6.13 have critical flaws in their NFS client implementations. If you plan to use the Linux OS as your Dynamic Cluster backends, make sure that your kernel version is 2.6.13 or higher.

Note: Linux kernels do not support x86 hyperthreading correctly. Make sure hyperthreading is switched off in the x86 server BIOS.

Installing on a MS Windows System

Use any "unzip"-type tool to unpack the CGatePro-Win32-Intel-version.zip file. The tool should be able to use long file names.

Some "unzip" applications have the Install option, use that option if available. If the Install option is not available, unpack the archive. The unpacked directory should contain the CommuniGate Pro application folder and the Installer.exe application. Launch the Installer.exe application.

If the CommuniGate Pro software is running, the Installer asks your permission to stop it.

The Installer asks you where to place the CommuniGate Pro application folder, and where to create the "base" directory. If a previous version of CommuniGate Pro has been already installed, the Installer shows the locations used, and the Install button is renamed into the Update button.

Click the Install/Update button to copy the CommuniGate Pro software into the selected location. If the CommuniGate Pro "base" folder does not exist, the Installer creates an empty folder in the selected location.

The information about the selected locations is stored in the System Registry.

Windows NT/200x/XP/Vista

The CommuniGate Pro Messaging Server (the CGStarter.exe application) is registered as a service that starts automatically when the system starts. This small application starts the CGServer.exe - the CommuniGate Pro Server application. The Installer asks if you want to start the Server now.
Note:you should use the Services control panel to verify or change the Log On as name for the CommuniGate Pro service. That name should have the Act as part of the operating system Windows NT privilege. If the CommuniGate Pro Server does not have this privilege, not only it will fail to authenticate users using the Windows NT password system, but an attempt to use an incorrect password may cause the server to crash. This problem is fixed in the Windows NT Service Pack 4.

Note:if your server should serve 100 accounts or more, check the description of the TIME_WAIT problem and follow the instructions to decrease the NT TIME_WAIT time interval.

Windows 95/98/ME

The CommuniGate Pro (the CGServer.exe application) is added to the RunServices Registry key, so the server is started up when the system starts. Restart the Windows 9x system to start the server.
Note:Unlike Windows 98/ME, the Windows 95 system does not have the "WinSock2" libarary installed. Download this library (.dll) from the http://www.microsoft.com and install it before you try to launch the CommuniGate Pro Server.
Launch the Server and proceed with Initial Configuration.

You can also start the CommuniGate Pro server manually, as a "console application", by launching the CGServer.exe file. If started without parameters, the Server creates the C:\CommuniGatePro folder and uses it as its "base" folder". If you want to use any other location, use the --Base command line parameter:
CGServer.exe --Base D:\OtherDirectory

Note: Windows kernels do not support x86 hyperthreading correctly. Make sure hyperthreading is switched off in the x86 server BIOS.

Installing on a MacOS X (Darwin) System.

Make sure you are running MacOS X version 10.3 or better.

Unpack the CommuniGate Pro archive using any uncompressing utility, or start the Terminal application and use the shell tar command:
tar xzpf CGatePro-Darwin-platform-version.tgz
the CommuniGate.pkg package directory will be created in the current directory.

Install the software by double-clicking the CommuniGate.pkg icon.
The CommuniGate Pro software will be installed in the /usr/sbin/ directory.

Note: The Installer creates the startup directory /Library/StartupItems/CommuniGatePro, so the CommuniGate Pro Server will auto-start when the MacOS X System starts.

Note: The Installer packs the startup directory /System/Library/StartupItems/Sendmail into the /System/Library/StartupItems/Sendmail.tar, and the /System/Library/StartupItems/Postfix directory into the /System/Library/StartupItems/Postfix.tar archive, so the legacy sendmail and postfix daemons will not auto-start. If you decide to uninstall CommuniGate Pro, these archives will be unpacked and the legacy startup directories will be restored.

If your system was running POP, IMAP, or poppwd servers, remove the lines describing those servers from the /etc/inetd.conf file.

The Installer renames the /usr/bin/mail program into the /usr/bin/LegacyMail. If you decide to uninstall the CommuniGate Pro system, the legacy mail program will be renamed back to /usr/bin/mail.

The Installer creates the new /usr/bin/mail application - a drop-in substitution for the legacy mail program.

Restart the MacOS X System.

Proceed with Initial Configuration.

Installing on a FreeBSD System.

There are two CommuniGate Pro packages: one for FreeBSD 4.x (supporting FreeBSD 4.x versions), one - supporting FreeBSD 5.3 and later versions.

Install the CommuniGate Pro package. FreeBSD 4.x:
pkg_add CGatePro-FreeBSD4-version.tgz
FreeBSD 5.x:
pkg_add CGatePro-FreeBSD-version.tgz
The CommuniGate Pro software will be installed in the /usr/local/sbin directory.

If your system was running sendmail or any other SMTP server, stop that server and modify the OS start-up scripts so the system will not start that other SMTP server automatically.

If your system was running POP, IMAP, or poppwd servers, remove the lines describing those servers from the /etc/inetd.conf file.

The Installer creates a script /usr/local/etc/rc.d/CommuniGate.sh, so the CommuniGate Pro Server is started automatically when the FreeBSD system starts.

The Installer creates a symbolic link /bin/cgmail for the command line mode mail program to use with the CommuniGate Pro system.

The Installer creates the "base directory" /var/CommuniGate and the Server uses it by default. You can move the "base directory" to any other location. In this case, open the start-up script file and update it.

Restart the system or launch the start-up script manually:
/usr/local/etc/rc.d/CommuniGate.sh start

Proceed with Initial Configuration.

set the maxdsiz kernel parameter to 100MB or more.
set the max_thread_proc (max number of threads per process) to 1024 or more.
set the ncallout parameter (max number of pending timeouts) to 1024 or more.
set the maxfiles parameter to 1024 or more.

Unpack the CommuniGate Pro archive with the gunzip and tar commands:
gunzip -xzpf CGatePro-HPUX-platform-version.tar.gz
tar -xf CGatePro-HPUX-platform-version.tar
The CGatePro.depot directory should appear in the current directory.

Install the CommuniGate Pro package:
swinstall -s `pwd`/CGatePro.depot (you should use the absolute path for the unpacked CGatePro.depot directory)
The CommuniGate Pro software will be installed in the /opt/CommuniGate directory.

If your system was running sendmail or any other SMTP server, stop that server and modify the OS start-up scripts so the system will not start that other SMTP server automatically.

If your system was running POP, IMAP, or poppwd servers, remove the lines describing those servers from the /etc/inetd.conf file.

The server startup script is created as /sbin/init.d/CommuniGate and its symbolic links /sbin/rc2.d/S80CommuniGate and /sbin/rc1.d/K80CommuniGate are automatically created.

The Server uses /var/CommuniGate as its "base directory" by default. You can move the "base directory" to any other location. In this case, open the /sbin/init.d/CommuniGate script file and update its BASEDIRECTORY parameter.

The symbolic link /bin/cgmail is created for the CommuniGate Pro "mail" program.

Restart the system or launch the start-up script manually:
/sbin/init.d/CommuniGate start

Proceed with Initial Configuration.

Installing on a Tru64 (Digital Unix) System.

Make sure the Tru64 version 5.0 or better is installed.

Unpack the CommuniGate Pro archive with the gtar command (or with the gunzip and tar commands):
gtar -xzf CGatePro-Tru647-platform-version.tar.gz.

Install the CommuniGate Pro package:
/usr/sbin/setld -l CGatePro.pkg
The CommuniGate Pro software will be installed in the /usr/opt/ directory.

If your system was running sendmail or any other SMTP server, stop that server and modify the OS start-up scripts so the system will not start that other SMTP server automatically.

If your system was running POP, IMAP, or poppwd servers, remove the lines describing those servers from the /etc/inetd.conf file.

The Installer creates the symbolic link /sbin/init.d/CommuniGate for the server startup script.

The Installer also creates the /sbin/rc0.d/K10CommuniGate, /sbin/rc2.d/K10CommuniGate, and /sbin/rc0.d/S80CommuniGate startup symbolic links.

The Server uses /var/CommuniGate as its "base directory" by default. You can move the "base directory" to any other location. In this case, open the /usr/opt/CGPversion/startup script file and update its BASEFOLDER parameter.

Restart the system or launch the start-up script manually:
/sbin/init.d/CommuniGate start

Proceed with Initial Configuration.

Installing on an SGI IRIX System.

Make sure you are using the IRIX System version 6.5 or better.

Install the CommuniGate Pro package:
inst -f CGatePro-IRIX-MIPS-version.tardist
or
swmgr -f CGatePro-IRIX-MIPS-version.tardist
The CommuniGate Pro software will be installed in the /opt/CommuniGate directory.

If your system was running POP, IMAP, or poppwd servers, remove the lines describing those servers from the /etc/inetd.conf file.

If your system was running sendmail, use the chkconfig to disable it:
/sbin/chkconfig sendmail off
The CommuniGate Pro installation script writes the word off into the /etc/config/sendmail file.

The installation script creates a startup script /etc/init.d/CommuniGate, and the symbolic links /etc/rc2.d/S75CommuniGate and /etc/rc0.d/K05CommuniGate for that script.

The installation script creates the "base directory" /var/CommuniGate and the Server uses this directory by default. You can move the "base directory" to any other location. In this case, open the /etc/init.d/CommuniGate script file and update it.

Restart the system or launch the start-up script manually:
/etc/init.d/CommuniGate start

Proceed with Initial Configuration.

Installing on an SCO UnixWare System.

Make sure that UnixWare 7.1 or better is installed.

Create a new directory, and "cd" into that directory; download the CGatePro-UnixWare-version.tar.gz archive.

Unpack the CommuniGate Pro archive with the gunzip and tar commands: gunzip CGatePro-UnixWare-Intel-version.tar.gz tar -xpf CGatePro-UnixWare-Intel-version.tar

Install the CommuniGate Pro package:
pkgadd -d `pwd`
The CommuniGate Pro software will be installed in the /usr/local/sbin directory.

If your system was running sendmail or any other SMTP server, stop that server and modify the OS start-up scripts so the system will not start that other SMTP server automatically.

If your system was running POP, IMAP, or poppwd servers, remove the lines describing those servers from the /etc/inetd.conf file.

The Installer creates a symbolic link /bin/cgmail for the command line mode mail program to use with the CommuniGate Pro system.

The Installer creates a startup script /etc/init.d/STLKCGPro.init, and the symbolic link /etc/rc2.d/S88CommuniGate for that script.

Restart the system or launch the start-up script manually:
/etc/init.d/STLKCGPro.init start

Proceed with Initial Configuration.
Note: UnixWare 7.1 has a very small per process limit for open listeners. To avoid the problem, the CommuniGate Pro ACAP server is disabled by default, and the LDAP server does not create a listener to accept secure connections. Do not try to create additional listeners before this limit is increased.

Installing on an SCO OpenServer System.

Make sure that OpenServer 6.0 or better is installed.

Create a new directory, and "cd" into that directory; download the CGatePro-OpenServer-version.tar.gz archive.

Unpack the CommuniGate Pro archive with the gunzip and tar commands: gunzip CGatePro-OpenServer-Intel-version.tar.gz tar -xpf CGatePro-OpenServer-Intel-version.tar

Install the CommuniGate Pro package:
pkgadd -d `pwd`
The CommuniGate Pro software will be installed in the /opt directory.

If your system was running sendmail or any other SMTP server, stop that server and modify the OS start-up scripts so the system will not start that other SMTP server automatically.

If your system was running SMTP, POP, IMAP, or poppwd servers, remove the lines describing those servers from the /etc/inetd.conf file.

The Installer creates a symbolic link /bin/cgmail for the command line mode mail program to use with the CommuniGate Pro system.

The Installer creates a startup script /etc/init.d/STLKCGPro.init, and the symbolic link /etc/rc2.d/S88CommuniGate for that script.

Restart the system or launch the start-up script manually:
/etc/init.d/STLKCGPro.init start

Proceed with Initial Configuration.

Installing on an IBM OS/400 System.

Make sure you have OS/400 version V4R4M0 or later.

Decide where to place the CommuniGate Pro base directory:

The files used by the CommuniGate Pro Software must reside in a thread-safe file system. Only the following file systems are thread-safe:
/ (root), QOpenSys, QNTC, QSYS.LIB, QOPT, QLANSrv, user-defined.
For details see the Integrated File System concepts book in the AS/400 Information Center.

If you need to have case-sensitive mailbox names you should place the CommuniGate Pro base directory into a case-sensitive file system. The QOpenSys file system is case-sensitive. User-defined file systems can be created as case-sensitive, too. The Installer program allows you to create a case-sensitive file system for the CommuniGate Pro base directory.
Note: If you are upgrading the CommuniGate Pro Server and the base directory already exists, then installer will ignore the case-sensitivity option you have specified, and will leave the base directory unmodified.
If your OS/400 system was running SMTP, POP, IMAP, ACAP, or poppwd servers, stop those servers, and modify the start-up defaults, so the system will not start those legacy servers automatically. You can change the start-up defaults using the AS400 Operations Navigator.
Make sure your OS/400 system has its TCP/IP stack active and the FTP server running.
Download the current CommuniGate Pro OS400 version (the CGatePro-OS400-AS400.exe file) to a computer running MS Windows OS and connected (via a TCP/IP network) to your OS/400 system.
Run the CGatePro-OS400-AS400.exe installer program on that MS Windows system. Follow the instructions the installer program provides.
On the OS/400 system, start the CommuniGate Pro Server job: QGPL/STRCGSRV. The CGSERVER job will start in the QSYSWRK subsystem.
You may want to create an autostart job entry for the CommuniGate Pro Server, or run it in a specially created subsystem. To setup the server as an autostart job:

Add request data to the server's job description:

CHGJOBD JOBD(CGSERVER/CGSERVERJD) RQSDTA('QGPL/STRCGSRV')

Add an autostart job entry:

ADDAJE SBSD(QSYSWRK) JOB(CGSERVER) JOBD(CGSERVER/CGSERVERJD)

If you have chosen the case-sensitive mailbox names option, then additional actions are required:

Authorize CGATEPRO to the command MOUNT:

GRTOBJAUT OBJ(CGATEPRO) OBJTYPE(*USRPRF) USER(CGATEPRO) AUT(*USE)

Grant CGATEPRO the *IOSYSCFG special authority:

CHGUSRPRF USRPRF(CGATEPRO) SPCAUT(*IOSYSCFG)
Note: the source code of the STRCGSRV and ENDCGSRV commands is included into the CGatePro distribution set, so you can modify those commands to meet your needs.
Proceed with Initial Configuration.

Installing on an OpenVMS System.

Make sure you are running OpenVMS version 7.2 or better.

If you plan to use the Server for a medium or heavy load, make sure that your system has at least 2048 "permanent I/O channels":

MCR SYSGEN SHOW CHANNELCNT

Download the CGatePro-OpenVMS-platform-version.zip archive file.

Unzip the archive file to get a POLYCENTER package file: STLK-platform-CGATEPRO-Vversion-1.PCSI

Install the CommuniGate Pro package:

PRODUCT INSTALL CGatePro

The CommuniGate Pro software will be installed in the SYS$COMMON:[CommuniGate] directory.
The CommuniGate Pro startup file STARTUP.COM can be found in that directory.

If your system was running any other SMTP, POP, IMAP server software, stop those packages and modify the OS configuration so the system will not start those other server programs automatically. Use the TCPIP$CONFIG command to disable the SMTP, POP, and IMAP servers that come with the OS.

The Installer creates the "base directory" SYS$SPECIFIC:[CommuniGate] and the Server uses it by default.

You may want to add the

$ @SYS$COMMON:[CommuniGate]STARTUP.COM START

command to your SYS$MANAGER:SYSTARTUP_VMS.COM file to start CommuniGate Pro automatically on system startup.
You may want to add the

$ @SYS$COMMON:[CommuniGate]STARTUP.COM STOP

command to your SYS$MANAGER:SYSHUTDWN.COM file to shut down the CommuniGate Pro server before the system shuts down.

Proceed with Initial Configuration.

Installing on a QNX System.

Make sure you are running QNX version 6.2 or better.

Download the CGatePro-QNX-platform-version.qpr package.

Install the CommuniGate Pro package:

cl-installer -i CGatePro-QNX-platform-version.qpr

The CommuniGate Pro software will be installed in the /opt directory.

If your system was running sendmail or any other SMTP server, stop that server and modify the OS start-up scripts so the system will not start that other SMTP server automatically.

If your system was running POP, IMAP, or poppwd servers, remove the lines describing those servers from the /etc/inetd.conf file.

The Installer adds a reference to the CommuniGate Pro startup script to the /etc/rc.local file, so the CommuniGate Pro Server is started automatically when the QNX system starts.

Restart the system or launch the start-up script manually:

/opt/CommuniGate/Startup.sh start

Proceed with Initial Configuration.

Installing on an IBM OS/2 System.

Make sure you are running OS/2 version 2.4 or better.

Make sure you are running OS/2 TCP version 4.1 or better.

Download the CGatePro-OS2-platform-version.zip package.

Install the CommuniGate Pro package:

cd C:\

unzip CGatePro-OS2-platform-version.zip

The CommuniGate Pro software will be installed in the C:\STALKER\CommuniGate directory.

If your system was running sendmail or any other SMTP server, stop and disable that server.

If your system was running POP, IMAP, or poppwd servers, stop and disable these servers.

The installed software contains the C:\STALKER\CommuniGate\Startup.CMD batch file.

If you do not have the STARTUP.CMD file in the root directory of your starup disk, create such a file.

Add the following line to the STARTUP.CMD file (stored in the root directory of your startup disk):

CMD /C C:\STALKER\CommuniGate\Startup.CMD start

this line will ensure that CommuniGate Pro server is started automatically when the OS/2 system starts.

The default "base directory" is C:\CommuniGate. You can move the "base directory" to any other location. In this case, open the start-up script file (C:\STALKER\CommuniGate\Startup.CMD) and update it.

Restart the system or launch the start-up script manually:

CMD /C C:\STALKER\CommuniGate\Startup.CMD start

Proceed with Initial Configuration.

Installing on a MacOS Rhapsody System.

Unpack the CommuniGate Pro archive using any uncompressing utility, or use the shell (Terminal.app) gnutar command:
gnutar xzpf CGatePro-Rhapsody-version.tgz
the CommuniGate.pkg package directory will be created in the current directory.

Install the software by double-clicking the CommuniGate.pkg icon. The CommuniGate Pro software will be installed in the /Local/Servers directory.

Note: The installer will create a file /etc/startup/1950_CommuniGate, so the CommuniGate Pro Server will auto-start when the System starts.

Note: The installer will disable the file /etc/startup/1800_Mail (/etc/startup/1900_Mail on DR Rhapsody versions) used to auto-start sendmail on your system.

If your system was running POP, IMAP, or poppwd servers, remove the lines describing those servers from the /etc/inetd.conf file.

The Installer creates the new /usr/bin/mail application - a drop-in substitution for the legacy mail program.

The Installer creates the "base directory" /Local/CommuniGate and the Server uses it by default. You can move the "base directory" to any other location. In this case, open the /etc/startup/1950_CommuniGate file and update it.

Restart the system or launch the startup script manually:
/etc/startup/1950_CommuniGate

Proceed with Initial Configuration.

Installing on a BeOS System.

Make sure that BeOS R5 or better is installed.

Download the CommuniGate Pro package: CGatePro-BeOS-version.pkg.

Double-click the package file and install it.
The CommuniGate Pro software will be installed in the /boot/Servers/ directory.

If your system was running sendmail or any other SMTP server, stop that server and modify the OS start-up scripts so the system will not start that other SMTP server automatically.

If your system was running POP, IMAP, or poppwd servers controlled with the inetd daemon, remove the lines describing those servers from the /etc/inetd.conf file.

The Installer adds commands to the /boot/home/config/boot/UserBootscript and /boot/home/config/boot/UserShutdownFinishScript files. Those commands call the CommuniGate Pro startup script when the BeOS starts and shuts down.

Restart the system or launch the start-up script manually:
/boot/Servers/CommuniGate/Startup start

Proceed with Initial Configuration.

Note: Under BeOS, each thread in a multi-threaded application is seen as a "process" when you use the ps system utility. As a result, you may see 30+ CGServer "processes" when the server is just started, and more after it has been actively used. All those "processes" are actually CommuniGate Pro Server threads, and they share all their resources - VRAM, File Descriptors, etc.

Initial Configuration

When the CommuniGate Pro software is installed:

Restart the OS or start the CommuniGate Pro Server manually.

Within 10 minutes, connect to the WebAdmin Interface with any Web browser, using the port number 8010. Type the following URL in your browser:

http://your.server.domain:8010

where your.server.domain is the domain name or the IP address of the computer running the CommuniGate Pro Server.

Read the License Agreement, enter the preferred password for the postmaster Account, and click the Accept button.

You will be redirected to the QuickStart page. Use the postmaster name and the selected password to open the page.

Proceed using the Quick Start instructions.

If you failed to enter a new postmaster password within 10 minutes, the Server will be shut down. When you are ready to enter the password, repeat the steps listed above.

The Migration section can help you to schedule your CommuniGate Pro deployment process.

Upgrading to a Newer Version

When you upgrade to a new version, the files in the application directory are substituted with the new files.

The base directory and all its files are not modified when you upgrade the CommuniGate Pro Server software, so all Accounts, Mailboxes, messages, settings, File Storage files, Licenses, customized Web Skin, and Real-Time Application files stay in place and continue to work with the new version of the CommuniGate Pro software.

Note: if you chose to manually modify Web Skin or Real-Time Application files right in the application directory, then you should save them before upgrading.

To upgrade:

Download the new version of the CommuniGate Pro Software.
Stop the CommuniGate Pro Server.
Remove the previous version of the software using the same installation utility you used to install the software (the base directory will not be removed). This step is needed if the OS installer does not allow you to install a new version "on top" of the old one (Solaris, FreeBSD, Linux).
Note: If you are using the Linux rpm package manager, do not use its "update" option: uninstall the old version, then install the new one:
rpm -e CGatePro-Linux rpm -i CGatePro-Linux-version.rpm
Install the new version of the CommuniGate Pro Software.
Start the CommuniGate Pro Server.

Moving to a New Hardware Server

You may want to move your CommuniGate Pro server to a different computer - running the same or a different OS. All your module settings, account and domain settings, mailboxes, licenses, and other data can be preserved.

CommuniGate Pro keeps all its data in the base directory. This is the only directory you need to copy to your new server computer.

CommuniGate Pro uses the same file formats on all hardware and software (OS) platforms, so usually you can just pack the entire CommuniGate Pro base directory into an archive file (using tar and gzip on Unix systems, zip on MS Windows systems), and unpack the archive on the new server computer.

Additional processing is needed when you move the CommuniGate Pro Server from a computer running any MS Windows operating system to a computer running any flavor of Unix, or vice versa. CommuniGate Pro files are text files, and text files on MS Windows and Unix have different EOL (end of line) symbols: CR-LF (return - linefeed) on MS Windows and bare LF (linefeed) symbol on Unix systems. To copy files properly, you may want to use any FTP software to copy files between those systems: when an FTP client is instructed to transfer files in the ASCII mode, it properly converts EOL symbols.
Note: CommuniGate Pro base directory can contain non-text (binary) files in the WebSkins and PBXApps directories inside the Account and Domains subdirectories - graphic, audio, and video files used in the custom Skin Interfaces and Real-Time Applications.
Account File Storage can also contain binary files. These files are stored in the account.web directories inside the Account directories.
When you move a CommuniGate Pro base directory between systems using different EOL conventions, check that those binary files are copied in the BINARY mode (i.e. without EOL re-coding).

If the new server computer is running a Unix system, check that the copied directory and all its files and subdirectories have the same access rights as they had on the old system.

After the CommuniGate Pro base directory is copied, download and install the proper version of the CommuniGate Pro Server on the new server computer. There is no need to copy the content of application directory from the old server computer, even if both new and old computers are running the same operating system.

Check that the newly installed copy of the CommuniGate Pro Server (its startup script, if any) is configured to use the copied base directory, and then start the CommuniGate Pro Server on the new computer. Use the WebAdmin Interface to modify the computer-related settings on the new server. For example, you may need to update the Client IP Addresses table or re-assign IP addresses to CommuniGate Pro Domains.