Re: [hylafax-users] Unspecified Transmit Phase C error

[Lee Howard <faxguy@xxxxxxxxxxxxxxxx>]

SCIN - Danilo Bottino wrote:

> > SCIN - Danilo Bottino wrote:
> >
> > > > SCIN - Danilo Bottino wrote:
> > > >
> > > > > How exactly are created those info files? I mean, is hylafax able 
> > > > > to change a troublesome value on the fly whenever it detects a 
> > > > > problem, as long as they're not manually locked with "&"?
> > > >
> > > >
> > > >
> > > >
> > > > Yes, and the problem with hasV17Trouble is that once it is turned 
> > > > on HylaFAX will never attempt V.17 again to know otherwise.  
> > > > However, this feature is necessary for situations where there 
> > > > really, truly are V.17 incompatibilities.
> > > >
> > > > The log that I was hoping you'd find was the one that says "Looks 
> > > > like this destination has trouble with V.17" or something to that 
> > > > effect.
> > >
> > > This means digging down five months of logs.. there are roughly 700 
> > > log files for that receiver. Any chance to feed egrep with some 
> > > useful string?
> >
> >
> >
> > The exact string is "The destination appears to have trouble with V.17."
>
> Too bad I had no luck, I guess I started to store the old logs too 
> late to find out what happened the day that hasV17Trouble was turned 
> on. Is there a way to reset this thing to the initial state? Maybe 
> deleting the info file? 


Yes, just deleting the info files from time to time is not a bad idea 
(unless you're a DIS or NSF packrat like me)... especially if you're 
using ModemSoftRTFCC (which you are by default).

Lee.

____________________ HylaFAX(tm) Users Mailing List _______________________
 To subscribe/unsubscribe, click http://lists.hylafax.org/cgi-bin/lsg2.cgi
On UNIX: mail -s unsubscribe hylafax-users-request@xxxxxxxxxxx < /dev/null
 *To learn about commercial HylaFAX(tm) support, mail sales@xxxxxxxxx*