Hylafax Mailing List Archives
|
[Date Prev][Date Next][Thread Prev][Thread Next]
[Date Index]
[Thread Index]
Re: faxgetty/mgetty problems
Hi David,
At 05:36 PM 10/27/99 +1000, DAVID ARNOLD wrote:
....
>ModemFlowControl: rtscts # default
....
>ModemAnswerFaxBeginCmd: "<19200><xon>" # modem switches on fax receive
...
>1 - we cannot receive faxes
Perhaps flow control? Show a session log of a failed receive.
>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.
Sometimes netcomm(and other rockwell) based modems have trouble with
Australia's dial tone, try adding a 'X3' or similar to the dial command to
get the modem to ignore the carrier.
>2 - Anyone know of the proper options pppd callers should include? ;)
Attached below are some (old) rough instructions i did a year or so ago -
if someone with some spare time could fix them up it would be a good FAQ
entry ;-)
>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.
I think your GettyArgs are wrong you need '-r' for direct connection
somewhere to stop mgetty resetting the modem on startup.
- Robert
----------cut here ----------------------
Redhat 5 installation in 6 easy steps
1) Install mgetty and ppp
rpm -i mgetty-1.1.9
rpm -i ppp-2.2.0
This will install mgetty on your machine in /sbin. pppd in /usr/sbin
2) Look in hylafax's setup.cache file PATHEGETTY param, symlink wherever
hylafax is looking for egetty to the mgetty executable
ie ln -s /sbin/mgetty /bin/egetty
3) Mgetty's config files
Mgetty's config is stored in /etc/mgetty+sendfax. Add to the mgetty.config
file lines similar to
port ttyS0, if you use /dev/modem or /dev/cua substitute accordingly
port ttyS0
direct y
toggle-dtr n
In login.config unremark the line:
/AutoPPP/ - a_ppp /usr/sbin/pppd auth -chap +pap login kdebug 7 debug
4) faxgetty config
In hylafax's modem config file ie config.ttyS0. Alter the GettyArgs
parameter to read:
GettyArgs: "-r -b -s %s %l"
Restart the faxgetty.
5)Setup ppp
pppd configuration, stored in /etc/ppp firstly the options file
asyncmap 0
netmask 255.255.255.0
proxyarp
lock
crtscts
modem
Then the per modem configuration /etc/ppp/options.ttyS0
linux1:ppp0 <-your server name first then dialup users name
dnsaddr 123.123.123.123 <-whatever your local dns is
Also /etc/pap-secrets
# client server secret acceptable local IP addresses
* * ""
Note the options above are slightly different for ppp-2.3.X
6) Testing
Use a windows machine to test the dialup setup. Just select "Make New
Connection" in dial up networking and type the servers phone number
in. Also more recent releases of windows default to encrypted
authentication only, this needs to be changed to "Accept any authorization
including plain text" in the dial up connections properties.
If if works - congratulations!!!!