======================================================================
VSI-FAX 6.1 version - Issued April 2009
======================================================================


This document provides release notes and other general information for
VSI-FAX 6.1 version. 


Table of Contents
-----------------
 - What's New in VSI-FAX 6.1 Version
 - Evaluation License
 - How to upgrade to Version 6.1
 - How to access the documentation
 - Troubleshooting
    
 
----------------------------------------------------------------------
-- What's New in VSI-FAX 6.1 Version----------------------------------
----------------------------------------------------------------------

-  Extended OS Support 

-  Fax over IP installation
   Esker VSI-FAX supports all Brooktrout Fax over IP solutions: 
   the TR1034 Intelligent Fax Board and the SR140 Host-based Fax over IP 
   processing software. The configuration procedures for SR140 has 
   changed since version 6.0. Follow the procedure described in 
   faxboardsinstallation.pdf for a successful configuration of your fax system.

 - Extended OS Support on Dialogic Brooktrout boards
   With the inclusion of the latest SDK, VSI-FAX 6.1 supports Brooktrout 
   fax boards on Microsoft Windows 2003 or 2008, and Red Hat 
   Enterprise 4 or 5. For more details, refer to the hardware.pdf
   file delivered in the \docs subfolder on the VSI-FAX 6.1 CD-ROM.

 - Citrix Metaframe is no more supported to install VSI-FAX 6.1.
   Use Windows TS instead.

----------------------------------------------------------------------
-- Evaluation License ------------------------------------------------
----------------------------------------------------------------------


Leave the License screen empty during VSI-FAX Server installation to
install a time-limited evaluation license of VSI-FAX Server 6.1. 
With the VSI-FAX 6.1 Evaluation license, you can test the product for 30
days starting from the installation day. After that you can reactivate with
another time-limited evaluation license or with a production license. 


----------------------------------------------------------------------
-- How to upgrade to Version 6.1 -------------------------------------
----------------------------------------------------------------------

You can only upgrade to version 6.1 from VSI-FAX 6.0.

Direct upgrades to 6.1 from versions prior to 6.0 are not advised.


Prerequisites
-------------

 - Maintenance keys have been removed since version 6.0 ; you need to contact
   your Esker Sales Representative to obtain a new license for version 6.1.
   The installation program will prompt you for a valid VSI-FAX 6.1 
   Serial Number and Activation Key. If you do not enter any license information
   at setup, an evaluation license will be installed.

 - Ensure that no application will try to access the server during the 
   upgrade operation. 

 - If you were using a Brooktrout fax board with your former version of VSI-FAX,
   refer to the faxboardsinstallation.pdf file for information about fax board upgrade.


Upgrade steps on Windows platforms
----------------------------------

1- Load the VSI-FAX CD-ROM. 

2- Click VSI-FAX Server under Fax Server on the Autorun screen.

3- The installation program detects that the VSI-FAX server has previously 
   been installed on the machine and proceeds with the upgrade. Existing 
   cover page information, telephony information, SMTP server and POP3 server
   connection settings and fax modem devices configuration are kept. Click 
   Next when the file copy is finished.  

4- In the VSI-FAX Server License screen, enter your Serial Number and Activation 
   Key or leave the screen empty to install the evaluation version. Click Next. 

5- Click Finish to complete the server upgrade.

6- When upgrading from VSI-FAX version 4.2.2b, run the vologcvt command if 
   you want to access to the logs of faxes sent before the upgrade. 
   See the vsifax_addendum.pdf file for more information on this command.

7- Then upgrade the other VSI-FAX components you were using by launching the 
   corresponding setup from VSI-FAX Autorun: 

 - Server Administration
 - LanFax Windows Client 
 - CoverMaker
 - VSI-FAX SDK
 - Outlook Client
 - MailMerge Client
 - Virtual Server
 - Add-On Formatters


Server Upgrade steps on Unix/Linux platforms
--------------------------------------------

1- Mount the CD-ROM drive. 

2- Change directory to the CD-ROM mount point by entering:
   cd /mnt/cdrom

3- Run the installation program by entering:
   ./install.sh
    
4- Confirm platform type.

5- The list of available packages appears. Enter "s" to install the Fax 
   Server package.
    
6- Follow the on-screen instructions. Answer yes when prompted to stop 
   the existing VSI-FAX server.

7- Enter your Serial Number, Activation Key and remote server addresses if 
   requested.

8- After the file copy, modify existing fax modem devices configuration, cover 
   page information, telephony information, SMTP server and POP3 server
   connection settings if needed.  

9- Answer yes when prompted to start the VSI-FAX Admin Server and Fax Server
   tasks.

10-When upgrading from VSI-FAX version 4.2.2b, run the vologcvt command if 
   you want to access to the logs of faxes sent before the upgrade. 
   See the vsifax_addendum.pdf file for more information on this command.

If you want to fax through Esker on Demand, refer to the vsifax_instadm.pdf file
to learn how to enable the Fax on Demand Connector device.



---------------------------------------------------------------------------------
-- Installing the libstdc.so.5 library on Red Hat Enterprise 4 or 5 -------------
---------------------------------------------------------------------------------

VSI-FAX Server requires that  the  libstdc++.so.5 library be installed 
on your Operating System to function  properly.
The VSI-FAXServer installation program checks the library version, so you might 
be prompted to install the  libstdc++.so.5 library during the server installation. 
In this case, cancel the installation, then install the libstdc++.so.5 library:
- For Red Hat 4.0, install the compat-libstdc++-33-3.2.3-47.3.i386.rpm RPM package 
  that you can find on the CD2 in the RedHat\RPMS folder.
