<div>I don't proclaim myself the best telephony engineer in the world, so I'm free to go wrong and open to learn. You can consider my contribution the most bizarre solution you've seen in a long time, we're all free to think and speak whatever we want (this is beyond discussion). IMHO, it is a simple way to integrate HylaFAX and FS without programming a line of code. SIP and t38 is out there to be used, in fact AFAIK all SIP trunk service providers offer fax support this way. Why you believe it's the most bizarre solution? </div>
<div><br></div><div>PS: I do not want to challenge you, just want to feed my knowledge.</div><div><br></div><div>Pablo</div><br><div class="gmail_quote">On Wed, Apr 6, 2011 at 9:27 AM, Steve Underwood <span dir="ltr"><<a href="mailto:steveu@coppice.org" target="_blank">steveu@coppice.org</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Wow. That's one of the most bizarre solutions I've seen in a long time. :-\<br>
<font color="#888888"><br>
Steve<br>
</font><div><br>
On 04/06/2011 01:58 PM, Pablo Hernan Saro wrote:<br>
> Hi Steve,<br>
><br>
> I'm not sure if the following will work. Let's say that you have a SIP<br>
> trunk service configured in a FS box for interconnection with the<br>
> PSTN. To avoid individual analog fax machines (reduce hardware costs<br>
> and attached maintenance costs) and take advantage of fax server<br>
> capabilities, a solution would be install HylaFAX with t38modem built<br>
> with OPAL support (this enables routing modems to SIP URIs)<br>
> sending/receiving calls to/from FS via SIP (configure your dialplan<br>
> for enabling t38 at FS side). That way you get the best from HylaFAX<br>
> (jub submission, scheduling, retrying, reporting and other facilities)<br>
> and FS (dealing with SIP trunk service providers, cdr, call routing)<br>
> at the same time.<br>
> End users can interact with HylaFAX using compatible windows clients,<br>
> email interface or web interface. A very good idea would be link<br>
> HylaFAX accounts to FS directory (connect HylaFAX to FS db may be?).<br>
> My two cents...<br>
><br>
><br>
> On Tue, Apr 5, 2011 at 4:20 PM, Kristian Kielhofner <<a href="mailto:kris@kriskinc.com" target="_blank">kris@kriskinc.com</a><br>
</div><div>> <mailto:<a href="mailto:kris@kriskinc.com" target="_blank">kris@kriskinc.com</a>>> wrote:<br>
><br>
> Steve,<br>
><br>
> Very cool (and I'm very interested).<br>
><br>
> What about using the existing user directory (perhaps with<br>
> additional params) for the accounts and the FreeSWITCH core DB<br>
> (whether SQLite or ODBC) for the jobs, etc?<br>
><br>
> On Tue, Apr 5, 2011 at 12:27 PM, Steve Underwood<br>
</div><div><div></div><div>> <<a href="mailto:steveu@coppice.org" target="_blank">steveu@coppice.org</a> <mailto:<a href="mailto:steveu@coppice.org" target="_blank">steveu@coppice.org</a>>> wrote:<br>
> > Hi,<br>
> ><br>
> > It has always been clear that a HylaFAX compatible FAX job<br>
> submission<br>
> > server would add considerably to the value of the FAX facilities in<br>
> > Asterisk and Freeswitch, but somehow it hasn't happened until now. I<br>
> > recently found that in 2005 someone produced something fairly<br>
> basic for<br>
> > Asterisk in Perl, but it doesn't seem to have been well<br>
> publicised, and<br>
> > it looks like development stalled long ago.<br>
> ><br>
> > I now have the skeleton of HylaFAX compatible FAX job submission<br>
> server,<br>
> > in C, working. It accepts FAX submissions from sendfax and a<br>
> couple of<br>
> > the windows HylaFAX clients, though it needs a lot more<br>
> polishing. Now I<br>
> > need to look at the best thing to do on the Freeswitch side. I<br>
> aim to<br>
> > make the server maintain its own database of FAX jobs. It will<br>
> attach to<br>
> > Freeswitch, by ESL; push the jobs through FS; deal with scheduling,<br>
> > retries, etc; and report the final result to the user, just as<br>
> HylaFAX<br>
> > does. The thing I am rather unsure about is the best way to<br>
> handle the<br>
> > accounts used to accept FAX jobs? Should I maintain a separate<br>
> database<br>
> > of FAX accounts, or hook into an existing database? I would welcome<br>
> > suggestions for what would be the most useful approach.<br>
> ><br>
> > Steve<br>
> ><br>
><br>
<br>
<br>
_______________________________________________<br>
FreeSWITCH-users mailing list<br>
<a href="mailto:FreeSWITCH-users@lists.freeswitch.org" target="_blank">FreeSWITCH-users@lists.freeswitch.org</a><br>
<a href="http://lists.freeswitch.org/mailman/listinfo/freeswitch-users" target="_blank">http://lists.freeswitch.org/mailman/listinfo/freeswitch-users</a><br>
UNSUBSCRIBE:<a href="http://lists.freeswitch.org/mailman/options/freeswitch-users" target="_blank">http://lists.freeswitch.org/mailman/options/freeswitch-users</a><br>
<a href="http://www.freeswitch.org" target="_blank">http://www.freeswitch.org</a><br>
</div></div></blockquote></div><br>