[Asterisk-Users] SoftFAX/spandsp

[Steve Underwood]

Hi Alex,

Which Dialogic hardware are you using? I have a VFX41/ESC, but I have 
not tried faxing to spandsp with it. I will try it. A lot of the 
problems I have had in the last week are with FAX machines that do not 
obey the spec properly. I expect this is one.

Regards,
Steve


Alex Zarubin wrote:

> Hi,
>
> With the latest release available (spandsp-0.0.1f) we still cannot 
> receive
> faxes from Dialogic. There are no problems with several fax machines 
> we've tried and
> it works fine with J2, so it shouldn't be slipping...
>
>     -- Executing RxFAX("Zap/26-1", 
> "/usr/tmp/nativefax-from-8772308094-1079985146.tif") in new stack
> Changed from phase 0 to 1
> Slow carrier up
> [03/22/04 13:52:26.985] DEBUG[507930]: File chan_zap.c, Line 3332 
> (zt_exception): Exception on 41, channel 26
> [03/22/04 13:52:26.985] DEBUG[507930]: File chan_zap.c, Line 2753 
> (zt_handle_event): Got event No event(0) on channel 26 (index 0)
>
> [03/22/04 13:52:26.985] DEBUG[507930]: File chan_zap.c, Line 3234 
> (zt_handle_event): Dunno what to do with event 0 on channel 26
>
> 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 20
> DIS:
> 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 01
> HDLC 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: 44
> Fast carrier up
> Coarse carrier frequency 1699.92 (56)
> Training failed (only 120 1's)
> Fast carrier training failed
> Fast carrier down
> 0 bad bits in trainability test
> >>> FTT: 44
> Fast carrier up
> Coarse carrier frequency 1700.14 (4834)
> Fast carrier down
> 0 bad bits in trainability test
> >>> FTT: 44
> 0 bad bits in trainability test
> >>> FTT: 44
> Fast carrier up
> Coarse carrier frequency 1699.87 (56)
> Fast carrier trained
> Fast carrier down
> 27 bad bits in trainability test
> >>> FTT: 44
> Fast carrier up
> Coarse carrier frequency 1700.01 (4848)
> Fast carrier down
> 27 bad bits in trainability test
> >>> FTT: 44
> Fast carrier up
> Coarse carrier frequency 1699.69 (56)
> Training failed (only 114 1's)
> Fast carrier training failed
> Fast carrier down
> 27 bad bits in trainability test
> >>> FTT: 44
> Fast carrier up
> Coarse carrier frequency 1699.84 (2904)
> Fast carrier down
> 27 bad bits in trainability test
> >>> FTT: 44
> Fast carrier up
> Fast carrier down
> 27 bad bits in trainability test
> >>> FTT: 44
> ^M    -- Channel 2, span 2 got hangup
> [03/22/04 13:52:57.848] DEBUG[507930]: File app_rxfax.c, Line 237 
> (rxfax_exec): Got hangup
> [03/22/04 13:52:57.848] DEBUG[507930]: File pbx.c, Line 1744 
> (ast_pbx_run): Extension 8663222818, priority 1 returned normally even 
> though call was hung up
>
> Thank you.
>
> Alex Zarubin
> Webley Systems
>
>
> -----Original Message-----
> From: Steve Underwood [mailto:steveu at coppice.org]
> Sent: Monday, March 22, 2004 8:14 AM
> To: asterisk-users at lists.digium.com
> Subject: [Asterisk-Users] SoftFAX/spandsp
>
>
> Hi all,
>
> If you have had trouble with multiple concurrent channels running
> app_rxfax or ap_txfax, where was a silly bug. Updated versions are
> available at ftp://ftp.opencall.org/pub/spandsp
>
> The latest spandsp-0.0.1f seems to working for quite a lot of people. I
> guess there will still be plenty more compatibility issues to deal with,
> though. If you try this software and find reliability problems try
> checking for frame slips. A single frame slip in the audio stream will
> kill a fax transfer. This is true for any fax modem, and is not a
> spandsp issue.
>
> Regards,
> Steve
>