HylaFAX The world's most advanced open source fax server

[Date Prev][Date Next][Thread Prev][Thread Next] [Date Index] [Thread Index]

[hylafax-users] Hylafax and modem blocked with long faxes



Hello

System: Debian etch 4.0 (kernel 2.6.18-4-686)
Hylafax version: 4.3.1
Interface: Serial:
Modem: US Robotics 5630

When we receive faxes with more than two pages, hylafax (or modem) crashed. The sender obtain an error and finished, but hylafax doesn't detect anything and remains receiving. After that, we have to reboot the system (not only hylafax, but all the system) or we are unable to make hylafax work again.

Here you have the log of our last try (you can see the HDLC error)...

may 23 17:05:24.04: [ 5253]: SESSION BEGIN 000000026 34942270139
may 23 17:05:24.04: [ 5253]: HylaFAX (tm) Version 4.3.1
may 23 17:05:24.04: [ 5253]: <-- [13:AT+FCLASS=1A\r]
may 23 17:05:29.23: [ 5253]: --> [7:CONNECT]
may 23 17:05:29.23: [ 5253]: ANSWER: FAX CONNECTION  DEVICE '/dev/ttyS0'
may 23 17:05:29.23: [ 5253]: RECV FAX: begin
may 23 17:05:29.24: [ 5253]: <-- data [32]
may 23 17:05:29.24: [ 5253]: <-- data [2]
may 23 17:05:29.39: [ 5253]: --> [7:CONNECT]
may 23 17:05:29.39: [ 5253]: <-- data [23]
may 23 17:05:29.39: [ 5253]: <-- data [2]
may 23 17:05:30.11: [ 5253]: --> [7:CONNECT]
may 23 17:05:30.11: [ 5253]: <-- data [13]
may 23 17:05:30.11: [ 5253]: <-- data [2]
may 23 17:05:32.38: [ 5253]: --> [2:OK]
may 23 17:05:32.38: [ 5253]: <-- [9:AT+FRH=3\r]
may 23 17:05:33.21: [ 5253]: --> [7:CONNECT]
may 23 17:05:34.71: [ 5253]: --> [2:OK]
may 23 17:05:34.71: [ 5253]: REMOTE TSI "942072802"
may 23 17:05:34.71: [ 5253]: <-- [9:AT+FRH=3\r]
may 23 17:05:34.73: [ 5253]: --> [7:CONNECT]
may 23 17:05:35.17: [ 5253]: --> [2:OK]
may 23 17:05:35.17: [ 5253]: REMOTE wants 14400 bit/s
may 23 17:05:35.17: [ 5253]: REMOTE wants A4 page width (215 mm)
may 23 17:05:35.17: [ 5253]: REMOTE wants unlimited page length
may 23 17:05:35.17: [ 5253]: REMOTE wants 7.7 line/mm
may 23 17:05:35.17: [ 5253]: REMOTE wants 2-D MMR
may 23 17:05:35.17: [ 5253]: REMOTE wants T.30 Annex A, 256-byte ECM
may 23 17:05:35.17: [ 5253]: RECV training at v.17 14400 bit/s
may 23 17:05:35.17: [ 5253]: <-- [11:AT+FRM=145\r]
may 23 17:05:36.91: [ 5253]: --> [7:CONNECT]
may 23 17:05:38.42: [ 5253]: RECV: TCF 2722 bytes, 1% non-zero, 2669 zero-run
may 23 17:05:38.43: [ 5253]: --> [10:NO CARRIER]
may 23 17:05:38.43: [ 5253]: DELAY 70 ms
may 23 17:05:38.50: [ 5253]: TRAINING succeeded
may 23 17:05:38.50: [ 5253]: <-- [9:AT+FTH=3\r]
may 23 17:05:38.70: [ 5253]: --> [7:CONNECT]
may 23 17:05:38.70: [ 5253]: <-- data [3]
may 23 17:05:38.70: [ 5253]: <-- data [2]
may 23 17:05:39.88: [ 5253]: --> [2:OK]
may 23 17:05:39.88: [ 5253]: <-- [11:AT+FRM=146\r]
may 23 17:05:40.89: [ 5253]: --> [7:CONNECT]
may 23 17:06:08.19: [ 5253]: RECV received frame number 0
may 23 17:06:08.33: [ 5253]: RECV received frame number 1
may 23 17:06:08.47: [ 5253]: RECV received frame number 2
may 23 17:06:09.98: [ 5253]: RECV received frame number 3
may 23 17:06:10.12: [ 5253]: RECV received frame number 4
may 23 17:06:10.27: [ 5253]: RECV received frame number 5
may 23 17:06:10.41: [ 5253]: RECV received frame number 6
may 23 17:06:10.63: [ 5253]: RECV received frame number 7
may 23 17:06:10.77: [ 5253]: RECV received frame number 8
may 23 17:06:10.92: [ 5253]: RECV received frame number 9
may 23 17:06:11.06: [ 5253]: RECV received frame number 10
may 23 17:06:11.21: [ 5253]: RECV received frame number 11
may 23 17:06:11.35: [ 5253]: RECV received frame number 12
may 23 17:06:11.49: [ 5253]: RECV received frame number 13
may 23 17:06:11.63: [ 5253]: RECV received frame number 14
may 23 17:06:11.77: [ 5253]: RECV received frame number 15
may 23 17:06:11.92: [ 5253]: RECV received frame number 16
may 23 17:06:12.07: [ 5253]: RECV received frame number 17
may 23 17:06:12.28: [ 5253]: RECV received frame number 18
may 23 17:06:12.43: [ 5253]: RECV received frame number 19
may 23 17:06:12.57: [ 5253]: RECV received frame number 20
may 23 17:06:12.71: [ 5253]: RECV received frame number 21
may 23 17:06:12.85: [ 5253]: RECV received frame number 22
may 23 17:06:13.00: [ 5253]: RECV received frame number 23
may 23 17:06:13.14: [ 5253]: RECV received frame number 24
may 23 17:06:13.28: [ 5253]: RECV received frame number 25
may 23 17:06:13.43: [ 5253]: RECV received frame number 26
may 23 17:06:13.57: [ 5253]: RECV received frame number 27
may 23 17:07:13.75: [ 5253]: Bad HDLC terminating flag received.
may 23 17:07:16.00: [ 5253]: Timeout awaiting synchronization sequence
may 23 17:07:16.00: [ 5253]: Bad HDLC terminating flag received.
may 23 17:07:19.00: [ 5253]: Timeout awaiting synchronization sequence
may 23 17:07:19.00: [ 5253]: Bad HDLC terminating flag received.
may 23 17:07:22.00: [ 5253]: Timeout awaiting synchronization sequence
may 23 17:07:22.00: [ 5253]: Bad HDLC terminating flag received.
may 23 17:07:25.00: [ 5253]: Timeout awaiting synchronization sequence
may 23 17:07:25.00: [ 5253]: Bad HDLC terminating flag received.
may 23 17:07:28.00: [ 5253]: Timeout awaiting synchronization sequence
may 23 17:07:28.00: [ 5253]: Bad HDLC terminating flag received.
may 23 17:07:31.00: [ 5253]: Timeout awaiting synchronization sequence
may 23 17:07:31.00: [ 5253]: Bad HDLC terminating flag received.
may 23 17:07:34.00: [ 5253]: Timeout awaiting synchronization sequence
may 23 17:07:34.00: [ 5253]: Bad HDLC terminating flag received.
may 23 17:07:37.00: [ 5253]: Timeout awaiting synchronization sequence
may 23 17:07:37.00: [ 5253]: Bad HDLC terminating flag received.
may 23 17:07:40.00: [ 5253]: Timeout awaiting synchronization sequence
may 23 17:07:40.00: [ 5253]: Bad HDLC terminating flag received.
may 23 17:07:43.00: [ 5253]: Timeout awaiting synchronization sequence
may 23 17:07:43.00: [ 5253]: Bad HDLC terminating flag received.
may 23 17:07:46.00: [ 5253]: Timeout awaiting synchronization sequence
may 23 17:07:46.00: [ 5253]: Bad HDLC terminating flag received.
may 23 17:07:49.00: [ 5253]: Timeout awaiting synchronization sequence
may 23 17:07:49.00: [ 5253]: Bad HDLC terminating flag received.
may 23 17:07:52.00: [ 5253]: Timeout awaiting synchronization sequence
may 23 17:07:52.00: [ 5253]: Bad HDLC terminating flag received.
may 23 17:07:55.00: [ 5253]: Timeout awaiting synchronization sequence
may 23 17:07:55.00: [ 5253]: Bad HDLC terminating flag received.
may 23 17:07:58.00: [ 5253]: Timeout awaiting synchronization sequence
may 23 17:07:58.00: [ 5253]: Bad HDLC terminating flag received.
may 23 17:08:01.00: [ 5253]: Timeout awaiting synchronization sequence
may 23 17:08:01.00: [ 5253]: Bad HDLC terminating flag received.
may 23 17:08:04.00: [ 5253]: Timeout awaiting synchronization sequence
may 23 17:08:04.00: [ 5253]: Bad HDLC terminating flag received.
may 23 17:08:07.00: [ 5253]: Timeout awaiting synchronization sequence
may 23 17:08:07.00: [ 5253]: Bad HDLC terminating flag received.
may 23 17:08:10.00: [ 5253]: Timeout awaiting synchronization sequence
may 23 17:08:10.00: [ 5253]: Bad HDLC terminating flag received.
may 23 17:08:10.98: [ 5253]: CLOSE /dev/ttyS0

