[asterisk-users] Free Fax for Asterisk -- benchfax utility hangs.

[Barry L. Kline]

I'm trying to install my first channel of FAX. When I run the benchfax
utility, I get to various stages and then the program simply hangs.
There is no excessive CPU utilization and the benchfax program readily
responds to ^C.  Sometimes I get fairly far into the test, other times
it hangs almost immediately.

The version of benchfax version I'm using is 1.0.7. I heard tell of a
newer version, 1.0.10, but I have been unable to find it. I'm running
CentOS5, on an IBM x3250, , Asterisk 1.6.0.10, with dual Xeon 1.6G
processors.

In my last test, I got this far (the farthest along so far):

[root at corp-asterisk ~]# ./benchfax
benchfax version 1.0.7

Use the '-l' option to see license information for software
included in this program.

Running test using CCITT FAX test page, US letter size, 204x196
resolution, MMR encoding, ECM enabled and V.17 (14.4kbps) modem

NOTE: Each individual test could take 20 seconds or longer; be patient.
Test run 1 for flavor 'i686' used 632 milliseconds of CPU time.
Test run 2 for flavor 'i686' used 604 milliseconds of CPU time.
Test run 3 for flavor 'i686' used 656 milliseconds of CPU time.
Test run 4 for flavor 'i686' used 207 milliseconds of CPU time.
Test run 5 for flavor 'i686' used 624 milliseconds of CPU time.
Test run 1 for flavor 'pentium3m' used 232 milliseconds of CPU time.
Test run 2 for flavor 'pentium3m' used 668 milliseconds of CPU time.
Test run 3 for flavor 'pentium3m' used 651 milliseconds of CPU time.
Test run 4 for flavor 'pentium3m' used 641 milliseconds of CPU time.
Test run 5 for flavor 'pentium3m' used 649 milliseconds of CPU time.
Test run 1 for flavor 'pentium-m' used 194 milliseconds of CPU time.
Test run 2 for flavor 'pentium-m' used 640 milliseconds of CPU time.
Test run 3 for flavor 'pentium-m' used 673 milliseconds of CPU time.
Test run 4 for flavor 'pentium-m' used 251 milliseconds of CPU time.
Test run 5 for flavor 'pentium-m' used 617 milliseconds of CPU time.
Test run 1 for flavor 'pentium4m' used 613 milliseconds of CPU time.
Test run 2 for flavor 'pentium4m' used 664 milliseconds of CPU time.
Test run 3 for flavor 'pentium4m' used 644 milliseconds of CPU time.
Test run 4 for flavor 'pentium4m' used 628 milliseconds of CPU time.
Test run 5 for flavor 'pentium4m' used 650 milliseconds of CPU time.
Test run 1 for flavor 'prescott' used 749 milliseconds of CPU time.
Test run 2 for flavor 'prescott' used 672 milliseconds of CPU time.
Test run 3 for flavor 'prescott' used 737 milliseconds of CPU time.
Test run 4 for flavor 'prescott' used 665 milliseconds of CPU time.
Test run 5 for flavor 'prescott' used 649 milliseconds of CPU time.
Beginning test run 1 of 5 for flavor 'nocona'...

Is there a newer version of this software and can anyone give me an
indication if they, too, have had this problem and what they did to get
past it.

Thanks!

Barry