![]() |
On Sat, 28 Feb 1998, Philippe JAOUEN wrote: > hylafax 4.0pl1-1 on Linux Redhat 4.2 work fine for fax in/out on my > server. > It is OK for outbound calls: cu uucp ppp > > My problem is that I cannot receive data calls [snip] > /var/log/messages > ... > Feb 16 16:13:45 net FaxGetty[9516]: <-- [12:AT+FCLASS=2\r] > Feb 16 16:13:45 net FaxGetty[9516]: --> [2:OK] > Feb 16 16:13:45 net FaxGetty[9516]: <-- [9:AT+FMFR?\r] > Feb 16 16:13:45 net FaxGetty[9516]: --> [20:ROCKWELL ] > Feb 16 16:13:45 net FaxGetty[9516]: --> [2:OK] > Feb 16 16:13:45 net FaxGetty[9516]: <-- [9:AT+FMDL?\r] > Feb 16 16:13:45 net FaxGetty[9516]: --> [20:AC/V34 ] > Feb 16 16:13:45 net FaxGetty[9516]: --> [2:OK] > Feb 16 16:13:45 net FaxGetty[9516]: <-- [9:AT+FREV?\r] ... > Feb 16 16:13:49 net FaxGetty[9516]: <-- [9:AT+FAA=1\r] > Feb 16 16:13:49 net FaxGetty[9516]: --> [2:OK] Here's your problem. Rockwell chips require you to be idling in Class 0 (ie data mode) for Adapative Answer to work correctly. Your config file needs the following: --- ModemSetupAACmd: AT+FAA=1+FCLASS=0 # enable adaptive-answer, Class 0 idle # # Chip locks the line rate and switches to xon/xoff flow # control when receiving facsimile--we must follow suit. # ModemAnswerFaxBeginCmd: "<19200><xon>" # lock line rate & switch flow control --- Hope this helps. -- Jonathan Chen <jonc@pinnacle.co.nz> --------------------------------------------------------------------- When all other forms of communication fail, use words