Hi, I have investigated some more fax machines that did not work with spandsp, and made it more tolerant. ftp://ftp.opencall.org/pub/spandsp/spandsp-0.0.1c.tar.gz is the result. From what I have seen in today's investigations, I think this one will work with considerably more quirky fax machines and bad phone lines. Regards, Steve
Hi, There is a progress, we were able to receive several faxes through J2 service! Our Dialogic based faxing still fails though. This is how it goes: -- Executing RxFAX("Zap/36-1", "/usr/tmp/nativefax-from-8772308094-1079728088.tif") in new stack Changed from phase 0 to 1 Slow carrier up Slow carrier down Slow carrier up Slow carrier down Start receiving document Changed from phase 1 to 4 Sending ident>>> CSI: 40 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20DIS: Preferred octets: 256 Can receive fax Supported data signalling rates: V.27ter and V.29 R8x7.7lines/mm and/or 200x200pels/25.4mm OK 2D coding OK Scan line length: 215mm Recording length: A4 (297mm) Receiver's minimum scan line time: 0ms at 3.85 l/mm: T7.7 = T3.85 R8x15.4lines/mm OK Minimum scan line time for higher resolutions: T15.4 = T7.7>>> DIS: 80 00 ce f0 80 80 01HDLC underflow in state 9 Changed from phase 4 to 3 Slow carrier up <<< TSI: 43 4e 49 42 55 52 41 5a 20 58 45 4c 41 20 20 20 20 20 20 20 20 TSI without final frame tag Remote fax gave TSI as: "ALEX ZARUBIN" <<< DCS: 83 00 c6 70 DCS with final frame tag In state 9 DCS: Can receive fax Selected data signalling rate: V.29, 9600bps R8x7.7lines/mm and/or 200x200pels/25.4mm OK 2D coding OK Scan line length: 215mm Recording length: A4 (297mm) Minimum scan line time: 0ms Get at 9600 Changed from phase 3 to 5 Fast carrier up Fast carrier down 0 bad bits in trainability test>>> FTT: 44Fast carrier up Coarse carrier frequency 1699.98 (56) Training failed (only 123 1's) Fast carrier training failed Fast carrier down 0 bad bits in trainability test>>> FTT: 44Fast carrier up Fast carrier down 0 bad bits in trainability test>>> FTT: 44Fast carrier up Coarse carrier frequency 1700.07 (58) Training failed (only 153 1's) Fast carrier training failed Fast carrier down 0 bad bits in trainability test>>> FTT: 44Fast carrier up Coarse carrier frequency 1700.19 (4834) Fast carrier down 0 bad bits in trainability test>>> FTT: 44Fast carrier up Coarse carrier frequency 1699.72 (58) Training failed (only 162 1's) Fast carrier training failed Fast carrier down 0 bad bits in trainability test>>> FTT: 44Fast carrier up Coarse carrier frequency 1700.04 (2922) Fast carrier down 0 bad bits in trainability test>>> FTT: 44-- Channel 12, span 2 got hangup [03/19/04 14:28:38.608] DEBUG[524314]: File app_rxfax.c, Line 200 (rxfax_exec): Got hangup Hope this one can be coquered, too. Thank you. Alex Zarubin Webley Systems -----Original Message----- From: Steve Underwood [mailto:steveu@coppice.org] Sent: Friday, March 19, 2004 1:02 PM To: asterisk-users@lists.digium.com Subject: [Asterisk-Users] SoftFAX/spndsp Hi, I have investigated some more fax machines that did not work with spandsp, and made it more tolerant. ftp://ftp.opencall.org/pub/spandsp/spandsp-0.0.1c.tar.gz is the result. From what I have seen in today's investigations, I think this one will work with considerably more quirky fax machines and bad phone lines. Regards, Steve _______________________________________________ Asterisk-Users mailing list Asterisk-Users@lists.digium.com http://lists.digium.com/mailman/listinfo/asterisk-users To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.digium.com/pipermail/asterisk-users/attachments/20040319/a9159cb3/attachment.htm
Steve, Many thanks for your work, first of all. We have also been testing spandsp lib with rxfax * app here via RTP/ULAW (on LAN, direct from Sipura SPA2000 and GS HT-286 to *). It seems to be getting better with each new release of spandsp ;-). We do not get any more fast carrier training problems with various PC fax modems and a couple HP all-in-one fax machines, but the received faxes (tiff files) still come out garbled. It works much better with fax modems, faxing from win2000 using its 'native' fax driver. The line errors usually begin somewhere around scanline 1700 (in fine resolution; 200 dpi ?) and after that everything is garbled. With HP fax machines, the line errors start immediately and everything is garbled. It also takes an awful long time to transmit a single page (retransmits?). The only thing that is readable in faxes received from HP machines is the header with date, TSI name/number and page # (is that generated by spandsp or transmitted in the image by the fax?). In both of above cases, the negotiated protocol is V.29 at 9600bps. I can send the logs if you want, they tend to get too big for inclusion in this email with all those line errors. I can also send the received .tiffs. Now, the question I had was if it is practically possible to fax over RTP/ULAW with asterisk. Do you think some changes to asterisk RTP stack might be necessary to accomplish this? It seems very promising as it is right now. Transmitting a fax over POTS with the same fax modems into asterisk with an X100P board works like a charm! But we could not try the same with the fax machines -- don't have a spare line right now. Cheers! Alex. ----- Original Message ----- From: "Steve Underwood" <steveu@coppice.org> To: <asterisk-users@lists.digium.com> Sent: Friday, March 19, 2004 2:02 PM Subject: [Asterisk-Users] SoftFAX/spndsp> Hi, > > I have investigated some more fax machines that did not work with > spandsp, and made it more tolerant. > ftp://ftp.opencall.org/pub/spandsp/spandsp-0.0.1c.tar.gz is the result. > From what I have seen in today's investigations, I think this one will > work with considerably more quirky fax machines and bad phone lines. > > Regards, > Steve > >