Thanks in advance

Alberto Iglesias


-- 

Alberto Iglesias
Gerente
aiglesias@xxxxxxxxxx

-----------------------------------------------------------
ARCANOS INTERCOM S.L.
Centro de Empresas Camargo (local 211)
Polígono Industrial de Trascueto s/n
39600 Revilla de Camargo (Cantabria)

Tel:          942 072 801
Tel IP:      700 754 960
Fax:          942 072 802
@mail:    arcanos@xxxxxxxxxx
Web:        http://www.arcanos.es

------------------------------------------------------------------------------------------------------------
Este e-mail y cualquiera de sus ficheros anexos son confidenciales y pueden
incluir información privilegiada. Si usted no es el destinatario adecuado
(o responsable de remitirlo a la persona indicada), agradeceríamos lo
notificase o reenviase inmediatamente al emisor. No revele estos contenidos a
ninguna otra persona, no los utilice para otra finalidad, ni almacene y, o,
copie esta información en medio alguno. Opiniones, conclusiones y otro tipo
de información relacionada con este mensaje que no sean relativas a la
actividad propia de ARCANOS INTERCOM S.L., deberán ser entendidas como
exclusivas del emisor.
begin:vcard
fn:Alberto Iglesias
n:Iglesias Aquesolo;Alberto
org:Arcanos Intercom S.L.
adr;quoted-printable;quoted-printable:Pol=C3=ADgono de Trascueto s/n;;Centro Empresas Camargo (local 211);Revilla de Camargo;Cantabria;39600;Espa=C3=B1a
email;internet:aiglesias@xxxxxxxxxx
title:Gerente
tel;work:942072801
tel;fax:942072802
x-mozilla-html:TRUE
url:http://www.arcanos.es
version:2.1
end:vcard




Project hosted by iFAX Solutions