Copyright: Gareth Williams
Citation: Frequently Asked Questions


Zetafax - Frequently Asked Questions - December 1996

Zetafax Support FAQ

This article contains the answers to many frequently asked questions regarding technical aspects of Zetafax fax software for PC networks.

Contact details

EQUISYS Limited, London

Phone: 0171-403 2227 (Intl +44 171 403 2227)

Fax: 0171-378 6886 (Intl +44 171 378 6886)

Email: sales@equisys.com

Compuserve: 100023,2100

http://www.equisys.com  (a UK based web site)

USA and Canada

Phone: (770) 622 2810

Fax: (770) 232 9624

Email: sales@zetafax.com

Compuserve: 70613,457

http://www.zetafax.com  (a US based web site)

Zetafax is distributed in many other countries

Please contact EQUISYS for details of your local supplier

All trademarks acknowledged

Copyright Equisys Limited 1996 Ref ZFAX_FAQ3


Section A - Fax modems

This section of the FAQ deals with common questions concerning modems, differences between fax classes and the setup of fax devices.


Q.A.1   What fax devices do I need to use with Zetafax?

Zetafax supports class 2 and 2.0 fax modems, Brooktrout fax cards, GammaLink fax cards, ISDN modems and terminal adapters.

Fax class 2 and 2.0 fax modems

Zetafax can be used with modems which support the Class 2 or Class 2.0 standards.  It also supports voice fax modems, using the Rockwell voice command set, for use with DDI/DTMF automatic inward routing.

For a full list of currently supported modems go to  Q.A.6   Is there a supported list of modems?

Brooktrout fax cards

Zetafax 5.0 supports the Brooktrout intelligent fax cards including the TR114 and Trufax range under Windows NT.  The Brooktrout boards support DDI, reduce call times and transfer more of the call processing load from the fax server’s main processor to the fax board.

GammaLink fax cards

Zetafax 5.0 supports the GammaLink intelligent fax cards under Windows NT.  The GammaLink boards support DDI, reduce call times and transfer more of the call processing load from the fax server’s main processor to the fax board.

ISDN modems and terminal adapters

Support has been added for the ZyXEL 2864I and Spartacom Spartadis ISDN terminal adapters.  These both act like a normal fax modem, but because they connect to an ISDN line rather than a standard analogue phone line, they can also be used with Direct Dial numbers (MSN or DDI) to support automatic inbound routing.  They are therefore equivalent to the combination of an ISDN fax router and a voice modem.


Q.A.2   What is the difference between the class and group of fax modem?

The service class of the fax modem describes the specification that a PC uses to communicate with the fax modem.  The most common classes of fax modem are Class 1, Class 2 and Class 2.0.  These classes are specified as extensions to the Hayes command set.

The group of a fax device describes the method it uses to communicate with other fax devices (eg. over the telephone PSTN).  The most common group is group III.


Q.A.3   What is the difference between service class 1,2 and 2.0?

Class 1

A class 1 fax modem is little more than a data modem with a few extra frequencies that are necessary for group III fax transmission.

Class 2

Class 2 is a higher level specification than class 1.  More of the fax protocol work is done within the fax modem firmware.  This fax service class specification was never formally approved by the ITU.

Class 2.0

Class 2.0 is similar to the Class 2 specification, but has been formally approved by the ITU.

The advantage of class 2/2.0 support over class 1 is that driving the modem does not hold up the PC with fax timing issues.  This is particularly important in a multitasking environment and for network fax servers (as opposed to single user fax systems - where the user is often happy to wait for a fax to be transmitted).  The advantage of class 1 over class 2/2.0 is that the fax standard can be totally controlled by software rather than being dependent upon the quality of the fax firmware in the modem.

Class 2.0 has the advantage over Class 2 that it has been formally documented and approved by the ITU.  Hence, all class 2.0 devices should behave in the same way.  Although Class 2 devices lack this uniformity they have been in use many years longer than class 2.0 devices - and hence, generally, the fax modem firmware (and its software support) has settled over time to become much more stable and reliable.


Q.A.4   How do I find out what class my fax modem supports?

Windows NT 3.51, 3.1 & 3.11

Make sure that any communications programs that you might use are not currently accessing the com port used by your modem.

Type the following at Windows Terminal.

AT+FCLASS=?

The modem reply will be of the form:

0,1,2,2.0

where 0 is for data, 1 is Class 1 fax, 2 is Class 2 fax and 2.0 is Class 2.0 fax.

Windows 95

Make sure that any communications programs that you might use are not currently accessing the com port used by your modem.

Run HyperTerminal.  When prompted for a connection name type in ‘test’ and click OK.  You will then be asked which modem to connect with, choost ‘Direct to COMn’, where ‘n’ is the com port number used by your modem.  Click OK twice.

Type the following in the terminal window:

AT+FCLASS=?

The modem reply will be of the form:

0,1,2,2.0

where 0 is for data, 1 is Class 1 fax, 2 is Class 2 fax and 2.0 is Class 2.0 fax.

Windows NT 4.0

Make sure that any communications programs that you might use are not currently accessing the com port used by your modem.

Run HyperTerminal.  When prompted for a connection name type in ‘test’ and click OK.  You will then be asked which modem to connect with, choost ‘COMn’, where ‘n’ is the com port number used by your modem.  Click OK twice.

Type the following in the terminal window:

AT+FCLASS=?

The modem reply will be of the form:

0,1,2,2.0

where 0 is for data, 1 is Class 1 fax, 2 is Class 2 fax and 2.0 is Class 2.0 fax.


Q.A.5   What is FCLASS-1?

FCLASS is the name of the Zetafax device driver that is used to control Class 2/2.0 fax modems.  Hence FCLASS-1 is the default name of the first fax modem attached to the Zetafax server.

Note that the number after the device name does not relate to the fax service Class of the modem.  For example, a Zetafax server that has been configured to use 4 fax modems would have drivers named (by default), FCLASS-1, FCLASS-2, FCLASS-3 and FCLASS-4.


Q.A.6   Is there a supported list of modems?

ZETAFAX - Supported modems - 1 May 96

Zetafax can be used with modems which support the Class 2 or Class 2.0 standards.  It also supports voice fax modems, using the Rockwell voice command set, for use with DDI/DTMF automatic inward routing.  Modems supporting these standards include the following:

Amber Logic AL9642 fax modem

Amber Logic Mistral 14400B fax modem

Amber Logic Mistral FX144e fax modem

Amber Logic Mistral FX144i fax modem

Amber Logic Mistral FX144s fax modem

Amber Logic Mistral FX24e fax modem

Amber Logic Mistral FX24i fax modem

Amber Logic Mistral FX24s fax modem

Amber Logic Mistral FX96e fax modem

Amber Logic Mistral FX96i fax modem

Amber Logic Mistral FX96s fax modem

Andest Roadrunner fax modem

Ascom AM2496F fax modem

Banksia MyFastInModem fax modem

Banksia MyFastModem fax modem

Banksia MyInModem fax modem

Banksia MyModem fax modem

Banksia MyPocketModem fax modem

Banksia MX6 fax modem

Brooktrout TR112 fax board port

Brooktrout TR114 fax board port

Brooktrout Trufax fax board port

Dataflex Comfax II fax modem

Dataflex Desktop Hypergem fax modem

Dataflex Desktop Rapier+ fax modem

Dataflex Desktop Supergem fax modem

Dataflex PC Comfax fax modem

Dataflex PC Hypergem fax modem

Dataflex PC Rapier+ Enhanced fax modem

Dataflex PC Rapier+ fax modem

Dataflex PCMCIA Hypergem fax modem

Dataflex PCMCIA Rapier+ fax modem

Dataflex Portable Comfax fax modem

Dataflex Portable Hypergem fax modem

Elink 323 ISDN terminal adapter

Multitech MultiModem MT1432 BLK fax modem

Multitech MultiModem MT1432 LTI-UK fax modem

Multitech MultiModem MT1432 MK fax modem

Multitech MultiModem MT1932 ZDX K fax modem

Multitech MultiModem MT932 BK fax modem

Nokia DTP2 data adaptor

Pace Linnet 32Plus fx fax modem

Pace Linnet 32Plus vfx voice fax modem

Pace Linnet 34 fax modem

Pace Linnet 34 Vfc fax modem

Pace Linnet Message desk voice fax modem (external only)

Pace Linnet Quad fx fax modem

Pace Microlin fx 24 fax modem

Pace Microlin fx 32Plus fax modem (black case only)

Pace Microlin fx fax modem

Pace Microlin NB24Plus fax modem

Pace Microlin NB32Plus fax modem

Practical Peripherals fax modem

Psion Dacom Gold card V22bis fax modem

Psion Dacom Gold card V32 fax modem

Psion Dacom Gold card V32bis fax modem

Psion Dacom Gold card V34 fax modem

Psion Dacom Gold card VFC fax modem

Psion Dacom Meteor 144 fax modem

Psion Dacom Meteor 288 fax modem

Psion Dacom PDM40F fax modem

Psion Dacom PDM4F fax modem

Psion Dacom PDM50F fax modem

Psion Dacom PDM60F fax modem

Psion Dacom PDM6F fax modem

Racal Maxam fax modem

Smartlink InModem E4F fax modem

Smartlink M4F fax modem

SpartaCom Spartadis terminal adapter

Supra fax modem

Twincomm fax modem

USRobotics Courier Terbo fax modem

USRobotics Courier V.34 fax modem

USRobotics Courier V.F.C. fax modem

USRobotics Sportster 14,400 FAX fax modem

USRobotics Sportster 28,800 FAX fax modem

USRobotics Worldport Dual Standard fax modem

USRobotics Worldport PCMCIA DS fax modem

Zoom v.34 fax modem

Zoom vfp 14.4 fax modem

Zoom vfp 28.8 fax modem

Zoom vfp v32bisv voice fax modem

Zoom vfx 14.4 fax modem

Zoom vfx 28.8 fax modem

Zoom vfx v32bisv voice fax modem

ZyXEL 2864I ISDN voice fax modem

ZyXEL U-1496 fax modem

ZyXEL U-1496B fax modem

ZyXEL U-1496B PLUS fax modem

ZyXEL U-1496E fax modem

ZyXEL U-1496E PLUS fax modem

ZyXEL U-1496EG fax modem

ZyXEL U-1496EG PLUS fax modem

ZyXEL U-1496P fax modem

ZyXEL U-1496P PLUS fax modem

ZyXEL U-1496R fax modem

ZyXEL U-1496R PLUS fax modem

ZyXEL U-1496S fax modem

If your modem is not listed, select another modem by the same manufacturer or choose "Other EIA Class 2 or 2.0 modem".  Please contact Equisys for further details.

Please note that this list does get updated occasionally


Q.A.7  Can Zetafax work with a Hayes Optima or Accura fax modem?

Yes, Hayes optima (class 2 only) and Accura (class 2 only) modems will work with Zetafax.  Hayes incorporated support for fax class 2 in these ranges of modems in January 1996.  Here is list of Hayes modems which support fax class 2.

OPTIMA 288 Business Modem

OPTIMA 144 Business Modem

OPTIMA 288 V.34 + FAX for PCMCIA

ACCURA 288 Message Modem

ACCURA 288 V.34 + FAX

ACCURA 144 + FAX144

Please note that the above have not yet been formally tested by Equisys.


Q.A.8  How do I add extra modem initialisation strings in Zetafax?

There follows a short extract from SETUP.WRI.  This file is shipped with the full Zetafax system and describes the setting in zfax\SYSTEM\Z-DB\SETUP.INI.

[FCLASS-n] Section Settings

The [FCLASS-n] section contains settings which are used by the device controller for Class 2 fax modems.  Each device has its own section with the same name as the device (eg "[FCLASS-1]"), and each can be changed independently.

The [FCLASS-n] section can contain the following settings:

CheckInit1: <string>

Default:	none

Purpose:	Specifies a set of Hayes commands to send to the modem just before the regular poll which initialises the modem and checks that it is present.  It may be used to send additional "AT" commands to the modem.  For example to send the command "ATS6=10S7=10" you could add the line:

CheckInit1: S6=10S7=10

Care should be taken with this command.  A number of Hayes commands (such as enabling short replies) are sent automatically and required by the device controller.  See also the CheckInit2, SendInit and ReceiveInit parameters.

CheckInit2: <string>

Default:	none

Purpose:	Specifies a set of Hayes commands to send to the modem just after the regular poll which initialises the modem and checks that it is present.  For details see the CheckInit1 parameter.

ReceiveInit: <string>

Default:	none

Purpose:	Specifies a set of Hayes commands to send to the modem just before answering an incoming call, after the other initialisation commands.  For details see the CheckInit1 parameter.

SendInit: <string>

Default:	none

Purpose:	Specifies a set of Hayes commands to send to the modem just before dialling a fax number, after the other initialisation commands.  For details see the CheckInit1 parameter.


Q.A.9  How do I find out what firmware I have in my modem?

Windows NT 3.51, 3.1 & 3.11

Make sure that any communications programs that you might use are not currently accessing the com port used by your modem.

Type the following in the terminal window:

ATi1

or

ATi3

If neither of these commands result in the firmware revision being displayed, check your modem manual or with the modem manufacturer.

Windows 95

Make sure that any communications programs that you might use are not currently accessing the com port used by your modem.

Run HyperTerminal.  When prompted for a connection name type in ‘test’ and click OK.  You will then be asked which modem to connect with, choost ‘Direct to COMn’, where ‘n’ is the com port number used by your modem.  Click OK twice.

Type the following in the terminal window:

ATi1

or

ATi3

If neither of these commands result in the firmware revision being displayed, check your modem manual or with the modem manufacturer.

Windows NT 4.0

Make sure that any communications programs that you might use are not currently accessing the com port used by your modem.

Run HyperTerminal.  When prompted for a connection name type in ‘test’ and click OK.  You will then be asked which modem to connect with, choost ‘COMn’, where ‘n’ is the com port number used by your modem.  Click OK twice.

Type the following in the terminal window:

ATi1

or

ATi3

If neither of these commands result in the firmware revision being displayed, check your modem manual or with the modem manufacturer.


Q.A.10  Does Zetafax support intelligent fax boards?

Yes, Zetafax 5.0 supports the Brooktrout intelligent fax cards including the TR114 and Trufax range under Windows NT.  GammaLink support is also available under Windows NT.  These intelligent fax boards support DDI, reduce call times and transfer more of the call processing load from the fax server’s main processor to the fax board.


Q.A.11  Does Zetafax work with multi-port serial cards?

Yes, Zetafax supports DIGI’s PC/4e, PC/8e, Acceleport 4 port and Acceleport 8 port intelligent ISA bus cards.  These intelligent cards facilitate multiple line support on the Zetafax server by transferring more of the call processing load from the fax server’s main processor.


Q.A.12  My modem is not working.  What should I try doing?

1.	If the modem is internal check for interrupt or memory address clashes.  You will need to find out what interrupt and memory address each peripheral within the PC is using.

2.	Under 16 bit Windows, do not run any DOS applications full screen, with the fax server in the background.  Try closing down any other applications.

3.	Check whether your fax modem is on the Zetafax supported modem list.  If not check that it supports Class 2 or Class 2.0 fax service class.

4.	Check that your fax server PC meets Zetafax minimum hardware requirements.

5.	Check with the modem manufacturer that you have the latest release of the fax modem firmware, and find out when the next maintenance firmware release will be.  Ask whether their are any known problems with the firmware you have.

6.	If you are using an intelligent serial card and/or special COM port drivers, remove them from the system.

7.	If you have another class 2 fax modem, try configuring that for use with Zetafax.

8.	Check that you have the correct type of serial cable.  Replace it if possible.

9.	Try attaching the modem to a different PC on the network, and running the fax server from that PC.

10.	Ensure that the fax modem you are using is compatible with the telephone PSTN in the country you are in.  An easy way to check this is to look for local telephone authority approval.

11.	If characters are being dropped or erroneous data received on receiving faxes, try reducing the ReceiveSpeed setting in the [FCLASS-n] paragraph of the Zetafax SETUP.INI file.

12.	If you are experiencing difficulties with sending / receiving check if this is happening with all devices sent to or receiving from.  If you can successfully send to other devices it is most likely that there is an incompatibility between your fax modem and the other fax device.  This can usually be fixed with a firmware upgrade which can be obtained from the modem manufacturer (usually free).


Section B - Installation and removal

This section of the FAQ deals with the installation and removal of Zetafax under various PC operating systems.


Q.B.1   How do I install Zetafax under Windows NT?

Zetafax 5

Zetafax 5 installs automatically under NT 3.51 or NT 4.0.  Simply run the SETUP.EXE program from the installation disk and follow on screen prompts.

NOTE:  If you are running the 16 bit fax server, note that the best performance is often obtained by running it under Windows 3.x.

Zetafax 4.5

Before installing Zetafax v4.5 under Windows NT, read the WIN-NT.TXT file on the disk.  After installation, this file can be found in the zfax\SYSTEM directory.

ZETAFAX for Windows NT

Zetafax can be used with a mixture of Windows, Windows NT and Windows 95 machines as required.

To install on Windows NT:

1.	Ensure that you have full Administrator rights, then run the Zetafax Installation program (INSTALL.EXE) from the 32 bit Zetafax server disks supplied.

The workstation installation program will make some changes to the WIN.INI file [ports] and [extensions] sections.  Under Windows NT these are mapped into sections of the Registry database.

By default Administrators are allowed to make these changes.  However if this has been changed on your computer you will get an error message when installing.  If you do not wish to use the Windows NT machine as a workstation you can ignore this message; otherwise you should log in as a user with additional rights (or correct the permissions using REGEDT32), and rerun the installation.

Restart Windows NT (just logging off is not sufficient), then create a printer as described below.

2.	To configure a Zetafax workstation under Windows NT, log in as a user with full Administrator rights and then run the Workstation Setup program (zfax\SYSTEM\WKSETUP.EXE).  This is done on the fax server PC automatically during installation.  See above if an error is displayed when trying to update the device settings.

Restart Windows NT (just logging off is not sufficient).

Now use print manager to add a new printer with name set to "Zetafax printer", driver "Epson LQ-1000", and printing to "C:\WINNT\ZETAFAX.SPL" (in your Windows NT directory).  This will be in the list of available ports provided you have restarted Windows NT since running the WKSETUP program.

3.	Finally, to send a fax you just run the Zetafax workstation, then print to the Zetafax printer.  Provided the workstation is running and its title bar does not say "offline", the addressing dialog box will be displayed after a few moments.  (If the workstation is offline you should check the Zetafax server is running.)

If you are running the 16 bit fax server, note that the best performance is often obtained by running it under Windows 3.x.


Q.B.2   How do I remove a default Zetafax installation from my system?

ZETAFAX - Default System Uninstallation Notes - Release 5.0

This article describes how to remove a default Zetafax installation from a Windows 3.x, Windows 95 or Windows NT system.  Advanced options are marked by a *.

A. Removing the Zetafax workstation

1.	*Stop loading the workstation on Windows startup

If you have set up the workstation program to automatically start whenever Windows is started  - an advanced option -  run the WKSETUP.EXE program stored in the zfax\SYSTEM directory and select "Edit configuration - advanced settings after installation" to turn off this feature.

2.	Delete the Zetafax group in Program Manager

3.	Remove the Zetafax printer driver

Under Windows 3.x, remove the Zetafax printer using the Printers applet in Control Panel.

Under Windows 95, remove the Zetafax printer by selecting Settings and printers from the taskbar.

Under Windows NT, use Print Manager to remove the printer.

4. Delete the workstation files

Delete ZETAFAX.* and ZSPOOL.EXE from the C:\WINDOWS directory.

Delete ZFAX.DRV from the C:\WINDOWS\SYSTEM directory.

Under Windows NT, these files are situated in the directory pointed to by the WINDIR environment variable, usually WINNT or WINNT35.

*If you have moved the workstation files to a new directory using WKSETUP.EXE  - an advanced option -  delete the files from that directory.

B. Removing the Zetafax Server

5. Delete the Zetafax directory structure.

By default all of the Zetafax files are installed under a base directory named ZFAX.  *If you have opted to install the Server, System, User and Request areas onto different directories/drives (perhaps for security reasons) you need to delete them from these areas.


Q.B.3   How do I totally remove a complex Zetafax installation from my system?

ZETAFAX  - Advanced System Uninstallation Notes - Release 5.0

This article describes how to remove Zetafax from a Windows 3.x, Windows 95 or Windows NT system.  Many of these steps will not apply if you have installed Zetafax with the default options.  Advanced options are marked by a *.

A. Removing the Zetafax workstation

1.  *Stop loading the workstation on Windows startup

If you have set up the workstation program to automatically start whenever Windows is started  - an advanced option -  run the WKSETUP.EXE program stored in the zfax\SYSTEM directory and select "Edit configuration - advanced settings after installation" to turn off this feature.

2.  Delete the Zetafax group in Program Manager

3.  Remove the Zetafax printer driver

Under Windows 3.x, remove the Zetafax printer using the Printers applet in Control Panel.

Under Windows 95, remove the Zetafax printer by selecting Settings and printers from the taskbar.

Under Windows NT, use Print Manager to remove the printer.

4.  Remove the Zetafax file extension associations.

Select File|Associate in File Manager.  Enter the extension G3N, then

blank the "Associate With:" field and click OK.  Do the same for the G3F, G3N and SPL extensions.

5.  Delete the ports entries used by the Zetafax printer driver

Under Windows 3.x, open WIN.INI in a text editor, and remove the entries for ZETAFAX.SPL from the [Ports] section.

Under Windows NT the [Ports] section is mapped to

HKEY_LOCAL_MACHINE|SOFTWARE|Microsoft|Windows NT|CurrentVersion|Ports

in the registry.  Use the registry editor to remove the entries for ZETAFAX.SPL.

6.  Delete the workstation files

Delete ZETAFAX.* and ZSPOOL.EXE from the C:\WINDOWS directory.

Delete ZFAX.DRV from the C:\WINDOWS\SYSTEM directory.

Under Windows NT, these files are situated in the directory pointed to by the WINDIR environment variable, usually WINNT or WINNT35.

*If you have moved the workstation files to a new directory using

WKSETUP.EXE  - an advanced option -  delete the files from that directory.

7.  *Remove the USERNAME environment variable

If you have opted for Zetafax to determine the Zetafax user name

from the USERNAME environment variable - an advanced option - remove the "SET USERNAME" line from AUTOEXEC.BAT.

8.  *Remove the ZFAXINIT environment variable

