Re: [hylafax-users] High failure rate on sending

To: Lee Howard <faxguy@xxxxxxxxxxxxxxxx>
Subject: Re: [hylafax-users] High failure rate on sending
From: Daniel Hillhouse <daniel.hillhouse@xxxxxxxxxxxxxxxx>
Cc: hylafax-users@xxxxxxxxxxx
Date: Fri, 04 Nov 2005 15:52:25 +1100

Thanks Lee.

I was using xonxoff so I changed that to rtscts but it still had errors. This time it didn't resubmit those sections. Here is the bottom of the new log. Everything went fine up to frame 255.

...
Nov 04 15:46:04.22: [ 9837]: SEND send frame number 255
Nov 04 15:46:04.22: [ 9837]: DELAY 200 ms
Nov 04 15:46:04.41: [ 9837]: <-- [11:AT+FTM=146\r]
Nov 04 15:46:04.91: [ 9837]: --> [7:CONNECT]
Nov 04 15:46:43.30: [ 9837]: --> [2:OK]
Nov 04 15:46:43.30: [ 9837]: <-- [9:AT+FTS=9\r]
Nov 04 15:46:43.32: [ 9837]: --> [2:OK]
Nov 04 15:46:43.32: [ 9837]: <-- [9:AT+FTH=3\r]
Nov 04 15:46:43.37: [ 9837]: --> [7:CONNECT]
Nov 04 15:46:44.79: [ 9837]: --> [2:OK]
Nov 04 15:46:44.79: [ 9837]: SEND send PPS (partial page signal)
Nov 04 15:46:44.79: [ 9837]: SEND send NULL (more blocks, same page)
Nov 04 15:46:44.79: [ 9837]: <-- [9:AT+FRH=3\r]
Nov 04 15:46:45.47: [ 9837]: --> [7:CONNECT]
Nov 04 15:46:49.72: [ 9837]: --> [2:OK]
Nov 04 15:46:49.72: [ 9837]: HDLC frame too short (0 bytes)
Nov 04 15:46:49.72: [ 9837]: <-- [9:AT+FRS=7\r]
Nov 04 15:46:49.74: [ 9837]: --> [2:OK]
Nov 04 15:46:49.74: [ 9837]: <-- [9:AT+FTH=3\r]
Nov 04 15:46:49.79: [ 9837]: --> [7:CONNECT]
Nov 04 15:46:51.11: [ 9837]: --> [2:OK]
Nov 04 15:46:51.11: [ 9837]: SEND send CRP (command repeat)
Nov 04 15:46:51.11: [ 9837]: <-- [9:AT+FRH=3\r]
Nov 04 15:46:54.21: [ 9837]: --> [0:]
Nov 04 15:46:54.21: [ 9837]: MODEM <Empty line>
Nov 04 15:46:54.41: [ 9837]: MODEM <Timeout>
Nov 04 15:46:54.41: [ 9837]: <-- [9:AT+FTH=3\r]
Nov 04 15:46:54.46: [ 9837]: --> [7:CONNECT]
Nov 04 15:46:55.88: [ 9837]: --> [2:OK]
Nov 04 15:46:55.88: [ 9837]: SEND send PPS (partial page signal)
Nov 04 15:46:55.88: [ 9837]: SEND send NULL (more blocks, same page)
Nov 04 15:46:55.88: [ 9837]: <-- [9:AT+FRH=3\r]
Nov 04 15:46:56.54: [ 9837]: --> [7:CONNECT]
Nov 04 15:47:00.82: [ 9837]: --> [2:OK]
Nov 04 15:47:00.82: [ 9837]: HDLC frame too short (0 bytes)
Nov 04 15:47:00.82: [ 9837]: <-- [9:AT+FRS=7\r]
Nov 04 15:47:00.84: [ 9837]: --> [2:OK]
Nov 04 15:47:00.84: [ 9837]: <-- [9:AT+FTH=3\r]
Nov 04 15:47:00.89: [ 9837]: --> [7:CONNECT]
Nov 04 15:47:02.21: [ 9837]: --> [2:OK]
Nov 04 15:47:02.21: [ 9837]: SEND send CRP (command repeat)
Nov 04 15:47:02.21: [ 9837]: <-- [9:AT+FRH=3\r]
Nov 04 15:47:05.31: [ 9837]: --> [0:]
Nov 04 15:47:05.31: [ 9837]: MODEM <Empty line>
Nov 04 15:47:05.51: [ 9837]: MODEM <Timeout>
Nov 04 15:47:05.51: [ 9837]: <-- [9:AT+FTH=3\r]
Nov 04 15:47:05.56: [ 9837]: --> [7:CONNECT]
Nov 04 15:47:06.98: [ 9837]: --> [2:OK]
Nov 04 15:47:06.98: [ 9837]: SEND send PPS (partial page signal)
Nov 04 15:47:06.98: [ 9837]: SEND send NULL (more blocks, same page)
Nov 04 15:47:06.98: [ 9837]: <-- [9:AT+FRH=3\r]
Nov 04 15:47:07.66: [ 9837]: --> [7:CONNECT]
Nov 04 15:47:09.73: [ 9837]: --> [2:OK]
Nov 04 15:47:09.73: [ 9837]: HDLC frame with bad control field 0x20
Nov 04 15:47:09.73: [ 9837]: <-- [9:AT+FRS=7\r]
Nov 04 15:47:09.75: [ 9837]: --> [2:OK]
Nov 04 15:47:09.75: [ 9837]: <-- [9:AT+FTH=3\r]
Nov 04 15:47:09.80: [ 9837]: --> [7:CONNECT]
Nov 04 15:47:11.11: [ 9837]: --> [2:OK]
Nov 04 15:47:11.11: [ 9837]: SEND send CRP (command repeat)
Nov 04 15:47:11.11: [ 9837]: <-- [9:AT+FRH=3\r]
Nov 04 15:47:14.21: [ 9837]: --> [0:]
Nov 04 15:47:14.21: [ 9837]: MODEM <Empty line>
Nov 04 15:47:14.41: [ 9837]: MODEM <Timeout>
Nov 04 15:47:14.41: [ 9837]: No response to PPS repeated 3 times.
Nov 04 15:47:14.41: [ 9837]: SEND end page
Nov 04 15:47:14.41: [ 9837]: <-- [9:AT+FTH=3\r]
Nov 04 15:47:14.46: [ 9837]: --> [7:CONNECT]
Nov 04 15:47:15.78: [ 9837]: --> [2:OK]
Nov 04 15:47:15.78: [ 9837]: SEND FAILED: JOB 367

