It is a stand-alone application which has three GUIs. The first is the configuration and troubleshooting GUI which allows access to most program variables and dependencies. User is able to configure the program, specify location of any/all used binaries, troubleshoot permission issues, run tests, etc. The second GUI is for receiving, viewing, sorting (to print or delete), and archiving/recalling faxes. It automatically scales the incoming FAXes and visually presents them as groups of pages (for each transmission). FAXes that are printed are (by default) archived. FAXes may also be exported in several formats. The third GUI performs the scanning tasks such as selecting templates (medical RXes use a special carboard template to assure ideal scanning), selecting and editing cover pages (and end-pages), scanning and manipulation of images, annotating received pages to fax back (Rx refill requests from pharmacies) and also signing a page and faxing back, managing the phone-book, assembling scanned pages into packages, and checking on status of jobs. The receiving GUI is beta, scanning and config GUIs are alpha.
The sending module adapts (but can also be tweaked by the user) to any scanner that SANE supports. It uses Tk::Imager module from CPAN for filtering as well as the existing Tk imaging routines and NetPBM for more mundane tasks.
The target audience is [business] offices that must accept all FAXes (i.e. can not use Caller-ID to block) yet want to be able to quickly sort the fluff from what to print. My clients are medical and dental offices. Known Caller-ID FAXes are routed to an Auto-print folder but all other faxes must be manually sorted by an employee.
It should work on any OS that supports Perl/Tk and can be even used to sort static archives of FAXes (G3 format is default but that can be easily modified). The tested platform is Linux with RH9 and Fedora Core 2.
It is currently being used in production in several offices and has processed over 30,000 FAXes combined. It is in semi-active development (meaning that new features are added when clients request them). The code is being commented and cleaned up each time a new feature is added.
Hylafax support (client) is almost working reliably. Mgetty works fine. efax needs to be tested.
Home Page