[Home]

Summary:ASTERISK-16409: FAXOPT(modem)=V27,V29 does not have an effect on spandsp, fax still get received with V17
Reporter:Kristijan Vrban (vrban)Labels:
Date Opened:2010-07-22 14:39:34Date Closed:2012-01-23 13:14:42.000-0600
Priority:MinorRegression?No
Status:Closed/CompleteComponents:Resources/res_fax_spandsp
Versions:Frequency of
Occurrence
Related
Issues:
Environment:Attachments:( 0) spandsp-modems-1.8.diff
( 1) spandsp-modems-10.diff
Description:I set:
FAXOPT(modem)=V27,V29
FAXOPT(maxrate)=9600
FAXOPT(minrate)=2400
FAXOPT(ecm)=yes
ReceiveFAX("SIP/1xx.xx.xx.xx-00000001", "/tmp/fax-1279827012.1.tif")

But:
FAXBITRATE: 14400 and V.17 modem are used by spandsp

with res_fax_digium it is working
Comments:By: Paul Belanger (pabelanger) 2010-07-22 15:34:41

We require a complete debug log to help triage the issue.

This document will provide instructions on how to collect debugging logs from an Asterisk machine for the purpose of helping bug marshals troubleshoot an issue:

http://svn.digium.com/svn/asterisk/trunk/doc/HOWTO_collect_debug_information.txt

By: Tilghman Lesher (tilghman) 2010-07-22 23:45:23

Please read:

http://www.soft-switch.org/spandsp_faq/ar01s04.html

In short, Digium provides support for these fax standards which are still under patent and includes licensing for those standards.  Spandsp does not.

By: Leif Madsen (lmadsen) 2010-07-23 10:31:38

Reopened per kpfleming and the mailing list post referenced here: http://lists.digium.com/pipermail/asterisk-dev/2010-July/045283.html

By: Matthew Nicholson (mnicholson) 2011-12-14 12:34:09.521-0600

Hmm, it looks like we completely ignore the modems setting in res_fax_spandsp. I am looking into it.

By: Matthew Nicholson (mnicholson) 2011-12-14 15:49:40.947-0600

Test with one of the attached patches and let me know if they resolve the issue.

By: Matt Jordan (mjordan) 2012-01-23 13:14:20.551-0600

Kristijan - I've gone ahead and committed this, as the fix is fairly straightforward and it passed the internal tests.  If you have a problem with the patch, please feel free to have this issue reopened.