|
Hylafax Mailing List Archives
|
[Date Prev][Date Next][Thread Prev][Thread Next]
[Date Index]
[Thread Index]
Re: [hylafax-users] Adaptive Answer and Mgetty Issues
I have experienced this problem too. To get an authoritative answer on
this it is probably best to ask on the mgetty list, although I'd hate to
tell them that I'm using hylafax to launch mgetty ;). My guess is that
the -r option (same as the "direct y" configuration in mgetty.config)
which allows mgetty to answer on an already opened line is also causing
it to ignore carrier detect. So if for some reason the connection drops
ungracefully during the session mgetty won't know about it and keep
running on the tty. One possible solution to this is if all you need
is to establish ppp sessions you can start pppd directly from hylafax
without going through mgetty first.
George
On Fri, 2005-07-08 at 12:24 -0500, Nestor A. Diaz wrote:
> Hello, i have setup a modem for hylafax and everyting works fine, i use
> the cirrus configuration that comes with the default hylafax
> distribution, however i use it for adaptive answer, and it works nice,
> except that sometimes when the connection negotiation can not be made,
> mgetty do not release the line when the other party was unable to make
> the connection, it happen sometimes.
>
> Is there any way for mgetty to check if there is activity on the line ?
> in order to hang up ?
>
> If i switch off and on then, mgetty dieds and faxgetty can run again
> from initttab.
>
> The paramters i use are:
>
> CountryCode: 57
> AreaCode: 1
> FAXNumber: +57.1.XXXXXX
> LongDistancePrefix: 01
> InternationalPrefix: 001
> DialStringRules: etc/dialrules
> ServerTracing: 1
> SessionTracing: 11
> RecvFileMode: 0644
> LogFileMode: 0644
> DeviceMode: 0600
> RingsBeforeAnswer: 1
> SpeakerVolume: high
> GettyArgs: "-r -b -s %s %l"
> LocalIdentifier: "XXXXXX"
> TagLineFont: etc/lutRS18.pcf
> TagLineFormat: "From %%l|%c|Page %%P of %%T"
> MaxRecvPages: 25
> ModemType: Class1 # use this to supply a hint
> ModemRate: 57600 # rate for DCE-DTE communication
> ModemFlowControl: rtscts # RTS/CTS flow control assumed
> #
> ModemSoftFlowCmd: AT\Q1 # set desired flow control method
> ModemHardFlowCmd: AT\Q3 # set desired flow control method
> ModemSetupDTRCmd: AT&D3 # setup so DTR drop resets modem
> ModemSetupDCDCmd: AT&C1 # setup so DCD follows carrier
> ModemDialCmd: ATDT%s
> #
> AdaptiveAnswer: yes # enable adaptive answer
> AnswerRotary: "fax data" # answerfor fax, then data
> ModemAnswerCmd: AT+FCLASS=1;A # default is to answer as fax
> ModemAnswerDataCmd: ATH+FCLASS=0;A # hangup and answer as data
> Class1RecvIdentTimer: 20000 # timeout fax answer in 20 secs
> Class1SwitchingCmd: "<delay:7>" # silence between HDLC recv and
> trans
> #
> ModemMfrQueryCmd: AT+FMFR?
> ModemModelQueryCmd: AT+FMDL?
> ModemRevQueryCmd: AT+FREV?
>
> On /etc/mgetty/mgetty.config
>
> # modem controlled by faxgetty
> port ttyS0
> direct y
> # already accepted data call, do not reset
> toggle-dtr n
>
> And on login.config i have:
>
> /AutoPPP/ - a_ppp /usr/sbin/pppd auth -chap +pap login debug
> * - - /bin/login @
>
> I am not sure if the problem could be /bin/login .... that is not able
> to detect modem hangups
>
> This is the session (notice that the process was running for 8 hours,
> before a turn off/on the modem):
>
> Jul 05 21:15:52.16: [ 3138]: SESSION BEGIN 000000060 5716220143
> Jul 05 21:15:52.16: [ 3138]: HylaFAX (tm) Version 4.2.1
> Jul 05 21:15:52.16: [ 3138]: <-- [14:AT+FCLASS=1;A\r]
> Jul 05 21:15:55.28: [ 3138]: --> [7:CONNECT]
> Jul 05 21:15:55.28: [ 3138]: ANSWER: FAX CONNECTION DEVICE '/dev/ttyS0'
> Jul 05 21:15:55.28: [ 3138]: RECV FAX: begin
> Jul 05 21:15:55.28: [ 3138]: <-- data [32]
> Jul 05 21:15:55.28: [ 3138]: <-- data [2]
> Jul 05 21:15:57.16: [ 3138]: --> [7:CONNECT]
> Jul 05 21:15:57.16: [ 3138]: <-- data [23]
> Jul 05 21:15:57.16: [ 3138]: <-- data [2]
> Jul 05 21:15:57.91: [ 3138]: --> [7:CONNECT]
> Jul 05 21:15:57.91: [ 3138]: <-- data [10]
> Jul 05 21:15:57.91: [ 3138]: <-- data [2]
> Jul 05 21:15:58.40: [ 3138]: --> [2:OK]
> Jul 05 21:15:58.40: [ 3138]: <-- [9:AT+FRH=3\r]
> Jul 05 21:16:01.50: [ 3138]: --> [0:]
> Jul 05 21:16:01.50: [ 3138]: MODEM <Empty line>
> Jul 05 21:16:01.50: [ 3138]: <-- data [1]
> Jul 05 21:16:01.51: [ 3138]: --> [2:OK]
> Jul 05 21:16:01.51: [ 3138]: DELAY 1500 ms
> Jul 05 21:16:03.01: [ 3138]: <-- [9:AT+FTH=3\r]
> Jul 05 21:16:03.19: [ 3138]: --> [7:CONNECT]
> Jul 05 21:16:03.19: [ 3138]: <-- data [32]
> Jul 05 21:16:03.19: [ 3138]: <-- data [2]
> Jul 05 21:16:05.17: [ 3138]: --> [7:CONNECT]
> Jul 05 21:16:05.17: [ 3138]: <-- data [23]
> Jul 05 21:16:05.17: [ 3138]: <-- data [2]
> Jul 05 21:16:05.92: [ 3138]: --> [7:CONNECT]
> Jul 05 21:16:05.92: [ 3138]: <-- data [10]
> Jul 05 21:16:05.92: [ 3138]: <-- data [2]
> Jul 05 21:16:06.41: [ 3138]: --> [2:OK]
> Jul 05 21:16:06.41: [ 3138]: <-- [9:AT+FRH=3\r]
> Jul 05 21:16:09.51: [ 3138]: --> [0:]
> Jul 05 21:16:09.51: [ 3138]: MODEM <Empty line>
> Jul 05 21:16:09.51: [ 3138]: <-- data [1]
> Jul 05 21:16:09.52: [ 3138]: --> [2:OK]
> Jul 05 21:16:09.52: [ 3138]: DELAY 1500 ms
> Jul 05 21:16:11.02: [ 3138]: <-- [9:AT+FTH=3\r]
> Jul 05 21:16:11.20: [ 3138]: --> [7:CONNECT]
> Jul 05 21:16:11.20: [ 3138]: <-- data [32]
> Jul 05 21:16:11.20: [ 3138]: <-- data [2]
> Jul 05 21:16:13.18: [ 3138]: --> [7:CONNECT]
> Jul 05 21:16:13.18: [ 3138]: <-- data [23]
> Jul 05 21:16:13.18: [ 3138]: <-- data [2]
> Jul 05 21:16:13.93: [ 3138]: --> [7:CONNECT]
> Jul 05 21:16:13.93: [ 3138]: <-- data [10]
> Jul 05 21:16:13.93: [ 3138]: <-- data [2]
> Jul 05 21:16:14.42: [ 3138]: --> [2:OK]
> Jul 05 21:16:14.42: [ 3138]: <-- [9:AT+FRH=3\r]
> Jul 05 21:16:17.52: [ 3138]: --> [0:]
> Jul 05 21:16:17.52: [ 3138]: MODEM <Empty line>
> Jul 05 21:16:17.52: [ 3138]: <-- data [1]
> Jul 05 21:16:17.53: [ 3138]: --> [2:OK]
> Jul 05 21:16:17.53: [ 3138]: RECV FAX: No answer (T.30 T1 timeout)
> Jul 05 21:16:17.53: [ 3138]: RECV FAX: end
> Jul 05 21:16:17.53: [ 3138]: <-- [15:ATH+FCLASS=0;A\r]
> Jul 05 21:17:17.44: [ 3138]: --> [13:CONNECT 57600]
> Jul 05 21:17:17.44: [ 3138]: ANSWER: DATA CONNECTION
> Jul 05 21:17:17.44: [ 3138]: runGetty::initgroups: Operation not permitted
What's this? I thought we fixed this.
> Jul 05 21:17:17.44: [ 3138]: GETTY: START "/sbin/mgetty -r -b -s 57600 ttyS0", pid 21032
> Jul 06 10:26:58.03: [ 3138]: GETTY: exit status 05000
> Jul 06 10:26:58.05: [ 3138]: SESSION END
>
> Thanks for your help.
>
____________________ 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*
