In my case, I am playing with Asterisk 1.6.1, downgrading my previous 1.6.2 which can't have FAX modules for now.

You must synchronise the correct FAX version with your Asterisk version !

After having received your FAX license and registered it with the "register" tool, you must download and execute the "benchfax" to know what is the correct FAX module version for your Asteris kserver environment :

You must have downloaded the tarballs within the first few hours they were available. We had a build error with them that we corrected. We did not rev the version number of the tarballs though.

Please download res_fax and res_fax_digium again from the Digium downloads server. We've seen your specific problem before, exactly, and we've fixed it with the new tarballs.

Cheers.

Malcolm,

Great Sir! that worked so i downloaded tarballs within first few hours of release and now i removed the old and installed new and its working.

Now another help i need....! hope you dont mind?

Im using AsteriskNow 1.5 which has freepbx as GUI and most things i do is with GUI and not hand edit as im not good at this.....so if you can please show me how to do make a fax working with FreePBX or a dialplan example for sending and receiving fax....!

as on FreePBX there is Fax Detection application is NVFaxdetect would that word with Digium Fax Application after successful tests we will go for commercial one and will continue using free version for testing purposes.

In my case, I am playing with Asterisk 1.6.1, downgrading my previous 1.6.2 which can't have FAX modules for now.

You must synchronise the correct FAX version with your Asterisk version !

Hey f6hqz,

Thank you very much for your guide i actually followed that but the problem was with source tarballs which is solved.

now if you can really guide me through a step by step guide for making it work with AsteriskNow 1.5 and FreePBX as GUI, also some pointers on how to do windows PC to Fax (send/receive). that would be a great help.

Test run 1 for flavor 'i686' used 649 milliseconds of CPU time.
Test run 2 for flavor 'i686' used 682 milliseconds of CPU time.
Test run 3 for flavor 'i686' used 667 milliseconds of CPU time.
Test run 4 for flavor 'i686' used 660 milliseconds of CPU time.
Test run 5 for flavor 'i686' used 650 milliseconds of CPU time.
Test run 1 for flavor 'pentium3m' used 694 milliseconds of CPU time.
Test run 2 for flavor 'pentium3m' used 689 milliseconds of CPU time.
Test run 3 for flavor 'pentium3m' used 687 milliseconds of CPU time.
Test run 4 for flavor 'pentium3m' used 665 milliseconds of CPU time.
Test run 5 for flavor 'pentium3m' used 692 milliseconds of CPU time.
Flavor 'pentium-m' failed, skipping.'pentium-m'...
Segmentation faultad run for flavor 'pentium4m'...