TRK19200 Modem

• Messages sorted by:[ date ][ thread ][ subject ][ author ]

This week I try to receive a fax from a
Windowsmachine. But I get some truble. My modem
(TRK19200)
could not etablish a connection with the ather
machine and my modem does not hanging up
corectly
the phoneline. After this the line was
occupated. I think this is not very cheap. But
where can I
find the bug ?
Greatings

Simon Schmidig
--------------------------------------------------------------------------

05/07 16:56:15 yS1  waiting...
05/07 17:11:15 yS1  checking if modem is still
alive
05/07 17:11:15 yS1  mdm_send: 'AT' -> OK
05/07 17:11:15 yS1  waiting...
05/07 17:24:02 yS1  lock not made: lock file
exists (pid=160)
--
05/07 17:26:47 yS1  mgetty: experimental test
release 1.1.18-Sep11
05/07 17:26:47 yS1  check for lockfiles
05/07 17:26:47 yS1  locking the line
05/07 17:26:48 yS1  lowering DTR to reset Modem
05/07 17:26:48 yS1  send: \dATQ0V1H0[0d]
05/07 17:26:49 yS1  waiting for ``OK'' ** found
**
05/07 17:26:49 yS1  send: ATS0=0Q0&D3&C1[0d]
05/07 17:26:49 yS1  waiting for ``OK'' ** found
**
05/07 17:26:49 yS1  mdm_send: 'AT+FCLASS=2' ->
OK
05/07 17:26:50 yS1  mdm_send: 'AT+FCLASS=0' ->
OK
05/07 17:26:50 yS1  mdm_send: 'AT+FAA=1;+FCR=1'
-> OK
05/07 17:26:50 yS1  mdm_send: 'AT+FBOR=0' -> OK
05/07 17:26:50 yS1  mdm_send:
'AT+FLID="+41(61)2817680"' -> OK
05/07 17:26:51 yS1  mdm_send:
'AT+FDCC=1,5,0,2,0,0,0,0' -> OK
05/07 17:26:51 yS1  waiting...
05/07 17:38:03 yS1  wfr: waiting for ``RING''
05/07 17:38:03 yS1  send: ATA[0d]
05/07 17:38:03 yS1  waiting for ``CONNECT''
05/07 17:38:09 yS1  found action string: ``FAX''

05/07 17:38:09 yS1  start fax receiver...
05/07 17:38:09 yS1  fax_wait_for(OK)
05/07 17:38:14 yS1  fax_id: '+FTSI:"
CABALUS"'
05/07 17:38:14 yS1  transmission par.: '+FDCS:
1,5,0,0,0,0,0,0'
05/07 17:40:09 yS1  Warning: got alarm signal!
05/07 17:40:09 yS1  mdm_read_byte: read returned
-1: Interrupted system call
05/07 17:40:09 yS1  mdm_get_line: cannot read
byte, return: Interrupted system call
05/07 17:40:09 yS1  >> The problem seen above
might be caused by a wrong value of the
05/07 17:40:09 yS1  >> 'switchbd' option in
'mgetty.config' (currently set to '0')
05/07 17:40:09 yS1  >> try using 'switchbd
19200'
05/07 17:40:09 yS1  fax_get_pages: no pages to
receive
05/07 17:40:13 ##### fax dev=ttyS1, pid=9712,
caller='none', name='', id='_
CABALUS_', +FHNG=-06, pages=0, time=00:02:06
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ ???

05/07 17:40:15 yS1  mdm_send: 'ATH0'
05/07 17:40:25 yS1  Warning: got alarm signal!
05/07 17:40:25 yS1  mdm_read_byte: read returned
-1: Interrupted system call
05/07 17:40:25 yS1  mdm_get_line: cannot read
byte, return: Interrupted system call -> ERROR
--
05/07 17:40:25 yS1  mgetty: experimental test
release 1.1.18-Sep11
05/07 17:40:25 yS1  check for lockfiles
05/07 17:40:25 yS1  locking the line
05/07 17:40:25 yS1  lowering DTR to reset Modem
05/07 17:40:26 yS1  send: \dATQ0V1H0[0d]
05/07 17:40:27 yS1  waiting for ``OK''
05/07 17:40:47 yS1  timeout in chat script,
waiting for `OK'
05/07 17:40:47 yS1  init chat timed out, trying
force-init-chat
05/07 17:40:47 yS1  send:
\d[10][03]\d\d\d+++\d\d\d[0d]\dATQ0V1H0[0d]
05/07 17:40:51 yS1  waiting for ``OK''
05/07 17:41:11 yS1  timeout in chat script,
waiting for `OK'
05/07 17:41:11 yS1  init chat failed,
exiting...: Interrupted system call
05/07 17:41:11 ##### failed in mg_init_data,
dev=ttyS1, pid=9721

-----------------------------------------------------------------------------