If you have opted for Zetafax to determine the location of ZETAFAX.INI using the ZFAXINIT environment variable - an advanced option - remove the "SET ZFAXINIT" line from AUTOEXEC.BAT.

Under Windows NT, remove ZFAXINIT from the System Environment Variables by running the System applet from Control Panel.

9.  *Stop running the DOS spooler TSR

If you have opted to run the TSR program for an old DOS application

running under Windows - an advanced option - remove the entry for ZSPOOL.EXE from AUTOEXEC.BAT.

B. Removing the Zetafax Server

10. Delete the Zetafax directory structure.

By default all of the Zetafax files are installed under a base directory named ZFAX.  *If you have opted to install the Server, System, User and Request areas onto different directories/drives (perhaps for security reasons) you need to delete them from these areas.


Q.B.4 How can I move my fax server from one machine to another?

Zetafax is supported across numerous different networks resulting in numerous types of installation.  Here are some typical scenarios:

Current fax server machine:

Workstation on Windows for Workgroups peer to peer network

New fax server machine:

Another workstation on the network

Current installation:

The Zetafax server files and directories are installed on a the local drive of a workstation on the network, and the Zetafax clients have a drive mapping to this workstation which runs the fax server programs.

Action:

I.	Move the server files from the current fax server machine to the intended fax server machine.

II.	Run WKSETUP.EXE on the new fax server machine which will automatically create a new C:\WINDOWS\ZETAFAX.INI as well as Zetafax program group and program items for the workstation setup program and the Zetafax workstation.

III.	Add the following items in the new Zetafax program group:

A.	Zetafax server, command line: \zfax\SYSTEM\ZSERVER.EXE

B.	Zetafax setup, command line: \zfax\SYSTEM\SETUP.EXE

IV.	For each of the Zetafax workstations on the network, run the WKSETUP program and select “install workstation - standard settings” to create new pointers to the new Zetafax server machine.  If you have mapped the new location of the fax server to the same logical network drive as it was previously, there is no need to perform step 4.

V.	Connect all fax modem devices to the new Zetafax server machine.

Current fax server machine:

Windows workstation on Novell or NT file server.

New fax server machine:

Windows workstation dedicated as a fax server on the network.

Current installation:

On Novell networks (and some NT networks), the Zetafax files and directories are installed onto a network drive and run over the network on either a dedicated fax server machine or in the background of an existing workstation on the network.

Action:

I.	The Zetafax server files and directories remain on the file server.

II.	Run the workstation setup program on the new fax server machine.  This will create a program group containing the workstation and the workstation setup icons.  You will have to add extra program items for the Zetafax  server (\zfax\SYSTEM\ZSERVER.EXE)and the Zetafax setup program (\zfax\SYSTEM\SETUP.EXE).

III.	Connect all fax modem devices to the new Zetafax server machine.

Current fax server machine:

Windows workstation set up as a dedicated fax server on Novell network.

New fax server machine:

Windows NT workstation on Novell network running the 32-bit Zetafax server programs.

Current installation:

The Zetafax files and directories have been installed on a network drive and are being run across the network on a dedicated fax server machine running Windows 3.x.

Action:

I.	Run the workstation setup program on the NT workstation machine.  This will create a program group containing the workstation and the workstation setup icons.

II.	Move the entire \zfax\SERVER directory from the network drive to the local drive on the NT Workstation machine.  Note the REQUEST, SYSTEM and USERS directories still remain on the network drive.

III.	Open the file C:\WINNT35\ZETAFAX.INI in a text editor such as notepad and change the line ServerArea: in the [SERVER] paragraph to correspond with the local path containing the Zetafax files and directories eg C:\ZFAX\SERVER.Connect all fax modem devices to the new Zetafax server machine.

You can upgrade the Zetafax server software from the 16-bit version of the server to the 32-bit version which will run as a service under Windows NT Workstation or Server.  If you have purchased version 5.0 (also applies to version 4.5), you will be in possession of 4 disks, 2 for installing the 16-bit server software, and 2 for installing the 32-bit server software.  To upgrade from the 16-bit version of the server to the 32-bit version perform the following:

I.	Insert the 32-bit installation disk 1 into the floppy drive.

II.	Select File | Run from program manager then type A:\INSTALL.

III.	Select “update selected server files” from the next dialog box.

IV.	Select “Programs and Fonts” and the following dialog box (make sure you only select this option if you want to retain your current settings).  The install program will overwrite the existing 16-bit server modules with their 32-bit equivalent.

V.	From the Zetafax program group, run the NTSETUP application to install the Zetafax server as a service.

Current fax server machine:

Windows NT server.

New fax server machine:

Another Windows NT machine on the same LAN.

Current Installation:

The Zetafax files and directories have been installed on a drive local to the NT server machine and are made available to other Zetafax users via mapped logical drives from the network client machines.

Action:

I.	Run the NTSETUP.EXE program on the current fax server machine and select the “Remove Zetafax Service” option to remove the relevant entries from the registry.

II.	Move the server files from the current fax server machine to the intended fax server machine.

III.	Run WKSETUP.EXE on the new fax server machine which will automatically create a new C:\WINDOWS\ZETAFAX.INI as well as Zetafax program group and program items for the workstation setup program and the Zetafax workstation.

IV.	Add the following items in the new Zetafax program group:

A.	Zetafax  server, command line: \zfax\SYSTEM\ZSERVER.EXE

B.	Zetafax setup, command line: \zfax\SYSTEM\SETUP.EXE

V.	For each of the Zetafax workstations on the network, run the WKSETUP program and select “install workstation - standard settings” to create new pointers to the new Zetafax server machine.  If you have mapped the new location of the fax server to the same mapped network drive as it was previously, there is no need to perform step 5.

VI.	Run the NTSETUP.EXE program on the new fax server machine and select the “Install Zetafax Service” option to make the relevant changes to the registry to allow you to run the Zetafax server as a 32-bit service.

VII.	Connect all fax modem devices to the new Zetafax server machine.


Q.B.5  How do I install Zetafax onto Windows NT 4.0?

Zetafax 5.0 will install automatically under Windows NT 4.0 without any need for user intervention.

To install Zetafax 4.5 on NT 4.0

1.	Install the 32-bit version of the fax server from another machine running a 32-bit operating system, to a network drive either Windows 95 or Windows NT 3.5x.

2.	Run WKSETUP.EXE on the NT 4.0 fax server machine which will automatically create a new C:\WINNT\ZETAFAX.INI as well as Zetafax program group and program items for the workstation setup program and the Zetafax workstation.

3.	Add the following items in the new Zetafax program group:
a) Zetafax  server, command line: \zfax\SERVER\ZSERVER.EXE
b) Zetafax setup, command line: \zfax\SERVER\SETUP.EXE
c) NT Setup, command line: \zfax\SERVER\NTSETUP.EXE

4.	Run the NTSETUP.EXE program on the new fax server machine and select the "Install Zetafax Service" option to make the relevant changes to the registry to allow you to run the Zetafax server as a 32-bit service.


Q.B.6  How do I configure a modem for incoming fax plus outgoing fax/RAS/data?

The same modem can be used to receive incoming fax calls and make outgoing fax, RAS and data calls.  This means that you no longer have to stop running the Zetafax Server (or switch the modem off-line) if you want to make an outgoing call from another package.

To do this, all you need is the SAPS modem sharing product for Windows NT, for more information on SAPS take a look at question number Q.D.2.

Following are instructions for configuring your modem for incoming fax and outgoing fax, RAS and data:

1.	The SAPS client and server must be installed on the NT machine with the modems attached.

2.	Configure RAS to access the modem through the SAPS redirector.

3.	Share the modem from the SAPS server and give it a share name which is meaningful (using COM2 as a share name can get confusing - I’d suggest using the make of the modem eg USR for a US Robotics modem).

4.	Connect to this new shared resource via the SAPS port redirector using one of the additional COM ports the software has created eg COM3.

5.	Configure your modem within Zetafax to access the modem directly (ie not through the SAPS redirector), so if the modem is attached to COM2, Zetafax should be configured for COM2.  (Make sure that you select a user to receive incoming faxes).


Q.B.7  How do I configure a modem for incoming RAS plus outgoing fax/RAS/data?

The same modem can be used to receive incoming RAS calls and make outgoing fax, RAS and data calls.  This means that you no longer have to stop running the RAS if you want to make an outgoing call from another package (Zetafax for example).

To do this, all you need is the SAPS modem sharing product for Windows NT, for more information on SAPS take a look at question number Q.D.2.

Following are instructions for configuring your modem for incoming RAS and outgoing fax, RAS and data:

1.	The SAPS client and server must be installed on the NT machine with the modems attached.

2.	Configure RAS to access the modem directly (ie not through the SAPS redirector), so if the modem is attached to COM2, RAS should be configured for COM2.

3.	Share the modem from the SAPS server and give it a share name which is meaningful (using COM2 as a share name can get confusing - I’d suggest using the make of the modem eg USR for a US Robotics modem).

4.	Connect to this new shared resource via the SAPS port redirector using one of the additional COM ports the software has created eg COM3.

5.	Configure your modem within Zetafax to use the new share (COM3) and to be set to send outgoing calls only (by selecting disabled as the user to receive incoming faxes).

6.	Start the Zetafax server first, then the RAS Admin Service (you can automate this by making the RAS server service dependent on Zetafax by adding the string ZetafaxServer to the HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\RemoteAccess\DependOnService subkey in the Windows NT registry).  This allows Zetafax to recognise the modem on startup and allow it to be shared between both applications.


Q.B.8   How can I install Zetafax to run with Citrix WinFrame?

1.	Create M:\ZFSPOOL\ROGERB (M: is the equivalent of users C: drive), share this, then connected it to the Z: drive.

2.	Use WKSETUP to set the spool directory to Z:\

3.	Set system environment variable ZFAXINIT=Z:\

4.	Move ZETAFAX.INI to Z:\

For each new user you will simply have to create a new directory, map Z: to it, then copy the ZETAFAX.INI to that directory.


Section C - Software feature lists

This section of the FAQ answers common questions about the various features supported by both the Zetafax Server and Workstation.


Q.C.1  Does Zetafax support different fax resolutions?

Yes.  Zetafax supports both standard (200x100 dpi) and fine (200 dpi) mode fax, as defined by the group III fax specification.


Q.C.2  What networks does Zetafax support?

Artisoft LANtastic

Banyan Vines

IBM LAN Server

Microsoft LAN Manager (OS/2 and Unix servers)

Microsoft Windows NT Server

Microsoft Windows for Workgroups

NETBIOS

Novell Netware

Performance Technology POWERLan

Sun PC NFS

All other leading networks


Q.C.3  Can I scan a document directly into Zetafax?

Yes.  Zetafax supports all TWAIN compatible scanners.


Q.C.4  Which file formats are supported directly by the Zetafax workstation?

ASCII, DCX, EPS bitmaps, Epson FX and LQ series, GIF, JPEG, PCX, PICT, Targa, TIFF, Windows metafile bitmaps, WordPerfect metafile bitmaps.

Any other format file may be sent as a fax by printing from the application that created it.


Q.C.5  What are the main features of the fax server?

Single prioritised queue of faxes for all users

Automatic redial on busy line

Automatic reconnection after communications failure (sending remaining pages only)

Delayed and off-peak transmission

Up to 32 fax lines for send and receive

Each fax line may be reserved for receive only or send only

Shared and private address books

Import and export of address books

Broadcast/mailmerge using address books, embedded addressing information, ODBC databases or CSV text files

Distribution lists

Export of billing log to spreadsheets, databases and accounting software

Automatic archiving and printing (1, 2 or 4 pages per sheet) of faxes sent and received

Full use of file server permissions to protect fax messages and signature graphics files

Single user mode when disconnected from LAN

Automatic recovery after a power failure

Windows, Windows 95 and Windows NT versions available

Fax routing via e-mail

Group receipt of faxes and Departmental DID

Automatic printing of faxes per user


Q.C.6  What are the minimum hardware requirements for the fax server?

Windows 3.1 or 3.11 fax server:  486 PC or faster, 6MB RAM, fax modem

Windows 95 fax server:  486 PC or faster, 12MB RAM, fax modem

Windows NT (Intel) 3.51 or 4.0 fax server:  486 PC or faster, 16MB RAM, fax modem or intelligent fax board

Windows NT 3.51 (RISC) fax server:  Alpha AXP or PowerPC computer, 32MB RAM, fax modem

Fax client:  Microsoft Windows 3.x, Windows 95, Windows NT (Intel or RISC) 3.51 or 4.0

A Windows NT or dedicated fax server is recommended for over 25 users or multiple fax lines.


Q.C.7  What are the main features of the workstation?

Verification that faxes have been sent

Warning that faxes have failed

Notification that a fax has been received

Handles graphics and Truetype fonts

Signatures and graphics may be placed in documents at any position

Automatic coversheet generation (fully configurable)

Documents overprinted onto letterheads and continuation sheets

Graphics file attachments

Logs of usage and errors for a given message, fax modem or user

Long term transmission history for a given file

Barred fax numbers (per user)

Ability to submit urgent messages (per user)

Limited transmission times (per user) eg off-peak only

Ability to edit the shared address book (per user)

System administrator privileges (per user)

Viewing of faxes at four resolutions

On-screen rotation of faxes when being viewed

Windows printer driver and workstation program

TSR program for use with DOS applications (if required)

32bit and 16bit version available


Q.C.8  What are the minimum hardware requirements for the workstation?

Workstation: 386SX PC, 4 MB RAM, DOS 3.3 or above, Microsoft Windows 3.1 or above


Section D - Miscellaneous Q&A

This section contains any miscellaneous questions that are asked frequently.


Q.D.1   How can another communications software packages access the fax modem that is being used by Zetafax?

In versions of Zetafax prior to 4.50k, you needed to turn the modem device offline at the server before it could be used by other communications software packages.  This is done at the server by clicking the Option|Devices menu item to display a dialog that will allow devices to be turned online and offline.  A device could also turned offline automatically or remotely by using a Zetafax server request file.

Version 4.50k and later of Zetafax incorporates support for Spartacom’s SAPS modem sharing software which allows the same fax modem which was previously reserved only for sending and receiving faxes to be used by users across a network to make outgoing data calls to online services such as the Internet or CompuServe.  This can be done without the need for any manual intervention, for example if a user wants to make a call via the modem the SAPS server software “asks” Zetafax whether the modem is in use or not.  If the modem is not in use, Zetafax will release it for use by another comms package via SAPS.


Q.D.2 What is SAPS modem sharing software, and how can it be used with Zetafax?

SAPS answers the long-standing problem of modem sharing.  It is a software solution which allows you to use modems connected to one computer from any computer on the network.

Make better use of modems and phone lines

SAPS lets users access pooled modems for outbound calls as if the modem was connected to their own computer.  You can share modems on the network just as you share directories and printers, saving the cost of installing separate modems and phone lines for each user.

Control communications use

The system administrator can determine who can access the shared modems, giving each modem or pool a password if required.  It can also disconnect automatically if the modem has not been used for a given period - ideal for those users who forget to hang up before going off to lunch!

Share modems for data, fax and remote access

Now SAPS integrates with Zetafax and Microsoft RAS to let you to use the same modem for fax, data and remote access calls.

Separately, Zetafax and SAPS are leaders in their fields. Used together they enable you to build a powerful communications server, using your modems more effectively.

Configuration

With Zetafax, SAPS and RAS together, each modem can handle any type of outgoing call: fax or data.  If a modem is also to answer incoming calls, it is configured either to receive faxes or answer RAS calls, but not both.

Here is an example communications server which handles faxing and Internet access, while also allowing dial-up to the network from home:

Modem 1 - reserved for incoming fax

Modem 2 - incoming fax plus outgoing fax and data calls

Modem 3 - incoming RAS calls plus overflow outgoing fax and data calls

The exact configuration you choose may depend on the relative amounts and priorities of fax and data traffic, and those needs can change with time.  For example, you may want to add additional lines for outgoing data or fax calls as the traffic levels increase, or reserve lines for incoming RAS only.

With SAPS modem pooling feature and the Zetafax server’s single managed queue, users on the network do not need to worry about the exact configuration used, or even be aware when changes are made by the network administrator.

Incoming fax lines on a Windows NT server

When a modem is used for incoming calls, Zetafax “owns” it and is continually checking for an incoming call.  With the Windows NT version of the Zetafax and SAPS servers, this modem can also be made available to network users for data calls.

When a SAPS workstation asks to connect to the modem, SAPS tells Zetafax to release it.  Provided it is not currently being used to send or receive a fax, Zetafax hands the modem to SAPS.  When the data call is completed, SAPS returns the modem to Zetafax.

Incoming Microsoft RAS lines

When awaiting incoming calls, RAS takes hold of a modem, keeping the COM port “open” to check for ringing.  SAPS asks RAS to release the modem whenever it is required for an outgoing call, returning it to RAS when the call is over.

If you want to send faxes with the modem, then Zetafax uses it via SAPS in the same way as other applications.  The modem is normally physically connected to the computer running the Zetafax server software, but can be on a different computer if required.

Outgoing only lines

When a modem is configured for outgoing calls only, Zetafax releases it when it is not being used.  It can therefore be shared with other applications using SAPS.

Zetafax can be configured to use the modem directly or through SAPS: useful if the modem is physically connected to another computer.  SAPS’ password and access logging features help manage how the modem is used.

Server platforms

A full range of features are available on Windows NT based communications servers.  The Windows 3.x versions of the Zetafax and SAPS servers allow modems to be shared for outgoing fax and data calls, but not incoming calls.


Q.D.3   Can the Zetafax server be shutdown or restarted remotely?

Yes, using a shutdown or restart server request file.  See question Q.D.4 for more information.


Q.D.4   What are Zetafax server request files?

Overview

The Zetafax server programs are run and controlled by the system manager program, SYSMAN.  When a workstation wants the server to perform a function (eg to queue a new message for sending) it creates a request file in the zfax\REQUEST directory, containing details of the function required.  This mechanism is also used by certain utility programs.

SYSMAN regularly checks the zfax\REQUEST directory for request files (any file with extension .CTL).  Each time one is found, a message is displayed on the server screen, and the request is passed to the appropriate server program.

The request files are simple ASCII text files.  User written programs or batch files can therefore control certain server functions by creating the appropriate file in the directory.

This article details certain of the request files.  The mechanism described in this document, including the format of the request files, is correct for the current version of the Zetafax server (version 4.0).

Server shutdown request

Causes SYSMAN to shutdown the server programs in an orderly fashion then exit (as with the "Options | Shutdown" ZSERVER menu choice).

[REQUEST]

Server: SYSMAN

Type: SHUTDOWN

Restart server request

Requests SYSMAN to shutdown the server programs then restart them in turn.  This might be used after modifying certain server settings, or configuring additional devices.

[REQUEST]

Server: SYSMAN

Type: RESTART

Set device offline request

Requests a given device (eg "FCLASS-1") to go offline.  This stops messages being sent or received on the given device, and also frees the COM port for use by other programs.  The device remains offline until an online request is issued, or the server is restarted.

The "Wait" and "Abort" lines determine the behaviour if the device is currently processing a message.  If "Wait" is set to NO, the command will be rejected (and an error message displayed).  If "Wait" is YES the device remembers the request, and goes offline when it completes the current task.

If "Abort" is set to YES the current job will be aborted.  Therefore to force the device offline as quickly as possible, both "Wait" and "Abort" should be set to YES.

[REQUEST]

Server: DEVICE

Type: OFFLINE

Device: devicename

Wait: [YES | NO]

Abort: [YES | NO]

Set device online request

Requests a device which has been set offline to return to the idle state, making it available for sending and receiving messages.

[REQUEST]

Server: DEVICE

Type: ONLINE

Device: devicename


Q.D.5   How can I read and scroll through all the server messages?

Click Options|Messages at the fax server to scroll through the server messages.

The SERVER.LOG file in the zfax\SERVER\Z-DB directory contains all of the server messages since the last time the server was started. When the Zetafax server is closed and re-started, it renames SERVER.LOG to SERVER.OLD and creates a new SERVER.LOG.


Q.D.6   What major features have been added to Zetafax 5.0 since 4.5?

The major new features that have been added to Zetafax v5.0 since v4.5 are:

1.  New user interface for the address book

    The manner in which addressees are selected from the address book has

    changed radically.

    The Unique Name in an address book record is now optional, and is

    used only as a quick (alternative) method of searching for the entry.

    Editing of groups and entries in the Zetafax default address book has

    been improved, with a new "point-and-click" user interface.

2.  Support for ODBC databases and CSV files

    The workstation now allows you to use a range of different databases to

    store fax recipients.  In addition to the default Zetafax address book

    (comprising a network book and a private book for each user), you can

    also now use ODBC compliant databases or text files (in CSV, comma or

    TAB separated formats).

    The data source is selected on the address book search dialog box, and

    the last 10 external data sources used (including the connection

    information) are remembered for quick selection.

    Having selected an external data source type (ie a database or text file)

    you are first asked to choose the source.  The IMPORT dialog then allows

    asks you to map the required and optional fields (name, organisation,

    fax number etc) to the fields in the data source.  Formats supported

    include:

        DBASE

        SQL Server 6.0

        Microsoft Access 7.0

        Comma and TAB separated text files

3.  High volume fax shots

    You can now send a faxshot to a list of recipients contained in

    a separate text file, either directly from the Zetafax workstation

    program, or by importing it into the main Zetafax address book.

    The text file can be in comma or TAB separated format, and would

    normally contain the name, fax number and (optionally) the

    organisation name.

    To send a faxshot from the workstation you specify the text file

    directly - you do not need to import the entries into the address

    book.  Selection is made by clicking ADDRESS BOOK on the first Zetafax

    addressing dialog, which causes the Address book search dialog to be

    displayed.  Choose "Import text file" in the list of sources, and the

    workstation will then prompt for the import file name, and ask which

    fields in the file to use for name, fax number etc.

    You can also now import comma or TAB separated lists into the address

    book using the ADBUTIL program.  This has been extended to create

    entries and groups automatically from the same format text file,

    prompting for the names to create (eg "FAXSHOT" will create entries

    FAXSHOT1, FAXSHOT2 etc and optionally groups "@FAXSHOT1" etc).

    The server Queue Manager program has been enhanced to ensure that

    there is a negligible performance overhead as the number of

    queued entries increases.