Lee Howard wrote:

Daniel Hillhouse wrote:
Nov 04 13:57:06.99: [ 7935]: SEND recv PPR (partial page request)
Nov 04 13:57:06.99: [ 7935]: <-- [9:AT+FRS=7\r]
Nov 04 13:57:07.01: [ 7935]: --> [2:OK]
Nov 04 13:57:07.01: [ 7935]: SEND send frame number 0
Nov 04 13:57:07.01: [ 7935]: SEND send frame number 1
Nov 04 13:57:07.01: [ 7935]: SEND send frame number 59
Nov 04 13:57:07.01: [ 7935]: SEND send frame number 60
Nov 04 13:57:07.01: [ 7935]: SEND send frame number 61
Nov 04 13:57:07.02: [ 7935]: SEND send frame number 62
Nov 04 13:57:07.02: [ 7935]: SEND send frame number 63
Nov 04 13:57:07.02: [ 7935]: SEND send frame number 122
Nov 04 13:57:07.02: [ 7935]: SEND send frame number 123
Nov 04 13:57:07.02: [ 7935]: SEND send frame number 124
Nov 04 13:57:07.02: [ 7935]: SEND send frame number 125
Nov 04 13:57:07.02: [ 7935]: SEND send frame number 126
Nov 04 13:57:07.02: [ 7935]: SEND send frame number 186
Nov 04 13:57:07.02: [ 7935]: SEND send frame number 187
Nov 04 13:57:07.02: [ 7935]: SEND send frame number 188
Nov 04 13:57:07.02: [ 7935]: SEND send frame number 189
Nov 04 13:57:07.02: [ 7935]: SEND send frame number 190
Nov 04 13:57:07.02: [ 7935]: SEND send frame number 248
Nov 04 13:57:07.02: [ 7935]: SEND send frame number 249
Nov 04 13:57:07.02: [ 7935]: SEND send frame number 250
Nov 04 13:57:07.02: [ 7935]: SEND send frame number 251
Nov 04 13:57:07.03: [ 7935]: SEND send frame number 252
Notice that there seem to be "chunks" of data that need to get resent... frames 0-1, 59-63, 122-126, 186-190, 248-252. This is highly suspicious of sender-side flow-control errors between HylaFAX and the modem. In simple terms, I think that your modem has broken flow control for whichever flow-control setting you are using in your modem config file. So in your modem config file if you have "ModemFlowControl: xonxoff" please change that to "rtscts" or vice-versa. If you have no ModemFlowControl entry in your modem config file then add "ModemFlowControl: rtscts".

Nov 04 13:58:11.09: [ 7935]: SEND recv RNR (receive not ready) Nov 04 13:58:11.09: [ 7935]: <-- [9:AT+FRS=7\r] Nov 04 13:58:11.11: [ 7935]: --> [2:OK] Nov 04 13:58:11.11: [ 7935]: Receiver flow control exceeded timer.

This happens when sending to some receivers and for some reason the data that the receiver gets is unintelligible. The fact that you had to retransmit frame 0 so many times makes things even more suspicious.

Anyway, fix the flow control problem and then see how things go.

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*


____________________ 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*

Follow-Ups:
- Re: [hylafax-users] High failure rate on sending
  - From: Lee Howard

References:
- [hylafax-users] High failure rate on sending
  - From: Daniel Hillhouse
- Re: [hylafax-users] High failure rate on sending
  - From: Lee Howard

Prev by Date: Re: [hylafax-users] High failure rate on sending
Next by Date: Re: [hylafax-users] T.30 T2 timeout, expected signal not received
Previous by thread: Re: [hylafax-users] High failure rate on sending
Next by thread: Re: [hylafax-users] High failure rate on sending
Index(es):
- Main
- Thread

Report any problems to webmaster@hylafax.org

HylaFAX is a trademark of Silicon Graphics Corporation.
Internet connectivity for hylafax.org is provided by:
VirtuALL Private Host Services