Hylafax Mailing List Archives
|
[Date Prev][Date Next][Thread Prev][Thread Next]
[Date Index]
[Thread Index]
Re: [hylafax-users] waiting for second page
On 2002.06.22 15:51 Michael Berg wrote:
> This faxes move in the faxes and If no more faxes are moved in, then the
> fax hangup.
> And now the problem for my hylafaxserver. He receive from the remotefax
> a MBS(more pages follow) signal, because the remotefax fill take care
> the connection.
> But the user on the remotefax isnot sending any more faxes. After an few
> time my faxserver is getting an timeout error and deleting the received
> pages.
> Here the logfile:
>
> Jun 21 17:29:08.78: [ 432]: SESSION BEGIN 00000124 493438153970
> Jun 21 17:29:08.80: [ 432]: <-- [4:ATA\r]
Firstly, what version of HylaFAX are you using?
> Jun 21 17:29:10.50: [ 432]: --> [3:FAX]
> Jun 21 17:29:10.50: [ 432]: ANSWER: FAX CONNECTION
> Jun 21 17:29:10.50: [ 432]: MODEM input buffering enabled
> Jun 21 17:29:10.50: [ 432]: RECV FAX: begin
> Jun 21 17:29:10.50: [ 432]: RECV FAX: CDPN
> Jun 21 17:29:16.26: [ 432]: --> [5:+FCON]
Secondly, what kind of modem are you using and have you tried using Class
1?
....
> Jun 21 17:29:58.55: [ 432]: --> [17:+FPTS: 1,2219,0,0]
> Jun 21 17:29:59.57: [ 432]: --> [8:+FHNG: 0]
> Jun 21 17:29:59.57: [ 432]: REMOTE HANGUP: Normal and proper end of
> connection (code 0)
> Jun 21 17:30:01.40: [ 432]: --> [2:OK]
> Jun 21 17:30:01.40: [ 432]: RECV recv MPS (more pages, same document)
I believe that this shows that HylaFAX misread +FHNG as +FET. Why we did
not get an +FET signal is troubling, though. So, what we have here is a
bug both in HylaFAX and possibly in the remote's protocol usage, too. If
you're using HylaFAX 4.1.1 or newer it may be worth looking into -
otherwise I'd recommend an upgrade first.
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@hylafax.org < /dev/null