4.  Quick tidy of messages from the IN and OUT windows

    The IN and OUT windows now allow multiple selection (by holding down the

    SHIFT or CONTROL keys before clicking with the mouse, as with other

    Windows programs).  The File Delete and File Abort menu choices can

    be used with multiple files selected, improving the speed of deleting

    large numbers of entries from the windows.

    The Window Tidy-up option has also been improved, and allows you to

    choose the type of message to delete (received, sent OK, failed or

    previewed), as well as giving an age limit.

5.  Import and export from viewer improved.

    Most graphics formats are now supported directly from the Zetafax

    viewer when importing and exporting pages.  Editing features also allow

    you to add or delete pages to the file being viewed.

6.  Allowing groups of users to view incoming faxes

    You can create groups of users who will be notified when a new fax

    is received.  Group names start with an "@" sign, and are created

    using the Zetafax Setup program.  Groups names can be used with the

    automatic routing and printing options in the same way as user

    names, in cases where departmental DDI fax numbers are being used,

    or if you want several users to share the task of checking and

    forwarding received faxes.

7.  Automatic printing of sent and received faxes

    The automatic printing options for sent and received faxes can now

    be specified independently for each user.  This includes what to print

    (full message and/or the status page), the printer to use, and whether

    to delete the fax from the IN box after printing.

    These settings, as well as the format of the printed page can be set

    separately for sent and received faxes, using the Zetafax Setup program.

    This is particularly useful in departmental DDI environments, where the

    fax number dialled can determine which printer is used to print the

    fax, rather than use a single central printer.

8.  Receiving faxes directly to email accounts

    Users may choose whether to receive faxes to their Zetafax IN box, or

    direct to their email Universal Inbox.  This can be used with Microsoft

    Exchange, Microsoft Mail, or cc:Mail (using an additional MAPIVIM.DLL).

    This is configured in the Zetafax configuration program: the email

    account for the Zetafax server to use is set in the "Change server

    settings" section, and the email account for each user is set under

    "Users and user groups".

    This will apply to all faxes they receive (whether directly, via the

    automatic routing mechanisms or when forwarded from another user).

    Note that the email address you enter for the user is a name from the

    mail address book (eg "Gareth Williams"), not a direct email address

    (eg "MSMAIL:GWILLIAMS").

    Some mail systems (eg Microsoft Mail) only allow one mail account to be

    logged in at a time on a given computer - in this case you should make

    sure the mail client is not already running on the computer, or use a

    single mail account for all applications on that computer (eg "Server").

9.  Zetafax 32-bit client

    A 32-bit native workstation is now provided for Intel machines.

    The 16-bit and 32-bit versions of the workstation remain functionally

    equivalent, with the same user interface to ensure a simple

    upgrade path for users switching from Windows 3.x to Windows NT

    or Windows 95.

    Long file name and directory names are now supported by the 32-bit

    version of the workstation.  To ensure the system remains

    independent of the operating system used at the server, files

    such as coversheets and letterheads are restricted to 8 characters;

    however the description field can be used for these to give a

    fuller description if required.

10. Zetafax 32-bit printer

    A 32-bit Zetafax FaxMerge printer driver is now provided which installs

    automatically on Windows NT 3.51 and 4.0. This includes the ability

    to insert FaxMerge fields in documents to be faxed, which will be

    replaced with details of each recipient by the server at the time of

    sending.

11. Support for Windows NT 4

    The Zetafax workstation and server programs may be used with

    Windows NT version 4.

12. Extra fields on coversheet

    Four new FaxMerge fields have been added for use on coversheets.

    These specify details for each user: email address, DDI telephone

    and fax numbers, plus a user definable field suitable for explaining

    the sender’s location within a larger building or site.  These fields

    get filled out automatically on the coversheet.

    The fields can be set by the user, via the Options | Name menu choice

    on the workstation.  They can be included on coversheets in the same

    way as other FaxMerge fields, using the following fields:

%%[FROMPHONE]

%%[FROMFAX]

%%[FROMEMAIL]

%%[FROMOTHER]

13. Zetafax API DLL

    The Zetafax API now includes a DLL for use with applications such as

    Visual Basic and use with previously unsupported compilers.  New

    features include:

        Support for incoming faxes

        Sending multiple message files using SUBMIT files

        Specifying covernote text in the SUBMIT file

        Determining the default name and coversheet for the user.

14. RISC versions of NT 32-bit server

    In addition to the Intel version, versions of the 32-bit Zetafax

    server are also available for use with DEC Alpha and Motorola PowerPC.

    These are functionally identical to the standard Windows NT

    (Intel) version, except that Brooktrout boards are not yet supported

    with the RISC versions.

Enhancements in this release (since version 5.00)

1.  Regular server check speed improved

    The workstation checks regularly (about once a minute) that the

    Zetafax server is still running, changing to "offline" if not.  With

    some network operating systems this check could cause the workstation

    program to pause for a couple of seconds.

    The mechanism used for this check has been changed to remove any

    noticeable pause.

2.  Company name length increased for ODBC databases

    The maximum length of the company name retrieved from ODBC

    databases has been increased from 20 to 30 characters.

3.  Support for additional mail systems in 32-bit workstation

    Mail systems which support the MAPI standard do so using a DLL file.

    Usually a pair of DLLs are supplied, for 16-bit and 32-bit programs.

    For Microsoft Mail these are called MAPI.DLL and MAPI32.DLL

    respectively.

    For other mail systems the DLL files can have different names - eg for

    cc:Mail the files are MAPIVIM.DLL and MAPIVI32.DLL.  The Zetafax

    workstation now reads a line in the WIN.INI file [MAIL] section to

    determine the DLL to use: "MAPIDLL=" for the 16-bit workstation, and

    "MAPIDLL32=" for the 32-bit workstation.  These lines will normally

    be added automatically when the mail system is installed.

4.  Deleting messages and address book entries in 16-bit workstations

    In some installations on Windows 3.x, deleting the final entry from

    the IN or OUT window, and deleting an entry from the address book

    did not work correctly.  This has now been corrected.

Enhancements in this release (since version 4.0)

1.  Use with cc:Mail

    The workstation program's MAPI email support has been extended to

    work with cc:Mail.  It now looks for the line "MapiDLL=..." in the

    [MAIL] section in WIN.INI which specifies whether to use the default

    MAPI DLL (MAPI.DLL), or the version for use with cc:Mail (MAPIVIM.DLL,

    supplied with Microsoft Office programs or available from Microsoft

    bulletin boards).

2.  Running server over Windows NT 3.5 Netware client

    Workstations were unable to connect to a fax server running on a

    Windows NT machine, when the files were installed on a Novell volume

    (with certain versions of Netware only).

    There is a compatibility issue if running the Windows NT fax server

    with the shared files on a Novell server - see the section on

    "compatibility issues" below for more information.

3.  Running Zetafax viewer

    Viewing a fax (for example double clicking a G3F file in File

    Manager) brings up the Zetafax viewer more quickly, and without

    needing to login as a Zetafax user.  It can also now be run on a

    workstation which has not had Zetafax installed.

4.  Accented character support

    Support has been added for extended (accented) characters in

    the Zetafax Roman fonts, and the address book and workstation

    programs.  This means that recipient names and the note on

    coversheet field may now contain accented characters which will

    be displayed correctly on the coversheet and top line of faxes.

5.  International date formats

    Zetafax now allows the format of dates on the coversheet and

    top line of faxes to be modified, for allowing country specific

    date formats.  New Zetafax systems will use the date formats

    set in Windows (for Windows or Windows NT versions of the fax

    server), though this can be overridden if required.

    Two dates are used.  The long format date (eg "21 January 1995")

    is used on coversheets with the %%[DATE] field.  Short format

    dates (eg "21/01/95") are used on coversheets (with the new

    %%[SHORTDATE] field), and also on the header line of faxes

    Existing Zetafax systems can be changed to use the system

    settings by adding the following lines to [OPTIONS] section in

    the SETUP.INI file:

DateFormatLong:

DateFormatShort:

    These lines can also be used to override the default settings

    - see SETUP.WRI for details.

6.  Support for Brooktrout intelligent fax boards

    The 32-bit Zetafax server under Windows NT (Intel) now supports

    Brooktrout intelligent fax boards (TR111, TR114 and Trufax

    models).  These give a number of performance and other advantages

    over standard fax modems.

    Full details about installing and using Brooktrout boards with

    Zetafax are given in the README.WRI file in the zfax\SERVER\BTROUT

    directory.

7.  Support for ZyXEL and Spartadis ISDN fax modems.

    Support has been added for the ZyXEL 2864I and Spartacom Spartadis

    ISDN terminal adaptors.  These both act like a normal fax modem,

    but because they connect to an ISDN line rather than a standard

    analogue phone line, they can also be used with Direct Dial numbers

    (MSN or DDI) to support automatic inbound routing.	They are

    therefore equivalent to the combination of an ISDN fax router and

    a voice modem.

8.  Allow correction of faxes received upside-down

    The Zetafax workstation File Export option now exports the

    page in the orientation it is being viewed.  Thus if a page is

    received upside down you can correct it by viewing the page the

    correct way up (using Page Rotate), exporting it to a temporary

    PCX file, then reimporting the same file.

    This is useful if you want to save the fax as an attachment, or

    process it with an optical character recognition (OCR) program.

9.  Support for East European fonts

    The Zetafax server now supports the East European character set

    (codepage) as well as the standard Windows character set.  It

    uses the current language setting in Windows to determine which

    set to use on a given system, though this can be overridden by

    adding the following line to the [OPTIONS] section in the

    SETUP.INI file:

Language: <lang>

    where <lang> is ENG to use the standard Windows fonts or PLK

    to use the East European set.  This is a system-wide setting

    and affects messages submitted by all workstations.

10. Allow use of modem serial port by other programs

    Modems devices which are configured for send-only (ie where the

    incoming user is set to "(disabled)" in the SETUP program) now

    release the COM port when not sending a fax.

    Similarly, if the port is in use by another program when the

    device is asked to send a fax, a warning message is displayed,

    the device status is set to ERROR, and the device then waits

    until it is allowed to open the port.

    Used in conjunction with the Spartacom SAPS modem sharing program

    these two changes also allow the Zetafax server to use ports on

    other computers or ports used by Microsoft RAS.

    The KeepPortOpen line in SETUP.INI can be used to change to the

    previous behaviour - see SETUP.WRI for details.

11. Support for UNC path names

    The server and workstation programs now support UNC directory

    names (eg "\\SERVER\ZFAX\SYSTEM" instead of "F:\ZFAX\SYSTEM").

    Drive letters must be used for the initial installation of the

    server, but these will then be changed to UNC paths automatically

    by the NTSETUP program, and can also be entered directly in the

    Server and Workstation configuration programs.

12. Renamed programs

    To comply with the Windows 95 convention of naming installation

    programs SETUP.EXE, two of the Zetafax programs have been renamed.

    The Zetafax server configuration program has been renamed from

    SETUP.EXE to ZFSETUP.EXE, while the initial installation program

    has been renamed from INSTALL.EXE to SETUP.EXE.

    The Program Manager items in the Zetafax group are automatically

    updated to the new names if upgrading from an older version of

    Zetafax.

Compatibility issues with other software

1.  Creating coversheets with Windows 95.

    The Zetafax printer driver under Windows 95 does not yet support

    the Zetafax fonts (for use with FaxMerge commands or embedded

    addressing).  If you wish to create new coversheet foreground files

    it is therefore simplest to do this from a Windows 3.x or

    Windows NT PC.

    If you only have Windows 95 workstations available, you can create

    a new coversheet foreground file by configuring an Epson LQ-1000

    printer driver, as described in the WIN-NT.TXT file.  The Epson

    resident fonts (eg "Roman 10cpi") behave in the same way as the

    Zetafax fonts referred to in the online help.

2.  Changing paper size in Word for Windows 2.0

    Word for Windows version 2.0 does not notify printers of the paper

    size which it wishes to use.  Therefore when using Word with the

    Zetafax printer you should ensure that the paper size configured

    in printer setup agrees with Word's page setup size.

    Word 6.0 has this problem corrected.

3.  Use with Sun PC NFS

    PC NFS uses a special character in file names to identify Unix

    files with names longer than the standard DOS 8+3 format.

    By default this is the tilda character '~'.  If you create a

    file on a PC whose name contains this character, then do a

    DIR, the file has a different name (eg "~TEST000.TMP" gets

    stored as "~TEST~RA.TMP").

    Zetafax uses file names which contain tilda characters, and

    therefore does not work correctly when PC NFS changes the

    file names in this manner.  You can correct the problem by

    telling NFS to use another character (eg '%').  This is done

    by modifying the line which loads PCNFS.SYS in the CONFIG.SYS

    file on each PC, adding a parameter "/C%" to the end - eg

        Device = C:\NFS\PCNFS.SYS /C%

4.  Background printing in Microsoft Word 6.0

    When you print to the Zetafax printer from an application

    Zetafax waits until printing has finished before displaying

    the addressing dialog box, in case the file being printed

    contains any automatic addressing commands.

    With most applications this means that the addressing dialog

    is displayed immediately the application's "Printing page nnn"

    message box is removed.  However Word 6.0 (and some other

    applications) performs printing in the background, giving

    just a small visual indication on the status bar to say that it

    is in progress.

    With Word 6.0, background printing to the Zetafax printer is

    now disabled.  If you install Word after installing Zetafax,

    you should run the Zetafax Workstation Setup program and

    choose the "update programs" option to make this change.

5.  Using embedded addressing commands with WordPerfect 5.1

    Faxes may be addressed automatically by including special

    commands in the text of the fax (eg "%%[FAX:1234]"), using one

    of the Zetafax fonts.  This is not currently supported under

    WordPerfect 5.1 (as it prints each character of the command

    individually).  This will be corrected in a future maintenance

    release - please contact Equisys for details.

6.  Running server over Windows NT 3.5 Netware client

    There is a compatibility problem between the Windows NT Netware

    client software and certain versions of Novell, causing an error

    when reading data which has just been written.  The Zetafax

    server programs check for this problem while running, and if

    detected an error message is displayed and the server will

    be shutdown.  If this occurs it may be corrected as follows.

    If you are running the server on a Windows NT PC, using a Novell

    server for the shared files, you should install the ServerArea files

    (normally in zfax\SERVER) on the server PCs local disk instead of

    on the fileserver.	If you have already installed Zetafax you can

    change this by copying the SERVER directory to the local disk

    (including any empty subdirectories), then editing the [SERVER]

    section in the ZETAFAX.INI file to change the ServerArea: line.

    This is due to faults in the standard version of the Netware client

    software for Windows NT when used with older versions of Novell

    (3.11), and therefore may not be necessary with later versions of

    the Netware client.

Features for future release

The following additional items will be included in a service pack for

Zetafax, due for release at the end of 1996.  This service pack will be

sent to all registered users of Zetafax 5.0.

1.  Mail gateway

    This version of Zetafax allows received faxes to be delivered

    direct to your e-mail account with MAPI compliant e-mail systems.

    This includes Exchange, Microsoft Mail, and Lotus cc:Mail (with

    the latest version, or using the MAPIVIM and MAPIVI32 DLL files).

    Faxes can be sent from an e-mail client by printing to the Zetafax

    printer, as with other Windows applications.

    The service pack will include full e-mail support to allow faxes

    to be sent directly from e-mail client.  It will include a gateway

    or connector for Exchange, Microsoft Mail, Lotus Notes, cc:Mail

    and Groupwise.

2.  Gammafax support

    The service pack will includes drivers for Gammafax intelligent fax

    boards, for Windows NT (Intel)

3.  Embedded addressing support for Windows NT and Windows 95

    New printer drivers for Windows NT 3.51 and Windows 95 will support

    the embedded addressing features of the API.  These will also allow

    attachments to be created directly by clicking the "Save as" button

    on the addressing dialog, rather than having to forward the message

    to your IN window first.


Q.D.7   Can I import my phonebook into the Zetafax address book?

Yes.

Background

Zetafax maintains a number of address books on the system.  There are two levels of address book - private and network.

In addition, any fax number you enter is kept automatically in a list of past recipients (this feature is not discussed in detail in this section).

Each user can freely add, change and remove entries from his or her own private address book.  No other user has access to this.  There is only one network-wide address book, and all users have access to it.  The network supervisor determines which users are allowed to add, delete or edit network address book entries.

In addition to the Zetafax address books you can also directly use an ODBC database (eg Access) or a CSV (comma delimited) text file as your data source.  This functionality is especially useful for sending faxes to distribution lists.

ADBUTIL.EXE - Address book maintenance

This program is used to update and maintain the address book files.  These are a pair of files ADB.DB and ADB.IDX, which are stored in the zfax\SERVER\Z-DB directory, and contain the address book entries and an index into the database file respectively.

We recommend that you make a backup copy of the address book file ADB.DB before making changes to the structure of the file using this program.

ADBUTIL is run without parameters, with the fax server stopped, and is menu driven.  Functions available are as follows :-

Export address book	Import address book  	Validate records

Create address book	Modify address book	List statistics

Delete user	Rename user


Export address book

This is used to produce an ASCII text file of the address book.  You can select between the system address book, a user's private address book, or the complete address book.

Use this option to view the ASCII format required for import into the address book.


Import address book

This is used to import an ASCII text file (in the same format as that produced by the Export command) into the address book.  An error will be displayed if an entry already exists (in the same way as if the entry had been added using the workstation program).  The "Delete user" command can be used to clear a specific set of entries before importing.


Validate records

This runs various checks on the address book files and reports and corrects any errors which it finds.  It should be run if any consistency errors are reported by ADDMAN, or if the fax server is stopped improperly at any time (eg power failure).


Create address book

This deletes all entries in the existing address book and creates a new, empty book.  It should not normally be required.


Modify address book

This is used to alter the size of the address book file or of the index file.  It can be used to extend an existing address book retaining the old entries, although it is advisable to make a backup copy of the files first.  The size of the index file is determined by a "provision factor" - this gives the ratio between the number of entries in the index and the maximum number of entries it would be possible to index.  A factor of 1.0 is suitable for most installations - however, if you use aliases ("also known as ...") on most records and disk space is not a problem, then you may improve the performance on a nearly full address book by using a value of 2.0 or 3.0.  Similarly, if you have a large address book but do not use aliases much, and disk space is more important than access time, then a value of 0.4 or 0.5 could be used.


List statistics

This displays statistics from the last run of ADDMAN, giving details about the number of disk accesses for particular operations, etc.  Note that the disk access count does not take into account any disk caching software being used on the machine.


Delete user

This is used to remove all private address book entries for a given user, or all the system address book entries.  These are not removed automatically when a user is deleted using the INSTALL program, to allow users to be renamed or temporarily disabled.


Rename user

This renames a private address book and is used if the name for a user is to be changed.

Please note that ADBUTIL is only shipped with the full Zetafax package.


Q.D.8   When my notebook is not hooked up to the network, can I setup a local Zetafax server to run automatically?

Yes.  To setup this feature:

On the network fax server machine:

1.  If Zetafax is not already installed on the network, install it onto a network drive - eg F:\ZFAX.

On the notebook machine:

1.  Install a local copy of Zetafax onto the local disk of the notebook - eg C:\ZFAX.

2.  Open C:\WINDOWS\ZETAFAX.INI in Notepad, and edit the [WORKSTATION] section heading so that it reads [WORKSTATION-1].  Save ZETAFAX.INI and close Notepad.

3.   Run the workstation setup program from the network based fax server - eg F:\ZFAX\SYSTEM\WKSETUP.EXE.  Select "Install Workstation - standard settings" and click OK.  Exit WKSETUP.

Installation is now complete.  If the notebook machine is connected to the network, and the network fax server is running, the workstation will connect to the network fax server.  If not it will ask whether the user wishes to run a local fax server.

This technique can be used in other scenarios, such as on a large network which has multiple Zetafax servers.  Important fax users could have a secondary fax server to connect to should their primary fax server fail.


Q.D.9   If I am running a local fax server on my notebook when I am not hooked up to the network what are the licensing implicat
Q.D.9   If I am running a local fax server on my notebook when I am not hooked up to the network what are the licensing implications?

Zetafax starter systems are licensed for a fixed number of users with a single Zetafax server, and allow you to create that number of user accounts on the server.  In addition, any of those users are allowed to run a standalone copy of the Zetafax server on a notebook computer (one which is sometimes connected to the network), provided their network account is not being used by anyone else at the time.

For example, if you have a 10 user Zetafax licence and 3 of your users are out of the office, then they can each run a standalone copy of Zetafax provided no more than 7 of the network accounts are in use.

For a Zetafax server with an unlimited user licence, there is no restriction to the number of network accounts you create.  You are also entitled to have up to 75 notebook users run a local fax server.  Should you require more than 75 notebook users to run a local version of the fax server, then you should contact Equisys to obtain a licence upgrade.


Q.D.10   Can I control the security of the Zetafax system?

Yes.

File access permissions

User file access

The files used by Zetafax are split between four areas, depending on the type of access required by the workstations.  These are listed below, together with the type of access required by the workstations to all files and subdirectories in that area.

There are four "areas" within the Zetafax file structure comprising subdirectories and files.  The following table gives the access rights or permissions required for workstations.

Area name: 	Default directory (eg): 	Workstation access

Server	F:\ZFAX\SERVER	NONE

System	F:\ZFAX\SYSTEM	READ-ONLY

User	F:\ZFAX\USERS\username	FULL for owning user, NONE for other users

Request	F:\ZFAX\REQUEST	FULL

If you want to control the security of the system and the privacy of faxes between users you can restrict the file access rights which users have for the Zetafax directories.  Otherwise it may be simpler to give all users full access to the complete Zetafax file structure and ignore the remainder of this section.  Details for restricting file access rights on Novell NetWare networks are given separately below.

Stop the fax server if it is running and give all Zetafax users read-only access to F:\ZFAX\SYSTEM and full access rights to F:\ZFAX\REQUEST.  If your network supports user groups, it may be quickest to do this by creating a group called "ZFAX", making each Zetafax user a member of the group and giving these access rights to the new group.

If you are not concerned with privacy between users you should also give all Zetafax users full access rights to F:\ZFAX\USERS.  However if you wish to keep each user's fax area private you should give each user full access rights only to his or her private area within the Zetafax directory structure - for example, give Zetafax user JOHN full access rights to F:\ZFAX\USERS\JOHN.

Finally give the user account which the fax server will be logged on as full access rights to F:\ZFAX and all sub-directories.  Log back into the fax server PC, and run the Zetafax server.

For Novell NetWare:

