Wolfgang Liegel wrote: > This is with or without error correction. If I disable ecm I have better > chances receiving more than 5 pages. Unfortunately the latest snapshot of > spandsp doesn't fix it either (I don't have to recompile CW, do I?). > > In my debug output of the CLI I get a lot of these messages, just before the > transmission fails: > >> FLOW T.38 Rx 2346: (0) data v17-14400/hdlc-data + 3 byte(s) >> FLOW T.38 Rx 2346: (1) data v17-14400/hdlc-fcs-BAD + 0 byte(s) >> FLOW T.38T Type CFR - CRC bad (clean) >> FLOW T.30 Bad CRC received >> This the far end gateway saying it got rubbish from the far end FAX machine. This much is not a spandsp/Callweaver issue at all. > Documentation for udptl.conf is hard to find and so I don't know exactly > which options are required to be set: > >> udptlchecksums=yes >> T38FaxUdpEC = t38UDPRedundancy ;this seems to work better than t38UDPFEC >> T38FaxMaxDatagram = 300 >> udptlfecentries = 3 >> udptlfecspan = 3 >> udptlstart=4000 >> udptlend=4999 >> I don't think the udptlstart and udptlend parameters have any purpose these days. I should check that up. The rest is OK.
It is certainly possible to send endless faxes with T.38 gateway and termination. If you can't its either something in your setup or a compatibility issue with specific equipment. We have found quite a few compatibility issues I have had to fix or work around in the code. I will need PCAP files to look into issues any further. Regards, Steve _______________________________________________ Callweaver-users mailing list [email protected] http://lists.callweaver.org/mailman/listinfo/callweaver-users
