asterisk users - Aug 2004 - spandsp and certain (e.g. Canon) fax machines

Hi,

Several people have reported problems sending faxes from spandsp-0.0.1k 
to Canon FAX machines. A spandsp user had the same problem with another 
make of FAX machine, and traced the problem to a bug in the file t30.c 
of spandsp. Line 542 says s->t4.rx_file[0] where it should say 
s->t4.tx_file[0]. This fixes his problem, and I suspect it will also fix 
the Canon fax machine problem. Can someone having problems with Canon 
machines try this change, and tell me the result?

Regards,
Steve

Dear Steve
        i have try the SpanDSP (ver.k and latest Asterisk cvs) with the mod 
you have 
write below, but nothing my Canon Fax still dont send the fax:
-----
    -- Executing RxFAX("Zap/35-1", "/home/user/testfax.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 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 37 30 38 30 35 33 31 33 33 30 20 20 20 20 20 20 20 20 20 20
TSI without final frame tag
Remote fax gave TSI as: "0331350807"
<<< DCS: 83 00 86 a0 00
DCS with final frame tag
In state 9
DCS:
Can receive fax
Selected data signalling rate: V.29, 9600bps
2D coding OK
Scan line length: 215mm
Recording length: A4 (297mm)
Minimum scan line time: 10ms
Get at 9600
Changed from phase 3 to 5
Fast carrier up
Coarse carrier frequency 1728.81 (11)
Fast carrier down
Fast carrier up
Coarse carrier frequency 1699.38 (86)
Fast carrier training failed
Fast carrier down
Fast carrier up
Coarse carrier frequency 1700.06 (4917)
Fast carrier down
Fast carrier up
Coarse carrier frequency 1699.33 (86)
Fast carrier training failed
Fast carrier down
Fast carrier up
Coarse carrier 1700.09 (4915)
Fast carrier down
Fast carrier up
Coarse carrier frequency 1699.33 (86)
Fast carrier training failed
Fast carrier down
Fast carrier up
Coarse carrier frequency 1700.07 (2924)
Fast carrier down
    -- Executing NoOp("Zap/35-1", "DIALEDTIME=") in new
stack
    -- Executing NoOp("Zap/35-1", "ANSWEREDTIME=") in new
stack
    -- Executing Hangup("Zap/35-1", "") in new stack
----

I dont know how to debug more, you can give more help to trace the problem?
Thanks in advance.
Dimitri

On Wednesday 25 August 2004 11:34, Steve Underwood
wrote:
> Hi,
>
> Several people have reported problems sending faxes from spandsp-0.0.1k
> to Canon FAX machines. A spandsp user had the same problem with another
> make of FAX machine, and traced the problem to a bug in the file t30.c
> of spandsp. Line 542 says s->t4.rx_file[0] where it should say
> s->t4.tx_file[0]. This fixes his problem, and I suspect it will also fix
> the Canon fax machine problem. Can someone having problems with Canon
> machines try this change, and tell me the result?
>
> 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

Hi,

Several people have reported problems sending faxes from spandsp-0.0.1k 
to Canon FAX machines. A spandsp user had the same problem with another 
make of FAX machine, and traced the problem to a bug in the file t30.c 
of spandsp. Line 542 says s->t4.rx_file[0] where it should say 
s->t4.tx_file[0]. This fixes his problem, and I suspect it will also fix 
the Canon fax machine problem. Can someone having problems with Canon 
machines try this change, and tell me the result?

Regards,
Steve