![]() |
On Mon, 2 Aug 2004, Stephen Carville wrote: > On Mon August 2 2004 10:50 am, Lee Howard wrote: > > <snip> > > > Again, the receiver hung up when HylaFAX told them that the page was > > not received properly. > > > > HylaFAX can only do so much. If there is noise on the line or if the > > modulators on the modem generate noise, then HylaFAX cannot resolve > > that. Both of these logs indicate that some catastrophic noise event > > occurred to interfere with the data it received from the sender. > > HylaFAX informed the sender that the data was not acceptable, and the > > sender chose to hang up. What more can HylaFAX do? > Stephen, I saw a similar problem on my test machine a while ago. I hate to sound simplistic, but is there any chance call-waiting has been enabled on the line? Or perhaps it's a PBX based system that signals through when a second line is ringin? I just seem to actually remember saying the words "catastrophic line noise" before we figured that out. Also, Lee, can't he set the # of bad lines higher? That might get him past the threshold he's facing. He'll get uglier faxes, but more of them. Bill ____________________ 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*