Re: [hylafax-users] MODEM <Empty line>

[Lee Howard <faxguy@xxxxxxxxxxxxxxxx>]

On 2005.02.18 08:33 Eduardo Páez Trujillo wrote:
> Hello everybody,
>
> I'm currently using hylafax-4.2.1 on a Linux RedHat 9.0. My modem is a
> U.S.
> Robotics 56K FAX EXT V4.11.2 (as shown at /var/log/messages). I had an
> old
> server with the same modem attached with hylafax-4.1.8 and Linux
> RedHat 9.0.
>
> At first, I tested hylafax sending a test fax from a Macintosh
> PowerBook G3
> Series (Wallstreet). It has an integrated 56K modem. Everything was
> fine.
>
> The problem is that sometimes, when a customer sends a fax, there are
> errors
> and the fax is not recieved. The following is part of the log:
>
> Feb 14 13:31:33.80: [ 3149]: SESSION BEGIN 000000024 5114457732
> Feb 14 13:31:33.80: [ 3149]: HylaFAX (tm) Version 4.2.1
> Feb 14 13:31:33.80: [ 3149]: <-- [13:AT+FCLASS=1A\r]
> Feb 14 13:31:39.09: [ 3149]: --> [7:CONNECT]
> Feb 14 13:31:39.09: [ 3149]: ANSWER: FAX CONNECTION  DEVICE
> '/dev/ttyS0'
> Feb 14 13:31:39.09: [ 3149]: RECV FAX: begin
> Feb 14 13:31:39.09: [ 3149]: <-- data [32]
> Feb 14 13:31:39.09: [ 3149]: <-- data [2]
> Feb 14 13:31:39.15: [ 3149]: --> [7:CONNECT]
> Feb 14 13:31:39.15: [ 3149]: <-- data [23]
> Feb 14 13:31:39.15: [ 3149]: <-- data [2]
> Feb 14 13:31:39.87: [ 3149]: --> [7:CONNECT]
> Feb 14 13:31:39.87: [ 3149]: <-- data [10]
> Feb 14 13:31:39.87: [ 3149]: <-- data [2]
> Feb 14 13:31:42.06: [ 3149]: --> [2:OK]
> Feb 14 13:31:42.06: [ 3149]: <-- [9:AT+FRH=3\r]
> Feb 14 13:31:45.16: [ 3149]: --> [0:]
> Feb 14 13:31:45.16: [ 3149]: MODEM <Empty line>
> Feb 14 13:31:45.16: [ 3149]: <-- data [1]
> Feb 14 13:31:45.17: [ 3149]: --> [2:OK]

It basically means that the modem doesn't think that the caller is a 
fax machine.  Specifically it means that the modem isn't able to detect 
a V.21 carrier.  If there *really* is a fax machine calling then the 
modem manufacturer would need to get involved to help you.  Since 
that's USR... I'd say you're stuck.

> There's a log that shows the following and maybe it's part of the
> problem.
> Dunno.
>
> Feb 15 14:31:13.17: [ 3069]: SESSION BEGIN 000000027 5114457732
> Feb 15 14:31:13.17: [ 3069]: HylaFAX (tm) Version 4.2.1
> Feb 15 14:31:13.17: [ 3069]: <-- [4:ATA\r]
> Feb 15 14:31:30.06: [ 3069]: --> [4:+FDM]
> Feb 15 14:31:30.06: [ 3069]: ANSWER: DATA CONNECTION
> Feb 15 14:31:30.06: [ 3069]: runGetty::initgroups: Operation not
> permitted

I believe that this is fixed in HylaFAX CVS HEAD.

> Feb 15 14:31:30.06: [ 3069]: GETTY: START "/sbin/agetty -h ttyS0
> dx_19200",
> pid 3739
> Feb 15 14:31:40.12: [ 3069]: GETTY: exit status 0400
> Feb 15 14:31:40.12: [ 3069]: SESSION END

In any case, it means that adaptive answer detected the call as a data 
call.  This is why you should not have AT+FAA=1 set.

> I've googled for these errors and I found no problem solved :(
> The big problem is that this error ocurred on my old server without
> any
> notice. I didn't even know that this was happening and almost half of
> the
> time this problem ocurred.

Which is why, beginning in 4.2.1, you'll see CALL entries in xferfaxlog.

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@xxxxxxxxxxx < /dev/null
 *To learn about commercial HylaFAX(tm) support, mail sales@xxxxxxxxx*