reports bad fax receive

Christoph Kukulies (kuku@gilberto.physik.RWTH-Aachen.DE)
Thu, 14 Jan 1999 09:39:32 +0100



I installed mgetty-1.1.16 on a FreeBSD 2.2.7 machine here yesterday,
enabled mgetty in /etc/ttys and did a login via /dev/cuaa1 (the
device mgetty was running on) and that login worked fine.

This morning I found a mail in my inbasket from root of the above
machine (it was sent to me as the admin because the user faxadmin didn't
exist - I fixed that meanwhile) tellling the following:


Communication parameters:                                                   
    Resolution : normal
    Bit Rate   : 2400                                                
    Page Width : 1728 pixels
    Page Length: A4 (297 mm)
    Compression: 0 (1d mod Huffman)
    Error Corr.: none
    Scan Time  : 0                                                        

Reception Time : 02:14


The fax receive was *not* fully successful
The Modem returned +FHNG: -6                
                   (TIMEOUT waiting for modem response (int.))


regards, your modem subsystem.

Here is my mgetty.config:


port cuaa1
debug 4
fax-id xx xxxx xxxxx
speed 38400
direct NO
blocking NO
port-owner uucp
port-group uucp
port-mode 0660
toggle-dtr YES
toggle-dtr-waittime 500
data-only NO
fax-only NO
modem-type auto
init-chat "" ATS0=0Q0&D3&C1 OK
modem-check-time 3600
rings 1
answer-chat "" ATA CONNECT \c \r
answer-chat-timeout 80
autobauding NO
ringback NO
ringback-time 30
ignore-carrier false
issue-file /etc/issue
prompt-waittime 500
login-prompt @!login:
login-time 240
diskspace 1024
notify 
fax-owner uucp
fax-group modem
fax-mode 0660

And here is the log:

--
01/13 19:21:31 aa1  mgetty: experimental test release 1.1.16-Jul05
01/13 19:21:31 aa1  check for lockfiles
01/13 19:21:31 aa1  locking the line
01/13 19:21:34 aa1  lowering DTR to reset Modem
01/13 19:21:34 aa1  send: ATS0=0Q0&D3&C1[0d]
01/13 19:21:34 aa1  waiting for ``OK'' ** found **
01/13 19:21:34 aa1  mdm_send: 'ATI'
01/13 19:21:35 aa1  unknown numerical modem id 144
01/13 19:21:35 aa1  mdm_send: 'AT+FCLASS=2.0' -> ERROR
01/13 19:21:35 aa1  mdm_send: 'AT+FCLASS=2' -> OK
01/13 19:21:35 aa1  mdm_send: 'AT+FCLASS=0' -> OK
01/13 19:21:35 aa1  mdm_send: 'AT+FAA=1;+FCR=1' -> OK
01/13 19:21:35 aa1  mdm_send: 'AT+FBOR=0' -> OK
01/13 19:21:35 aa1  mdm_send: 'AT+FLID="49 xxxx xxxxx"' -> OK
01/13 19:21:35 aa1  mdm_send: 'AT+FDCC=1,5,0,2,0,0,0,0' -> OK
01/13 19:21:36 aa1  waiting...
01/13 19:22:09 aa1  wfr: waiting for ``RING''
01/13 19:22:09 aa1  send: ATA[0d]
01/13 19:22:09 aa1  waiting for ``CONNECT'' ** found **
01/13 19:22:26 aa1  send: 
01/13 19:22:26 aa1  waiting for ``_'' ** found **
01/13 19:22:33 ##### data dev=cuaa1, pid=3794, caller='none', conn='14400/LAPM-V', name='', cmd='/usr/bin/login', user='chris'

