[Freeswitch-users] Hylafax server emulation

[Anthony Minessale]

This is a common cross-roads.  I think your choices are:

1) Try and be agnostic like we have done in FreeSWITCH or to just
choose a particular database and make it a dependency.  There is a
fair argument to either side.  I personally chose the agnostic
approach because I did not want to limit the possibilities of how
developers chose to integrate FreeSWITCH into their existing
infrastructure.  It allows you to use it standalone or connect to any
existing db with ODBC and create its own tables.

2) Use a specific DB.  You have a fairly specific application with a
fairly specific task so it would not be a bad decision to just choose
a db with a well-developed client API like postgres, sqlite etc.
There are some disadvantages to ODBC if the implementation of the
connector of choice is poorly done or has memory leaks or artificial
limitations.  Also you must then conform to ANSI sql with ODBC.
Native db API would give you any specific extension etc to that db.


I may have just re-iterated your question with more specific details
but maybe that can help you decide.  I guess it would be based on your
intentions and how flexible you want to make it at the cost of extra
abstraction.




On Tue, Apr 5, 2011 at 11:27 AM, Steve Underwood <steveu at 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
>
>
> _______________________________________________
> FreeSWITCH-users mailing list
> FreeSWITCH-users at lists.freeswitch.org
> http://lists.freeswitch.org/mailman/listinfo/freeswitch-users
> UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users
> http://www.freeswitch.org
>



-- 
Anthony Minessale II

FreeSWITCH http://www.freeswitch.org/
ClueCon http://www.cluecon.com/
Twitter: http://twitter.com/FreeSWITCH_wire

AIM: anthm
MSN:anthony_minessale at hotmail.com
GTALK/JABBER/PAYPAL:anthony.minessale at gmail.com
IRC: irc.freenode.net #freeswitch

FreeSWITCH Developer Conference
sip:888 at conference.freeswitch.org
googletalk:conf+888 at conference.freeswitch.org
pstn:+19193869900