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 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 Especially, when receiving multiple faxes at the same time the transmission is quite instable. Sending faxes is even worse. I can't even send a single page: > Fax send not successful - result (25) No response after sending a page. As ISDN/SIP->T.38 Gateway I'm using a Cisco 2851. Direct T.38 Negotiation is not possible. So I'm not able to use > Set: T38CALL=1 Regards, Wolfgang > > Can anyone tell me, what I'm doing wrong? > > > Not without seeing your trace. > > Is this with error correcting FAX, or non-error correcting? If it is > with error correction, try today's snapshot of spandsp. I have been > fixing things in the handling of ECM FAX. > > Steve > > _______________________________________________ > Callweaver-users mailing list > [email protected] > http://lists.callweaver.org/mailman/listinfo/callweaver-users _______________________________________________ Callweaver-users mailing list [email protected] http://lists.callweaver.org/mailman/listinfo/callweaver-users
