HylaFAX The world's
most advanced open source fax server
|
|
[
Date Prev][
Date Next][
Thread Prev][
Thread Next]
[
Date Index]
[
Thread Index]
Re: Strange error
> I receied an error with a fax. But weird. I was in the retraining part.
> The first few pages went through, with the following log for the retrain parts
> May 22 12:10:44.08: [14630]: SEND send MPS (more pages, same document)
> May 22 12:10:44.08: [14630]: <-- [9:AT+FET=0\r]
> May 22 12:10:47.04: [14630]: --> [8:+FPTS: 2]
> May 22 12:10:47.04: [14630]: --> [2:OK]
> May 22 12:10:47.04: [14630]: SEND recv RTN (retrain negative)
> May 22 12:10:47.04: [14630]: <-- [7:AT+FDT\r]
> May 22 12:11:05.68: [14630]: --> [22:+FDCS: 1,0,0,2,0,0,0,0]
> May 22 12:11:05.68: [14630]: --> [7:CONNECT]
> May 22 12:11:05.68: [14630]: SEND wait for XON
> May 22 12:11:05.68: [14630]: --> [1:^Q]
> May 22 12:11:05.68: [14630]: SEND begin page
> May 22 12:11:05.68: [14630]: <-- data [1027]
> May 22 12:11:05.68: [14630]: <-- data [1026]
> May 22 12:11:05.68: [14630]: <-- data [1027]
Here it's basically agreeing that the page did not send properly, and is
going to try it again. It will go through this loop a few times, and then
give up. Your recipient will hopefully confim they they have received
three copies of the first page, then nothing at all.
We've seen this quite a lot with USR modems (*spit*), and a ZyXEL with
slightly older firmware. The problem is compounded by the fact that
HylaFAX thinks the page never got sent according to the recieving machine's
complaining, and so faithfully every few minutes it will try to send the
FAX again, sending another three copies of the first page. In my
experience, this is a nasty intermittent problem which depends on the
identity of the receiving FAX machine . . .
I suspect, but do not know for certain, that HylaFAX is not really to blame
here - Sam followed class 2 fax specs to the tiniest letter as I recall.
> But the last page sent (not the last page of the document had the following
> log:
> (Note that the command issured after the SEND recv RTN is different from
> the first few retrains.)
>
> May 22 12:14:18.78: [14630]: SEND send MPS (more pages, same document)
> May 22 12:14:18.78: [14630]: <-- [9:AT+FET=0\r]
> May 22 12:14:21.62: [14630]: --> [8:+FPTS: 2]
> May 22 12:14:21.73: [14630]: --> [2:OK]
> May 22 12:14:21.73: [14630]: SEND recv RTN (retrain negative)
> May 22 12:14:21.73: [14630]: <-- [6:AT+FK\r]
> May 22 12:14:27.36: [14630]: --> [9:+FHNG: 50]
> May 22 12:14:27.36: [14630]: REMOTE HANGUP: Unspecified Transmit Phase D
> error,
> including +FPHCTO timeout between data and +FET command (code 50)
> May 22 12:14:28.04: [14630]: --> [2:OK]
> May 22 12:14:28.04: [14630]: SEND FAILED: Unable to transmit page (giving
> up aft
> er 3 attempts); too many attempts to send
> May 22 12:14:28.04: [14630]: <-- [5:ATH0\r]
> May 22 12:14:28.15: [14630]: --> [2:OK]
> May 22 12:14:28.15: [14630]: SESSION END
>
>
>
> Shouldn't they be the same?
No, this is where they're deciding to call it quits.
-DPN
Attachment Converted: c:\program files\eudora\attach\Re Strange error