Hylafax Mailing List Archives
|
[Date Prev][Date Next][Thread Prev][Thread Next]
[Date Index]
[Thread Index]
Re: Problem viewing(recieving?)
> Feb 21 10:25:41.83: [ 449]: REMOTE wants 1-D MR
> Feb 21 10:25:41.83: [ 449]: --> [7:CONNECT]
> Feb 21 10:25:41.83: [ 449]: RECV: begin page
> Feb 21 10:25:41.83: [ 449]: RECV: send trigger 021
> Feb 21 10:25:41.83: [ 449]: <-- data [1]
> Feb 21 10:26:24.49: [ 449]: RECV: 17 total lines, 0 bad lines, 0
> consecutive bad lines
> Feb 21 10:26:24.50: [ 449]: --> [17:+FPTS: 1,2219,0,0]
Someone suggested a local flow control problem, although I can't understand
why that should produce this result. The timing is consistent with a
fairly full detailed page and the lack of errors suggest that the modem
didn't send the lines, rather than that there was an overrun.
>
> In another mail you recomended I rm the /dev/modem and point faxgetty to
> the real device (/dev/cua1 in this case)
If you don't use the same device name for all applications, locking will
fail and cu could well get into difficulties.
> I've done this. Everything is as it where, and I still dont get hfaxd
> when I run ps ax | grep fax - which was one of my questions.
> It seems as if this daemon isn't running..? Is that not a problem?
The daemon should be running - you need to look for error messages during
the system startup.
> PS: My modem is a UCOM Skylink v.34 (33600bps) with a Rockwell chipset.
>
Unfortunately the only machine I have with Hylafax running is using
a Multitech and the Rockwell modem I have has traded voice capability for
Class 2 fax, so I can't reproduce your configuration.