![]() |
At 15:54 01/12/98 +0100, Uli wrote: >Hi, > >some time ago there was here a thread about a problem with >RTN and that HylaFAX does not lower the transmission speed >after receiving a RTN. As i remember, someone has announce >a patch against it. > No, I don't think there was an actual patch. In the mailing-list the subject of RTN must have a top 10 spot in the 'HylaFAX Review of the Year', but most relevant is a thread between Robert Coluqhoun and David Wolley around the 4 Aug 98. Then, on the 11 Aug 98, David Weiss said : >5. If HylaFAX can be persuaded to transmit at 2400 b/s, rather than >9600, the encoding error sometimes disappears, and so too, do the RTNs. >The difficulty here is in persuading HylaFAX to use 2400 for certain >targets. This is a non-trivial exercise. None of the techniques >described in the documentation (sendfax -B, destctrls) actually >functioned (for me) as advertised. Of course, this could be due to my >ignorance, lack of experience etc, and so I welcome correction. >However I tried everything I could think of for several days with >limited success. The _only_ approach that worked, required hacking of >FaxMachineInfo.c++ to ignore the "info" files, so that the -B option >to sendfax, actually had an effect. > Further info from David enabled Robert to come up with the tagline patch, which *may* reduce the incidence of RTN responses on the first page, but doesn't alter transmission rates, etc. Hope this is of some help, Phil Watkinson, Boston, UK. - Bet it's a bit nippy in Dieburg today?