<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>: "Kevin P. Fleming" <kpfleming@digium.com><br />
<b>Sent</b>: Wednesday, January 26, 2011 5:21 PM<br />
<b>To</b>: asterisk-users@lists.digium.com<br />
<b>Subject</b>: Re: [asterisk-users] res_fax</span><br />
<br />
On 01/26/2011 04:16 PM, Bryant Zimmerman wrote:<br />
> ------------------------------------------------------------------------<br />
> *From*: "Kevin P. Fleming" <kpfleming@digium.com><br />
> *Sent*: Wednesday, January 26, 2011 4:52 PM<br />
> *To*: asterisk-users@lists.digium.com<br />
> *Subject*: Re: [asterisk-users] res_fax<br />
><br />
> On 01/26/2011 03:14 PM, Bryant Zimmerman wrote:<br />
><br />
>> Is there a way for me to force t.38 off for a call but to allow t.38 for<br />
>> other calls. What I am thinking is if a t.38 fails to flag the next call<br />
>> from that number to g711 audio. This would at least let me work arround<br />
>> the issue for now where t.38 fails with some endpoints but not others<br />
>> and the g711 audio will work. The issue I am seeing is it appears that<br />
>> with some endpoinds on Level 3 that the t.38 tunnel comes up fine but no<br />
>> fax data starts flowing but this only is happening with faxes coming<br />
>> from some Cisco gateways sending out via PRI using t.30<br />
><br />
> No, unfortunately there isn't a way to do that that I can see. It<br />
> wouldn't be terribly hard to add to res_fax.c, but I don't think we ever<br />
> thought of doing that before.<br />
> ------------------------------------------------------------------------<br />
> With out this I have no way to force the fall back then and the faxes<br />
> will always fail in this case because t38 successfully negotiates.. Do<br />
> you have any other ideas?<br />
> If I pick arround in the source what might it take to add another option<br />
> to the ReceiveFAX to only do g711 audio? Is this somthing that I could<br />
> get submitted back into the tree if I can figure it out?<br />
<br />
Most definitely; I can see cases like yours where someone would want to <br />
be able to forcibly disable T.38 for specific calls for troubleshooting <br />
purposes. In fact... if you give me about 15 minutes, I'll commit a <br />
patch to Asterisk trunk to add an option to do that, and you can <br />
backport it to the version you are using :-)<br />
<hr width="100%" size="2" align="center" />
Kevin<br />
<br />
That is grate. I dove into the code and tried to add it my self I added a F option but I have not figured out the right spot to force the exclusion to shut off the T38.<br />
<br />
Where will the patch be posted?<br />
<br />
Much thanks on this.<br />
<br />
Bryant<br /></span>