Stop the server and log on as Supervisor at one of the users' workstations.  Using SYSCON, create a group called "ZFAX".  Make each Zetafax user a member of this group.  Give members of the ZFAX group trustee directory assignments of [ R    F ] for F:\ZFAX\SYSTEM and [ RWCEMF ] for F:\ZFAX\REQUEST.

If you are not concerned with privacy between users you should also give all members of the ZFAX group [ RWCEMF ] trustee rights to F:\ZFAX\USERS.  However if you wish to keep each user's fax area private you should give each user [ RWCEMF ] access only to his or her private area within the Zetafax directory structure - for example, give Zetafax user JOHN the rights [ RWCEMF ] to F:\ZFAX\USERS\JOHN.

Finally give the Novell user who the fax server will be logged on as [ RWCEMF ] trustee rights to F:\ZFAX.  Log back into the fax server PC, and run the Zetafax server.


Q.D.11   Is Zetafax secure?

Yes.


How can you reassure me as regards to the risk of virus infection when running Zetafax?

There is no risk of a virus being introduced when receiving faxes direct to your computer with Zetafax.  Viruses are basically programs which damage a computer on which they are run.  This happens in one of two ways, depending on the virus.  The first type “attach” themselves to an existing executable program file (.EXE, .COM etc) so that when a user runs this they are actually running the virus program.  The second type of virus modifies the boot sector on a disk, so that when that disk is used to boot a computer the virus program is run.

The main point is that data files, which are not run, cannot therefore introduce a virus.  Data files are used by application programs, which typically open the files and read or write bits of them.  The file is not being “executed”, which means that there is no opportunity for any virus to install itself into the system from a data file.  It is for this reason that most virus protection packages default to only checking executable program files (as well as checking the boot sector, and memory in case a virus is already running).  The only reason these programs allow you to check other files, is in case an executable file has been renamed (for example, renaming MYPROG.EXE to MYPROG.SAV).

Incoming faxes received by Zetafax are stored as TIFF data files.  The data received over the phone line is stored in the data file with a header being added giving general information such as the number of pages received.  Zetafax would under no circumstances execute one of these files or the data within them, and if a user tried to run them accidentally or maliciously (eg by renaming them to .EXE) they would not be able to do so, as the TIFF header format is different from the standard EXE file header which the operating system requires to run the file.

A further issue to be aware of is the availability of products which allow you to perform binary file transfer via fax.  I know of one  such product, called 3D Fax which produces an ‘infoimage’ of a binary file which can be faxed to any type of fax device.  Without the proprietary reader software, however such faxes are harmless for passing on executable files and hence viruses.


Is my system safe from hacking?

The Zetafax server requires you to dedicate a modem which can be used exclusively for sending and receiving fax messages.  The Zetafax server controls the modem to which it is attached and will only answer incoming fax calls.  In this way, there is no possibility for anyone to dial into a modem connected to the Zetafax server to remotely access the network.

How?

Sending

1.	The Zetafax printer driver converts your document into EPS graphics file format to a file named ZETAFAX.SPL in the C:\WINDOWS directory.

2.	After the fax has been addressed, the Zetafax workstation sends the graphics file to server (by copying it onto a network drive)

3.	The Zetafax server adds a coversheet (if requested) and merges to letterhead , creating new graphics file in multi-page TIFF format

4.	The Zetafax server switches modem into "fax only" mode (not data), dials the recipients fax number, and provided it is answered by a fax machine sends the graphics data, otherwise it hangs up.

Receiving

1.	On initialisation, the Zetafax server disables the modems auto-answer

2.	When the fax modem tells server there is an incoming call, the Zetafax server switches the modem into "fax only" mode (ie not data), instructs it to answer, and provided it is answered by a fax machine receives graphics data to a TIFF format graphics file; otherwise it hangs up.


Q.D.12   Can I track fax usage for billing purposes?

Billing log - FAX.LOG

A record of all faxes sent is kept in the billing log - FAX.LOG.  This file is stored in the zfax\SERVER\Z-DB directory.

A line is added for every message addressee sent to by fax, giving details such as the Zetafax user name, addressee name and company, the phone number, the connection time and number of pages sent.

The billing log file may be converted into a suitable format for a spreadsheet or analysis program using the LOGCVT program see page 196 of the User Guide.

Charge Codes

Charge codes can be enabled, and made optional or compulsory,  using the Zetafax Setup program - Change Server Settings|General.  Users select the charge code after addressing the fax in the Addressing Dialog Box.  Charge codes are logged in the billing log (FAX.LOG).


Q.D.13  Do I need to install each Zetafax workstation from floppy disk?

No.  After having installed the fax server onto a network drive - eg. F:\ZFAX, you just need to run the workstation setup program (WKSETUP) on the other machines - eg F:\ZFAX\SYSTEM\WKSETUP.EXE.


Q.D.14  I only have 2 COM ports.  How can I add more fax lines to my fax server?

Zetafax supports up to 32 fax modems per fax server.  For more than 2 fax modems, we recommend the use of a multi-port serial card or intelligent fax board.

Brooktrout TR114-I2L two port fax board  ISA bus full length card.  IRQ 3-7, 9-12, 14, 15.  I/O ports 12, 20, 36.  DMA channel 8 bit 0-3, 16 bit 5-7 software selectable.  Group III fax on two ports at 14400/12000/9600/7200/4800/2400 bps (V21, V29, V27, V17) with error correction mode (ECM).  Compression conversion on the fly between T.4 (MH and MR) and T.6 (MMR).  Downloadable firmware.

Brooktrout TR114-I4L four port fax board  Specification as above but with four ports.

DIGI PC/4e   Intelligent 4 port ISA bus card with DB25 I/O DTE male cable (38Kbps total).

DIGI PC/8e   Intelligent 8 port ISA bus card with DB25 I/O DTE male cable (56Kbps total).

DIGI Acceleport 4 port   Intelligent 4 port ISA bus card with DB25 I/O DTE male cable (230Kbps total).

DIGI Acceleport 8 port   Intelligent 8 port ISA bus card with DB25 I/O DTE male cable (230Kbps total).

The Star Gate OneSlot 16550 provides 4 COM ports, each require their own interrupt and memory address space.

The Star Gate ACL2-001 is an intelligent card, capable of sharing a single interrupt to support 8 separate COM ports.


Q.D.15  Can I send faxes from DOS applications that are running under Windows?

Yes.

The simplest way to send a fax from a DOS application that is running in a DOS box under Windows is to setup an Epson printer driver within the application, and print to the Zetafax spool file - by default this is C:\WINDOWS\ZETAFAX.SPL.  If the Zetafax Workstation is already running, it will display the addressing dialog box, as usual.

There are three ways to use the Zetafax TSR program (ZSPOOL.EXE) to intercept printer output and display the addressing window.  Firstly, output to a physical device can be intercepted.  For example, the TSR can be configured to intercept output to LPT2, or COM1.  This method is supported by just about all software.  Secondly, some applications allow you to direct printed output to a file device.  This is a file setup to fool the system into thinking it is a device.  It can be given any valid filename, for example, ~ZFAX.  Thirdly, output can often be directed to an actual file, called for example ~ZFAX.  Output to this file is captured by the TSR.

The final option is to print to disk and manually send the fax from within the Zetafax workstation program.

If you did not run the DOS application from within Windows (or if the Zetafax workstation program was not running) then you should wait until printing has finished, then run Windows and start the Zetafax workstation program - the addressing screen will then be displayed.


Q.D.16  Does Zetafax have DOS client software?

No.

Faxes can be submitted from DOS applications, but must be addressed using either the Zetafax workstation (under Windows) or using the Zetafax API.

In a purely DOS environment, it is possible to send faxes to the Zetafax server using the ZSUBMIT feature of the Zetafax API.  See section I, the Zetafax API for more information.


Q.D.17  Can I have multiple fax servers on the same network?

Yes.

Each Zetafax system will be separate; each server will have its own centralised queue of faxes and list of Zetafax users etc.

It is possible to offer important fax users a secondary fax server should their primary fax sever be closed down or fail.


Q.D.18  Can I register the Zetafax evaluation system?

The Zetafax evaluation system is not shareware and cannot be registered.  It is a 5 user working evaluation of Zetafax for demonstration, evaluation and testing purposes.  An evaluation system may be upgraded to the full system (on purchasing Zetafax) if you wish to keep your Zetafax configuration (eg. coversheets, letterheads, fax modem & user setup etc.) by selecting the “update selected server files” then programs and fonts from the dialog box which appears when running INSTALL.EXE from the software disks.


Q.D.19  How can I add a unique reference to a fax message?

We generate a "message ID" for each message (but not each recipient - if you send a fax to 5 people each will have the same message id).  You can add this to the fax or coversheet with %%[MESSAGEID].

The message ID is 8 characters, in format ymddnnnn.  "y" is 6 for 1996, m is 1 for January to C for December, dd is day of month (01 to 31), and nnnn is a 4 digit sequence for the day, starting from 0001.  This is used for log files, displayed on log display on workstation, and also used for the archive files.


Q.D.20  I use Watermark and find that printed faxes are reduced in size.  How do I fix this?

If you are using a version of Watermark before 2.11, you may find that when you print faxes that have been received in standard resolution they are reduced by 25%.  Watermark have solved this problem and you should seek an upgrade to version 2.11 or later.


Section E - Coversheets, letterheads and attachments

This section of the FAQ gives answers to common questions concerning the creation and customisation of coversheets, letterheads and attachments.


Q.E.1   Can I create Zetafax graphic attachments, letterheads and coversheet background files under Windows NT?

Yes.

Under Windows 3.x, the 16 bit Zetafax printer driver can be setup in FaxMerge mode or a graphics mode.  Hence to save a graphics attachment under Windows 3.x you simply:

1.	Open the document to be saved as a fax attachment in the application that created it (eg. Word processor).

2.	Ensure that the Zetafax printer driver is setup in a graphics mode.

3.	Print to the Zetafax printer driver and click the "save as" button on the addressing dialog box to save the file as a graphics attachment.

Under Windows NT, an Epson printer driver is configured as the Zetafax printer driver.  The Epson driver is, in effect, always setup in FaxMerge mode.  Hence to save a graphics attachment under Windows NT you must perform the following work-around:

1.	Open the document to be saved as a fax attachment in the application that created it (eg. word processor).

2.	Print to the Zetafax printer driver, address the fax to a "dummy" user and click the "hold for preview before sending" check box.

3.	View the fax in your OUT window to check it is OK, quit the viewer and abort the message.

4.	 Forward the message from your OUT window to yourself, by selecting it and clicking the "forward" button.

5.	Select the new message in your IN window and click the "File|Move/Save” menu item to save the file as a graphics attachment.


Q.E.2   Can I create new fax coversheets under Windows NT with Zetafax?

Yes.

Zetafax 5

Simply use the FaxMerge printer driver provided with Zetafax and follow standard instructions.

Zetafax 4.5

A Zetafax coversheet consists of two files: a foreground file which contains text which is different for each fax (such as the name and organisation), and a background file, containing fixed information such as the company logo.  The background file is optional, and can be omitted if all the fixed information is in the foreground file.

Coversheets are stored in the zfax\SYSTEM\Z-COVER directory.  The foreground is a FaxMerge format file with an extension of .EPN.  It can be produced using any Windows word processor program.  The background is a graphics file, with extension .G3F for fine mode faxing, or .G3N for standard mode.  Zetafax is shipped with a standard coversheet (called COVSHEET) plus a number of example foreground files (called EXAMPLE1 etc), all in Write format.  The examples are not distributed with the evaluation system due to disk space limitations.

The simplest way of personalising the coversheet is to use the standard foreground (COVSHEET), and just replace the background with your company logo or letterhead.  If you want to do this skip the "foreground file" section below, and go straight to the "background file" section.  Alternatively you can create a completely new foreground file, changing the design as required.

Foreground file

The coversheet foreground file contains the variable information which is overlaid onto the background file at sending time.  Items such as addressee, sender, date, and number of pages are added by Zetafax automatically replacing fields contained in the foreground file.  These fields are called FaxMerge commands, and have the form %%[...]

You can change the layout of the foreground information on the coversheet if required.  This is done by creating a file in your word processor containing a number of FaxMerge commands, which must be in one of the Zetafax printer fonts (for example Zetafax Roman 10cpi).  NOTE: the Zetafax printer fonts are only available in your Windows application when the Zetafax printer is selected.

There are several example files in the zfax\SYSTEM\Z-COVER directory in WRITE format, though you can use any Windows word processor.  An example file might be:

Date:	%%[DATE]

To:	%%[NAME]

Company:	%%[ORGANISATION]

From:	%%[FROM]

Pages:	%%[PAGES] (including this)

%%[NOTE]

%%[NOTE]

%%[NOTE]

%%[NOTE]

%%[NOTE]

%%[NOTE]

%%[NOTE]

%%[NOTE]

%%[NOTE]

%%[NOTE]

Each %%[NOTE] field gets replaced with the next line of the coversheet note field from the addressing dialog box, which is word-wrapped automatically by Zetafax.  You should ensure that there are at least 10 of these fields on the coversheet.

The steps to create a new coversheet foreground are as follows:

1.	Create the document in your word processor.  If you are running under Windows 3.x, ensure that the FaxMerge fields are in a Zetafax font.  You should remember that a printer font is specific to a particular printer driver (not like true type fonts which are resident throughout your system) so will need to select the Zetafax printer to choose these.  Under Windows NT the FaxMerge fields need to be in an Epson printer resident font so the Zetafax (Epson) printer should be selected for the fonts to be visible.  The document can also contain any other text or graphics, as required.

2.	Under Windows 3.x, set the Zetafax printer to FaxMerge mode (using Printer Setup).  If you are using an Epson printer driver (eg. under Windows NT or OS/2), this is effectively always in Fax Merge format.  Print.  When the addressing dialog box is displayed click on the SAVE AS button.  Note that you will not be able to view the file at this stage as it is not in a graphics format.

3.	Select the COVERSHEET, LETTERHEAD OR ATTACHMENT option and click OK.  This will display the "Save as system file" dialog, where you should select COVERSHEET FOREGROUND.   The option will be disabled if the Zetafax printer driver was set to the wrong format before printing.

4.	Enter a file name without any extension (eg COVSHEET to overwrite the default file), and a short description to help users.  Click OK and the coversheet will be created.

A number of other FaxMerge commands are available for including in the foreground file.

Background file

The coversheet background file is similar to a letterhead.  It is TIFF FAX format graphics file, and contains the fixed part of the coversheet, like the logo and address of the sender.

The foreground must be created before the background, though if one has not yet been created for this coversheet you will be given the option of just using the standard COVSHEET foreground.

If you already have the coversheet available in a word processor or other application program, this will generally give the best result.

1.	Under Windows 3.x, select the Zetafax printer driver and set its spool format to HIGH (200 x 200 dpi).  If you are using an Epson printer driver (eg. under Windows NT or OS/2) you will not be able to set it up into HIGH spool format.

2.	With the server and workstation running, print the document using the Zetafax printer driver.  After a short time the Zetafax Addressing window will appear.  If you are running the workstation under Windows 3.x, click the SAVE AS button to display the "Save file as" dialog box.  If you are using an Epson printer driver (eg. under Windows NT or OS/2), address the fax to a dummy user, select "Hold for preview before sending" and click OK.  Ensure no coversheet or letterhead is selected and click OK again.  The message will appear in your OUT window as usual.  Now select the message and click the forward button.  Forward the message to yourself, select the new message that appears in your IN window and click the Move/Save command under the file menu.  The "Save as" dialog box will now be displayed.

3.	Select the COVERSHEET, LETTERHEAD OR ATTACHMENT option and click OK.  This will display the "Save as system file" dialog, where you should select COVERSHEET BACKGROUND.   The option will be disabled if the Zetafax printer driver was set to the wrong format before printing.

4.	Enter a file name without any extension or select a coversheet from the list (eg "COVSHEET" to overwrite the default file), and a short description to help users.  Click OK and provided a foreground file is already present, the coversheet background will be replaced.

If you do not have a word processor version of your coversheet, you can still create a new Zetafax coversheet simply by sending from another fax machine (effectively using the other fax machine as a scanner).


Q.E.3   How can I add extra lines to the note on coversheet?

Increase the number of %%[NOTE] fields that you use when creating the coversheet foreground file.


Q.E.4   After adding extra %%[NOTE] lines to my coversheet, why does Zetafax still warn that the note on coversheet may be trunc
Q.E.4   After adding extra %%[NOTE] lines to my coversheet, why does Zetafax still warn that the note on coversheet may be truncated?

You need to change the CoverMaxLine: line in the [WORKSTATION] section of zfax\SYSTEM\Z-DB\SETUP.INI, from its default of 10 to the number of %%[NOTE] lines in your coversheet foreground file.


Q.E.5   How can I insert a blank line into the note on coversheet with version 4.5 of Zetafax?

NOTE:  With Zetafax 5 you can simply press <RETURN> for a new line.

Hitting the <ENTER> key when typing in the “note on coversheet” closes the “Zetafax-Options” dialog box (ie. is the same as clicking the OK button).  To insert a blank line into the “note on coversheet”, press <CTRL><ENTER> twice.

Note that hitting <CTRL><ENTER> once will look as if a carriage return has been entered when viewed in the “Zetafax-Options” dialog, but will not necessarily enter a carriage return on the fax page.  The “note on coversheet” is due to be updated in a future Zetafax maintenance release.


Q.E.6   How do I install the Zetafax printer fonts?

The Zetafax printer fonts are automatically installed when you run WKSETUP and the Zetafax printer is installed.  Printer fonts are specific to a given printer and are only available when that printer is selected within your application.  True type fonts on the other hand are scaleable fonts that appear in your printed document exactly as they appear on your screen.  They remain resident throughout your system.


Q.E.7   I have run the WKSETUP program and I cannot find the Zetafax printer fonts.

1.	Check that the Zetafax printer selected in your application and set to FaxMerge mode.

2.	Ensure that you have not configured Windows to display only true type fonts in applications.  This can be disabled in the Control Panel | Fonts applet.

3.	Remember if you are running Windows 95, that the Zetafax printer is not fully supported.  If you want to use FaxMerge or create coversheets, you will have to configure a Zetafax printer using the Epson LQ1000 driver and then use the relevant Epson printer fonts.  Refer to the file \zfax\SYSTEM\WIN-NT.TXT file to find out how to install a Zetafax printer using the Epson LQ1000 driver.


Section F - Automatic printing, transmission reports and archiving

This section of the FAQ deals with questions concerning setting up automatic printing, extracting and creating transmission reports and archiving faxes.


Q.F.1   I have an OS/2 Zetafax server.  How can I automatically print incoming and outgoing faxes?

The device used for automatic printing (PRINT) is a Windows application.  Hence, to automatically print faxes when using an OS/2 fax server, you need to run PRINT-n from another machine on the network, that is running Windows.


Q.F.2   How do I setup automatic printing from a machine that is not the Zetafax fax server?

Printing may be performed on a different PC from the one running the Zetafax server software.  You might do this to reduce loading on the main Zetafax server if you have a large number of fax lines, or if you have an OS/2 version of the Zetafax server and want to print on a Windows printer.

The way this works is that the main Zetafax server is configured as to create print spool files, but told to ignore the spool files it creates.  It will not need to have any PRINT devices configured.  The second PC then has a separate copy of the Zetafax server installed on its local disk, but is told to look at the main Zetafax server’s spool directory for the print spool files.  To conform to the software licence agreement, this second server must not have any users or fax devices configured; just one or more PRINT devices.

The location for the print spool files and the “ignore spool files” option can be configured using the SETUP program for each fax server, choosing the “change server settings” option, in the “printing (2)” category.


Q.F.3   Can Zetafax save transmission reports with the original document, rather than with an image view of that document?

Yes.  Zetafax stores information about each message sent.  Click on the message in the OUT window, and click the Info button.  The Message information window appears.  The Document field will be blank if you did not save the document before sending it.

Saving outgoing fax

Choose File | Move/Save from the menu.  The Transmission report save window appears.  When a document has been sent as a fax, you can configure Zetafax to store information about whom it was sent to and when in the same directory as the original file.  This screen asks for the name of the original file (generally the word processor format file).

Saving incoming fax

Select the newly received fax in the IN window.  Choose File | Move/Save from the menu.  This time the you are saving an incoming fax image - enter the path and file name.


Q.F.4   Can I automatically archive sent and received faxes?

Zetafax allows you to archive on disk every fax sent or received, allowing you to retrieve them days or even months later.  You can also print faxes automatically on any Windows printer, with an optional status page giving the connection time and details.

Archiving

Zetafax has a variety of ways of allowing users or the system administrator to keep track of fax usage.  Every fax submitted by a user stays in their OUT window until they delete it, allowing them to view what was sent and to retrieve the transmission history.  The logging facility allows users to check whom they have sent faxes to, and administrators can obtain a list for all users.  Finally, the billing log has an entry made for every fax which is sent, including details such as the fax number and connection time.

The archiving feature works in addition to these mechanisms, and is configured on the fax server.  It stores a copy of every fax sent and/or received, exactly as transmitted.  The fax itself is saved as a graphics file, which can subsequently be viewed or printed, and a transmission history for the fax is saved in a separate file.  If you wish to keep a copy of faxes on disk, it is best to use this central archiving feature.  There are limits to the number of entries users may leave in their IN and OUT windows, so these should be cleared out regularly and not used for keeping long term copies.

Configuration

Archiving is configured using the SETUP program, installed in the Zetafax group in Windows Program Manager.  Choose the "server settings" option, and select the "archiving" category.

The dialog box lets you enable archiving for faxes received or sent independently.  You would normally select the "save fax images with transmission reports" option - otherwise the transmission report will be saved, but you will not be able to view the contents of the fax.

Files created

The archive files are created in the directories specified in the dialog box - by default these are zfax\SERVER\Z-RECD for received faxes and zfax\SERVER\Z-SENT for sent faxes.  A separate sub-directory is then created for each day, with a name of the form yymmdd (eg faxes received on the 12th March 1996 would be stored in the directory zfax\SERVER\Z-RECD\940312).

Each fax sent or received by Zetafax is given a message ID, which is an eight character code, and is unique for each message submitted to the Zetafax server.  The message ID is displayed on the message information and log display screens on the workstation, and also stored in the billing log.

Two archive files are created for each fax; one contains the transmission history (with extension CTL), and the other is a TIFF format graphics file containing the fax itself (with extension G3N or G3F).  The main part of the file name is the eight character message ID.

Retrieval

