[asterisk-users] res_fax

Kevin P. Fleming kpfleming at digium.com
Wed Jan 26 16:54:52 CST 2011


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

http://svnview.digium.com/svn/asterisk?view=rev&rev=304342

-- 
Kevin P. Fleming
Digium, Inc. | Director of Software Technologies
445 Jan Davis Drive NW - Huntsville, AL 35806 - USA
skype: kpfleming | jabber: kfleming at digium.com
Check us out at www.digium.com & www.asterisk.org



More information about the asterisk-users mailing list