Re: flexfax: Cannot Receive Faxes

["Chua Choon Hian" <choonhian@hotmail.com>]

Thanks Nico for you help.  You are right.  Something did screwed up in the
config.cuaa2 file.  But I have already over-written the old one with the
config/usr-rts.  It is working now.

BTW, I am using FreeBSD and not Linux.


----- Original Message -----
From: Nico Kadel-Garcia <raoul@cirl.meei.harvard.edu>
To: Chua Choon Hian <choonhian@hotmail.com>
Sent: Friday, July 09, 1999 9:07 AM
Subject: Re: flexfax: Cannot Receive Faxes


> -----BEGIN PGP SIGNED MESSAGE-----
>
> Choon, can you please send questions like this to the list? That way,
other
> people can see if they have the same problem or the same answers.
>
> On Fri, 9 Jul 1999, Chua Choon Hian wrote:
>
> > I am using the USR Sportster Internal Modem 33.6.  I overwrite the
> > config.cuaa2 file with config/usr-rts file and ruin faxmodem for cuaa2.
I
> > have tested it ok before I shifted it to another office.
>
> config.cuaa2? Are you using something special like a serial port expander,
> or did you mean to type "config.cua2?
>
> If you meant "config.cua2", be aware that the use of "/dev/cu*" is
> being dropped in the latest and future RedHat releases: the "/dev/cu*"
> was used for dial-out use, while "/dev/tty*" was used for dial-in
> under some operating systems. Packages like HylaFAX and mgetty handle
> choosing dial-in vs. dial-out themselves, and that old trick never worked
> very well, so they will use "/dev/ttyS[0-3]" instead in the future.
>
> > Also I have the line to the modem and fax machine to the phone jack of
the
> > modem.  I am just wondering if the faxmodem and fax machine are
conflicting
> > when answering a fax?
>
> This seems unlikely, but easy to test: unplug the fax machine
> connection. I suggest that something is screwed up in the
> "config.cua2" file, setting the modem in a permanentt "answer as data
> only" mode. Post the config file, and compare it to the standard
> usr-rts file.
>
> Also, there is in general no need to "overwite the config.caa2 file
> with the config/usr-rts" file. Re-running "faxaddmodem", not the
> "faxmodem" command you mentioned, will doublecheck your old settings
> and reset them based on the "config/usr-rts" file that matches the
> manufacturer and model identification codes sent by your modem. In
> fact, you might be best off entirely deleting the old "config.cua2"
> file and just running faxaddmodem, then checking the results of that.
>
> I wonder if you had set up your old config files to use the modem for
> dial-in only, and accidentally left it in? Or whether you have
> something running on "/dev/modem", and have that symbolically linked
> to "/dev/cua2"?
>
> > All out-going faxes are OK.
>
> That is re-assuring!
>
> > From: Nico Kadel-Garcia <raoul@cirl.meei.harvard.edu>
> > To: Chua Choon Hian <choonhian@hotmail.com>
> > Cc: <flexfax@sgi.com>
> > Sent: Thursday, July 08, 1999 8:54 PM
> > Subject: Re: flexfax: Cannot Receive Faxes
> >
> >
> > > -----BEGIN PGP SIGNED MESSAGE-----
> > >
> > > On Thu, 8 Jul 1999, Chua Choon Hian wrote:
> > >
> > > > Hi,
> > > >
> > > > I keep getting this in my logs.  And I just can't receive faxes.
Does
> > > > anyone have any idea?
> > > >
> > > > Jul 08 11:21:37.31: [  223]: SESSION BEGIN 00000145 6039455828
> > > > Jul 08 11:21:37.31: [  223]: <-- [13:AT+FCLASS=1A\r]
> > > > Jul 08 11:21:55.58: [  223]: --> [4:DATA]
> > > > Jul 08 11:21:55.58: [  223]: ANSWER: DATA CONNECTION
> > > > Jul 08 11:21:55.61: [  223]: GETTY: START "/usr/libexec/getty -h
cuaa2
> > > > dx_38400", pid 3221
> > > > Jul 08 11:21:55.61: [  223]: GETTY: exit status 0400
> > > > Jul 08 11:21:55.61: [  223]: SESSION END
> > >
> > > A *hint* as to what modem, what version of HylaFAX, and your settings
> > > would be helpful. It looks like your modem may be set to answer
> > > all calls as data, since it is trying to start up a getty.
>
>
> Nico Kadel-Garcia
> Senior Engineer, CIRL
> Mass. Eye and Ear Infirmary
> raoul@cirl.meei.harvard.edu
>
> -----BEGIN PGP SIGNATURE-----
> Version: 2.6.2
>
> iQCVAwUBN4VLPT/+ItycgIJRAQHYnwP/SLXbFPNJFx6gVnc3tAsoFe3FO+pFLJRG
> x0Bo/qLI3dM2gBupNwAurnMy0K1frbYVx0qJF/kEyubK6D5MaIjMoA8RgkdiSxaS
> QihVcE+m/Bz/KQ118g5NTnOFWgKXXwfRgXaku166Mjffx8JvjIwtjfr8YZTx4XTo
> 2gz2936gSXo=
> =P8ZJ
> -----END PGP SIGNATURE-----
>
>