![]() |
I've had this kind of problem before... it went on for 1/2 hour before I noticed it and used faxrm to terminate the call. I was especially pleased because it was long distance, too... to Redmond, Washington (to you-know-who). I presumed the problem to be something with the fact that my fax was on the order of 35 pages or so, and that the recipient's fax would hang up at approximately page 10 without any warning, and HylaFAX just kept on sending page after page after page without getting any responses, so it would resend each page a number of times or maybe it kept sending the data over and over and over like you've noticed here, and I never bothered really to analyse the logs too much, but it never loosed the phone line for at least 1/2 hour when I noticed it and ended it myself. I retried the fax in sets of 10 pages each, and it went through normally. HylaFAX has some imperfections when it comes to error (or non-response) handling... mostly due, I think, to the lack of an available testing base for troublesome fax machines. We see the errors, we have the logs, but it's not really an option to make a change and then retry a fax a number of times to a remote fax machine that belongs to someone else. Lee Howard >Jul 18 15:19:34.52: [27677]: --> [7:CONNECT] >Jul 18 15:19:34.52: [27677]: <-- data [6] >Jul 18 15:19:34.52: [27677]: <-- data [2] >Jul 18 15:19:36.48: [27677]: --> [2:OK] >Jul 18 15:19:36.56: [27677]: <-- [10:AT+FTM=48\r] >Jul 18 15:19:37.57: [27677]: --> [7:CONNECT] >Jul 18 15:19:37.57: [27677]: <-- data [900] >Jul 18 15:19:37.57: [27677]: <-- data [2] >Jul 18 15:19:39.11: [27677]: --> [2:OK] >Jul 18 15:19:39.11: [27677]: <-- [9:AT+FRH=3\r] >Jul 18 15:19:40.19: [27677]: --> [7:CONNECT] ____________________ HylaFAX(tm) Users Mailing List _______________________ To unsub: mail -s unsubscribe hylafax-users-request@hylafax.org < /dev/null