Return-Path: <MIKE@larse.com>
Return-Receipt-To: MIKE@larse.com
Newsgroups: bit.listserv.novell
Date:         Tue, 15 Dec 1992 22:48:00 LCL
Reply-To:     Novell LAN Interest Group <NOVELL@SUVM.BITNET>
From:         "Tisdell, Mike" <MIKE@LARSE.COM>
Subject:      Re: Help Me Purchase a Fax Serv

We use alcoms Fax email gateway with some custom software to support
faxing
PostScript documents. We have been using this for over 18 months w/o any
major problems.

>I need to purchase fax hardware and software for a 20+ user Netware
network
>running Netware ver. 2.15 (which will probably be upgraded to 3.X).

>Our requirements:

>Must work with Windows 3.X (we have 3.0, but will be upgrading to 3.1).
>Must allow each workstation user to have her own directory.

 Alcom's solution uses any MHS email package, if your email package works
with windows then you will not have a problem.

>Must be easy to use for _out-bound_ faxes.
Just use email, documents can be included as MHS attachments. Supports
.PCX, .DCX, .TXT, .TIFF, and with our enhancment .PS files.

>Must be affordable for 20+ users.
What is affordable?
The complete PC OEM's alcom's email gateway for less than $800.00. We
tried
it and it was pretty good, but had a couple of bugs, The Complete PC's
support was about the worst we had ever recieved (until SCO), so we
returned
the product. They have had 18 months work out the bugs so maybe it is
fixed
now, but I am sure support is still a problem. We ended up buying the
alcom
product it was worth the money for the support (to us).


>Must handle Windows documents and graphics, e.g., Word documents, Excel
>spreadsheets, and normal ASCII text files.

This is why we added Postscript support.

Our wishlist:

>Can output to HP LaserJet.
  No problem

>Can direct incoming faxes to users.
  There are only 2 methods for this and alcom supports them both, but
niether were able to solve our needs so we do not use inbound routing.
Instead we direct all incoming faxes into a admin mail box they are then
fowarded by a secritary to the proper recipients.
The methods for inbound routing are:
     1) use of a DID phone line (1 line, many phone numbers) each user
        is assigned a different phone number for faxes, and the Fax board

        able to route the fax based on the phone number called.
        Drawbacks: Many fax phone numbers, and expensive phone bills.

     2) use of an ID. each user is assigned a fax ID that must be dialed
       by the person sending the fax, the fax is routed based on this ID.
       Drawbacks: Not every FAX machine is capible of sending this ID,
and
       even if they were try convincing your vendors and suppliers to use
       these ID's

>Can use our print server PC, i.e., does not need its own PC to be a
server.
This I think is a dream, I have not seen any good solution that does not
require a dedicated server.

Info on Postscript conversions:
            Software to add to server:
                    Freedom of Press - does Postscipt > PCX conversion
                    Custom - does PCX > DCX conversion
                    Custom - manages the FAX queue to automate conversion
                             (unatented)
I can provide the custom programs and batch files, but not technical
support.


                             Mike Tisdell    email: mike@larse.com
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU