Wow. That's one of the most bizarre solutions I've seen in a long time. :-\ Steve On 04/06/2011 01:58 PM, Pablo Hernan Saro wrote:
Hi Steve,
I'm not sure if the following will work. Let's say that you have a SIP trunk service configured in a FS box for interconnection with the PSTN. To avoid individual analog fax machines (reduce hardware costs and attached maintenance costs) and take advantage of fax server capabilities, a solution would be install HylaFAX with t38modem built with OPAL support (this enables routing modems to SIP URIs) sending/receiving calls to/from FS via SIP (configure your dialplan for enabling t38 at FS side). That way you get the best from HylaFAX (jub submission, scheduling, retrying, reporting and other facilities) and FS (dealing with SIP trunk service providers, cdr, call routing) at the same time. End users can interact with HylaFAX using compatible windows clients, email interface or web interface. A very good idea would be link HylaFAX accounts to FS directory (connect HylaFAX to FS db may be?). My two cents...
On Tue, Apr 5, 2011 at 4:20 PM, Kristian Kielhofner <kris@kriskinc.com <mailto:kris@kriskinc.com>> wrote:
Steve,
Very cool (and I'm very interested).
What about using the existing user directory (perhaps with additional params) for the accounts and the FreeSWITCH core DB (whether SQLite or ODBC) for the jobs, etc?
On Tue, Apr 5, 2011 at 12:27 PM, Steve Underwood <steveu@coppice.org <mailto:steveu@coppice.org>> wrote: > Hi, > > It has always been clear that a HylaFAX compatible FAX job submission > server would add considerably to the value of the FAX facilities in > Asterisk and Freeswitch, but somehow it hasn't happened until now. I > recently found that in 2005 someone produced something fairly basic for > Asterisk in Perl, but it doesn't seem to have been well publicised, and > it looks like development stalled long ago. > > I now have the skeleton of HylaFAX compatible FAX job submission server, > in C, working. It accepts FAX submissions from sendfax and a couple of > the windows HylaFAX clients, though it needs a lot more polishing. Now I > need to look at the best thing to do on the Freeswitch side. I aim to > make the server maintain its own database of FAX jobs. It will attach to > Freeswitch, by ESL; push the jobs through FS; deal with scheduling, > retries, etc; and report the final result to the user, just as HylaFAX > does. The thing I am rather unsure about is the best way to handle the > accounts used to accept FAX jobs? Should I maintain a separate database > of FAX accounts, or hook into an existing database? I would welcome > suggestions for what would be the most useful approach. > > Steve >