Muchas gracias a Carlos! Got it in one!
For some reason, faxgetty doesn't work completely right when the "device"
specified is a symbolic link. I changed it from /dev/modem to /dev/cua2
and it worked fine.
The funny thing is that faxgetty clearly did open the port even when it
was directed to /dev/modem (a symlink to /dev/cua2), because it opened the
port successfully and correctly got the modem's ID string...
Anyway, it works now for incoming data calls. I'll try an incoming fax
call in a minute, and I just sent an outgoing fax which "faxstat -d"
reports worked correctly (though my "faxsend -R ..." failed to generate a
success email message; maybe it isn't configured for the right mail
sending binary path or something?).
Well, receiving didn't quite work (got the banner line from the sending
fax, but no data on the actual faxed page of paper).. but I'll work on
that another time.
Again, thanks to Carlos for his suggestion!
Jay
On Sun, 24 May 1998, J. Carlos Cristobal wrote:
> > 2. And, once it is all set up and a faxgetty is running on /dev/modem
> > (symlinked to /dev/cua2), faxgetty never answers the phone when incoming
> > calls ring :( I haven't tried sending a fax out yet.
>
> I think here is the mistake, I installed a HylaFAX on RH too, but it never worked
>that
> way, it said that it was waiting the modem to answer but it never happened use ttys*
> instead of that, someone from the HylaFAX told that to me.
>
> Hope this helps.
Jay Vassos-Libove [EMAIL PROTECTED]
+1 404 876 8190 home +1 404 705 2867 work
Atlanta, GA 30308 U.S.A.
--
PLEASE read the Red Hat FAQ, Tips, Errata and the MAILING LIST ARCHIVES!
http://www.redhat.com/RedHat-FAQ /RedHat-Errata /RedHat-Tips /mailing-lists
To unsubscribe: mail [EMAIL PROTECTED] with
"unsubscribe" as the Subject.
