Fax Server Solutions for 2005? 39
Glove d'OJ asks: "For a recent project at work, we are investigating enterprise-wide fax server solutions. Ideally, it would have a rich API for custom development, as well as all of the standard 'fax as a printer' and 'email out a fax' capabilities. Throughout all of my research, however, most of the decent reviewing sites all appear to have last reviewed this technology sometime last century, i.e., 1999 (or in 2000 for the purists.) I cannot find a single somewhat-recent review. Timeliness is definitely important in looking for the API. if the latest documentation refers to 'that new fangled C++' and was written in the pre-C# era, I could have some rough choices ahead. Is this an old technology that is no longer in vogue, or is there a single clear choice with no competition (thus not even requiring a recent review)?"
hylafax (Score:5, Informative)
http://www.hylafax.org/
Re:hylafax (Score:4, Interesting)
Re:hylafax (Score:1)
HylaFax is very nice but I have a Lucent Max I'd like to use its modems for Hylafax. Basically if you telnet to port 9000 you get an AT command session to one of the modems. I've been looking for a serial port emulator that when you open /dev/fakettyx it simply opens a telnet session to s.o.me.ip:9000 and relays data back and forth.
I've found plenty of things that do the opposite (telnet to them and they open a real serial port) but so far my quest has been unfulfilled.
Re:hylafax (Score:2)
Is it a work thing? If so someone like ifax.com might well write you a patch for some dorrah.
Re:hylafax (Score:2)
In my organization, we have hylafax receiving incoming faxes, dropping them to a high end laser printer (to get away from the horrible reliability of even high end fax devices), and droping it in PDF form to a read only smb share. That part is incase something bad happens to the paper copy, and for our document archival system.
For outgoing, we have a simple VB app for windows systems, that will take a scanned document, or any pdf, tiff, ps or text file, pro
Re:hylafax (Score:2)
For incoming faxes, we have 50 fax numbers mapped to 6 incoming DID lines, connected to some fancy fax device connect to a Hylafax server. That converts the incoming fax to an e-mail with an attached PDF, and drops it into a site e-mail box. Secretaries at each site check the box and either print it, delete it, or forward it on via
VSIfax (Score:5, Informative)
Re:VSIfax (Score:2)
After years of running fine on SCO UNIX, the same configuration and faxmodem was brought over to Linux (I give discounts for converting businesses from SCO to Linux...it's my way of giving something back to the world), and it proved extremely cantankerous. The servers would just stop working on a semi-daily basis. Nothing in the logs. They just stopped. Worse, they refuse
hylafax + some glue-code (Score:5, Informative)
Its been running for just over a month now, 3000 faxes in, 2000 faxes out, no issues.
RTFQ :hylafax + some glue-code (Score:1)
DAMN! Fed the troll again. Hey, where's the end of my finger?
Re:RTFQ :hylafax + some glue-code (Score:2)
RightFax (Score:5, Interesting)
The company that I recently joined is/has been using RightFax, and it seems like a quality product, I spoke with our local helpdesk and there are a very low occurance of problems with it.
A link to RightFax [captaris.com]
Re:RightFax (Score:1)
Capisuite (Score:2, Informative)
zetafax (Score:2, Informative)
Active Fax (Score:3, Informative)
Tried it once for a few users, they grew completely dependent on it, next everyone wanted it. There are so many ways to fax: email, drop folder, print to fax, and all faxes can be saved in an ODBC location. Has its own user administration, per-user cover pages and great scheduling features.
I'd do anything to have a linux version. They did apparently once have a solaris version, dont know where that went
Fax Server Solution: (Score:3, Interesting)
OK well you can sign a peice of paper then fax it, which becomes a contract, I don't think you can do this with email but thats' the only downside.
Re:Fax Server Solution: (Score:1)
Re:Fax Server Solution: (Score:1)
In Belgium, digital signing is legal and is already being used by many organisations (be it internal or external).
Re:Fax Server Solution: (Score:1)
Re:Fax Server Solution: (Score:2)
Saves time on printing (already signed), and saves money on faxes.
Just be sure to keep the image file secure.
another option (Score:2)
Lack of currency (Score:5, Insightful)
As far as recommending a fax product, there are numerous commercial ones available, some are even "New and Improved" but, since you asked on Slashdot, I'll recommend the open source choice, Hylafax, despite your C# requirement. It's open so you can develop on or against it to your heart's content. Something I doubt any of the commercial offerings will permit.
This brings us to your final requirement where the api's language must be modern. I'm not certain, but, I think that Hylafax is written in C so it definitely doesn't fit your C# requirements, despite the fact that the two languages are not mutually exclusive unless you make them so in your own head. But, requiring that a decades old solution be "up-to-date" in terms of the programming language seems a bit unreasonable to me. Must a fax application be rewritten in the latest fad language solely for the the sake of the language?
What I suspect you will wind up doing is some VB script that uses DCOM to print-to-fax from a Windows 2003 server.
Re:Lack of currency (Score:2)
Re:Lack of currency (Score:2)
Rightfax (Score:2)
Overall, a win for everyone. It was relatively inexpensive for our needs... and it faxes too!
http://www.captaris.com/rightfax/
just a hunch... (Score:1)
http://www.datadesigns.com/products/pro
RelayFax (Score:1)
Have a look at Relayfax [relayfax.com]. They have opensourced their engine on Sourceforge [sourceforge.net] although it is a Windows only C++ solution.
I just recently installed Relayfax at a clients site and it is working well.
--
Evolution - Still a theory just dont tell its religious zealouts, the Evolutionians.
Re:RelayFax (Score:2)
License: Other/Proprietary License
= 9J =
It's all about the HylaFax (Score:3, Informative)
It is an extremely capable fax server and there are a bunch of clients for it for Windows.
I run a HylaFax server at work, it's a 2Ghz 1GB machine with a 30 channel diva card. Our peak load so far is a little under 3000 faxes sent and slightly more than 3000 received per week, which was handled with only 8 of the phone lines active. The various conversions between postscript and tiff are pretty quick, so the system load stayed pretty low). The machine was also doing database, email, intranet and dns duties at the peak point.
We don't actually use any of the client software, so I can't speak directly on those in any depth, but I believe they are quite numerous and vary in quality/price; instead we have a samba printer which is actually a shell script that converts the postscript received from windows into a tiff and feeds it to hylafax, extracting the destination fax number from a specially formatted string in the document (this is fantastically useful for batch sending reports and you can hide the ugly special string by colouring the font white
At both the point of receiving a fax and that of sending a fax, control of all behaviour is handled with shell scripts and some awking. This means the server is pretty much infinitely flexible. You can get a service from the telecom provider (it may be included) that identifies the caller's number (if available) and the number they called (because you will probably have several aliased to the line). All of this information is available in the script, so you can get a bunch of cheap DID numbers on the line and give each dept or even each person a fax line, which will be identified by the script and any faxes sent to them will be emailed to them as pdfs, or printed to their printer, or (as we do) placed in a directory visible to a webserver and indexed in a database, so people can view their faxes online. That obviously required some external work, but it's a very simple sort of script to write, as are most of the things people want to do
HylaFax also has an outstanding mailing list, with several very active and very helpful people. If that fails, you can throw a couple of hundred bucks at ifax.com for some of their time to fix it for you.
You do get the odd persistant offender of a crappy old fax machine that it just won't talk to, but there is a lot of tweaking you can do if you want, to try and work around this. We have a single manual fax line and machine for the situations when things simply will not talk to our card/hylafax, but I think it's less than 0.1% of our customers and I have done zero tweaking to workround it so far.
Originally we used a machine with 8 analogue modems hanging off it and it still coped very well, but the modems were easily confused and hung a lot, which is what pushed us to spend the money on a PRI card, but it was well worth it because the DSP modems on it never hang (or "wedge" in hylafax terms) so it requires almost no intervention from me for extended periods, which is ultimately the reason I like it so much. When you finish setting it up right, it Just Works[tm]
Cheers,
Re:It's all about the HylaFax (Score:1)
Your best research tool is the vendors. Shoot off a mess of emails outlining what you want to do and you'll have a wastebasket full of options, for sorting through, by the end of the day.
Re:It's all about the HylaFax (Score:2)
Asking a bunch of people who know about it is far better than asking a bunch of companies who want to sell it to you
The qeustion is finding those people though. This guy chose to ask slashdot, so he might be screwed
SBS 2003 (Score:2, Interesting)
OS X (Score:1)
Get a G5.