Archived files may be retrieved and viewed by any user who has access rights to the archive directories by using the Zetafax workstation programs FILED window.  Use the "Window | Change directory" menu choice to view the directory for the required day, setting the "Show only files with transmission reports" option.

The description field displays the name of the user who sent or received the fax, and the original description (eg "To: Fred Smith" or "From: Equisys").  The name of the archive file is also displayed, which allows you to find the correct message if you already know the message ID.

Once the correct message is found you can view it, print it or look at the message transmission history in the same way as for entries in the IN or OUT windows.


Section G - Email and OCR integration

This section of the FAQ explains how to use your email system with Zetafax and also how OCR can be integrated with Zetafax.


Q.G.1   Does Zetafax integrate with email software?

Yes.  Zetafax includes facilities for distributing fax messages to other Zetafax users on the LAN, using facilities similar to those in electronic mail (email) packages.  However Zetafax can also integrate with email more directly, by allowing received faxes to be forwarded by mail and by using an email address book rather than the Zetafax address book.


Q.G.2   How can I forward received faxes via email?

Received faxes can be forwarded to another user via email using the workstation’s “File | Send mail” option (instead of “File | Forward” which sends to another Zetafax user).  This displays the standard mail addressing dialog box, with the currently selected file as an attachment.

By default the attachment file is in TIFF format, using fax Group III compression.  The file extension is set to G3F (for fine resolution faxes) or G3N (for standard resolution faxes).

Provided the receiver’s PC has been set up as a Zetafax workstation (by running the WKSETUP program) they will be able to view the attached file by double-clicking on it when they receive the mail message.

With version 5.0 of Zetafax the fax server can be configured to send faxes to a users e-mail account rather that their workstation.  This option can be configured through the ‘Users and user groups’ section of the Zetafax Configuration program.  You must also setup the e-mail facility within the ‘Change server settings’ section of the Zetafax configuration.  A valid e-mail username must be provided for Zetafax to use.

Format conversion

You can configure Zetafax to convert the attachment file into a different format before sending it, with a different file extension if required.  You might do this if you want to use an alternative viewer, or link into a document management system.  Formats available include TIFF Group 4 fax and DCX (multi-page PCX).

This option is a system-wide setting, configured by editing the [OPTIONS] MailSendFormat and MailSendFileExt lines in the SETUP.INI file.


Q.G.3   Can I use my email system address book rather than the Zetafax address book?

Yes.

Zetafax has its address books: a network one shared by all users, and a private one for each user.  If you have an email system configured, you can also use the email address books in the same way as when you are addressing a mail message.

The choice of whether to use the Zetafax or email address books is made by a checkbox on the message options dialog box (displayed by the “Options | Message” menu choice on the workstation).  If you select the email address books, any address book searches (by either entering a name without a fax number, or clicking SEARCH on the addressing dialog box) will look in the email address books.

Adding or modifying email address book entries must be done using the normal email client program - these options are disabled in Zetafax while the email address book is selected.

Mail entry format

Fax entries in the email address book should be given a type of “Fax” or “Zetafax”.  The parameter should be set to the fax number.

The default settings for the recipient’s name and organisation are the entry name and blank respectively.  They can be set explicitly by adding \name=... \organisation=... to the end of the fax number (replacing the ... with the required name and organisation).  You can abbreviate “\organisation” to “\org” if preferred.  Note the syntax uses a backward oblique (‘\) rather than the more usual forward one (‘/’).

Address book formats which include fields for the name and organisation (such as Microsoft’s At Work fax format) are supported directly by Zetafax, without the need for the syntax above.

Sending to groups

The recipients specified when sending must be individual entries, rather than group entries, to allow Zetafax to get the fax number and other details from the mail address book.  However, most email packages will allow you to list the group members individually using their addressing dialog (displayed by clicking SEARCH on the Zetafax addressing dialog instead of entering a name directly in the TO field).

With Microsoft mail, for example, you edit the group to display a list of the members, select all the entries in the list then click ADD.

All the usual Zetafax features, such as coversheets, attachment files or delayed send can be used as for any other fax.  By electing to use the email address book as described above, all address book entries can be stored together, for both email and fax recipients.


Q.G.4   How can I send faxes from my email package?

Sending an email message by fax, including any attachment files, is as simple as faxing from any other application.  From within the email package just select the Zetafax printer and print the message to it.  The Zetafax addressing dialog will be displayed, and you can either specify the fax number directly or just enter a name from the address book.


Q.G.5   Can I use a VIM email system with Zetafax?

Zetafax has the ability to use a MAPI mail address book and to send faxes as email attachments on MAPI mail systems (for example Microsoft Mail).  However should you have a VIM email system (for example cc:Mail) then you can also make use of these features.  To do this you should make sure that you have the MAPIVIM.DLL file installed on your system.

The MAPIVIM.DLL file will be installed automatically if you use a VIM mail system and have installed Microsoft Office products.  If you do not have this file installed then you could either extract it from a set of Microsoft Office disks (or CD) or download it from Microsoft’s web page, Forums on CompuServe or bulletin boards.

Obtaining MAPIVIM.DLL

To download the file from Microsoft’s web page point your browser to WWW.MICROSOFT.COM, click on the SUPPORT button then select FREE SOFTWARE.  Once on the FREE SOFTWARE page use the search utility to find MAPIVIM.DLL.

To extract the file from MS-Office installation disks use the EXTRACT.EXE program supplied on the installation disks as follows:

EXTRACT A:\MAPIVIM.DL_ c:\windows\SYSTEM\MAPIVIM.DLL

(assuming that your Windows directory is on your C drive)

Configuring Windows to use MAPIVIM.DLL

Once the MAPIVIM.DLL file has been installed to c:\windows\SYSTEM, then its functions must be made available to Zetafax.  This is done on each workstation as follows:

•	Open the WIN.INI file which is located in your windows directory (normally c:\windows) in NOTEPAD.EXE or another text editor.

•	Locate the [MAIL] paragraph and make sure that the following lines are present.  If a [MAIL] paragraph does not exist then create one.

•	Save these changes and reboot the PC.

[MAIL]

MAPIDLL=MAPIVIM.DLL

MAPI=1

Once the MAPIVIM.DLL file has been correctly installed and any necessary modifications made to the WIN.INI file you should find that the ‘Send mail’ option within the Zetafax workstation has been enabled.


Q.G.6   Is Zetafax compatible with OCR software?

Yes.

Optical character recognition (OCR) is used to convert a received fax image into a text file, suitable for reading into a word processor.  This requires the program to look at the dots in the received image, trying to recognise the individual letters and words.

Zetafax can be used both with its own OCR option, and also with other third party OCR products.  This section describes how to configure and use Zetafax with OCR.


Q.G.7   How is the OCR option installed?

Directory selection

The OCR facilities are provided by TextBridge, the leading OCR package from XEROX.  This is sold as a separate option, and must be on each PC which needs OCR capability.

The program files are usually installed in their own directory on the PC’s local disk (eg C:\TXBRIDGE).  However, you may prefer to install them on a network drive (eg F:\APPS\TXBRIDGE, where F: is a network drive visible to all users) - this can save time when installing subsequent PCs.

Software installation

The OCR option has its own installation program.  To install the files simply run the installation program and follow the directions given - full instructions are given with the package.

Zetafax will automatically use TextBridge if present.  It does this by looking for a file TXBRIDGE.INI in the PC’s Windows directory (eg C:\WINDOWS).  This file contains a line giving the directory containing the TextBridge files - you will need to edit the file (using NOTEPAD) if you move the TextBridge files, or rename the directory containing them.

If you install TextBridge onto a network drive visible to all workstations, you can enable the Zetafax OCR option on a new workstation simply by copying the TXBRIDGE.INI file from the PC on which you originally installed TextBridge.


Q.G.8   How do I process received faxes using OCR?

To perform OCR on a received fax, you should first view it (using “File | View” as normal).  You can then choose “File | OCR” (from the View mode menu) to start the OCR processing.

After a few moments a dialog box will be displayed, which gives you the opportunity to change the settings (eg to set landscape orientation, or set the language used).  These settings are stored, so remember to change back any settings you only want to use for a single fax.

The next dialog asks you where to save the resulting file, and what format to use.  Most of the popular word processor formats are supported directly, or you can save as a simple ASCII text file.

Processing

Once you click OK on the file name dialog box, OCR processing starts with a dialog box displayed to show its progress.  This will process all pages in the fax, not just the page being viewed.

Zetafax, or other programs on the PC, can still be used while OCR processing is taking place (though you may need to move the OCR box to the edge of your screen if you want to do this).  However, you can only perform OCR on one file at a time.


Q.G.9   How does Zetafax support other OCR software?

Fax file format

Zetafax stores each received fax in a multi-page graphics file, in a standard format (TIFF with Group III fax Modified Huffman compression).  The file extension is either G3N (for normal mode 200 x 100 dpi faxes) or G3F (for fine mode 200 x 200 dpi faxes).

This format is supported directly by most popular OCR packages.  You will need to specify the directory and file name for each fax file.  This is displayed on the status line (at the bottom of the workstation main window) when you select it in the IN window.  It is also displayed when viewing the fax.

Resolution problems

Some OCR packages perform badly on images where the horizontal and vertical resolution are different (as is the case with standard mode 200 x 100 dpi faxes).  If this is a problem you can get Zetafax to convert a standard mode fax to fine mode by “sending” it to yourself (via the LAN) at HIGH resolution.

To add an address book entry for yourself, set the route to LAN and the route parameter to your Zetafax username.  For more details see the user guide or online help for the address book editor dialog box.


Section H - Automatic inward routing

This section of the FAQ explains how faxes can be routed automatically to the intended recipient.


Q.H.1   Can faxes be routed inward to a particular user on the network automatically?

Yes.  Zetafax can use a number of methods for delivering received faxes automatically to their intended recipient.  These include giving each user their own fax number or specifying that all faxes from a given company should be sent to a particular user.


Q.H.2   What are the different types of automatic inward routing?

When you add a new fax line to a Zetafax server you specify the user to receive incoming faxes.  This is the person who is notified when faxes are received without any specific information about for whom they are intended.  The person who is notified can view the new faxes then either print them or forward them to the correct user, using the workstation “File | Forward” or “File | Send mail” menu options.  This is called manual routing.

Automatic inward routing with Zetafax is split into three main types.  The three types are configured and used independently.

The first and most direct type is Sub-address routing, where the sender identifies the recipient directly, for example by dialling a specific fax number.  Zetafax supports four different methods of sub-address routing, as described below.

The second main routing type is Sender ID routing, which looks at who sent the fax to determine the intended recipient.  The third type is Automatic forwarding, where all faxes for a specific user will be forwarded to another user.  This might be used when someone is sick or away on vacation.

Note that some of the routing types require additional hardware and  software options to be purchased.

Sub-address routing

Sub-address routing is the most direct of the automatic routing methods available, allowing the sender to specify the intended recipient directly.  There are four different methods of doing this.

DDI/DID routing

Many companies already have a phone system (PBX) where each extension can be dialled directly from outside the company, rather than having to go via the switchboard.  The technology behind this is called Direct Dialling Inwards (DDI or DID), and is as applicable to fax as it is to voice calls.

This is the most direct of the inward routing methods.  Each user is given their own fax number - not a separate fax line, just their own number.  Faxes sent to that number are routed directly to the user.

The number of fax numbers allocated is independent of the number of fax lines on your Zetafax system - all you do is define a table of fax numbers, giving the Zetafax user account or user group  corresponding to each one.

If your phone system supports DDI for telephone calls already, it can be configured simply to allow DDI for fax.  If you do not already have DDI you can install a separate digital telephone line (ISDN) to support it just for fax.  Details of both these methods are given below.

DDI routing requires the direct dial routing licence upgrade.

DTMF routing

The method Zetafax uses for DDI routing is to recognise DTMF tones sent to the fax server just after it answers the call, telling it what number was dialled.  These are the musical tones generated by modern phones when the number keys are pressed.

Even without giving each user their own fax number, you can still get the same effect by getting the sender to key in extra digits after Zetafax answers the call.  This is normally done by adding them to the fax number, after a few “pause” characters.  Because of the relatively high level of sophistication required this is suitable for expert fax senders only!

DTMF routing requires the direct dial routing licence upgrade.

Station ID suffix

If you are sending a fax to another Zetafax system, you can specify the recipient’s user name to cause the fax to be routed directly to that user.  This is done by adding the user name to the end of the destination fax number, separated by a colon (eg “012 345 9876:SAM”).  You can also set up other routing names for use with this mechanism such as extension numbers or descriptive names (for example “SALES”).

The user name or parameter is sent to the remote fax system by adding it to the end of the station identifier, or CSID.  This is the identifier programmed into all fax machines and printed on the top line of faxes they send, and is usually set to the sender’s fax number.  Sometimes called “colon routing”, this routing method is also supported for faxes sent to and from other PC fax systems.

ITU sub-addressing or T30 sub-addressing

The Group III fax specification has recently been extended to allow for sub-addressing in addition to the basic fax number.  At first only fax software will support this, but in the future expect to see fax machines with an extra button or two.  It works in the same way as Sender ID extension routing, as described above.

Sender ID routing

Each fax machine (or other fax system) has a “signature” which allows the recipient to recognise who sent the fax.  This is called the Station Identifier or CSID, and is usually set to the sending machine’s own fax number.  As an alternative, Calling Line Identification (CLI) is being introduced by most telephone companies to identify the phone number of the sender.  The CLI can be used if the CSID is not configured for a received fax.

Often only one person in your company deals with a particular sender, and so wants all faxes from that company to be routed directly to them.  Zetafax allows you to set up a list of sender IDs with the users faxes from those companies should be routed to.

Automatic forwarding

If you are going away on holiday, you can tell Zetafax to forward all faxes sent to you to another user.  You can even choose whether to keep your own copy of the faxes for when you return.

The automatic forwarding can work repeatedly in a chain if necessary.  For example, if the person looking after your messages also goes on holiday, his or her messages (including those forwarded from your account) can be forwarded on to someone else.


Q.H.3   Do I need special hardware for direct dial automatic inward routing?

PBX with DDI

If your phone system (PBX) already supports Direct Dialling Inwards (DDI), you can add DDI routing for fax very simply.  The PBX needs to be configured so that calls to any of the fax DDI numbers you allocate are routed to the phone extensions used by the Zetafax server.

Note that the number of DDI fax numbers is independent of the number of fax modems and lines in use.  On fax servers using more than one fax modem the extensions would need to be configured so that if one was engaged the PBX moved on to the next (sometimes called “divert on busy” or “hunt groups”).

When Zetafax answers the call the PBX also must be configured to identify the extension (DDI) number being dialled, by sending a series of DTMF tones.  This is the method used for connecting to voice mail systems, and is supported by most PBXs which support DDI.

ISDN router

ISDN (the new digital telephone network) comes to the rescue of people who do not have a PBX which handles direct dialling, or who want to keep fax separate.  By installing an ISDN line with a fax router box, you can allocate a series of DDI numbers without using the PBX.

The fax router box sits between the ISDN line and the fax modem.  When an incoming call is answered, it identifies the DDI number dialled by sending DTMF tones before connecting the call.

Many telephone companies offer an alternative to DDI on ISDN lines called Multiple Subscriber Numbering (MSN).  It is suitable where only ten or fewer separate numbers are required.  Fax routers can usually handle both MSN and DDI.

Fax modem

The fax modems used for DDI routing, using either of the two options above, must support DTMF tone recognition in fax mode.  They still must support class 2 / 2.0 and use the Rockwell Voice Command  Check with Equisys for a full list of supported modems with this feature.

ISDN Modem

The latest ISDN fax modems combine the functionality of a conventional voice fax modem and an ISDN terminal adapter in one box.  The ZyXEL 2864i is compatible with Zetafax and can also be used with Microsoft RAS and the SpartaCom SAPS modem sharing upgrade to give users higher access speeds - up to 128 Kbps.  The device replaces the combination of a fax router and a fax modem when used with the direct dial routing upgrade.

Intelligent Fax Boards

Zetafax may be used with a Brooktrout or Gammalink intelligent fax boards, which support DDI, reduce call times and transfer more of the call processing load from the fax server’s main processor to the fax board.


Q.H.4   How do I setup automatic inward routing rules in Zetafax?

Configuring the automatic routing options is done by the system administrator using the SETUP program.  The “Routing” option on the “Server options” dialog box allows you to specify whether Sub-address and/or Sender ID routing will be used.  They are enabled by default.

The “Inward routing rules” dialog box allows you to modify the routing information (though some items may also be configured from the workstation program - see below).  You can configure each of the three types of routing independently, as described below.

This dialog box is also displayed by clicking the “Routing” button on the User Edit dialog.  In this case it just displays the rules for the given user.  Deleting a user removes all rules relating to that user.

Sub-address

The sub-address option configures the rules for DDI and DTMF routing, as well as for the other sub-address options (Station Identifier Suffix and ITU sub-addressing).

Each rule comprises a sub-address and a user to route the message to.  For DDI routing the sub-address should be the number reported to the fax modem on answering (usually the extension number or last few digits of the phone number dialled).

For example if user FRED has a DDI number of 0171 378 4122,  HARRY’s DDI number is 0171 378 4123, and HARRY is also looking after faxes directed to SALES (using the station ID suffix method), the rules might appear as

4122	FRED

4123	HARRY

SALES	HARRY

It is not necessary to add an explicit rule for each user if their name is specified in a station ID suffix - this is done automatically, though can be disabled by adding a blank rule for that name (ie routing to “(none)”).

Sender ID

Sender ID rules store two pieces of information for each sender: the organisation name, and the person to receive faxes from that sender.  Both these items can be set from the workstation as well as from the SETUP program.

The organisation name is used for labelling the message in the workstation’s IN window when a fax is received (eg “From: Smith and Sons” instead of “From: 012 345 9876”).  Note that changing the organisation name in the SETUP program only affects messages received from that time onwards.

The new person to receive the fax depends on whom it was originally sent to.  For example, suppose you have two general fax numbers for SALES and ACCOUNTS.  Faxes from Smith and Sons for SALES are being handled by FRED, while faxes from Smith and Sons for ACCOUNTS are looked after by JIM.  The rules would then be:

SALES     Smith and Sons (012 345 9876)  to FRED

ACCOUNTS  Smith and Sons (012 345 9876)  to JIM

When adding rules using the SETUP program you can set the “Messages for” field (the name of the person who originally received the fax) to “(unaddressed)”.  This means that the rule will be applied to messages from that company sent to any user, rather than just for a specific user.  Any rules for specific users are applied in preference to the general rule.

You can also have rules which just give the company name, without specifying a user to forward messages on to.  These appear in the list with the two user name fields left blank.

Generally most sender ID rules are added by the user who receives unaddressed incoming faxes, using the workstation program (see below).  The SETUP program is then used for reviewing and adjusting the rules when required.

Forwarding

The third routing option is for automatic forwarding when a user is away (eg on vacation).  To configure this you specify the original recipient of the messages (the person going away), and the user to receive their faxes.  For each rule configured you can specify whether the original user keeps a copy of the original message (“copied to” in the list), instead of deleting the original (“forwarded to”).

For example, if messages for SUE and JIM are being looked after by MIKE and HARRY respectively, and SUE wants to keep a copy for her records while JIM doesn’t, the rules would be:

SUE	copied to 	MIKE

JIM	forwarded to	HARRY


Q.H.5   How do I use automatic inward routing from the Zetafax workstation?

Forwarding messages

Sender ID forwarding is configured from the workstation with the “File | Forward” menu option.  If you select the “Forward all future messages” checkbox on the forwarding dialog box, a new Sender ID rule will be added.  Any future faxes received from the same sender for this user will be routed to the user you are forwarding to instead.

Once a rule is configured it can be changed using the SETUP program, as described above.

The organisation name is displayed in the workstation’s IN window when a fax is received.  After viewing a fax received from an unknown organisation, you are prompted for the organisation name (provided you have administrator privilege, and the fax has not been forwarded to you by another Zetafax user).

When you set the organisation name for a received fax the IN window entry is updated, and any future faxes from this company will be labelled with the company name (eg “From: First Fisheries” instead of “From: 012 666 7888”).

The organisation name for a message in your IN window may be changed using the “File | Name of Sender” option when viewing it.  Other entries may be edited using the SETUP program, as described above.


Q.H.6   What is T.30 sub-addressing, and is it supported in Zetafax?

T.30 sub-addressing is a new addition to the T.30 fax protocol, which is the ITU standard protocol for group III faxing. As yet, it is unsupported by many fax manufacturers and hence is used infrequently. Zetafax supports this standard in conjunction with Amber Logic modems. The sub-addressing allows extra “electronic” information to be passed down the telephone line as a suffix to the phone number. It works in a very similar way to the Zetafax addressing function of station ID suffix routing, inasmuch as you can be prompted to add an extension to the phone number as additional routing information.


Section I - The Zetafax API

Zetafax has a very comprehensive API (Application Programmers Interface) licence upgrade available.  This section of the FAQ contains detailed information about the Zetafax API.


Q.I.1   What is the Zetafax API?

Application Programmers Interface (API)

Zetafax has an API licence upgrade which makes it simple to automate the sending of faxes from other applications.  It is designed for use with Windows applications, DOS programs, minis and mainframes.

The API has been used in a wide range of tailor-made solutions ranging from the automatic faxing of financial statements to the forwarding of faxes from unattended satellite ground stations around the world.  Please call us to discuss your specific requirements.


Automatic submission program

The APIs ZSUBMIT program lets DOS, mini and mainframe programs send faxes by creating text files in a shared directory on a file server.  For example, faxing purchase orders or invoices usually only requires adjusting an accounts packages report writer.

A text file needs a few lines added to give the fax number and message options.  Logos and signatures can be included and the text may be merged onto a multi-page form using the letterhead feature in Zetafax.  This approach gives results rapidly.


Embedded addressing

Like many fax packages, Zetafax has a Windows printer driver.  Print from a Windows application, and a dialog box will pop-up asking you where the fax is to be sent.  With the API this can be automated by including options such as the fax number in the document being printed.  Zetafax will pick out the embedded addressing information and act upon it.

You can use embedded addressing to broadcast faxes from a database or using a word processor mail-merge.  Each recipients copy will be personalised. Embedded addressing is not yet supported in Windows NT.

Addressing options controlled by embedding or DDE

•	Name, organisation and fax number

•	Senders name and charge code

•	Coversheet and letterhead to use

•	Time to send and priority (urgent, normal or background)

•	Attachment files such as product literature or maps


Dynamic Data Exchange (DDE)

An alternative way of passing addressing information to Zetafax is DDE.  The same range of options can be controlled by sending DDE messages to the client software.


C language callable functions

For the greatest degree of control, the API includes a library of 18 functions which may be called from Windows 3.x, Windows 95, Windows NT, DOS and OS/2 'C' programs.  Application programs can submit new faxes for sending, and monitor/control faxes already in the central queue.

•	Specify the Zetafax user account to use

•	Submit a new message for sending

•	Abort a message already in the queue

•	Get a list of all messages queued for the user

•	Check the current status of a given message

•	Retrieve the transmission history for a message


DLL functions

For the greatest degree of control, the API includes a DLL of 18 functions which may be called from Windows 3.x, Windows 95, Windows NT, DOS programs.  Application programs can submit new faxes for sending, and monitor/control faxes already in the central queue.

•	Specify the Zetafax user account to use

•	Submit a new message for sending

•	Abort a message already in the queue

•	Get a list of all messages queued for the user

•	Check the current status of a given message

•	Retrieve the transmission history for a message


Q.I.2   Can I evaluate the Zetafax API?

Yes.  The Zetafax 5-user working evaluation systems come with the API enabled, so you can “try before you buy”.  Please note, the API upgrade is an optional upgrade to Zetafax and must be purchased if you wish to continue using its features when you buy the full Zetafax software.

The C language libraries are not available for evaluation and are only shipped when the API upgrade is purchased as an upgrade to a full Zetafax starter system.

NOTE:  For reasons of limited disk space, the ZSUBMIT program does not come with the single disk 16-bit server evaluation system.  If you would like to evaluate the ZSUBMIT feature with the 16-bit version of the fax server, you can download the software from the Zetafax web site at http://www.equisys.com/ or from the WUGNET libraries on CompuServe.  GO WUGNET and search the library files for ZF*.*.  The 16-bit version of the server is entitled ZFAX45.ZIP.  Alternatively, if you do not have access to the Internet or CompuServe please contact Equisys.


Q.I.3   How can I use DDE to automate faxing?

The concept

Applications such as word processors may communicate with the Zetafax workstation program directly using DDE commands.  Provided adequate details have first been given using the DDE commands, when a document is "printed" using the Zetafax Windows printer driver no dialog boxes will be displayed and the fax or faxes will be submitted to the fax server automatically.

DDE conversation

Before issuing any addressing commands, a DDE conversation must be established between the application and the Zetafax workstation program.  The name of the DDE server is Zetafax, the topic for the purposes of addressing faxes is Addressing.

The Zetafax workstation program should be put under the control of DDE by issuing a DDEControl command (a DDE Execute call).

Addressing commands can then be issued using DDE Poke calls.  Details of the commands which may be used are given below.

