<div dir="ltr"><br><br><div class="gmail_quote">On Fri, Jul 22, 2011 at 12:39 AM, Kevin P. Fleming <span dir="ltr"><<a href="mailto:kpfleming@digium.com">kpfleming@digium.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div class="im">On 07/21/2011 04:34 PM, Joaquin Sosa wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
On Mon, Jul 18, 2011 at 07:58, Steve Davies<<a href="mailto:davies147@gmail.com" target="_blank">davies147@gmail.com</a>> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
The magic sauce that you need is "T.38" - Asterisk 1.6 supports this<br>
to a limited degree, and your ITSP will need to support it.<br>
<br>
The sip.conf.sample file and the voip-info wiki has all the<br>
information you need to try it out.<br>
<br>
</blockquote>
<br>
Correct. However it would be helpful to note T.38 support in Asterisk<br>
is broken. Take a T.38 ITSP, T.38 enabled Asterisk and T.38 ATA and<br>
try to send a fax. It won't work!<br>
</blockquote>
<br></div>
We do this in our testing all the time, and it works fine. Since you didn't specify any particular version of Asterisk, there's no way to associate your "It won't work" statement with anything in particular. Given the variations of T.38 implementations that exist in ATAs, carrier networks and other places, *any* T.38 connection that involves implementations from more than one vendor is (unfortunately) likely to have problems, whether any version of Asterisk is involved or not<br>
</blockquote><div><br><br>well I tried a linksys spa 8000 and 2102 thru <br>asterisk 1.8.3<br>1.8.4<br>1.6.2.16-19<br>sonus switch at itsp (012 israel) <br><br>and no luck<br></div></div></div>