Tired of getting up from your desk to fax a document? Have you ever wondered why your company’s call center maintains wall-sized desks of fax machines? Employees at many large organizations are asking the same questions. Fortunately, so is Biscom, Inc. While there are a few companies providing enterprise fax solutions, Biscom, in this author’s opinion, stands out as the market leader.
Biscom is a small company headquartered in Chelmsford Massachusetts. The company was founded in 1986 and soon became a market leader releasing quality and innovative products year-after-year. A quick peek at their impressive customer list reflects many big names such as Federal Express, Hewlett-Packard, and Nike. Equally impressive as the customer list is the product list.
Biscom offers many fax solutions including turn-key fax servers, custom APIs, desktop fax clients, email integration, and directory integration. At the heart of product list is FAXCOM Server and FAXCOM Suite for Windows. The combination of these two products can provide most organizations with true enterprise-class faxing.
FAXCOM Server & FAXCOM Suite for Windows
So enterprise faxing sounds appealing? Enter Biscom’s flagship products FAXCOM Server and FAXCOM Suite for Windows. FAXCOM Server is the center of the fax environment. This combination of software and hardware allows for the sending and receiving of faxes by integrating with the telephony network. The product can be purchased as turn-key or built on your company’s standard server hardware.
Complementing FAXCOM Server is FAXCOM Suite for Windows. FAXCOM Suite, which is comprised of many individual products, provides inbound and outbound fax routing for E-mail environments such as Exchange and SMTP. In addition, FAXCOM Suite can configure a web server (IIS) to act as a portal for faxing.
The components of a typical FAXCOM server
Server hardware – As mentioned above, FAXCOM Server can be purchased as a turn-key solution, or you can provide your own hardware. A typical customer provided solution would consist of an HP Proliant DL380 server along with minimal disk and memory requirements.
Fax board – Biscom has standardized on Brooktrout as the fax board manufacturer. The fax boards come in different flavors and port configurations.
Server operating system – FAXOM Server comes in both a Windows and Linux version.
Application software for translation – FAXCOM Server can translate many different file types for outbound faxing (more on this later).
Fax software – FAXCOM Server is the product name for the application that provides the faxing capabilities. At the time of this writing, FAXCOM Server is at version 5.05.0100.
FAXCOM Server Administrator
Functionality Overview
FAXCOM Server can be configured to provide different levels of functionality depending on the business requirements. The basic functions provided by FAXCOM Server are as follows:
* Routing of inbound faxes based on caller ID, TSID (Transmitting Station ID), fax port, or dialed digits.
* Delivery of inbound faxes to SMTP E-mail, Windows share (UNC), printer, FTP, or quarantine.
* Quarantining of inbound junk faxes.
* Least-cost routing (LCR) of faxes.
* Translation of outbound fax attachments into faxable format.
* Integration with email servers for outbound faxing using FAXCOM Suite for Windows.
Inbound Routing
FAXCOM Server provides many possibilities for inbound routing of faxes. In a typical configuration, the inbound fax is received by FAXCOM Server. Based on either the caller ID, TSID, fax port, or dialed digits, FAXCOM delivers the fax to the recipient. To illustrate, the flow of an inbound fax coming to 9085551212, using dialed digits as the routing method could be:
Sender transmits fax to 9085551212 > FAXCOM Server receives transmission > FAXCOM Server looks through its route list for a match to 9085551212 > FAXCOM Server delivers the fax to [email protected] as SMTP E-mail.
Note: you can choose to deliver inbound faxes using any of the methods mentioned in the prior section. These include SMTP E-mail, UNC, printer, FTP, or quarantine.
Junk Faxes
OK so we are all sick of that dinnertime call from some salesperson trying to sell you car insurance. Here in the U.S., consumers have a choice and can be put on a list preventing such calls. However, the same is not true of faxes. Have you ever come into the office to find a tray full of faxes offering to sell you the dream vacation or some incredible interest rate if you refinance your mortgage? Wouldn’t it be nice if you could prevent these somehow? FAXCOM Server provides this ability using FAXCOM Quarantine Doctor.
The way FAXCOM Quarantine Doctor works is fairly simple. Let’s say you keep getting those dream vacation junk faxes. While you would love to take your wife on a trip to Hawaii, you despise these sales tactics. You note that the fax has a TSID of Dream Vacations, Inc. In FAXCOM Server, you simply setup an inbound route that in plain English translates to “when a fax comes in from TSID Dream Vacations, Inc., quarantine the fax.” The FAXCOM Quarantine Doctor application can then be used to view the contents of the quarantine repository. You can then choose to delete or save the faxes.
Quarantine Doctor
The Quarantining process has a major limitation though. Similar to how spammers change the message to defeat anti-spam software, those sending junk faxes change the TSID. Since quarantining can only be based on TSID, Caller ID, fax port, or dialed digits, and doesn’t actually scan the content of the fax, its use is limited. The addition of a fax content scanning engine, similar to that of anti-spam filtering software, would be a welcomed improvement.
Least Cost Routing (LCR) & Attachment Translation
For those larger organizations, which might be looking to implement multiple fax servers in multiple locations, the use of LCR can reduce long distance costs. LCR is functionality provided by FAXCOM Server that allows for outbound faxes to be routed to an alternate fax server right over your own network. The alternate fax server then transmits the fax. This is useful in the situation where you have servers in different geographic areas. For example, you wouldn’t want your server in New Jersey to transmit a fax to a California number when the server in California could have done it. Simply stated, LCR saves you money! But LCR isn’t the only feature which deserves recognition, let’s look at Translation Server.
Think about what the traditional fax sender transmits. Typically, the content of a fax is a based on a printed document. The sender composes a fax in a word processing application, prints it out, and then walks it over to the fax machine and faxes it. This entire process is streamlined with FAXCOM Server’s child component, Translation Server. Translation Server allows for the outbound faxing of typical file types such as doc, ppt, xls, and pdf. Provided the associated application is installed on the fax server, Translation Server will translate the attachment converting it to a faxable format.
Outbound Faxing
Up until now, only an overview of outbound faxing was discussed. You are probably wondering how outbound faxing actually works. There are several offerings from Biscom that can manage outbound faxing. These range from custom APIs to E-mail integration. For purposes of this discussion, the focus will be on the functionality provided by FAXCOM Suite for Windows.
FAXCOM Suite for Windows is a combination of products marketed in a single package. FAXCOM Suite provides many methods for enabling outbound faxing. Faxes can be sent using a web portal, Microsoft Exchange connector, Win32 fax client, or SMTP Gateways. A brief overview of each can be found below:
Web portal – Using the FAXCOM Suite for Windows MMC console, you can automatically create and configure an IIS website which will serve as a web portal for sending outbound faxes.
Microsoft Exchange Connector – Using the MMC, a connector can automatically be installed in Exchange 2000 or 2003 enabling faxing right from the Microsoft Outlook client. The user simply formats the To: field of the message properly, and the Exchange connector automatically handles the fax message.
Outbound Fax Sent from Outlook with Attachment
Win32 Fax Client – If you are not looking to integrate with your mail environment, the Windows client is the way to go. Using the MMC, custom configured desktop setup packages can be created. Once installed on the client PC, a user can launch the fax client and send faxes directly from it.
SMTP Gateways – Lastly, FAXCOM Suite for Windows can configure a SMTP Gateway. This allows for faxing from any mail client provided the recipient address is formatted properly.
Cost
While the FAXCOM solution is easy to implement and feature rich, the functionality doesn’t come cheap. The Brooktrout fax board alone can run upwards of $20,000. Add to that the software and server hardware cost, and you could be looking at 40-50K for a typical 24 port solution. However, for most organizations, this is small change. The benefits of retiring traditional fax machines and replacing them with a server-based solution will far outweigh the initial cost.
Final Thoughts
The combination of FAXCOM Server and FAXCOM Suite for Windows can provide organizations with enterprise-wide faxing capabilities. The configuration can be used stand-alone, or can be tailored to the specific environment. Get past the cost, and the only difficult part about implementing FAXCOM will be saying goodbye to your traditional fax machines; but they do make great door stops!
About the Author
Keith Burgess is an information technology professional currently working for one of United States’ largest wireless carriers. In his spare time, Keith enjoys using and writing about computers and computer software.
If you would like to see your thoughts or experiences with technology published, please consider writing an article for OSNews.
I couldn’t help not reading page 2, 3 and 4 and I couldn’t stop thinking about Hylafax.
This is not the place to have this “article” !
Why couldn’t you help it but thinking about Hylafax? What if that article WAS about Hylafax? Would you think about the article the same way?
Just because a piece of software is commercial does not mean that it does not have a place here. OSNews is not about OSS software you know, it’s about /all/ software, commercial or not.
If you can’t deal with the fact that OSNews is a non-OSS-only site, I suggest you move to another site for your daily reading. I am not part of osnews anymore (I resigned last week, but I will be helping out for this week as David is on vacations), but the osnews goal remains the same, nothing has changed. So, either deal with it, or go elsewhere to troll.
May be if the Author mention not just one product, and review the features of several competing product to give us better view, it won’t feel as an advertisement.
Do the features also available at competing products?
What is unique in this product?
You have to admit Eugenia this article smacks of an advertorial. When magazines run obvious advertorials they often loose a lot of credibility. Same might happen here.
You can probably tell us, was this article paid for?
When I read the intro that was the first thing that entered my mind. Apologies if it is not, but it does have a lot of the elements.
>You can probably tell us, was this article paid for?
I don’t know if the author was paid by Biscom, we will never know that. OSNews simply accepts articles by its readers for publication. But I stay by my opinion, if this was an OSS project we wouldn’t be having this conversation right now, and this is unacceptable as OSNews does not promote software racism: all software is the same and they should have equal limelight in the press.
Why don’t you give the guy the benefit of the doubt? Maybe he really likes that product, maybe it IS a good product!
Please get on topic. If you want to really bring that article down do it in a way that makes sense: COMPARE this product to another and make this forum USEFUL for people who need to know what’s best for their daily work.
I didn’t get paid for the article. In fact, it was an article written out of my interest and respect for the product. I feel that commercial software has its place, and many osnews readers might be able to take advantage of the functionality within their own companies.
However, I certainly respect the opinions of the osnews readers and appreciate your feedback.
Well you wrote a nice article then.
FYI – the background info to the company probably makes your article seem like an advertorial. Most people don’t really care about who makes the software, well the boring kind of software anyway, except when they want to be assured that the company is in a solid financial situation and has the resources to support them and the product.
> FYI – the background info to the company probably makes your article seem like an advertorial.
Very good point! I appreciate the feedback. It certainly helps for future reviews/articles.
This is exactly the kind of text you would read in a product brochure. I agree that software should get its portion of the limelight regardless of the license but this is taking it way across the borders of responsible journalism. In fact it tramples straight over every principle a good journalist is supposed to abide by.
Now I don’t know the exact policy of OSNews so maybe this kind of article is perfectly acceptable here. However I would suggest a policy change if you intend to retain your current readership.
Journalistic principles are there for a sole reason: credibility of the medium. Post more of these obviously promotional articles without any regard for the mentioned product’s competitors (like Hylafax, which does much the same thing on *NIX platforms) and OSNews’ credibility as an objective source for tech news will sink faster than Titanic.
This is not meant as a troll but rather a constructive comment from someone who’s actually in the publication business.
> This is exactly the kind of text you would read in a product brochure.
I am appreciative of your comment!
My motivation for writing this article was to introduce Biscom’s product line to the community and to further develop my writing skills. I feel that I evaluated the product in a neutral fashion and also provided my criticisms of the product shortcomings. The article wasn’t intended to be a commercial, nor was it intended to be a comparison to similar products. I can’t apologize for it seeming advertisement-like. In reality, I was unable to find much to criticize.
Again, I appreciate the feedback from the readers.
Yes. Most of the stuff mentioned in the article can be done with HylaFax. I have here HylaFax working without problems.
I don’t see anything special (for me) in this Biscom solution. However… I have to admint, that I absolutly see a market and a reason for this Biscom Fax solution.
They even have a solution for IBM Domino! This shows me, that they have a well designed product.
I know that you can do most of the stuff mentioned in the article with HylaFax. But with HylaFax you don’t get that much confort out of the box as you get with this Biscom solution. I don’t know the Biscom product, but it seams to be okay. It took me alot of time to integrate HylaFax into Domino (writing many many lines of C code to integrate HylaFax as an DSAPI filter) and it looks like, that Biscom has that all already. Anyway… inboud and outbound faxing is just half of the game. The stuff around the faxing service is much more dificult to do then just plain faxing. A good enterprise solution must have easy interface for managing the fax service, support for many diffrend file formats (automatic sending of Excel, World, PowerPoint, etc.), support for diffrend policies, ….
I want to see that already offered by HylaFax! And all that out of the box. If you know a easy way of automaticly sending attachments, then let me know. Because than I can replace the solution I have now done on my Linux server (runing Wine on a frame buffer and using the varios Microsoft viewers to generate a Postscript document out of the doc, xls, ppt, …) with the more easy one.
cheers
reflex
Problem is, Hylafax only works on Unix. This is a Windows application. So, it’s like comparing apples and oranges. Administrators running on Win will need to see a comparison between two or more similar apps running on the same OS.
Regardless of the nature of the “article”, who uses fax any more? I get maybe two or three requests a year to “fax something to someone” or to get a “fax sent” to me from someone (usually from new clients). They get the hint after the first 4 or 5 minutes of continual laughing on my part. Fax is soooooooo last decade (no matter how much technology you bolt on to it). Way better ways to pass documents around (even documents with hand scribbling on it).
Faxing is still extremely common in the business world. I still send numerous faxes each week at work to order specific parts that my customers want. A lot of companies prefer to have their orders faxed because then they have a paper copy that can immediatly be handled and archived. I must say that it are mostly the higher-class brands and dealers that want faxes.
Assuming that faxing is dead is extremely shortsighted and plain stupid.
I want to see that already offered by HylaFax! And all that out of the box. If you know a easy way of automaticly sending attachments, then let me know. Because than I can replace the solution I have now done on my Linux server (runing Wine on a frame buffer and using the varios Microsoft viewers to generate a Postscript document out of the doc, xls, ppt, …) with the more easy one.
Wow, you’ve gone all out with the integration. 🙂 I’ve seen this done on linux servers much more cleanly by integrating it with a Samba printer share and web interface. What you want to do is set up a Samba printer share (generic postscript) that will accept postscript documents, convert them into PDFs or a standard PS, and then store them in a directory somewhere. Then, set up a web interface in which users can view the contents of the directory, select a file, enter a fax number, and release it to hylafax (if you store them as PDF files, they can proof the document before releasing it). You’ll need a little bit of programming on the web interface, but it’s easy enough to do with PHP.
Another, easier method is to install a PDF printer (CutePDF or equivalent) on each machine and have the users generate a PDF which they can attach to an e-mail to send to the hylafax machine (or drop in a folder with the correct name – however you have it currently set up). This is much easier than supporting various windows-only file formats on a linux box. (I would consider running them through OpenOffice somehow before fiddling with WINE).
Anyway, good luck.
Assuming that faxing is dead is extremely shortsighted and plain stupid.
I agree. While I personally detest using a fax machine (I refuse to most of the time) you are going to have a hard time doing business in certain markets without some type of fax solution. While new technologies are emerging that will hopefully make faxing obsolete, it is going to be so hard to kill because it usually works well and when something works well for a business, they aren’t going to change until it doesn’t work well any longer … the joys of business.
Biscom has a relase (not entreprise, although)that performs in linux enviroments.
I used AVT/captaris Rightfax from version 4 to 7.2, and it does integrate wery well with Lotus and Exchange.
it integrates also with Oracle financials and some CRM solutions, with minimum programing
Although it performed wery well on OS/2 systems, now it only runs under windows 2k, only.
You can also integrate it under a unified messaging system, using a voice mails servar called callxpress.
Fax is not dead: a lot of comercial and legal systems depends on it.
Problem is, Hylafax only works on Unix. This is a Windows application. So, it’s like comparing apples and oranges. Administrators running on Win will need to see a comparison between two or more similar apps running on the same OS.
There are many products for enterprise faxing working on Microsoft Windows. I could name a hand full of solutions in the same area as the described Biscom solution.
What I can tell from my experiance is, that from the function viewpoint most of them are the same (at least the one falling in the same category as the described Biscom solution). The difference is in the way how the management interface is an how scalable the solution is.
However… I see more solutions like TopCall ( http://www.topcall.com/ ) in the enterprise then solutions like Biscom.
I don’t have anything against such solutions as Biscom, but enterprise wiede faxing is another beast and has to offer more stuff then the Biscom solution. I personaly would see the Biscom solution on a small department level or on a small (<1000 employees) company.
Anyway… anyone juping up and down and jelling HylaFax, when they spot the word FAX, has no clue about enterprise faxing (this is my personal view and yes! I use HylaFax, but my company is small…)
I think we had a few of these at my last place of employment. I couldn’t tell you if they worked fine or not, we only supported the hardware and OS, the application was left to another department.
At my current place of employment we use a product from Interactive Intelligence, which includes phone and fax services. I never have to leave my desk to fax again
Wow, you’ve gone all out with the integration. 🙂 I’ve seen this done on linux servers much more cleanly by integrating it with a Samba printer share and web interface. What you want to do is set up a Samba printer share (generic postscript) that will accept postscript documents, convert them into PDFs or a standard PS, and then store them in a directory somewhere. Then, set up a web interface in which users can view the contents of the directory, select a file, enter a fax number, and release it to hylafax (if you store them as PDF files, they can proof the document before releasing it). You’ll need a little bit of programming on the web interface, but it’s easy enough to do with PHP.
You missed my point or maybe I did not described well my problem (english is not my native language).
The problem is, that users would like to send a fax from within their current mailsystem/mail client. They want to just send the message to <[email protected]> (as example) and then just write some small stuff into the body and attach serval *.doc, *.xls and other files directly to the mail and then send that mail to the fax server.
Most comercial fax servers do automaticly detach the attachments and convert them to the fax specific image format and then the fax server sends the attachments as images to the recipient.
This is a very common functionality found in many fax servers.
I know that I can capture the output of a Samba shared virtual printer and then convert that to Postscript or TIFF and send that stuff over HylaFax. But tell me please how do you handle that inside a mail client? And tell me how do you send (with the print to Samba share solution) a fax wich has 1 cover sheet, 5 xls documents and 1 pdf? And all this in one run?
Another, easier method is to install a PDF printer (CutePDF or equivalent) on each machine and have the users generate a PDF which they can attach to an e-mail to send to the hylafax machine (or drop in a folder with the correct name – however you have it currently set up). This is much easier than supporting various windows-only file formats on a linux box. (I would consider running them through OpenOffice somehow before fiddling with WINE).
If you are using HylaFax, then you can many of the HylaFax clients ( http://www.hylafax.org/links.html ) and avoid using CutePDF or anything like this and still fax any document you can print (most of the clients install as printer driver doing the conversation automaticly for you and sending the data to the HylaFax server in the proper format).
Anyway, good luck.
Thanks
We’ve been using Biscom Fax Servers for quite a number of years now. Yes, it a Windows product but now they have a Linux based version as well. We started out wa-a-a-ay back when Biscom faxservers were still running SunOS (located right next door to Biscom) with about 8 2-port, 4-wire analog lines (called E&M). You can easily see the unix roots in the file structure. My company was partially instrumental in getting them to support european PRAs (30-line ISDN trunks)
It a nice product and certainly a lot better than a couple of dozen fax machines mounted on racks (yes, we had those too. Major fun when they ran out of paper or toner and you only notice ofter a couple of dozen faxes arrived…)
They support quite a number of systems (anyone remember Banyan Vines?) and you can buy a SAP Connector based product from Aventix for faxing right from within SAP
Nice product. It does read a bit like an infomercial one has to admit..
Sorry, but I don’t see very much what this type of article is doing here either. Nothing to do with OSes, Internet (well, they did have a machine that allowed you to fax to an email-adress….) or Open Source. If OSNEWS is also the place to read about commercial SW in general well, there are a couple of hunderd thousand other similar articles bound for this space…. (yeah, I know, user submitted, not an open source site, go back to slashdot yada yada yada) This is just my view. Please don’t take offence.
It sure does seem like a one-sided sales pitch for Biscom. Over the years I’ve had to set up and implement a bunch of enterprise fax servers to test our software against for use by investment banks (talk about large clients…), and Biscom isn’t at the top of the list. Not even close.
Where’s the Captaris RightFax or Omtool Genifax formerly known as Omtool Fax Sr??? These were what I’ve seen as the industry leaders for non-OSS fax server market.
I remember all the crap us at NeXT got for our system pricing and that the built-in Faxing capabilities weren’t important.
If there is one thing Apple can do is make better solutions for such Corporate needs. Whether they ever will is one of the reasons I didn’t stick around to find out.
The reason why I object to this kind of article being posted here (and any other in the same way of writing), is that it is not concerned about what the consequences for the particular field of business are. This is purely a walk-through and a presentation of this software product, not an editorial analysis of what the release of this software or this software’s particular approach might bring with it – and thus, to my opinion, it is not of journalistic interest.
A product review with a “score” is, as far as I’m concerned, not journalism. However, I might have misunderstood the direction of this particular site – if that’s part of the editorial concept, that’s just fine with me.
The author is right that Faxing servers like this run to the $50,000 mark — even for small enterprises. It’s just the nature of centralized enterprise faxing (at least based on commercial products).
We’ve been using an ASP fax service that has reduced the faxing costs for our 250 attorney law firm to about $2,000 a month, and shares most of the features of a FAXCOM or RIGHTFAX (Bizcom’s competitor). When you add in the cost of supporting the FAXCOM product, include the cost of the phone calls themselves, the ASP model really starts to work.
It’s also intrisically nice to not have to deploy infrastructure resources and management time to a dying technology like faxing.
i first flew over few sentences in the article and thought: “paid ad”, then i went straight over to the comments, to read a debate on this subject.
after reading the comments, and then reading all pages of the article, i now have the following major point of view:
the whole faxing thing has nothing to do with an os, so it shouldn’t be here. like there are no articles about office suits or editors, aren’t they? osnews.com should stay os-centric.
okay, then here are some points, why i still consider this article an ad, whether someone got paid for it or not:
– it is about an unknown product from an unknown company and the purpose of this article was to advertise about it to the masses.
– it is not a comparison, but solely dedicated only to this commercial software product.
– it is about commercial product and this makes a huge difference for me. for me, f/oss is not the same and not even equal to commercial software. if it were about a f/oss fax server software, then i would not consider it an ad. but still consider it giga-off-topic, see above, my major pov.
you can call it “software racism”, but for me it is not. i just do not want to get news about commercial applications (= ads) here, where i was used to get info about operating systems, whether commercial or not.
if this is going to change – bad, as it is a good site. and sure, i will consider eugenias advice and go away, if this changes will come.
i am a little not up-to-date, eugenia: you wrote, that you are out of this site. ?!?. please, point me to informations about why it became so, who is ruling osnews now, which direction will the site take and so on, thank you in advice.
So what if a corporation managed to get a story in? On more than one occasion I have managed to post completely false stories. Maybe if your overall editorial standards went up this wouldn’t be a problem.
We use Omtools old FaxSr, and Genifax. Both work well.
I have to say, this read as an advert. Sorry, but there was little merit to it as a review. I’m not against reviews for commercial software here, but I think there should be more review and less evangelism.
I don’t know if the author was paid by Biscom, we will never know that.
This sounds funny, not that I’m saying it is not true (author said he didn’t get paid) but sounds funny.
OSNews simply accepts articles by its readers for publication. But I stay by my opinion, if this was an OSS project we wouldn’t be having this conversation right now, and this is unacceptable as OSNews does not promote software racism: all software is the same and they should have equal limelight in the press.
Hey Eugenia, you were the last person I was expecting
b…s..t from. This is not about the product being proprietary, but about if the article was a cheeky, cheap and poorly disguised advertisement attempt.
Adding the word racism to the mix doesn’t help you very much to defend your position.
Why don’t you give the guy the benefit of the doubt? Maybe he really likes that product, maybe it IS a good product!
Maybe because this site has got a good reputation about twisting headlines and histories so they do not look what they are to get more hits????
I reiterate that the product is an excellent product. With little to criticize, any walkthrough of a good product will sound advertisement-like. I am not certain what the future requirements will be for OSnews, but I encourage those who mention that this article was not appropriate to visit the submission guidelines. Until the guidelines change, I remain thankful to OSnews and the readers for allowing casual and professional authors to share their work.
http://www.osnews.com/story.php?news_id=168
No one is saying that the product is good or bad, what we complain about is that if it is not an AD it looks like, you should understand that.
As for the argument that articles about comercial products are not apropiate here that is not true, any article is welcomed as long as it is not a disguised lame-marketing attempt.
And ultimately the owners of the site decide what gets published and what does not.
I had to go through a recent evaluation of competing enterprise fax products to replace our old one (which actually worked pretty well, but was end-of-life’d). For us, most of the products were feature-rich and had many features in common. The devil was really in the details, particularly with regards to pricing/licensing. Fax server products can license by a combination of one or more methods: per user, per server, per location, # of fax channels, and even by the # of documents transmitted per month. And many of the advertised features end up being add-on options, greatly increasing the cost, and are usually related to integration and methods of delivery.
The article really makes little case on why Faxcom should be perceived as the market leader. Might I suggest http://www.ntfaxfaq.com/ as a starting point on the different products which are available.
We’re in the early stages of a central fax pilot in the local school district. But we’ve gone a slightly different route than the rest who have posted here. Instead of replacing fax machines and integrating faxing into the desktop OS, we’ve replaced fax machines with uber-photocopiers. Every school in the district has a Toshiba e650 photocopier. This beast has a harddrive inside and runs Linux, providing Samba printers / shares, IP printing, Apple printers / shares, and Novell print queues. It also allows for scan-to-email.
What we did is put HylaFAX onto a server at the board office, installed a BrookTrout fax board, and connected 7 DID lines (giving us 70 incoming phone numbers). Then we programmed all the Toshibas with templates to scan-to-email (internal faxing) and scan-to-fax (external faxing). The Toshibas are connected to our LDAP server allowing for people to send to any employee in the district via a quick e-mail search.
To send a fax, they just send a print job to the document manager on the Toshiba. They walk over to the Toshiba, open the scan-to-fax template, type in the phone number and their e-mail, and release the document. The Toshiba converts the documents to a TIFF, transmits it via e-mail to the HylaFAX server, and then it gets faxed out as a normal fax. A status message is sent back to the sender’s e-mail.
Incoming faxes are routed to the HylaFAX server, where it compares the incoming number to a list of locations, converts the fax to a PDF, and then e-mails it to a school e-mail account. The secretary at the school just has to check the school e-mail account periodically.
All we paid for was a continual license for HylaFAX, the BrookTrout board, and a server. Much less than $25,000. And we save $3000 / year / fax line that we replaced (~50 sites if everything continues to work out so nicely).
The only problem is that all outgoing faxes are now relative to the location of the board office, which means that our out-of-town sites must pay long-distance charges to send faxes across the street.
Well if you are looking for a good commercial Fax Solution go to http://www.unison.co.za