[asterisk-users] Need fax solution for 1.4.xx (Resolution)

William Stillwell (Lists) william.stillwell-lists at ablebody.net
Fri May 14 16:14:16 CDT 2010


Steve, Thanks for the heads up, after extensive testing today, I have
decided to edit t30.c to mark as debug, as I recorded a call between two
analog fax machines using mixmonitor, and noticed the same waveform
patterns, as a call into spandsp/receivefax.

I must admit, I am way happier with spandsp/receivefax/asterisk 1.6.2.7 then
asterisk 1.4.x w/pikafax.

Keep up the good work :)


William Stillwell




-----Original Message-----
From: asterisk-users-bounces at lists.digium.com
[mailto:asterisk-users-bounces at lists.digium.com] On Behalf Of Steve
Underwood
Sent: Friday, May 14, 2010 12:33 PM
To: Asterisk Users Mailing List - Non-Commercial Discussion
Subject: Re: [asterisk-users] Need fax solution for 1.4.xx (Resolution)

On 05/13/2010 10:48 PM, William Stillwell (Lists) wrote:
> Ok, I ended up upgrading 2 of my 5 boxes to 1.6.2.7 , and using spandsp
> 0.0.6pre17, dahdi-linux-complete-2.3.0+2.3.0 , and enabled app_fax.
>
> Hint: you need to install spandsp then run ./configure then make
menuselect
> :)
>
>
> I was able to send over a 50 page fax from coast to coast with 0 issues
>
> However, did get this message in CLI:
>
> [May 13 07:27:31] WARNING[14700] app_fax.c: WARNING T.30 ECM carrier not
> found
> [May 13 07:27:31] WARNING[14700] app_fax.c: WARNING T.30 ECM carrier not
> found
> [May 13 07:28:14] WARNING[14700] app_fax.c: WARNING T.30 ECM carrier not
> found
> [May 13 07:28:14] WARNING[14700] app_fax.c: WARNING T.30 ECM carrier not
> found
> [May 13 07:28:27] WARNING[14700] app_fax.c: WARNING T.30 ECM carrier not
> found
> [May 13 07:28:27] WARNING[14700] app_fax.c: WARNING T.30 ECM carrier not
> found
> [May 13 07:28:39] WARNING[14700] app_fax.c: WARNING T.30 ECM carrier not
> found
> [May 13 07:28:39] WARNING[14700] app_fax.c: WARNING T.30 ECM carrier not
> found
>
> However, there was no noticeable errors in the fax., googling, the error
> didn't seem to make much since.
>
> This was via copper pair, over traditional LD carrier, into PRI
terminating
> into a Sangoma card.
>
> Intel Xeon x3460, 8 gb ram, 320gb raid 0 sata
>
>
> Thanks to all who offered suggestions, and such, I will try this out, and
> hopefully should work well, as Steve Hinted to a year ago.
>
> William Stillwell
>    
Those messages mean exactly what they say - a chunk of image data was 
not decoded by the modem. The FAX protocol will retry the missing chunk 
of image, and by the end of the FAX you probably see no problems at all. 
The FAX will, however, taking somewhat longer than it should.

Regards,
Steve


-- 
_____________________________________________________________________
-- Bandwidth and Colocation Provided by http://www.api-digital.com --
New to Asterisk? Join us for a live introductory webinar every Thurs:
               http://www.asterisk.org/hello

asterisk-users mailing list
To UNSUBSCRIBE or update options visit:
   http://lists.digium.com/mailman/listinfo/asterisk-users





More information about the asterisk-users mailing list