A message file should be created by "printing" using the Zetafax Windows printer driver.  Alternatively an ASCII, suitable Epson or suitable TIFF file may be copied to the spool file location used by the Zetafax workstation program (usually C:\WINDOWS\ZETAFAX.SPL, set by ZETAFAX.INI's LogArea: entry).

The message will be submitted to the fax server for sending when a Send DDE Execute call is made, or for preview when a Preview DDE Execute call is made.

If more messages are to be submitted, they may be done so.  Each new message will require a new addressee, organisation and fax number to be specified, a new message file created and then a Send or Preview DDE Execute call issued.  Note that each of the addressing settings such as the choice of letterhead will remain unchanged between messages until the appropriate DDE Poke call is made to alter it.  If these settings need to be reset to their default values between messages, the Zetafax workstation program should be released from DDE control (a DDERelease DDE Execute call) and then put back under DDE control (a DDEControl DDE Execute call)

After submitting the message or messages the Zetafax workstation program should be released from the control of DDE by issuing a DDERelease command (a DDE Execute call).

The DDE conversation should finally be terminated properly.

DDE command syntax

    The application name is:	Zetafax

    The topic is: 	Addressing


Q.I.4   What DDE commands can be issued?

The following commands (WM_DDE_EXECUTE) may be used using the Addressing topic:

DDEControl

Put the Zetafax workstation program under DDE control for addressing

Send

Submit a message to the fax server for sending.

Preview

Submit a message to the fax server for preview (only available if the API is licenced and the Zetafax workstation program is under DDE control)

DDERelease

Release the Zetafax workstation from DDE control


Q.I.5   What addressing parameters can be controlled via DDE calls using Zetafax without the API licence upgrade?

On all Zetafax configurations the items that may be poked (WM_DDE_POKE) using the Addressing topic whilst the Zetafax workstation program is under DDE control are listed below.  A description of the purpose of each command and its parameters may be found in the embedded addressing commands section earlier in this appendix.

Item	Parameters

To	fax, recipientname, organisation

Fax	fax

Name	recipientname

Organisation	organisation


Q.I.6   What additional addressing parameters can be controlled via DDE with the Zetafax API licence upgrade?

If the API is licenced the additional items that may be poked (WM_DDE_POKE) using the Addressing topic whilst the Zetafax workstation program is under DDE control are listed below.  Again,  a description of the purpose of each command and its parameters may be found earlier in this appendix.

Item	Parameters

From	sendername

Coversheet	coversheet

Letterhead	letterhead

Quality	quality

Priority	priority

After	time

Time	time

Header	header

Attach	files

Charge	charge code


Q.I.7   Is there an example DDE macro?

Here is an example Word for Windows macro which submits the current document to the fax server for sending by fax:

Sub MAIN

REM Set up DDE control of Zetafax

Conv1 = DDEInitiate("Zetafax", "Addressing")

DDEExecute(Conv1, "[DDEControl]")

REM Set the addressing options

DDEPoke(Conv1, "To", "071 378 6886, Chris Oswald, EQUISYS")

DDEPoke(Conv1, "Quality", "High")

DDEPoke(Conv1, "Time", "19:00:00")

DDEPoke(Conv1, "Attach", "infopack")

REM Set Zetafax to the default printer and print the document

FilePrintSetup .Printer = "Zetafax printer on ZETAFAX.SPL"

FilePrint

REM Submit the fax and release DDE control

DDEExecute(Conv1, "[Send][DDERelease]")

DDETerminate(Conv1)

End Sub

Here is an example Excel macro which will submit the current document to the fax server. In Excel, the DDEPoke instructions do not support a constant string as data. It must be a range address. So, instead of using the line:

DDEPoke Conv1, "From", "John Doe"

The instruction should appear as:

DDEPoke Conv1, "From", WorkSheets("Sheet1").Range("A1")

Sub Macro1()

    ZetaTalk = DDEInitiate( _

    app:="Zetafax", _

    topic:="Addressing")

    Application.ActivePrinter = "Zetafax printer on NE00:"

    ActiveSheet.PrintOut

    DDEExecute ZetaTalk, "[DDEControl]"

    Set RecipientName = Worksheets("Sheet1").Range("A1")

    Set OrganisationName = Worksheets("Sheet1").Range("B1")

    Set FaxNumber = Worksheets("Sheet1").Range("C1")

    Application.DDEPoke ZetaTalk, "Name", RecipientName

    Application.DDEPoke ZetaTalk, "Organisation", OrganisationName

    Application.DDEPoke ZetaTalk, "Fax", FaxNumber

    Rem Submit the fax and release DDE control

    DDEExecute ZetaTalk, "[Send][DDERelease]"

    DDETerminate ZetaTalk

End Sub


Q.I.8   Can I use DDE under Windows NT?

Yes.

You need to have Zetafax v4.00e or later for DDE under Windows NT.  In the example above, you need to change the FilePrintSetup call to specify the spool file path.

eg.

FilePrintSetup .Printer = "Zetafax printer on NE00:"

This is best done by recording a simple macro within Word of you selecting the Zetafax printer and copying the resulting Word Basic code to your Zetafax DDE macro.

Under Windows NT, it is also advisable to disable the background printing feature when printing to the Zetafax printer from within a macro.  This can be done by adding the following line:

ToolsOptionsPrint .Background = 0

You can also re-activate background printing by adding the following line to the end of your macro:

ToolsOptionsPrint .Background = 1

Here is an example Word for Windows macro which submits the current document to the fax server for sending by fax under Windows NT:

Sub MAIN

REM Set up DDE control of Zetafax

Conv1 = DDEInitiate("Zetafax", "Addressing")

REM Set Zetafax to the default printer and print the document

FilePrintSetup .Printer = "Zetafax printer on NE00:"

REM Disable background printing

ToolsOptionsPrint .Background = 0

FilePrint

DDEExecute(Conv1, "[DDEControl]")

REM Set the addressing options

DDEPoke(Conv1, "To", "0171 378 6886, Chris Oswald, EQUISYS")

DDEPoke(Conv1, "Quality", "High")

DDEPoke(Conv1, "Time", "19:00:00")

DDEPoke(Conv1, "Attach", "infopack")

REM Submit the fax and release DDE control

DDEExecute(Conv1, "[Send][DDERelease]")

DDETerminate(Conv1)

End Sub


Q.I.9   How can I use embedded addressing to automate faxing?

The Zetafax workstation program allows addressing instructions to be embedded into documents using FaxMerge commands.

Use without the API

Limited support for embedded (or FaxMerge) addressing commands and DDE is standard in Zetafax.  This appendix gives details of all of the options available when the API licence upgrade is purchased for the product.

The concept

Word processor and other applications' documents may contain commands to indicate where a fax should be sent, together with a wide range of settings such as the time of sending, priority, resolution, coversheet and letterhead to use.  If these commands are used in a document, they must be typed using one of Zetafax's own typefaces, and in the appropriate syntax - for example:

%%[Fax:071 378 6886]

When the document is "printed" using the Zetafax Windows printer driver, the FaxMerge addressing commands are used by the Zetafax workstation program in place of the addressing dialog boxes.  Provided adequate details are given using FaxMerge, no dialog boxes will be displayed and the fax or faxes will be submitted to the fax server automatically.


Q.I.10   What embedded addressing options commands are available using Zetafax without the API licence upgrade?

The FaxMerge addressing commands are similar in syntax to entries in SUBMIT files.  They are enclosed in the special characters %%[] to distinguish them from printable text and must be entered in one of the Zetafax printer fonts (eg Zetafax Roman 10cpi).  The FaxMerge text does not appear on the faxes produced by Zetafax.

The following commands are available on all Zetafax configurations:

Format:	%%[TO: fax, recipientname, organisation]

where fax is the fax number to send the fax to, recipientname is the person the fax is addressed to and organisation is that person's company or organisation - fax, recipientname and organisation may each appear in double quotation marks if required

Purpose:	Specifies the fax number to use and the details of the recipient which are put on the fax cover sheet and at the top of each page of the fax (cf the To: field on the Zetafax addressing dialog box)

Example:	%%[To: 071 378 6886, Chris Oswald, EQUISYS]

Format:	%%[FAX: fax]

where fax is the fax number to send the fax to

Purpose:	A subset of and alternative to the %%[To:] command above

Example:	%%[Fax: 071 378 6886]

Format:	%%[NAME: recipientname]

where recipientname is the person the fax is addressed to

Purpose:	A subset of and alternative to the %%[To:] command above - used with the %%[FAX] command

Example:	%%[Name: Chris Oswald]

Format:	%%[ORGANISATION: organisation]

where organisation is the recipient's company or organisation

Purpose:	A subset of and alternative to the %%[To:] command above - used with the %%[FAX] command.

Example:	%%[Organisation: EQUISYS]

Format:	%%[SEND]

Purpose:	Indicates that the document being printed should be split at the foot of this page and submitted as a fax.  The remaining page or pages will be treated as a separate fax or faxes.

Example:	%%[Send]


Q.I.11  What additional embedded addressing options commands are available using Zetafax with the API licence upgrade?

The following options commands are only available if the API is licenced:

Format:	%%[FROM: sendername]

where sendername is the originator of the fax - it may appear in double quotation marks

Purpose:  	Specifies the name which is put on the fax cover sheet as the sender of

the fax (cf the From: field on the Zetafax addressing dialog box)

Example:	%%[From: Gareth Williams]

Format:	%%[COVERSHEET: coversheet]

where coversheet is the name of the file to be used to generate a coversheet for the fax (1 to 8 characters long) or blank for no coversheet -  coversheet may appear in double quotation marks

Purpose:	Specifies what coversheet to generate for the fax onto before sending

Example:	%%[Coversheet: COVSHEET]

Format:	%%[LETTERHEAD: letterhead]

where letterhead is the name of the file to be used as the letterhead (1 to 8 characters long) or blank for no letterhead -  letterhead may appear in double quotation marks

Purpose:	Specifies what letterhead to merge the fax onto before sending

Example:	%%[Letterhead: LETTHEAD]

Format:	%%[QUALITY: quality]

where quality is one of DRAFT, NORMAL or HIGH.

Purpose:	Specifies the resolution to be used when sending the fax, in the same way as the "Resolution" radio button on the workstation sending options dialog box.  For fax, DRAFT and HIGH will normally force the fax to be sent at standard (100x200 dpi) and fine (200x200 dpi) resolutions respectively, whilst NORMAL will send at whichever resolution has been specified by the system administrator in the system initialisation file.

Example:	%%[Quality: NORMAL]

Format:	%%[PRIORITY: priority]

where priority is one of URGENT, NORMAL or BACKGROUND.

Purpose:	Specifies the priority to be used when queuing the fax, in the same way as the "Priority" radio button on the workstation sending options dialog box.

Example:	%%[Priority: NORMAL]

Format:	%%[AFTER: time] or %%[TIME: time]

where time specifies the earliest time that the message should be sent, for deferred sending.  The format of the time field may be one of the following:

hh:mm:ss	(given time today)

yy-mm-dd hh:mm:ss	(date and time specified)

OFFPEAK	(as defined in SETUP.INI)

If the time field is omitted the message is queued for sending immediately.

Purpose:	Specifies when the message is to be sent.

Example:	%%[After: 94-04-01 18:00:00]

Format:	%%[HEADER: header]

where header is one or more of No, To , Fr , Dt and Ti.

Purpose:	Specifies the header to appear at the top of each page of the fax, in the same way as the "Header" radio button on the workstation sending options dialog box.

No	page numbering (n/N)

To	name of recipient

Fr	name of sender

Dt	date

Ti	time

Example:	%%[Header: NoToFrDt]

Format:	%%[ATTACH: files]

where files is a comma separated list of graphics files to attach to the fax.

Purpose:	Specifies the attachment files in the user's private graphics directory (Z-GRAPH) or in the system graphics directory, in the same way as the "Attach" radio button on the workstation sending options dialog box.

Example:	%%[Attach: INFOPACK, PRICES]

Format:	%%[CHARGE: chargecode]

where chargecode is the charge code to be used for the fax

Purpose:	Specifies the charge code to be used when queuing the fax, in the same way as the "Charge" combo box on the workstation addressing dialog box.

Example:	%%[Charge: SALES]

Action commands

These remaining commands may be used within a document to split it into a number of faxes.  They are only available if the API is licenced.

Format:	%%[SEND]

Purpose:	Indicates that the document being printed should be split at the foot of this page and submitted as a fax.  The remaining page or pages will be treated as a separate fax or faxes.

Example:	%%[Send]

Format:	%%[PREVIEW]

Purpose:	Indicates that the document being printed should be split at the foot of this page and submitted as a fax for preview.  The remaining page or pages will be treated as a separate fax or faxes.

Example:	%%[Preview]


Q.I.12  How can I use ZSUBMIT to automate faxing?

Creating SUBMIT files

One of the API methods of submitting a fax for sending is to create a file in a specific format, termed SUBMIT file format.  This is an ASCII text file which usually contains details of the options to use in preparing the message, the recipients of the message, as well as the message text itself.

ZSUBMIT program

The message may then be sent using the ZSUBMIT program.  This program may be installed to run continuously as one of the Zetafax server programs, regularly checking a particular directory for the existence of a SUBMIT format file.  If one is found then it is interpreted and submitted to the fax server for sending - its progress may then be monitored using the workstation program as normal.

The ZSUBMIT program submits all messages as a given Zetafax user, and if required will monitor progress of the messages, limiting the number of outstanding messages at any one time or removing any entries which have been sent without errors.  Files for sending via the ZSUBMIT program may also contain more than one message for sending - the program will split it into separate messages before submitting it to the server.

Use with API calls

SUBMIT format files are also used by the Application Programmers Interface (API) routines to specify message options and text for sending.  These routines allow user written application programs to send messages directly without using either the workstation or ZSUBMIT program.  The ZSUBMIT program itself is written using these routines, and requires the API licence to run.


Q.I.13  What is the SUBMIT file format?

This article details the format of SUBMIT files, for use with both the ZSUBMIT program and with the API routines.  It gives the structure and fields allowed in the file for specifying message options and recipients, and also for formatting the message text.  It also describes how to install and use the ZSUBMIT program.

The SUBMIT file is a standard ASCII text file (multiple lines, each terminated with <CR><LF>).  The file information about the options to be used in preparing a given message, the recipients, and the message text itself.  The format is:

%%[MESSAGE]

(message option lines)

(message addressing lines)

%%[TEXT]

(text including message text fields)

or, if a separate file contains the message to be sent (eg to send a graphics file):

%%[MESSAGE]

(message option lines)

(message addressing lines)

%%[FILE]

(filename, including path)

Note that the first line of the file must be "%%[MESSAGE]".

The section headings ("%%[MESSAGE]" and "%%[TEXT]" or "%%[FILE]"), all message option and addressing lines, and the filename (if the second form is used) must start at the left of the line (ie there must be no spaces preceding them).  Finally TAB characters should not be used in the file - they will be replaced with a space character.

Files submitted using the ZSUBMIT program may contain information about one or more messages by simply concatenating the files (ie the %%[MESSAGE] section for the second message follows the end of the %%[TEXT] or %%[FILE] sections for the first message, etc).  The ZSUBMIT program splits the file into separate messages before submitting them to the server.

SUBMIT files used with the API functions may only contain information for a single message - everything from the first %%[TEXT] command to the end of the file is treated as message text.  Certain of the functions only look at one of the two sections - in this case the other section may of course be omitted.

SUBMIT file Message Option lines


Q.I.14  What SUBMIT file message option lines are available?

These lines appear at the start of the %%[MESSAGE] section, before the addressing lines (ie before the first "To:" line).  If omitted, all the lines (except the "Comment:", "Attach" and "Charge" lines) default to the values specified for the given user.  For files submitted by programs using the API functions, this is the user specified in the ZfAPIInit call.  For files submitted using the ZSUBMIT program, it is the user specified in the User: line, either in the %%[MESSAGE] section (if given), or in the SETUP.INI file.

AFTER: 	time

where time specifies the earliest time that the message should be sent, for deferred sending.  The format of the time field may be one of the following:

yy-mm-dd hh:mm:ss	(date and time specified)

OFFPEAK	(as defined in SETUP.INI)

If the time field is omitted the message is queued for sending immediately.

Purpose:	Specifies when the message is to be sent.

Example:	After: 94-02-22 18:00:00

ATTACH: 	files

where files is a comma separated list of graphics files to attach to the fax.

Purpose:	Specifies the attachment files in the user's private graphics directory (Z-GRAPH) or in the system graphics directory.  These are added to the end of the fax before sending.  A maximum of 30 files may be specified.

Example:	Attach: INFOPACK, PRICES

CHARGE: 	chargecode

where chargecode specifies the charge code to use for this message, and may be any text.

Purpose:	Specifies the charge code to use for this message.  Charge codes are stored in the Zetafax billing log when the fax completes, and may be used for charging the fax to a particular department or client.

Example:	Charge: Sales Dept

COMMENT:	comment

where comment is the message description (up to 40 characters long)

Purpose:	Specifies the message description as displayed on the right of the workstation OUT window.  If this line is omitted a message description detailing the first addressee is used.

Example:	Comment: Smith and Co January invoice

COVERSHEET: coversheet

where coversheet is the name of the file to be used to generate a coversheet for the fax (1 to 8 characters long) or blank for no coversheet

Purpose:	Specifies what coversheet to generate for the fax onto before sending

Example:	Coversheet: COVSHEET

FORMAT: 	format

where format specifies the file format of the data file to be sent.  The possible values of the format field (together with the data type and the associated data file extensions) are:

ASCII	(ASCII text, unformatted - TXT)

EPSON	(Epson FX or LQ print spool file - EPN)

TIFF-NORMAL	(100x200 dpi TIFF fax file - G3N)

TIFF-FINE	(200x200 dpi TIFF fax file - G3F)

TIFF-SUPERFINE	(400x200 dpi TIFF fax file - G3S)

Purpose:	Specifies what format the data file is in.  In a standard SUBMIT file (containing a %%[TEXT] section) the format should be "EPSON" or "ASCII".  Epson should be used if the message text contains any "%%" formatting commands (eg "%%[BOLD:ON]").  If however the message text just contains ASCII text then the format should be specified as "ASCII" (or the line omitted), in which case the result will be the same as using the workstation to send an ASCII text file.

Example:	Format: EPSON

FROM: 	sendername

where sendername is the originator of the fax

Purpose:	Specifies the name which is put on the fax cover sheet as the sender of the fax (cf the From: field on the Zetafax addressing dialog box)

Example:	From: Gareth Williams

HEADER: 	header

where header is one or more of No, To, Fr, Dt and Ti (with no separating spaces), as follows:

No	Page numbering (n/N)

To	Name of recipient

Fr	Name of sender

Dt	Date

Ti	Time

Purpose:	Specifies the format of the header line to appear at the top of each page of the fax.

Example:	Header: NoToFrDt

HOLD: 	hold

where hold is either "YES" or "NO".

Purpose:	Specifies whether the message will be held once it in the queue, meaning that it will not be sent until the user releases it (using the Zetafax workstation "File Release" command).  This gives a similar effect to the "Hold for preview before sending" check box on the Zetafax workstation addressing dialog, allowing the fax to be checked on screen before sending.

Example:	Hold: YES

LETTERHEAD: 	letterhead

where letterhead is the name of the file to be used as the letterhead (1 to 8 characters long) or blank for no letterhead

Purpose:	Specifies what letterhead to merge the fax onto before sending

Example:	Letterhead: LETTHEAD

PREVIEW: 	preview

where preview is either "YES" or "NO".

Purpose:	Specifies whether a preview file is to be prepared for this message.  This is a copy of the fax prepared for the first recipient, which can be viewed using the "File View" option on the workstation.  The default setting is "YES", but if disk space is short and there is no requirement to view the faxes from a workstation then this parameter may be set to "NO".

Note that to preview the fax on the Zetafax workstation before it is sent (in a similar way to the "Hold for preview before sending" check box on the workstation addressing dialog box) you should set this option to "YES" (the default), and also set the Hold: message option (qv)

Example:	Preview: NO

PRIORITY: 	priority

where priority is one of "URGENT", "NORMAL" or "BACKGROUND".

Purpose:	Specifies the priority to be used when queuing the fax, in the same way as the "Priority" radio button on the workstation sending options dialog box.

Example:	Priority: NORMAL

QUALITY: 	quality

where quality is one of "DRAFT", "NORMAL" or "HIGH".

Purpose:	Specifies the resolution to be used when sending the fax, in the same way as the "Quality" radio button on the workstation sending options dialog box.  For fax, "DRAFT" and "HIGH" will normally force the fax to be sent at standard (100x200 dpi) and fine (200x200 dpi) resolutions respectively, whilst "NORMAL" will send at whichever resolution has been specified by the system administrator in the system initialisation file.

Example:	Quality: NORMAL

USER: 	username

where username specifies a valid Zetafax user name.

Purpose:	Specifies the Zetafax user submitting this file.  The command may be omitted if the default user name specified in the [ZSUBMIT] section in the SETUP.INI initialisation file was not blank, or if submitting using the API "C" functions.

NOTE - this command can only be used in files submitted using the ZSUBMIT program (rather than using the API "C" function calls, where the name is specified in the ZfAPIInit function).  The ZSUBMIT program can be configured to disable this command, if desired for permissioning or security reasons.

Example:	User: JSMITH


Q.I.15  What SUBMIT file message addressing lines are available?

These lines appear in the %%[MESSAGE] section, after the message options lines detailed above.  Note that a "To:" line must be first line specified (after the last message option line), before any other message addressing lines.  The lines may be repeated if the message is to be sent to more than one person, with each repeated set starting with a "To:" line.

FAX: 	number

where number is the fax telephone number (cf the Zetafax address book editor fax number field) .

Purpose:	Specifies the fax number to send the fax to.  If the number is unknown at the time of creating the file the number can be omitted.  The fax server will reject the send to that recipient, and the message can be resubmitted manually entering the fax number as required.

Default:	None - mandatory field (unless LAN: line is specified - see below)

Example:	Fax: 0256 759821

FIELD: 	fieldname text

where fieldname is a single word (ie without any spaces) giving the name of a FaxMerge field, and text is the string which will be substituted for the field.

Purpose:	FaxMerge fields are identified in a document by the string "%%[fieldname]" (without the double quotes).  When the fax is prepared for sending these fields are replaced with the text given, allowing faxes to multiple addressees to be personalised, for example.  Multiple FIELD lines may be specified.  NOTE - the Field lines are not retained if a message is resubmitted using the Zetafax workstation program (for example, to correct a fax number).

The following field names are reserved, and should not be used with this command:

COVERTEXT	ORGANISATION

DATE	PAGE

FROM	PAGES

LANDSCAPE	PORTRAIT

NAME	TIME

NOTES

Default:	None - any fields not specified are left in the document with the leading "%%" removed.

Example:	Field: Department Sales and Marketing

LAN: 	username

where username is the Zetafax username of the person to be sent to.

Purpose:	Specifies the name of the Zetafax user for messages which are to be sent across the LAN (appearing in the user's IN window).  This can be useful when testing applications to check the appearance of faxes to be sent without actually sending them to the remote user, in the same way as one might use Preview from the workstation.

Default:	None - used as an alternative to the Fax: line

Example:	LAN: FSmith

ORGANISATION: organisation

where organisation is the name of the company or organisation to which the fax recipient belongs

Purpose:	The organisation name is used on the coversheet of the fax.

Default:	blank

Example:	Organisation: Smith and Sons Limited

TO: 	name

where name is the name of the person to whom the fax is to be sent.

Purpose:	Specifies a recipient of the fax (cf the Coversheet Name field in the Zetafax address book).  This name is used on the coversheet of the fax, on the header line of the fax, and also in the comment on the right hand side of the OUT window in the workstation display.

Default:	None - mandatory line.

Example:	To: Sam Smith


Q.I.16  What SUBMIT file message text commands are available?

These commands appear in the %%[TEXT] section and may be freely interspersed with the message text.

See the FaxMerge description in this user guide for details about what to do if you need to include the characters "%%[" in the message, without them being treated as a command.

%%[APPEND:file]

where file is the base name of a graphics file in the Z-GRAPH directory.

Purpose:	Appends a graphics image (eg a scanned information sheet) to the end of the message (similar to the Zetafax workstation "Attach" option).  Up to 30 of these commands may be entered, and the named files will be added to the end of the message as new pages.  This command can also be used in separate ASCII format files specified using the %%[FILE] option.

Example:	%%[Append:INFOPAGE]

%%[BOLD:state]

where state is either "ON" or "OFF".

Purpose:	The %%[BOLD:ON] command causes all characters following to be printed in bold until either a %%[BOLD:OFF] command is encountered or the end of the %%[TEXT] section is reached.

Example:	%%[Bold:ON]

%%[DATE]

Purpose:	Inserts the date when the message is prepared for sending, in the format

"1st January 1994".  This command can also be used in separate ASCII format files specified using the %%[FILE] option.

Example:	%%[Date]

%%[DOWN:distance]

where distance is the number of units to move down the page from the current position.  A unit is approximately 1/100th of an inch.

Purpose:	This command moves down the page a given distance and may be used, for example, to position the top line of text to fit within a merged form.  Note that the first line of text prints approximately 0.7 inches below the top of the page.

Example:	%%[Down:100]

%%[FONT:font]

where font is the font required, and is one of "ROMAN10", "ROMAN12", "ROMAN20", "ROMAN5", "ROMAN6" or "ROMANPS" giving 10cpi, 12cpi, 20cpi, 5cpi and 6cpi fixed space fonts, and proportional spaced font respectively.

Purpose:	This command is used to set the font to be used for the remainder of that message (ie until the end of the %%[TEXT] section).

Example:	%%[Font:ROMAN10]

%%[INSERT:file]

where file is the base name of a graphics file in the Z-GRAPH directory.

Purpose:	Inserts a single page graphics image (eg a signature) at the current position on the page.  The image is merged into the document - you must leave enough lines following the command blank if you wish to avoid the image overprinting the following text.  This command can also be used in separate ASCII format files specified using the %%[FILE] option.

Example:	%%[Insert:ABCLOGO]

%%[LANDSCAPE]

Purpose:	This command causes the text which follows (until a %%[PORTRAIT] command or the end of this message, whichever comes first) to be printed in landscape orientation.  The command must come before any other text - ie at the start of the first line following the %%[MESSAGE] command, or immediately after a %%[PAGE] command (on the same line).  This command can also be used in separate ASCII format files specified using the %%[FILE] option.

Example:	%%[Landscape]

%%[LMARGIN:width]

where width is the size of the left hand margin in character widths.  The width of each character is dependent upon the font being used.

Purpose:	This command is used to set the left margin for the remainder of that message (ie until the end of the %%[TEXT] section).  It should be placed at the start of a line.  Note that the margin width excludes a strip of width 0.5 inches at the left of the page which may not be used (ie a value of 0 would set the left hand margin 0.5 inches from the left of the page).

Example:	%%[LMargin:200]

%%[PAGE]

Purpose:	This command is used to start a new page.

Example:	%%[Page]

%%[PORTRAIT]

Purpose:	This command cancels a previous %%[LANDSCAPE] command, reverting to portrait orientation.  The command must come before any other text - ie at the start of the first line following the %%[MESSAGE] command, or immediately after a %%[PAGE] command (on the same line).  Note that the margin settings following a %%[PORTRAIT] command are different from the defaults for ASCII files, allowing slightly more of the page to be printed.  This can be useful when overprinting forms, for example.  This command can also be used in separate ASCII format files specified using the %%[FILE] option.

Example:	%%[Portrait]

%%[RIGHT:distance]

where distance is the number of units to the right from the current position.  A unit is approximately 1/100th of an inch.

Purpose:	This command moves across the page to the right a given distance and may be used, for example, to position a word precisely within a form.

Example:	%%[Right:100]

%%[TIME]

Purpose:	Inserts the time when the message is prepared for sending, using a 24 hour clock, in the format "12:34".  This command can also be used in separate ASCII format files specified using the %%[FILE] option.

Example:	%%[Time]

%%[UNDERLINE:state]  or  %%[UL:state]

where state is either "ON" or "OFF".

Purpose:	The %%[UNDERLINE:ON] command causes all characters following to be printed underlined until either a %%[UNDERLINE:OFF] command is encountered or the end of the %%[TEXT] section is reached.

Example:	%%[Underline:ON]

%%[fieldname]

where fieldname is the name of a FaxMerge field

Purpose:	Inserts the text for the given field for that addressee.  The following fieldnames are defined for all messages submitted using the API or ZSUBMIT program:

FROM	NAME	ORGANISATION

Other fields are only defined if they have been specified using the Field: message addressing line (see above).  This command can also be used in separate ASCII format files specified using the %%[FILE] option.

Example:	%%[Organisation]


Q.I.17  Where can I find example SUBMIT files?

Example SUBMIT files are given in the Zetafax user manual.  You can also find more documentation and example SUBMIT

Simple message

%%[MESSAGE]

From: Gareth Williams

To: Sam Smith

Organisation: Smith and Sons

Fax: 0256 738921

%%[TEXT]

Dear Sam

Here's a short fax produced automatically

Yours, Gareth

Multiple messages

%%[MESSAGE]

From: Gareth Williams

To: Sam Smith

Organisation: Smith and Sons

Fax: 0256 738921

%%[TEXT]

Hello Sam!

%%[MESSAGE]

From: Gareth Williams

Coversheet: COVSHEET

To: Jim Jones

Organisation: Jones Brothers

Fax: 0244 768112

%%[TEXT]

Hello Jim!

Multiple addressees

%%[MESSAGE]

From: Gareth Williams

Coversheet: COVSHEET

Letterhead: LETTHEAD

To: Sam Smith

Organisation: Smith and Sons

Fax: 0256 738921

To: Jim Jones

Organisation: Jones Brothers

Fax: 0244 768112

%%[TEXT]

Don't forget the steering group meeting this evening

Gareth

Text formatting

%%[MESSAGE]

From: Gareth Williams

Coversheet: COVSHEET

Letterhead: LETTHEAD

Format: EPSON

To: Sam Smith

Organisation: Smith and Sons

Fax: 0256 738921

%%[TEXT]

%%[LMARGIN:200]

%%[DOWN:200]

%%[FONT:ROMAN10]

Dear Sam

Here's a %%[BOLD:ON]short fax%%[BOLD:OFF] produced automatically

%%[PAGE]%%[DOWN:200]This is the second page

Now to end the letter with a signature added using the standard "insert graphics" command.

Yours

%%[INSERT:GWSIG]

Gareth Williams


Q.I.18  How is ZSUBMIT installed?

The ZSUBMIT program is distributed with the Zetafax server programs, and is stored in the same directory as the other programs (zfax\SERVER by default, where zfax is the server base directory specified when Zetafax was installed).

The program is configured using the Zetafax SETUP program (stored in the zfax\SERVER directory).  The "server options" section of the program contains a dialog box to set the various parameters used by ZSUBMIT.

These parameters are read on startup from the SETUP.INI file in directory zfax\SYSTEM\Z-DB, from the [ZSUBMIT] paragraph.  The following sections describe the parameters, giving the line name in SETUP.INI, although these correspond exactly to the SETUP program dialog box.

Default settings

The User line specifies the default Zetafax user name for the program to use.  All messages will be sent as if by this user, unless a user name is specified in the SUBMIT file.  If the user name is left blank, then each SUBMIT file must specify a user name.

Sending is similar to addressing files using the workstation - the settings used for items such as Coversheet, Letterhead, Priority and From name are the defaults for that user unless specifically overridden by lines in the SUBMIT file.

Because an existing user may inadvertently change these settings and so affect the settings for files being sent automatically, it is normally advisable to add a new user for use by the program (eg called "ZSUBMIT"), and log in as this user on the workstation when wishing to check the status of messages submitted by the program.

Polled directory

The Directory line gives the full path name of a directory to be polled by the program.  By default, the program regularly checks this directory for any files with the extension ".SUB".  If any are found, then they are interpreted as SUBMIT format files and submitted to the server for sending.

Configuration options

The optional parameter lines in SETUP.INI, which may be modified directly or by using the SETUP program, are as follows.

The File line specifies what files to search for in the given directory.  The default if omitted is "*.SUB".  If you change this you must ensure that a filename of the format "*.ERR" will not be matched, since the program changes the extension of files containing a syntax error to ".ERR".

The OtherUsers line is used to control whether users can specify the Zetafax username in the SUBMIT file, overriding the name given in the "User" configuration line.  Add the line "OtherUsers: NO" if you want to ensure that messages can only be submitted as the given user when using the ZSUBMIT program (eg for permissioning or security reasons).

The SpoolCheckTimer line specifies the polling interval, in seconds (ie how often it looks for submit files in the directory for sending and checks the status of messages already queued).  Reducing the value increases the processing overhead of the program.

The MessageTidy line specifies whether messages which have been sent successfully (ie they would be displayed by the workstation with a tick) should be deleted automatically.  This is useful in systems where a large number of messages are being submitted automatically and you just want to check for any which have failed.  The parameter is either "YES" (to delete completed messages) or "NO".

The MaxActive line is used to limit the number of messages in the queue at any one time.  If the value is 0 any SUBMIT file found in the directory will be submitted to the server immediately it is found.  Otherwise the file is only submitted if the number of active messages (ie those in the queue which are being converted or sent, or which are waiting for a converter or device to become free) is lower than the specified value - the program will wait for one of the existing messages to complete if not before submitting the file.

The SubmitWait and DeleteWait parameters specify the time in seconds to wait after submitting a file to the server or deleting a file which has completed.  They are used to protect against the program interfering with other server programs when submitting a large number of messages, although it should not normally be necessary to change them from the defaults.


Q.I.19  Can ZSUBMIT be run automatically?

The ZSUBMIT program requires the Application Programmers Interface (API) to be licenced before it can be run on a given machine.  The program may be run either as a server program, continually checking the given directory for files, or it may be run with a single file name as a parameter (although this may contain more than one message), which it will process and submit to the fax server, then exit.

If the program is to be run automatically when the Zetafax server is started, the following line should be added to the [SERVER] paragraph in the SETUP.INI file if not already present:

Service: ZSUBMIT "ZSUBMIT.EXE /S" "Automatic submitter" RR

You can stop the program being run automatically if this is not required by adding a semicolon to the start of the line..  The "/S" parameter causes the program to log any error or information messages to the server error log files, allowing them to be viewed from the workstation or the ZSERVER program display.

Creating a SUBMIT file

With the program running in polling mode (ie started using the Service: line given above, or run without parameters), files in SUBMIT file format may be submitted by simply copying them to a file in the specified directory with the extension ".SUB".  If the file contains more than one "%%[MESSAGE]" section (ie contains more than one message to be sent) then it is first split up by the program into separate message files in the polling directory, named ~ZSUBnnn.SUB, where "nnn" is a unique number for each file.  Each file is then interpreted separately and submitted to the server for sending.

Syntax errors

If an error is found in the format of one of the files (eg an invalid or missing line in the message options), an error message is logged giving the problem and file name, and the file extension is changed to ".ERR"; otherwise the file is deleted once it has been separated (in the case of multiple message files) or submitted successfully.  This directory should be checked if submit errors occur to identify the problem then delete the ".ERR" file - performance of the program will be affected if the number of files in the directory is allowed to become very large.


Q.I.20   How can I use the C language interface to automate faxing?

C Language API

The C language Application Programmers Interface (API) allows application programs to submit faxes to the Zetafax server for sending, and to control and monitor their progress as required.

A simple function call is provided to submit an ASCII text file in a given format.  This format (termed SUBMIT file format) includes details of the recipients of a message in addition to the message text, which can include text formatting such as bold and underlining.  The SUBMIT file format is defined above (see page 204).

A range of other function calls allow other supported file formats to be submitted, and give full control over messages queued for a given user.

ZSUBMIT

The ZSUBMIT program is an API program which may be run automatically as part of the Zetafax server.  This will poll a given directory for SUBMIT format files, submitting any which are found to the server for sending, thus allowing application programs to submit faxes indirectly by simply creating a file of the correct format - in this case the workstation would be used as normal to monitor progress.  The ZSUBMIT program is described above (see page 215).

Libraries

The API comprises a set of 'C' callable functions.  It is distributed as a set of object libraries (for use in different environments) for building into the application programs, together with a 'C' header file containing definitions required to call the API functions.  The operating systems currently supported are:

OS/2 (version 1.1 or later)

MS-DOS (version 3.0 or later)

Microsoft Windows 3.x

Microsoft Windows NT

Microsoft Windows 95

Compilers	The API is available for use with the Microsoft and Borland 'C' compilers.

It must be licenced on each Zetafax system on which you wish to run programs which use it (including the ZSUBMIT program).

File system structure

When the API is initialised a Zetafax user name must be specified.  Messages submitted by the API will appear as if submitted from a workstation logged on as this user, and the defaults for items such as coversheet, "From" name will be those for the user (exactly as if you submit a message from the workstation without changing any of the default values).  The user given must have been added in the normal manner.

Message files for sending are stored in the user's OUT directory.  The full pathname of this is zfax\USERS\username\Z-OUT, where zfax is the Zetafax base directory.  API programs should use the ZfGetUserOutDir() function to get the name of this directory if required.

A message for sending comprises two files in the OUT directory - a CONTROL file and a DATA file.  Both files (and all other files created by the server relating to this message) have a common file body name, with different extensions for the different files.  So for example files for message "~SEND000" would have file names of format "~SEND000.*".  "~SEND000" is referred to in the API as the message body name, and it is this which is supplied to the API functions when specifying messages to submit, delete, etc.  The ZfCreateAutoFile() function is used to create a file with a unique body name in a given directory.

The CONTROL file is a file with extension ".CTL".  This is an ASCII text file and gives full details of the options to be used in preparing a message for sending (the coversheet, letterhead, priority etc), together with details of the intended recipients of the message (name, organisation, fax number etc).  The file is updated by the server as the message is processed to give details of progress for each addressee, errors etc.  For use with the API this file will generally have been created by interpreting a SUBMIT format file.

The DATA file contains the message to be sent.  The extension depends on the format of the data.  Supported formats include:

TXT 	ASCII text

EPN 	Epson FX or Epson LQ Windows driver

G3N	TIFF fax format normal resolution (200x100 dpi)

G3F	TIFF fax format fine resolution (200x200 dpi)

G3S	TIFF fax format superfine resolution (200x400 dpi)

Message Information

When a message is submitted to the server for sending (after creating a CONTROL file and DATA file for the message), an entry is made in the INFO file in the user's OUT directory.  This entry includes the file name of the message, the comment associated with it, and the current status of the message (converting, sending etc).  The server is then notified that a new message is ready for sending, and will add the message to its queue.

The status field is updated by the server program as the message is processed.  When the server completes processing of the message (and the status has changed to OK or FAILED) the message may be deleted.  This is done by removing the INFO file entry then deleting the message files, and may be done either from the workstation or via the API.

Details of a message in the INFO file may be obtained using the ZfGetMsgInfo() or ZfGetMsgList() routines, giving details of a single message or all messages in the INFO file respectively.  These store the information in a data structure of type ZFMSGINFO.  The fields in this structure are as follows.

szBody	Character string giving the body name of the message files (ie the file name without extension or preceding '.').  The maximum length of this string (excluding terminating NULL) is given by the constant ZFMSG_BODY_LEN.

szComment	Character string giving the description of the message being sent (as displayed on the right in the workstation main display).  The maximum length of this string (excluding terminating NULL) is given by the constant ZFMSG_COMMENT_LEN.

Status	Current status of message.  This is a variable of type ZFMSGSTATUS, and the value is one of the ZFMSG_??? values listed below.

The following list gives the possible states for a message and their meanings.

•	ZFMSG_ADDING	- Message being added to queue

•	ZFMSG_HELD	- Message held by user

•	ZFMSG_DEFERRED	- Message waiting for sending after a specific time, either because that time was specified when the message was submitted, or the user does not have sufficient permissions to send until after the given time.

•	ZFMSG_WAITING	- Waiting for conversion or for a free device to send the message.

•	ZFMSG_CONVERTING	- Preparing the message for sending (merging with letterhead, creating coversheet etc).

•	ZFMSG_CONNECTING	- Dialling remote device, or connecting to local printer etc.

•	ZFMSG_SENDING	- Connection made, sending message to remote device.

•	ZFMSG_SCANNING	- (not applicable)

•	ZFMSG_ABORTING	- Processing an Abort request, waiting for device controller or convert program to cancel processing of the message.

•	ZFMSG_INCOMING	- (not applicable)

•	ZFMSG_WAITING_SCAN_DOC	- (not applicable)

•	ZFMSG_OK	- Completed (sent) successfully, with no errors.  The message may now be deleted (using the ZfDeleteMsg() function).

•	ZFMSG_FAILED	- Completed with one or more errors.  Details of the errors which occurred are listed in the CONTROL file, although this would normally be checked manually.  The message may now be deleted (using the ZfDeleteMsg() function).

•	ZFMSG_PREVIEW_OK	- Previewing completed successfully, and the preview file is ready for viewing.  The message may now be deleted (using the ZfDeleteMsg() function), though this would normally be done from the workstation after viewing the preview..

•	ZFMSG_PREVIEW_FAILED	- Previewing failed.  The message may now be deleted (using the ZfDeleteMsg() function)., although this would normally be done from the workstation.


Q.I.21  What C language functions are available in the Zetafax API?

Function overview

There follows a brief overview of the functions which comprise the API.  Full details of each function are given in a separate document.

User supplied functions

If an error occurs the API routines call the ZfPrintError routine with a textual error string as well as returning an error code to the calling program.  This routine is prototyped in the ZFAPI.H header file, but should be defined in the calling program, even if it ignores the text and simply returns immediately.

General routines

Before using any API functions the program should call ZfAPIInit.  This specifies the user name to use - note that it may be called more than once with different user names if required.  The ZfAPIClosedown routine should be called by the program before exiting.  The ZfGetAPIVersion function returns the version number of the library (for printing in a startup message if desired).  ZfCreateAutoFile generates a file in a given directory so that no other files exist with the same body name.  Finally ZfCheckServer checks whether the fax server is running (although several of the other routines will also return an error if the fax server is not running when they are called).  ZfStartServer and ZfStopServer start and stop the fax server software.

Location of files

The standard Zetafax installation gives each user a base directory called zfax\USERS\username, and places message files for sending in the directory zfax\USERS\username\Z-OUT (where zfax is the Zetafax base directory specified at installation time).  The full pathnames of these directories are returned by the ZfGetUserArea and ZfGetUserOutDir functions respectively.  Although not normally needed, the ZfGetSystemArea routine may be used to obtain the full pathname of the zfax\SYSTEM directory, used for storing letterheads etc.

Submitting a message

The simplest method of submitting a fax for sending is to create an ASCII text SUBMIT file containing both the message options and the message text, then call the ZfSendSubmitFile function.  This creates a CONTROL and DATA file in the user's OUT directory, then submits the message to the server (which also makes an entry in the INFO file for that user).

Alternatively these three stages may be carried out independently.  The ZfCreateCtlFile function interprets the %%[MESSAGE] section of a SUBMIT file, which contains details of the message options and addresses, and generates a CONTROL file.  The ZfCreateDataFile interprets the %%[TEXT] section of a SUBMIT file to generate an ASCII text or Epson FX format data file if required - alternatively a file of the correct format could simply be copied or created by the program.  Finally the ZfSendMsg function makes an entry in the INFO file and submits a CONTROL and DATA file pair to the server.

Message control

Once a message has been submitted to the fax server, its status may be obtained using the ZfGetMsgInfo function provided the message name is known.  Otherwise the ZfGetMsgList function may be used to return the status of all messages currently queued (or completed but not yet deleted) for the given user.  The ZfCheckNewMsgStatus function is used in conjunction with this - it checks whether the status of any messages for the user have changed since it was last called to save the overhead involved in calling ZfGetMsgList unnecessarily.  ZfGetMsgHistory may be used to obtain the full transmission history for a message.

The ZfAbortMsg function requests the fax server to abort processing of a given message (ie stop preparation or transmission of the message).  When the server has completed processing it sets the message status to OK or FAILED.  Messages in either of these states may be deleted from the INFO file by calling ZfDeleteMsg - optionally, this will also delete the CONTROL and DATA files for the message, together with any other temporary files generated by the server.


Glossary of terms


Address book

Zetafax has its address books: a network one shared by all users, and a private one for each user.  If you have an email system configured, you can also use the email address books in the same way as when you are addressing a mail message.


Application Programmers Interface (API)

Zetafax has an API licence upgrade available, which makes it simple to automate the sending of faxes from other applications.  It is designed for use with Windows applications, DOS programs, minis and mainframes.

The API has been used in a wide range of tailor-made solutions ranging from the automatic faxing of financial statements to the forwarding of faxes from unattended satellite ground stations around the world.  Please call us to discuss your specific requirements.


Archive

Zetafax allows you to archive on disk every fax sent or received, allowing you to retrieve them days or even months later.  You can also print faxes automatically on any Windows printer, with an optional status page giving the connection time and details.


Automatic forwarding

If you are going away on holiday, you can tell Zetafax to forward all faxes sent to you to another user.  You can even choose whether to keep your own copy of the faxes for when you return.

The automatic forwarding can work repeatedly in a chain if necessary.  For example, if the person looking after your messages also goes on holiday, his or her messages (including those forwarded from your account) can be forwarded on to someone else.


Automatic submission program

The APIs ZSUBMIT program lets DOS, mini and mainframe programs send faxes by creating text files in a shared directory on a file server.  For example, faxing purchase orders or invoices usually only requires adjusting an accounts packages report writer.

A text file needs a few lines added to give the fax number and message options.  Logos and signatures can be included and the text may be merged onto a multi-page form using the letterhead feature in Zetafax.  This approach gives results rapidly.


Billing log - FAX.LOG

A record of all faxes sent is kept in the billing log - FAX.LOG.  This file is stored in the zfax\SERVER\Z-DB directory.

A line is added for every message addressee sent to by fax, giving details such as the Zetafax user name, addressee name and company, the phone number, the connection time and number of pages sent.

The billing log file may be converted into a suitable format for a spreadsheet or analysis program using the LOGCVT program.


Brooktrout fax cards

Zetafax 4.5 supports the Brooktrout intelligent fax cards including the TR114 and Trufax range under Windows NT.  The Brooktrout boards support DDI, reduce call times and transfer more of the call processing load from the fax server’s main processor to the fax board.


C language callable functions

For the greatest degree of control, the API includes a library of 18 functions which may be called from Windows, DOS and OS/2 'C' programs.  Application programs can submit new faxes for sending, and monitor/control faxes already in the central queue.

•	Specify the Zetafax user account to use

•	Submit a new message for sending

•	Abort a message already in the queue

•	Get a list of all messages queued for the user

•	Check the current status of a given message

•	Retrieve the transmission history for a message


Charge Codes

Charge codes can be enabled, and made optional or compulsory,  using the Zetafax Setup program - Change Server Settings|General.  Users select the charge code after addressing the fax in the Addressing Dialog Box.  Charge codes are logged in the billing log (FAX.LOG).


Class

The group of a fax device describes the method it uses to communicate with other fax devices (eg. over the telephone PSTN).  The most common group is group III.


Class 1:

A class 1 fax modem is little more than a data modem with a few extra frequencies that are necessary for group III fax transmission.


Class 2:

Class 2 is a higher level specification than class 1.  More of the fax protocol work is done within the fax modem firmware.  This fax service class specification was never formally approved by the ITU.


Class 2.0:

Class 2.0 is similar to the Class 2 specification, but has been formally approved by the ITU.


DDE (Dynamic Data Exchange)

An alternative way of passing addressing information to Zetafax is DDE.  The same range of options can be controlled by sending DDE messages to the client software.


DDI/DID routing

Many companies already have a phone system (PBX) where each extension can be dialled directly from outside the company, rather than having to go via the switchboard.  The technology behind this is called Direct Dialling Inwards (DDI or DID), and is as applicable to fax as it is to voice calls.

This is the most direct of the inward routing methods.  Each user is given their own fax number - not a separate fax line, just their own number.  Faxes sent to that number are routed directly to the user.  Groups of users can also be allocated a DDI/DID number giving Departmental DID routing capabilities.

The number of fax numbers allocated is independent of the number of fax lines on your Zetafax system - all you do is define a table of fax numbers, giving the Zetafax user account corresponding to each one.

If your phone system supports DDI for telephone calls already, it can be configured simply to allow DDI for fax.  If you do not already have DDI you can install a separate digital telephone line (ISDN) to support it just for fax.  Details of both these methods are given below.

DDI routing requires the direct dial routing licence upgrade.


DLL callable functions

For the greatest degree of control, the API includes a library of 18 functions which may be called from Windows programs.  Application programs can submit new faxes for sending, and monitor/control faxes already in the central queue.

•	Specify the Zetafax user account to use

•	Submit a new message for sending

•	Abort a message already in the queue

•	Get a list of all messages queued for the user

•	Check the current status of a given message

•	Retrieve the transmission history for a message


DTMF routing

The method Zetafax uses for DDI routing is to recognise DTMF tones sent to the fax server just after it answers the call, telling it what number was dialled.  These are the musical tones generated by modern phones when the number keys are pressed.

Even without giving each user their own fax number, you can still get the same effect by getting the sender to key in extra digits after Zetafax answers the call.  This is normally done by adding them to the fax number, after a few “pause” characters.  Because of the relatively high level of sophistication required this is suitable for expert fax senders only!

DTMF routing requires the direct dial routing licence upgrade.


Dynamic Data Exchange (DDE)

An alternative way of passing addressing information to Zetafax is DDE.  The same range of options can be controlled by sending DDE messages to the client software.


e-mail

Zetafax includes facilities for distributing fax messages to other Zetafax users on the LAN, using facilities similar to those in electronic mail (email) packages.  However Zetafax can also integrate with email more directly, by allowing received faxes to be forwarded by mail and by using an email address book rather than the Zetafax address book.

Need our email address?

For information contact:	info@equisys.com

For support enquiries:	support@equisys.com


Embedded addressing

Like many fax packages, Zetafax has a Windows printer driver.  Print from a Windows application, and a dialog box will pop-up asking you where the fax is to be sent.  With the API this can be automated by including options such as the fax number in the document being printed.  Zetafax will pick out the embedded addressing information and act upon it.

You can use embedded addressing to broadcast faxes from a database or using a word processor mail-merge.  Each recipients copy will be personalised. Embedded addressing is not yet supported in Windows NT.

Addressing options controlled by embedding or DDE

•	Name, organisation and fax number

•	Senders name and charge code

•	Coversheet and letterhead to use

•	Time to send and priority (urgent, normal or background)

•	Attachment files such as product literature or maps


EQUISYS Limited

You can contact Equisys Limited at:

EQUISYS LTD

45 Curlew Street

London

SE1 2ND

Tel: +44 171 403 2227

Fax: +44 171 378 6886

CompuServe: 100023,2100

email: sales@equisys.com - Sales enquiries

email: support@equisys.com - Technical Support


Fax class

The service class of the fax modem describes the specification that a PC uses to communicate with the fax modem.  The most common classes of fax modem are Class 1, Class 2 and Class 2.0.  These classes are specified as extensions to the Hayes command set.


Fax group

The group of a fax device describes the method it uses to communicate with other fax devices (eg. over the telephone PSTN).  The most common group is group III.


FAX.LOG

A record of all faxes sent is kept in the billing log - FAX.LOG.  This file is stored in the zfax\SERVER\Z-DB directory.

A line is added for every message addressee sent to by fax, giving details such as the Zetafax user name, addressee name and company, the phone number, the connection time and number of pages sent.

The billing log file may be converted into a suitable format for a spreadsheet or analysis program using the LOGCVT program.


FCLASS

FCLASS is the name of the Zetafax device driver that is used to control class 2/2.0 fax modems.  Hence FCLASS-1 is the default name of the first fax modem attached to the Zetafax server.

Note that the number after the device name does not relate to the fax service class of the modem.  For example, a Zetafax server that has been configured to use 4 fax modems would have drivers named (by default), FCLASS-1, FCLASS-2, FCLASS-3 and FCLASS-4.


File access permissions

User file access

The files used by Zetafax are split between four areas, depending on the type of access required by the workstations.  These are listed below, together with the type of access required by the workstations to all files and subdirectories in that area.

There are four "areas" within the Zetafax file structure comprising subdirectories and files.  The following table gives the access rights or permissions required for workstations.

Area name: 	Default directory (eg): 	Workstation access

Server	F:\ZFAX\SERVER	NONE

System	F:\ZFAX\SYSTEM	READ-ONLY

User	F:\ZFAX\USERS\username	FULL for owning user, NONE for other users

Request	F:\ZFAX\REQUEST	FULL

If you want to control the security of the system and the privacy of faxes between users you can restrict the file access rights which users have for the Zetafax directories.  Otherwise it may be simpler to give all users full access to the complete Zetafax file structure and ignore the remainder of this section.  Details for restricting file access rights on Novell NetWare networks are given separately below.

Stop the fax server if it is running and give all Zetafax users read-only access to F:\ZFAX\SYSTEM and full access rights to F:\ZFAX\REQUEST.  If your network supports user groups, it may be quickest to do this by creating a group called "ZFAX", making each Zetafax user a member of the group and giving these access rights to the new group.

If you are not concerned with privacy between users you should also give all Zetafax users full access rights to F:\ZFAX\USERS.  However if you wish to keep each user's fax area private you should give each user full access rights only to his or her private area within the Zetafax directory structure - for example, give Zetafax user JOHN full access rights to F:\ZFAX\USERS\JOHN.

Finally give the user account which the fax server will be logged on as full access rights to F:\ZFAX and all sub-directories.  Log back into the fax server PC, and run the Zetafax server.

For Novell NetWare:

stop the server and log on as Supervisor at one of the users' workstations.  Using SYSCON, create a group called "ZFAX".  Make each Zetafax user a member of this group.  Give members of the ZFAX group trustee directory assignments of [ R    F ] for F:\ZFAX\SYSTEM and [ RWCEMF ] for F:\ZFAX\REQUEST.

If you are not concerned with privacy between users you should also give all members of the ZFAX group [ RWCEMF ] trustee rights to F:\ZFAX\USERS.  However if you wish to keep each user's fax area private you should give each user [ RWCEMF ] access only to his or her private area within the Zetafax directory structure - for example, give Zetafax user JOHN the rights [ RWCEMF ] to F:\ZFAX\USERS\JOHN.

Finally give the Novell user who the fax server will be logged on as [ RWCEMF ] trustee rights to F:\ZFAX.  Log back into the fax server PC, and run the Zetafax server.


File formats

The following file formats are supported by Zetafax.

ASCII, DCX, EPS bitmaps, Epson FX and LQ series, GIF, JPEG, PCX, PICT, Targa, TIFF, Windows metafile bitmaps, WordPerfect metafile bitmaps

Any other format file may be sent as a fax by printing from the application that created it.


Group

The group of a fax device describes the method it uses to communicate with other fax devices (eg. over the telephone PSTN).  The most common group is group III.


hardware requirements for the fax server

Windows 3.1 or 3.11 fax server:  486 PC or faster, 6MB RAM, fax modem

Windows 95 fax server:  486 PC or faster, 12MB RAM, fax modem

Windows NT (Intel) 3.51 or 4.0 fax server:  486 PC or faster, 16MB RAM, fax modem or intelligent fax board

Windows NT 3.51 (RISC) fax server:  Alpha AXP or PowerPC computer, 32MB RAM, fax modem

Fax client:  Microsoft Windows 3.x, Windows 95, Windows NT (Intel or RISC) 3.51 or 4.0

A Windows NT or dedicated fax server is recommended for over 25 users or multiple fax lines.


hardware requirements for the workstation

Workstation: 386SX PC, 2 MB RAM, DOS 3.3 or above, Microsoft Windows 3.1 or above.


Intelligent fax boards

Zetafax 4.5 supports the Brooktrout intelligent fax cards including the TR114 and Trufax range under Windows NT  Gammalink support is also available under Windows NT.  The Brooktrout and Gammalink boards support DDI, reduce call times and transfer more of the call processing load from the fax server’s main processor to the fax board.


Internet

Equisys have an internet address.  Our web address is:  http://www.equisys.com

We can also be contacted via email on:

Sales:  sales@equisys.com

Support:  support@equisys.com


ISDN

Integrated Services Digital Network

Following is a brief description of the terms used when talking about ISDN:

B channel - a 64 kbps data channel which can be used for voice/fax/modem calls at the same call charges as a conventional analogue telephone line (or for data calls at a slightly higher cost)

D channel - a 16 kbps control channel used for setting up calls, DDI info, call cost info, etc.

BRI - Basic Rate Interface.  This is a twisted pair copper connection which uses the same wires as analogue lines.  It has 2 B channels and one D channel (2B+D).  BT's service is called ISDN-2.  In the UK both DDI and MSN are available over BRI.  In some countries MSN is not available, and DDI is only available over

PRI or multiple BRIs.

PRI - Primary Rate Interface.  This is a fibre connection.  Traditionally 30B+D, it is now also available from BT as 15B+D and  even 8B+D.  Note that the service is called ISDN-30 (even if only 15 or 8 channels are purchased).

Bundling - If greater capacity is needed, more B channels can be used at once (sometimes called bundling).  The ZyXEL ISDN fax modem can handle data calls at V.34 modem speeds, 64kbps (1 B channel) or 128kbps (both B channels).  Typically, video conferencing needs more than 64kbps, and uses multiple channels - hence video conference calls can be quite expensive.

Group 4 - 64kbps fax at 300dpi.  Its use is reasonably widespread use in Germany, but practically nowhere else.

Group III bis - faster (64kbps) Group III fax.

CAPI - A German (becoming defacto world-wide) API standard for interfacing PC software to ISDN cards.  It includes Group 4 fax.  The other common alternative is the Hayes command set.  The ZyXEL ISDN fax modem offers both.

Protocols - ISDN provides a raw channel for passing data, it does not specify what protocols you should use for passing information across it securely.  Common examples are digitised analogue data (voice/fax/modem), X.25 (packet switched data), V.14 (async chars to 57.6kbps), V.120 (more sophisticated, often with compression and bundling), V.110 (American, similar to V.120), Group 4 (fax).  I believe that the ZyXEL and SpartaDIS hardware can do all of the list except V.110 (SpartaDIS) and Group 4 (SpartaDIS and ZyXEL).  Above these sit network layer protocols such as IP or IPX (used by remote ISDN routers) and proprietary protocols used by remote bridges and programs such as file transfer packages (eg 4Sight).

If you would like more information on ISDN you should contact your local telephone provider.


Mapivim

Zetafax has the ability to use a MAPI mail address book and to send faxes as email attachments on MAPI mail systems (for example Microsoft Mail).  However should you have a VIM email system (for example cc:Mail) then you can also make use of these features.  To do this you should make sure that you have the MAPIVIM.DLL file installed on your system.

For more information take a look at section I, question 5.


Minimum hardware requirements for the fax server are:

Windows 3.1 or 3.11 fax server:  486 PC or faster, 6MB RAM, fax modem

Windows 95 fax server:  486 PC or faster, 12MB RAM, fax modem

Windows NT (Intel) 3.51 or 4.0 fax server:  486 PC or faster, 16MB RAM, fax modem or intelligent fax board

Windows NT 3.51 (RISC) fax server:  Alpha AXP or PowerPC computer, 32MB RAM, fax modem

Fax client:  Microsoft Windows 3.x, Windows 95, Windows NT (Intel or RISC) 3.51 or 4.0

A Windows NT or dedicated fax server is recommended for over 25 users or multiple fax lines.


Modem

MoDem stands for Modulator Demodulator.  A device that allows the sending of data and/or fax between computers over the telephone network.


Modem sharing

SAPS answers the long-standing problem of modem sharing.  It is a software solution which allows you to use modems connected to one computer from any computer on the network.

For more information on SAPS see sections Q.D.1 and Q.D.2.


Multi-port serial cards?

Zetafax supports DIGI’s PC/4e, PC/8e, Acceleport 4 port and Acceleport 8 port intelligent ISA bus cards.  These intelligent cards facilitate multiple line support on the Zetafax server by transferring more of the call processing load from the fax server’s main processor.


OCR

Optical character recognition (OCR) is used to convert a received fax image into a text file, suitable for reading into a word processor.  This requires the program to look at the dots in the received image, trying to recognise the individual letters and words.

Zetafax can be used both with its own OCR option, and also with other third party OCR products.  This section describes how to configure and use Zetafax with OCR.


RAS

Remote Access Service (RAS) is a combination of two components: a server running on Windows NT Server and a client running on MS-DOS, Windows for Workgroups, or Windows NT Workstation.

Workstations connected to the network via RAS appear as if they are directly attached to the network. They can participate fully in the network, sharing files and printers, accessing databases such as SQL Server, connecting to SNA hosts via SNA Server, and communicating with colleagues via e-mail.

The transparency of network access provided by RAS makes it a useful tool for telecommuters, system administrators, and mobile workers. RAS also greatly facilitates branch office automation.


Routing

Zetafax can use a number of methods for delivering received faxes automatically to their intended recipient.  These include giving each user their own fax number or specifying that all faxes from a given company should be sent to a particular user.


SAPS

SAPS answers the long-standing problem of modem sharing.  It is a software solution which allows you to use modems connected to one computer from any computer on the network.

For more information on SAPS see sections Q.D.1 and Q.D.2.


Sender ID routing

Each fax machine (or other fax system) has a “signature” which allows the recipient to recognise who sent the fax.  This is called the Station Identifier or CSID, and is usually set to the sending machine’s own fax number.  As an alternative, Calling Line Identification (CLI) is being introduced by most telephone companies to identify the phone number of the sender.  The CLI can be used if the CSID is not configured for a received fax.

Often only one person in your company deals with a particular sender, and so wants all faxes from that company to be routed directly to them.  Zetafax allows you to set up a list of sender IDs with the users faxes from those companies should be routed to.


SpartaCom

Developers of the SAPS modem sharing system.  See SAPS for more information.


Station ID suffix

If you are sending a fax to another Zetafax system, you can specify the recipient’s user name to cause the fax to be routed directly to that user.  This is done by adding the user name to the end of the destination fax number, separated by a colon (eg “012 345 9876:SAM”).  You can also set up other routing names for use with this mechanism such as extension numbers or descriptive names (for example “SALES”).

The user name or parameter is sent to the remote fax system by adding it to the end of the station identifier, or CSID.  This is the identifier programmed into all fax machines and printed on the top line of faxes they send, and is usually set to the sender’s fax number.  Sometimes called “colon routing”, this routing method is also supported for faxes sent to and from other PC fax systems.

ITU sub-addressing or T30 sub-addressing

The Group III fax specification has recently been extended to allow for sub-addressing in addition to the basic fax number.  At first only fax software will support this, but in the future expect to see fax machines with an extra button or two.  It works in the same way as Sender ID extension routing, as described above.


Sub-address routing

Sub-address routing is the most direct of the automatic routing methods available, allowing the sender to specify the intended recipient directly.  There are four different methods of doing this.


T.30 sub-addressing

T.30 sub-addressing is a new addition to the T.30 fax protocol, which is the ITU standard protocol for group III faxing. As yet, it is unsupported by many fax manufacturers and hence is used infrequently. Zetafax supports this standard in conjunction with Amber Logic modems. The sub-addressing allows extra “electronic” information to be passed down the telephone line as a suffix to the phone number. It works in a very similar way to the Zetafax addressing function of station ID suffix routing, inasmuch as you can be prompted to add an extension to the phone number as additional routing information.


TIFF

Zetafax uses a multi-page fax TIFF (Tagged Image File Format) format for fax images.  For more information on supported file formats look up ‘file formats’ in the glossary.


WWW address

Feel free to visit the Equisys web pages.  The address is:

http://www.equisys.com


Zetafax

Fax software for PC networks.


ZSUBMIT

The APIs ZSUBMIT program lets DOS, mini and mainframe programs send faxes by creating text files in a shared directory on a file server.  For example, faxing purchase orders or invoices usually only requires adjusting an accounts packages report writer.

A text file needs a few lines added to give the fax number and message options.  Logos and signatures can be included and the text may be merged onto a multi-page form using the letterhead feature in Zetafax.  This approach gives results rapidly.