Re: [hylafax-users] problem receiving faxes with Hylafax v4.2.0 alpha 023

[Daniel Moreda García <daniel.moreda@xxxxxxxxx>]

Ok, thanks for your fast response.

I've used exactly the same modem, and the same phone line for the two tests.

I did the following:
I've updated and existing installation of Hylafax 4.2.0beta2 to 4.2.0 without changing any 
configuration parameter file and without changing the modem.
With 4.2.0beta2 this worked fine, and with 4.2.0 it doesn't work.

Lee Howard wrote:

> On 2004.08.18 09:12 Daniel Moreda García wrote:
>
> > This is a session of the same fax, but with Hylafax v4.2.0beta2:
> >
> > Aug 18 17:37:56.89: [ 3015]: SESSION BEGIN 000005165 34981xxxxxx
> > Aug 18 17:37:56.89: [ 3015]: HylaFAX (tm) Version 4.2.0beta2
> > Aug 18 17:37:56.89: [ 3015]: MODEM set XON/XOFF/FLUSH: input ignored, 
> > output disabled
> > Aug 18 17:37:56.89: [ 3015]: <-- [4:ATA\r]
> > Aug 18 17:38:03.39: [ 3015]: --> [7:CONNECT]
> > Aug 18 17:38:03.39: [ 3015]: ANSWER: FAX CONNECTION  DEVICE '/dev/ttyS1'
> > Aug 18 17:38:03.39: [ 3015]: MODEM input buffering enabled
> > Aug 18 17:38:03.39: [ 3015]: RECV FAX: begin
> > Aug 18 17:38:03.39: [ 3015]: MODEM input buffering disabled
> > Aug 18 17:38:03.39: [ 3015]: <-- data [37]
> > Aug 18 17:38:03.39: [ 3015]: <-- data [2]
> > Aug 18 17:38:03.43: [ 3015]: --> [7:CONNECT]
> > Aug 18 17:38:03.43: [ 3015]: <-- data [23]
> > Aug 18 17:38:03.43: [ 3015]: <-- data [2]
> > Aug 18 17:38:03.46: [ 3015]: --> [7:CONNECT]
> > Aug 18 17:38:03.46: [ 3015]: <-- data [10]
> > Aug 18 17:38:03.46: [ 3015]: <-- data [2]
> > Aug 18 17:38:06.68: [ 3015]: --> [2:OK]
>
>
> Here's the same segment from the 4.2.0 session that you sent:
>
> > Aug 18 11:37:39.01: [ 6052]: SESSION BEGIN 000000003 34981xxxxxx
> > Aug 18 11:37:39.01: [ 6052]: HylaFAX (tm) Version 4.2.0
> > Aug 18 11:37:39.01: [ 6052]: MODEM set XON/XOFF/FLUSH: input ignored, 
> > output disabled
> > Aug 18 11:37:39.01: [ 6052]: <-- [4:ATA\r]
> > Aug 18 11:37:45.58: [ 6052]: --> [7:CONNECT]
> > Aug 18 11:37:45.58: [ 6052]: ANSWER: FAX CONNECTION  DEVICE '/dev/ttyS0'
> > Aug 18 11:37:45.58: [ 6052]: STATE CHANGE: ANSWERING -> RECEIVING
> > Aug 18 11:37:45.58: [ 6052]: MODEM input buffering enabled
> > Aug 18 11:37:45.58: [ 6052]: RECV FAX: begin
> > Aug 18 11:37:45.58: [ 6052]: MODEM input buffering disabled
> > Aug 18 11:37:45.58: [ 6052]: <-- HDLC<32:FF C0 04 AD 00 55 12 9E 36 86 
> > 62 82 1A 04 14 2E B6 94 04 6A A6 4E CE 96 F6 76 04 2C 74 4C 74 0C>
> > Aug 18 11:37:45.58: [ 6052]: <-- data [32]
> > Aug 18 11:37:45.58: [ 6052]: <-- data [2]
> > Aug 18 11:37:45.61: [ 6052]: --> [7:CONNECT]
> > Aug 18 11:37:45.61: [ 6052]: <-- HDLC<23:FF C0 02 86 96 26 A6 B6 96 2E 
> > 36 AE B2 04 86 CE 76 96 A2 04 1E 86 62>
> > Aug 18 11:37:45.61: [ 6052]: <-- data [23]
> > Aug 18 11:37:45.61: [ 6052]: <-- data [2]
> > Aug 18 11:37:45.64: [ 6052]: --> [7:CONNECT]
> > Aug 18 11:37:45.64: [ 6052]: <-- HDLC<10:FF C8 01 00 76 5F 23 01 FB C0>
> > Aug 18 11:37:45.64: [ 6052]: <-- data [10]
> > Aug 18 11:37:45.64: [ 6052]: <-- data [2]
> > Aug 18 11:37:48.19: [ 6052]: --> [0:]
> > Aug 18 11:37:48.19: [ 6052]: MODEM <Empty line>
> > Aug 18 11:37:48.19: [ 6052]: MODEM TIMEOUT: sending DIS/DCS frame
>
>
> Notice that HylaFAX is waiting for the modem to respond OK and gives up 
> at 11:37:48.19.
>
> It looks like a different modem (perhaps just modem firmware) to me.  
> The modem is behaving differently in your 4.2.0beta2 installation than 
> it does in your 4.2.0 installation.  If the modem were to behave the 
> same in latter as in the first then it would be fine.
>
> Lee.

--
Daniel Moreda García
Dpto. Sistemas

Einsa Multimedia, S.A.
Ctra. Campolongo a Monfero km 0,4 (Campolongo)
15614 Pontedeume (A Coruña)
España

http://www.einsamultimedia.com
Tlf: +34 981 454 015
Fax: +34 981 495 680

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