On 05/08/2014 09:57 AM, Brian West wrote:
Was t.38 involved?
Could be - I've been having a few errors after changing the way I receive faxes.. After humbly rereading my subject - I see I wasn't as clear as I should be: - the "after FAX" meant that there is a fax detect line in the extension - before the bind_meta_app lines. Here is the faxrx extention: <extension name="faxrx"> <condition field="destination_number" expression="^33$"> <!-- The following sort of works--> <action application="set" data="file=/home/freeswitch/fax/${strftime(%Y-%m-%d_%H-%M-%S)}.tif"/> <action application="playback" data="silence_stream://2000"/> <action application="set" data="fax_enable_t38_request=false"/> <action application="set" data="fax_enable_t38=false"/> <action application="rxfax" data="${file}"/> <action application="system" data='echo "See attached FAX" | mutt -a ${file} -s "FAX" -- freeswitch@domain.tld' /> <action application="hangup" /> <action application="set_zombie_exec"/> </condition> </extension>
On May 6, 2014, at 6:15 PM, Karl Schmidt <karl@xtronics.com <mailto:karl@xtronics.com>> wrote:
This used to work - only changed a few things to get fax detect to work reliably. Could it be that the two interact?
If there isn't something obvious in the extension below:
What steps to debug? Do I need SIP logging?
<snip> -- -------------------------------------------------------------------------------- Karl Schmidt EMail Karl@xtronics.com Transtronics, Inc. WEB http://xtronics.com 3209 West 9th Street Ph (785) 841-3089 Lawrence, KS 66049 FAX (785) 841-0434 History may not repeat itself, but it does rhyme a lot. -Mark Twain --------------------------------------------------------------------------------