<span style="font-family: Arial, Helvetica, sans-serif; font-size: 10pt"><br />
<span style="font-family: tahoma,arial,sans-serif; font-size: 10pt;"><hr width="100%" size="2" align="center" />
<b>From</b>: "Jeff LaCoursiere" <jeff@sunfone.com><br />
<b>Sent</b>: Tuesday, September 25, 2012 11:35 AM<br />
<b>To</b>: asterisk-users@lists.digium.com<br />
<b>Subject</b>: Re: [asterisk-users] T.38 gateway ATA</span><br />
<br />
<div class="moz-cite-prefix">On 09/25/2012 10:29 AM, Bryant Zimmerman wrote:<br />
</div>
<blockquote cite="mid:28500713$b75da0d$17d8e3ae$@zktech.com" type="cite"><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>: "Jeff LaCoursiere" <a href="mailto:jeff@sunfone.com" class="moz-txt-link-rfc2396E"><jeff@sunfone.com></a><br />
<b>Sent</b>: Tuesday, September 25, 2012 11:05 AM<br />
<b>To</b>: <a href="mailto:asterisk-users@lists.digium.com" class="moz-txt-link-abbreviated">asterisk-users@lists.digium.com</a><br />
<b>Subject</b>: Re: [asterisk-users] T.38 gateway ATA</span><br />
<br />
<div class="moz-cite-prefix">On 09/25/2012 09:26 AM, Bryant Zimmerman wrote:<br />
</div>
<blockquote cite="mid:4253f1b8$74548bd$1735d5aa$@zktech.com" type="cite"><span style="font-family: arial, helvetica,
sans-serif; font-size: 10pt;">Jeff<br />
<br />
Can you please clarify your layout? If you have an asterisk 1.8 (I would use 10 for this if possible) server why can't you just take the gateway call on that via a sip trunk. If you are coming in from and land line and want to do t.38 to the asterisk 1.8 server you would need a FXO t.38 gateway. Based on your description I am not sure what your sources are and what your final desired destination is. Please be specific with your response. We do t.38 all the time and have great success with it but the success is in the setup and control of the endpoints (gateways and ATAs)<br />
<br />
<div>Thanks<br />
<br />
Bryant Zimmerman (ZK Tech Inc.)<br />
616-855-1030 Ext. 2003</div>
<br />
<br />
<span style="font-family: tahoma,arial,sans-serif; font-size: 10pt;"><hr width="100%" size="2" align="center" />
<b>From</b>: "Jeff LaCoursiere" <a href="mailto:jeff@sunfone.com" class="moz-txt-link-rfc2396E" moz-do-not-send="true"><jeff@sunfone.com></a><br />
<b>Sent</b>: Monday, September 24, 2012 9:20 PM<br />
<b>To</b>: "Asterisk Users Mailing List - Non-Commercial Discussion" <a href="mailto:asterisk-users@lists.digium.com" class="moz-txt-link-rfc2396E" moz-do-not-send="true"><asterisk-users@lists.digium.com></a><br />
<b>Subject</b>: [asterisk-users] T.38 gateway ATA</span><br />
<br />
<br />
Hoping for some clarification. I would like to setup a NORMAL (not <br />
T.38) fax machine on an ATA, and have the ATA be a T.38 gateway to a <br />
remote asterisk (1.8) server, which is doing T.38 relay (passthru) to a <br />
provider.<br />
<br />
Some amount of googling today seems to imply that most ATAs are just <br />
T.38 passthru devices, and expect a T.38 capable fax machine, otherwise <br />
just fallback to ulaw (and mostly fail, in my experience so far).<br />
<br />
So does anyone use an ATA that actually does the gateway transcoding to <br />
a normal fax machine? Or am I barking up the wrong tree?<br />
<br />
Thanks!<br />
<br />
j<br />
<br />
--<br />
_____________________________________________________________________<br />
-- Bandwidth and Colocation Provided by <a href="http://www.api-digital.com" class="moz-txt-link-freetext" moz-do-not-send="true">http://www.api-digital.com</a> --<br />
New to Asterisk? Join us for a live introductory webinar every Thurs:<br />
<a href="http://www.asterisk.org/hello" class="moz-txt-link-freetext" moz-do-not-send="true">http://www.asterisk.org/hello</a><br />
<br />
asterisk-users mailing list<br />
To UNSUBSCRIBE or update options visit:<br />
<a href="http://lists.digium.com/mailman/listinfo/asterisk-users" class="moz-txt-link-freetext" moz-do-not-send="true">http://lists.digium.com/mailman/listinfo/asterisk-users</a><br />
<br />
</span><br />
<fieldset class="mimeAttachmentHeader"></fieldset> <br />
<pre>--
_____________________________________________________________________
-- Bandwidth and Colocation Provided by <a href="http://www.api-digital.com" class="moz-txt-link-freetext" moz-do-not-send="true">http://www.api-digital.com</a> --
New to Asterisk? Join us for a live introductory webinar every Thurs:
<a href="http://www.asterisk.org/hello" class="moz-txt-link-freetext" moz-do-not-send="true">http://www.asterisk.org/hello</a>
asterisk-users mailing list
To UNSUBSCRIBE or update options visit:
<a href="http://lists.digium.com/mailman/listinfo/asterisk-users" class="moz-txt-link-freetext" moz-do-not-send="true">http://lists.digium.com/mailman/listinfo/asterisk-users</a></pre>
</blockquote><br />
Hi Bryan,<br />
<br />
To follow an inbound fax call, our intended setup would be:<br />
<br />
Our upstream sends a T.38 call to our border asterisk (1.8) server, which creates another T.38 call to the customer's hosted asterisk (1.8) instance, which creates another T.38 call to the ATA, which is over the Internet to their location. The ATA would do the transcoding (is that even the appropriate term in this case?) to T.30, to the FXS connected normal fax machine.<br />
<br />
Its that last bit that I am having trouble confirming is a feature of any mainstream ATA. When I dug into it yesterday it seems that the mainstream ATAs will passthru T.38, expecting the connected fax machine to work with T.38 natively. I can't depend on that. The asterisk servers are all remote, and though I could presumably do the gateway on the asterisk server I would then have a ulaw fax call over the internet to the ATA, which in my experience has not been very reliable.<br />
<br />
Of course I will need outbound faxing to follow the reverse path, letting the ATA turn the T.30 outbound fax call into T.38, which travels through our various asterisk servers to the upstream provider...<br />
<br />
So in a nutshell, is there anyone using an ATA as the *gateway* rather than passthru? I feel I am still not being clear... does that help?<br />
<br />
Thanks,<br />
<br />
j<br />
<br />
Jeff<br />
<br />
In your call stream you must make sure that all asterisk systems have the proper configurations for T.38 and that spandsp is loaded on the systems. Each peer entry must have the correct setup and the correct rtp port ranges must be set on all asterisk servers. Each server must have the correct configurations for their firewalls as well. I would flatten this to start. If possible connect the ATA's directly as a registration to your proxy. You will likely have better results. We have had the best luck with ATA's from audio codes and grandstream currently the HT-701, 702 have been working well. You must get the mix right and them keep it flat. Every time you allow user to drop an asterisk box between you and the ata you will give yourself a greater issues as they must become an asterisk t.38 expert to get the deployment to work or you must take it on. Hope this helps. T.38 works well when you get the right mix and control it. <br />
<br />
Bryant</span> <br />
</blockquote><br />
Hmm, I would think I would need spandsp only if the asterisk server(s) would be gateways... is that not the case? If all I want the asterisk servers to do is passthru T.38, I assumed nothing was needed other than asterisk. Our asterisk servers are all SIP - we have no TDM connectivity.<br />
<br />
Still interested to know if your ATAs are being used as T.38 gateways? It sounds to me like you are just using ulaw calls to your ATAs. True?<br />
<br />
Thanks,<br />
<br />
j<br />
<br />
Jeff<br />
<br />
We actually do T.38 to the ATA we do allow fall back to T.30 but we push the T.38. As for spandsp you are correct it is only required if you are running the gateway functions. We have just become so use to customers running the gateway functions it is compiled and loaded as part of every install that may handle faxing in some case. In any case the closer you can get the ATA to the origination points the better off you are. Any delays in the T.38 invites can cause issues. This also opens up for flatter routes should you need to fall back to T.30 as well. 95% of our faxes flow T.38 and 5% fall back to T.30 when compatability is an issue.<br />
<br />
Bryant</span>