![]() |
We're having a fair problem with our general setup. HylaFAX4.01-pl2, mgetty-1.0.0 and faxgetty? Netcomm Roadster II modems on Linux 2.2.9 Here is the relevant config.ttyE7 file... GettyArgs: "-s 115200 -x 4" ModemType: Class2 # use class 2 interface ModemRate: 38400 ModemFlowControl: rtscts # default #ModemResetCmds: AT&F2 # what you want for a Supra ModemNoFlowCmd: AT&K # disable flow control cmd ModemHardFlowCmd: AT&K3 # hardware flow control cmd ModemSoftFlowCmd: AT&K4 # software flow control cmd ModemSetupDTRCmd: AT&D3 # DTR off causes modem to reset #ModemSetupDTRCmd: AT&D2S25=1S38=0 # Dynalink 1414VE needs this ModemSetupDCDCmd: AT&C1 # DCD follows carrier ModemSetupAACmd: AT+FAA=1+FCLASS=0 # enable in current class ModemSendFillOrder: LSB2MSB # as expected ModemRecvFillOrder: MSB2LSB # opposite of what makes sense ModemAnswerFaxBeginCmd: "<19200><xon>" # modem switches on fax receive ModemDialCmd: ATDT0%s # escape our PABX 1 - we cannot receive faxes 2 - mgetty works with wins clients, not linux pppd callers 3 - faxgetty is not calling mgetty properly 1 - Simply put, dialling a number results in a "SEND FAILED : Ring detect without successful handshake" error. faxgetty is installed on the incoming line and seems to distinguish between a data and fax connection. 2 - Anyone know of the proper options pppd callers should include? ;) 3 - When I say "not calling properly" I mean faxgetty starts, recognizes the DATA CONNECTION (according to the logs) but when I check it dialling via windows, the popup screen is entirely black and I get disconnected from the server. /sbin/getty is a symbolic link to /usr/local/sbin/mgetty, and the GettyArgs get picked up fine in the logs. Oct 26 16:48:29.66: [ 5409]: SESSION BEGIN 00000377 6103610394880184 Oct 26 16:48:29.67: [ 5409]: <-- [4:ATA\r] Oct 26 16:48:50.95: [ 5409]: --> [4:DATA] Oct 26 16:48:50.95: [ 5409]: ANSWER: DATA CONNECTION Oct 26 16:48:50.96: [ 5409]: GETTY: START "/sbin/getty -s 115200 -x 4", pid 28221 Oct 26 16:48:51.11: [ 5409]: GETTY: exit status 01000 Oct 26 16:48:51.11: [ 5409]: SESSION END Any help appreciated David