Hylafax Mailing List Archives
|
[Date Prev][Date Next][Thread Prev][Thread Next]
[Date Index]
[Thread Index]
Problems With 4.0p2 and ROCKWELL RC32ACL/V1.410-AS29 (Class 2) [LINUX]
- To: flexfax@sgi.com
- Subject: flexfax: Problems With 4.0p2 and ROCKWELL RC32ACL/V1.410-AS29 (Class 2) [LINUX]
- From: Pierric <pierric@writeme.com>
- Date: Fri, 11 Sep 1998 05:44:14 +0000
Hi!
i got a really annoying problem with my setup.
I can send faxes without a problem, but
I cannot receive :(
here's a session tracing log:
====
sep 09 21:12:54.16: [ 397]: SESSION BEGIN 00000010 33478265578
sep 09 21:12:54.16: [ 397]: <-- [4:ATA\r]
sep 09 21:13:05.77: [ 397]: --> [3:FAX]
sep 09 21:13:11.58: [ 397]: --> [5:+FCON]
sep 09 21:13:11.58: [ 397]: ANSWER: FAX CONNECTION
sep 09 21:13:11.58: [ 397]: RECV FAX: begin
sep 09 21:16:11.62: [ 397]: REMOTE HANGUP: Unspecified Receive Phase B error (code 70)
sep 09 21:16:11.64: [ 397]: RECV FAX: Unspecified Receive Phase B error
sep 09 21:16:11.70: [ 397]: RECV FAX: end
sep 09 21:16:11.70: [ 397]: SESSION END
====
and this happens, no matter what the sending device is.
here's my etc/config.cua1
====
#
# Configuration for a Rockwell RC32ACL-based Class 2 modem.
# Boca M1440E firmware V1.000
# SupraFAX v.32bis firmware V1.000
# (and others)
#
# This configuration file sets up the modem to run at 38.4 for
# sending and for receiving. RTS/CTS is used for flow control
# which also works for data connections. Adaptive answer support
# is reliable, but to use it you must also enable ModemWaitForConnect
# to force the server to skip intermediate status messages and
# wait for the "CONNECT" message.
#
#
CountryCode: 33
AreaCode: 4
FAXNumber: +33-478265578
LongDistancePrefix: 0
InternationalPrefix: 00
DialStringRules: "etc/dialrules"
ServerTracing: 1
SessionTracing: 1087
RecvFileMode: 0600
LogFileMode: 0600
DeviceMode: 0666
RingsBeforeAnswer: 1
SpeakerVolume: low
GettyArgs: "-h %l dx_%s"
LocalIdentifier: "Linux_54"
TagLineFont: etc/lutRS18.pcf
TagLineFormat: "From %%l|%c|Page %%p of %%t"
Use2D: yes
#
#
# Modem-related stuff: should reflect modem command interface
# and hardware connection/cabling (e.g. flow control).
#
ModemType: Class2 # use class 2 interface
ModemRate: 38400
ModemFlowControl: rtscts # default
ModemWaitForConnect: yes # wait for CONNECT on answer
#
#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&D2 # DTR off causes modem to reset
ModemSetupDCDCmd: AT&C1 # DCD follows carrier
ModemSetupAACmd: AT+FCLASS=0;+FAA=1 # enable in class 0
#
ModemSendFillOrder: LSB2MSB # as expected
ModemRecvFillOrder: MSB2LSB # opposite of what makes sense
Class2RecvDataTrigger: "\022" # a la 2388-B