<div dir="ltr"><div style>My whole plan here is to replace the phone system currently in the office (a NexPath system, a really nice PC-chassis pbx system from the 1990's) to a more modern VoIP system, and git rid of all our POTS lines. But I need a simple solution for the users who send FAXes from their Windows systems.</div>
<div><br></div>On Tue, Jan 15, 2013 at 10:48 AM, Dave R. Kompel <span dir="ltr"><<a href="mailto:drk@drkngs.net" target="_blank">drk@drkngs.net</a>></span> wrote:<br><div class="gmail_extra"><div class="gmail_quote">
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><u></u>
<div>
<div>It seems that you may be debugging way too many things at once. Do you know much about the <a href="http://FAXBACK.COM" target="_blank">FAXBACK.COM</a> internals?</div></div></blockquote><div><br></div><div style>Yes, that's probably correct. No, I don't know much about <a href="http://faxback.com">faxback.com</a>.</div>
<div style><br></div><div style>However, I just tried a different one, <a href="http://www.t38faxvoip.com">www.t38faxvoip.com</a>. It's a much more involved Windows installation, but it came up with the same symptoms. This is leading me to believe that the problem is more likely my FS configuration.</div>
<div style><br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div>
<div>Just for a test you know you can bypass it. FreeSWITCH will work just fine on a windows box, using the FAXModem stuff, and com0com driver.</div></div></blockquote><div><br></div><div style>That's not my objective. I'm still early in the learning process for FreeSwitch, and I'd like to keep it to one installation, on an OS that I can understand (Linux).</div>
<div><br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div><div> That's what I use to have the M$ fax service talk to, and it works great. No hardware, and FS doing T38 right out of the Fax Service Server.</div>
</div></blockquote><div><br></div><div style>Let me see if I understand: MS Fax is talking through a virtual serial cable (com0com) to what it thinks is a FAX modem. On the other side of that virtual serial cable is something that takes the serial FAX data, translates it to T38, and injects it into FS. I'm a little unclear on the last 2 pieces, because it still sounds like a black box to me. What's "Fax Service Server"?</div>
<div style><br></div><div style><br></div><div style>On Mon, Jan 14, 2013 at 5:12 PM, Michael Collins <span dir="ltr"><<a href="mailto:msc@freeswitch.org" target="_blank">msc@freeswitch.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
Also, are you routing the call to the txfax app?</blockquote><div><br></div><div style>I'm not. I assumed that the purpose of txfax is to encode a TIFF file into a T.38 stream, and my source is already T.38. Am I missing something?</div>
<div style><br></div><div style>-- </div><div style>Steve</div></div></div></div></div>