It turns out I was too optimistic. It works *sometimes*. It makes a successful FAX transmission only about 20% of the time. Usually it fails. A typical failure is in http://pastebin.freeswitch.org/20570 This is HylaFax running on the Freeswitch machine, using the SpanDSP modems. I'm calling a FAX number that's an analog PSTN line. Can anybody tell me what I'm doing wrong? -- Steve On Wed, Feb 6, 2013 at 5:58 PM, Steven Schoch < schoch+freeswitch.org@xwin32.com> wrote:
On Fri, Feb 1, 2013 at 4:53 AM, shouldbe q931 <shouldbeq931@gmail.com>wrote:
As a replacement for the faxback plugin.
how about using hylafax+ with t38modem ? http://hylafax.sourceforge.net/
or the commercial "fork" from iFax ? http://www.ifax.com/products/hylafax/fax-over-ip.html
I am happy to report that I have (partial) success! I used HylaFSP (commercial HylaFAX Windows client) to send a FAX to HylaFAX running on the FS machine, connecting to /dev/FS0.
The FAX wasn't received 100%, because it didn't go through the T.38 gateway, and the Caller-ID didn't get set, so that's what I'd like to fix next.
I already have this rule in the outgoing dialplan:
<condition field="${fax_call}" expression="^true$" break="never"> <action application="set" data="fax_enable_t38=true"/> <action application="set" data="execute_on_answer=t38_gateway peer"/> </condition>
I set the $fax_call variable (and the $outbound_caller_id_number variable) in the directory entry that's used by the ATA that the analog FAX machine uses.
What I want to do now is set the same variables on channels opened by the /dev/FS0 modem. Where should I put these variables?
-- Steve