- For Red Hat 5.0, install the compat-libstdc++-33-3.2.3-61.i386.rpm RPMpackage 
  that you can find on the CD2 or DVD in the Server folder.
Next, perform the VSI-FAX Server installation.

----------------------------------------------------------------------
-- How to access the documentation -----------------------------------
----------------------------------------------------------------------

A complete set of electronic documentation is available on your VSI-FAX 
CD-ROM, in the \docs folder. To browse the manuals open the index.html file.

On Windows platforms, you can access the documentation in PDF format after
installing VSI-FAX Server with the VSI-FAX CD-ROM. For this, click the Start 
menu and select Programs > VSI-FAX > VSI-FAX Documentation. 
Documentation files are stored under \doc in the VSI-FAX Server installation
directory.

You can also search for and browse the latest technical documentation for 
Esker VSI-FAX on our documentation Web site, at http://doc.esker.com/vsi61.

----------------------------------------------------------------------
-- Troubleshooting ---------------------------------------------------
----------------------------------------------------------------------

 - Incorrect time on SCO OpenServer
   --------------------------------
   On SCO OpenServer, due to Daylight Saving Time changes in March 2007,
   the submitted job time can have an hour difference with the real time 
   after a clock shift.
   To set the correct hour, change the TZ (Time Zone) environment variable
   defined in the /etc/TIMEZONE file.
   Replace the standard time zone TZ='XXXX' 
   with TZ='XXXX,M3.2.0/2:00:00,M11.1.0/2:00:00'
 
 - Dialogic Brooktrout fax board
   -----------------------------
   If you have a Brooktrout board installed and the VSI-FAX Server cannot 
   start, it may be due to a bug in the Brooktrout Configuration Tool. 

   To fix this problem, issue the following from a command shell: 

   "%ProgramFiles%\brooktrout\bin\configtool" /a 

   and ensure that the "Country Telephony Parameter File" parameter under 
   "BTCall Parameters (All boards)" in the Brooktrout Configuration Tool 
   indicates the following: %ProgramFiles%\brooktrout\config\BT_CPARM.cfg


 - Unix installation
   ------------------
   During the installation of VSI-FAX server on some unix platforms, 
   the integration with the operating system is not correct. In this case,
   you must verify the following points:

   1- To update the PATH environment variable and to declare the VSIFAX
      environment variable, you must verify that:

      - the /etc/profile file exists, if you use sh
      - the /etc/cshrc file exists, if you use csh

   2- The user profiles must inherit these environment variables. The user 
      profiles must not update the environment variables that have been set 
      during the installation of VSI-FAX server. Be careful that the personal 
      user profile does not overwrite the PATH environment variable especially 
      if the current user is the root user.

   3- When csh is the default shell for the system, you must add 
      the following line at the beginning of the vsiadm.sh and vsifax.sh 
      files to automatically start the VSI-FAX services at boot time:

      #!/bin/sh


 - Digi AccelPort RAS modems
   -------------------------
   Digi AccelPort RAS modems have a fax class 2.0 bug when sending. 
   The AT+FPS? command returns a response of 384. The AT=FPS? 
   command queries the Post Page Response from the receiving fax 
   device. The correct response of 1 is page good, while 2 is page 
   bad. The workaround is to use fax class 2 mode or to use the 
   Digi AccelePort firmware tested with VSI-FAX. Contact Esker
   Technical Support for assistance.


 - Outlook Client
   --------------
   Embedded graphic files in fax body/email message field
   Due to limitations of the MAPI spooler, the VSI-FAX Outlook Client
   cannot support embedding of graphic files (e.g., GIF, BMP, JPEG, 
   etc.) directly into the fax message form fax  body/email message 
   field. However, graphic files can be added as attachments with no 
   known limitations.
 

 - Mailmerge Client
   ----------------
   - You must be a power user to use the VSI-FAX MailMerge Client 
   on a server with Terminal Services installed.
   
   - The printer port name has been renamed VSI-FAX Port 3.0 in VSI-FAX6.1.
   The macro used in Microsoft Word to customize the mail merge mechanism 
   uses the port name. Thus you should use the new macro version to send 
   your faxes with the MailMerge Client. 
   If you customized the Microsoft Word document or template provided with
   a previous version of VSI-FAX, you should update the macro contained 
   in your document. To do this, you must:
   - Edit your document in Microsoft Word.
   - Enter ALT + F8 to open the Macro dialog.
   - Click the Organizer button.
   - Delete the previous mergebox macro.
   - Use the Close File/Open File button on the right to open the template file provided with VSI-FAX6.1.
   - Copy the new mergebox macro in your document.


 - Modem configuration
   -------------------

   If you have modified the c2modems.ini file available 
   in the lib directory, the c2modems.ini file will not be replaced. 
   
   If you encounter problems with your modem after the upgrade, 
   copy the new version of this file available in the $VSIFAX/lib/cfg-new 
   directory to the lib directory.


 - Mulitech Modem with hardware flow control
   -----------------------------------------
   If you encounter problems with the Multitech modems, 
   you must activate the hardware flow control.
   For this, execute the following command on the server:

   $>vfxadmin device -u -Q hard devicename

   where devicename must be replaced by your devicename. 


 - Documentation
   -------------
   Due to a Microsoft limitation you cannot open remote content after
   you install security update 896358, security update 840315, or 
   Windows Server 2003 Service Pack 1. When you try to use a Universal 
   Naming Convention (UNC) path to open an HTML Help file (.chm file) 
   on a network shared folder, topics in the .chm file do not appear: 
   you get an error message in the right pane saying: 

   "The page cannot be displayed"

   See Microsoft knowledge base http://support.microsoft.com/kb/896054/en-us
   for more information.

   We suggest that you copy the file in a local folder to avoid this problem.