HylaFAX The world's most advanced open source fax server

[Date Prev][Date Next][Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: [hylafax-users] fax / data recognition



Now my configuration as
* config.ttyS1 file
        "GettyArgs:      -b -r -s %s %l" 
* mgetty.config file
        port ttyS1
        toggle-dtr n
I still use mgetty. It is working in this situation "AnswerRotary:           "data"" in config.ttyS1. However, it is hang in "AnswerRotary:           "fax data"" in config.ttyS1. the log file as 
* for hylafax
Feb 26 17:38:33.03: [27922]: SESSION BEGIN 00000091 852027543501
Feb 26 17:38:33.03: [27922]: HylaFAX (tm) Version 4.1.5
Feb 26 17:38:33.03: [27922]: <-- [14:AT+FCLASS=1;A\r]
Feb 26 17:38:37.70: [27922]: --> [7:CONNECT]
Feb 26 17:38:37.70: [27922]: ANSWER: FAX CONNECTION  DEVICE '/dev/ttyS1'
Feb 26 17:38:37.70: [27922]: RECV FAX: begin
Feb 26 17:38:37.73: [27922]: <-- data [23]
Feb 26 17:38:37.73: [27922]: <-- data [2]
Feb 26 17:38:39.57: [27922]: --> [7:CONNECT]
Feb 26 17:38:39.57: [27922]: <-- data [10]
Feb 26 17:38:39.57: [27922]: <-- data [2]
Feb 26 17:38:40.03: [27922]: --> [2:OK]
Feb 26 17:38:40.03: [27922]: <-- [9:AT+FRH=3\r]
Feb 26 17:38:43.13: [27922]: --> [0:]
Feb 26 17:38:43.13: [27922]: MODEM <Empty line>
Feb 26 17:38:43.13: [27922]: <-- data [1]
Feb 26 17:38:43.14: [27922]: --> [2:^P^C]
Feb 26 17:38:43.14: [27922]: --> [2:OK]
Feb 26 17:38:43.14: [27922]: RECV FAX: No answer (T.30 T1 timeout)
Feb 26 17:38:43.14: [27922]: RECV FAX: end
Feb 26 17:38:43.14: [27922]: <-- [15:ATH+FCLASS=0;A\r]
Feb 26 17:38:56.28: [27922]: --> [15:CONNECT 1200/75]
Feb 26 17:38:56.28: [27922]: ANSWER: DATA CONNECTION
Feb 26 17:38:56.28: [27922]: GETTY: START "/sbin/mgetty -b -r -s 19200 ttyS1", pid 27926
Feb 26 17:39:09.09: [27922]: GETTY: exit status 05000
Feb 26 17:39:09.09: [27922]: SESSION END
* /var/log/mgetty.log.ttyS1
--
02/26 17:38:56 yS1  mgetty: experimental test release 1.1.28-Jan10
02/26 17:38:56 yS1  check for lockfiles
02/26 17:38:56 yS1  huh? It's *our* lock file!
02/26 17:38:56 yS1  locking the line
02/26 17:38:56 yS1  we *have* the line!
02/26 17:38:56 yS1  WARNING: DCD line still active, check modem settings (AT&Dx)
02/26 17:39:04 yS1  waiting...
02/26 17:39:09 ##### failed dev=ttyS1, pid=27926, got signal 1, exiting
* /var/log/messages
Feb 26 17:38:25 ThinWst2 FaxGetty[27922]: MODEM E.C.  VERSION : T 288/
Feb 26 17:38:37 ThinWst2 FaxGetty[27922]: ANSWER: FAX CONNECTION  DEVICE '/dev/ttyS1'
Feb 26 17:38:56 ThinWst2 FaxGetty[27922]: ANSWER: DATA CONNECTION
Feb 26 17:38:56 ThinWst2 FaxGetty[27922]: GETTY: START "/sbin/mgetty -b -r -s 19200 ttyS1", pid 27926
Feb 26 17:39:09 ThinWst2 mgetty[27926]: failed dev=ttyS1, pid=27926, got signal 1, exiting
Feb 26 17:39:09 ThinWst2 FaxGetty[27922]: GETTY: exit status 05000
Feb 26 17:39:16 ThinWst2 FaxGetty[27922]: MODEM E.C.  VERSION : T 288/
Could you please give me a suggestion?
thanks
yan


______________________________________________________
HKDict - the latest and easy to use Online Dictionary
http://www.hkdict.com



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




Project hosted by iFAX Solutions