--
01/13 19:22:45 aa1  mgetty: experimental test release 1.1.16-Jul05
01/13 19:22:45 aa1  check for lockfiles
01/13 19:22:45 aa1  locking the line
01/13 19:22:48 aa1  lowering DTR to reset Modem
01/13 19:22:48 aa1  send: ATS0=0Q0&D3&C1[0d]
01/13 19:22:48 aa1  waiting for ``OK''
01/13 19:23:08 aa1  timeout in chat script, waiting for `OK'
01/13 19:23:08 aa1  init chat timed out, trying force-init-chat
01/13 19:23:08 aa1  send: \d[10][03]\d\d\d+++\d\d\d[0d]\dATQ0V1H0[0d]
01/13 19:23:12 aa1  waiting for ``OK'' ** found **
01/13 19:23:13 aa1  send: ATS0=0Q0&D3&C1[0d]
01/13 19:23:13 aa1  waiting for ``OK'' ** found **
01/13 19:23:13 aa1  mdm_send: 'ATI'
01/13 19:23:14 aa1  unknown numerical modem id 144
01/13 19:23:14 aa1  mdm_send: 'AT+FCLASS=2.0' -> ERROR
01/13 19:23:14 aa1  mdm_send: 'AT+FCLASS=2' -> OK
01/13 19:23:14 aa1  mdm_send: 'AT+FCLASS=0' -> OK
01/13 19:23:14 aa1  mdm_send: 'AT+FAA=1;+FCR=1' -> OK
01/13 19:23:14 aa1  mdm_send: 'AT+FBOR=0' -> OK
01/13 19:23:14 aa1  mdm_send: 'AT+FLID="49 xxxx xxxxx"' -> OK
01/13 19:23:14 aa1  mdm_send: 'AT+FDCC=1,5,0,2,0,0,0,0' -> OK
01/13 19:23:15 aa1  waiting...
01/13 19:31:07 ##### failed dev=cuaa1, pid=3807, got signal 15, exiting

--
01/13 19:40:09 aa1  mgetty: experimental test release 1.1.16-Jul05
01/13 19:40:09 aa1  check for lockfiles
01/13 19:40:09 aa1  locking the line
01/13 19:40:11 aa1  lowering DTR to reset Modem
01/13 19:40:12 aa1  send: ATS0=0Q0&D3&C1[0d]
01/13 19:40:12 aa1  waiting for ``OK'' ** found **
01/13 19:40:12 aa1  mdm_send: 'ATI'
01/13 19:40:12 aa1  unknown numerical modem id 144
01/13 19:40:12 aa1  mdm_send: 'AT+FCLASS=2.0' -> ERROR
01/13 19:40:12 aa1  mdm_send: 'AT+FCLASS=2' -> OK
01/13 19:40:12 aa1  mdm_send: 'AT+FCLASS=0' -> OK
01/13 19:40:13 aa1  mdm_send: 'AT+FAA=1;+FCR=1' -> OK
01/13 19:40:13 aa1  mdm_send: 'AT+FBOR=0' -> OK
01/13 19:40:13 aa1  mdm_send: 'AT+FLID="49 xxxx xxxxx"' -> OK
01/13 19:40:13 aa1  mdm_send: 'AT+FDCC=1,5,0,2,0,0,0,0' -> OK
01/13 19:40:13 aa1  waiting...
01/13 20:40:13 aa1  checking if modem is still alive
01/13 20:40:14 aa1  mdm_send: 'AT' -> OK
01/13 20:40:14 aa1  waiting...
01/13 21:40:14 aa1  checking if modem is still alive
01/13 21:40:14 aa1  mdm_send: 'AT' -> OK
01/13 21:40:14 aa1  waiting...
01/13 22:40:14 aa1  checking if modem is still alive
01/13 22:40:15 aa1  mdm_send: 'AT' -> OK
01/13 22:40:15 aa1  waiting...
01/13 23:40:15 aa1  checking if modem is still alive
01/13 23:40:15 aa1  mdm_send: 'AT' -> OK
01/13 23:40:15 aa1  waiting...
01/14 00:40:15 aa1  checking if modem is still alive
01/14 00:40:16 aa1  mdm_send: 'AT' -> OK
01/14 00:40:16 aa1  waiting...
01/14 01:40:16 aa1  checking if modem is still alive
01/14 01:40:16 aa1  mdm_send: 'AT' -> OK
01/14 01:40:16 aa1  waiting...
01/14 02:40:16 aa1  checking if modem is still alive
01/14 02:40:17 aa1  mdm_send: 'AT' -> OK
01/14 02:40:17 aa1  waiting...
01/14 03:40:17 aa1  checking if modem is still alive
01/14 03:40:17 aa1  mdm_send: 'AT' -> OK
01/14 03:40:17 aa1  waiting...
01/14 04:40:17 aa1  checking if modem is still alive
01/14 04:40:18 aa1  mdm_send: 'AT' -> OK
01/14 04:40:18 aa1  waiting...
01/14 05:40:18 aa1  checking if modem is still alive
01/14 05:40:18 aa1  mdm_send: 'AT' -> OK
01/14 05:40:18 aa1  waiting...
01/14 06:40:18 aa1  checking if modem is still alive
01/14 06:40:19 aa1  mdm_send: 'AT' -> OK
01/14 06:40:19 aa1  waiting...
01/14 07:40:19 aa1  checking if modem is still alive
01/14 07:40:19 aa1  mdm_send: 'AT' -> OK
01/14 07:40:19 aa1  waiting...
01/14 08:31:27 aa1  wfr: waiting for ``RING''
01/14 08:31:27 aa1  send: ATA[0d]
01/14 08:31:27 aa1  waiting for ``CONNECT''
01/14 08:31:41 aa1  found action string: ``FAX''
01/14 08:31:41 aa1  start fax receiver...
01/14 08:31:41 aa1  can't get group 'modem': Undefined error: 0
01/14 08:31:41 aa1  fax_wait_for(OK)
01/14 08:33:41 aa1  Warning: got alarm signal!
01/14 08:33:41 aa1  mdm_read_byte: read returned -1: Interrupted system call
01/14 08:33:41 aa1  mdm_get_line: cannot read byte, return: Interrupted system call
01/14 08:33:41 aa1  >> The problem seen above might be caused by a wrong value of the
01/14 08:33:41 aa1  >> 'switchbd' option in 'mgetty.config' (currently set to '0')
01/14 08:33:41 aa1  >> try using 'switchbd 19200'
01/14 08:33:41 aa1  fax_get_pages: no pages to receive
01/14 08:33:44 aa1  fax_notify_mail: mailer exit status: 17152_
01/14 08:33:44 ##### fax dev=cuaa1, pid=305, caller='none', name='', id='', +FHNG=-06, pages=0, time=00:02:14


01/14 08:33:44 aa1  system() failed: Interrupted system call
01/14 08:33:46 aa1  mdm_send: 'ATH0' -> OK
--
01/14 08:33:46 aa1  mgetty: experimental test release 1.1.16-Jul05
01/14 08:33:46 aa1  check for lockfiles
01/14 08:33:46 aa1  locking the line
01/14 08:33:49 aa1  lowering DTR to reset Modem
01/14 08:33:50 aa1  send: ATS0=0Q0&D3&C1[0d]
01/14 08:33:50 aa1  waiting for ``OK'' ** found **
01/14 08:33:50 aa1  mdm_send: 'ATI'
01/14 08:33:50 aa1  unknown numerical modem id 144
01/14 08:33:50 aa1  mdm_send: 'AT+FCLASS=2.0' -> ERROR
01/14 08:33:50 aa1  mdm_send: 'AT+FCLASS=2' -> OK
01/14 08:33:50 aa1  mdm_send: 'AT+FCLASS=0' -> OK
01/14 08:33:50 aa1  mdm_send: 'AT+FAA=1;+FCR=1' -> OK
01/14 08:33:51 aa1  mdm_send: 'AT+FBOR=0' -> OK
01/14 08:33:51 aa1  mdm_send: 'AT+FLID="49 xxxx xxxxx"' -> OK
01/14 08:33:51 aa1  mdm_send: 'AT+FDCC=1,5,0,2,0,0,0,0' -> OK
01/14 08:33:51 aa1  waiting...
01/14 08:45:22 aa1  wfr: waiting for ``RING''
01/14 08:45:22 aa1  send: ATA[0d]
01/14 08:45:22 aa1  waiting for ``CONNECT''
01/14 08:45:36 aa1  found action string: ``FAX''
01/14 08:45:36 aa1  start fax receiver...
01/14 08:45:36 aa1  can't get group 'modem': Undefined error: 0
01/14 08:45:36 aa1  fax_wait_for(OK)
01/14 08:47:36 aa1  Warning: got alarm signal!
01/14 08:47:36 aa1  mdm_read_byte: read returned -1: Interrupted system call
01/14 08:47:36 aa1  mdm_get_line: cannot read byte, return: Interrupted system call
01/14 08:47:36 aa1  >> The problem seen above might be caused by a wrong value of the
01/14 08:47:36 aa1  >> 'switchbd' option in 'mgetty.config' (currently set to '0')
01/14 08:47:36 aa1  >> try using 'switchbd 19200'
01/14 08:47:36 aa1  fax_get_pages: no pages to receive
01/14 08:47:40 aa1  fax_notify_mail: mailer exit status: 17152_
01/14 08:47:40 ##### fax dev=cuaa1, pid=1093, caller='none', name='', id='', +FHNG=-06, pages=0, time=00:02:14


01/14 08:47:40 aa1  system() failed: Interrupted system call
01/14 08:47:41 aa1  mdm_send: 'ATH0' -> OK
--
01/14 08:47:42 aa1  mgetty: experimental test release 1.1.16-Jul05
01/14 08:47:42 aa1  check for lockfiles
01/14 08:47:42 aa1  locking the line
01/14 08:47:45 aa1  lowering DTR to reset Modem
01/14 08:47:45 aa1  send: ATS0=0Q0&D3&C1[0d]
01/14 08:47:45 aa1  waiting for ``OK'' ** found **
01/14 08:47:46 aa1  mdm_send: 'ATI'
01/14 08:47:46 aa1  unknown numerical modem id 144
01/14 08:47:46 aa1  mdm_send: 'AT+FCLASS=2.0' -> ERROR
01/14 08:47:46 aa1  mdm_send: 'AT+FCLASS=2' -> OK
01/14 08:47:46 aa1  mdm_send: 'AT+FCLASS=0' -> OK
01/14 08:47:46 aa1  mdm_send: 'AT+FAA=1;+FCR=1' -> OK
01/14 08:47:46 aa1  mdm_send: 'AT+FBOR=0' -> OK
01/14 08:47:46 aa1  mdm_send: 'AT+FLID="49 xxxx xxxxx"' -> OK
01/14 08:47:47 aa1  mdm_send: 'AT+FDCC=1,5,0,2,0,0,0,0' -> OK
01/14 08:47:47 aa1  waiting...

---
Any ideas?
-- 
Chris Christoph P. U. Kukulies kuku@gil.physik.rwth-aachen.de