<span style="font-family: Arial, Helvetica, sans-serif; font-size: 10pt"><span style="font-family: tahoma,arial,sans-serif; font-size: 10pt;"> <hr width="100%" size="2" align="center" />
<b>From</b>: "Warren Selby" <wcselby@selbytech.com><br />
<b>Sent</b>: Monday, June 20, 2011 3:00 PM<br />
<b>To</b>: "Asterisk Users Mailing List - Non-Commercial Discussion" <asterisk-users@lists.digium.com><br />
<b>Subject</b>: Re: [asterisk-users] Problem with ReceiveFAX app from FFA</span><br />
<br />
<div class="gmail_quote">On Mon, Jun 20, 2011 at 7:44 AM, Larry Moore <span dir="ltr"><<a href="mailto:lmoore@starwon.com.au">lmoore@starwon.com.au</a>></span> wrote:<br />
<div><snip> <br />
</div>
<blockquote class="gmail_quote" style="border-left: rgb(204,204,204) 1px solid; margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">I personally have considered this behaviour to possibly be a bug.<br />
</blockquote></div>
<br />
Once a fax is sent, the sending fax machine typically hangs up the call - sending the call to the "h" extension. It's the same as if you are on an actual call that was connected using the Dial() application, and the other end hangs up - the next step is the 'h' extension, not to continue in the current dialplan. I don't see how this is a bug, unless you think the entire call-flow paradigm that currently exists in asterisk is a bug.<br />
<br />
Now, if you're not getting certain variables to pass into the 'h' extension, that you feel should indeed be passed into the 'h' extension, that may be considered a bug...but you would need to show us CLI output and existing dialplan for followup.<br />
<br clear="all" />
<br />
-- <br />
Thanks,<br />
--Warren Selby, dCAP<br />
<a href="http://www.selbytech.com" target="_blank">http://www.SelbyTech.com</a><br />
<hr width="100%" size="2" align="center" />
<p><span style="font-family: tahoma; color: #333333; font-size: 10pt;">Waren<br />
<br />
I concur we use the "h" extension to log inbound faxes to a database and then we process them outside the asterisk platform. Our biggest issue with ReceiveFAX is about a 20% t.38 negotiation fail ratio. We then force fall back to t.30 for the next call from that number. We would like to see better success with t.38. Today our primary server has had 910 faxes of which 707 negotiated t.38, 44 have failed darn robo dialers, The rest failed the first attempt and came in T.30 on the second call.<br />
<br />
Thanks<br />
Bryant</span></p></span>