|
Hylafax Mailing List Archives
|
[Date Prev][Date Next][Thread Prev][Thread Next]
[Date Index]
[Thread Index]
Re: Adaptive Answer support for USR Sportster 28.8 ???
Thomas Kuerten wrote:
>
> Brett wrote:
> >
> > On Sat, 14 Jun 1997, Thomas Kuerten wrote:
> > Somehow I cannot tell the hylafax getty to try first fax, then data.
> > > > > Is this impossible with the modem in 2.0 ?
> > > > > do I have to use class 1 ?
> > > >
> > > > man config(4f). The entry you're looking for is:
> > > >
> > > > ModemSetupAACmd: AT+FAA=1 # enable adaptive answer in Class 2
> > > Any help about this ?
> > > what should I use with my sportster 28.8, Class2.0 and Adaptive
> > > answer and Answer Rotary ? or leaving out something or adding
> > > something ?
> > As I remember, you really do not want to use Rotary Answer.
> > This is supposed to switch the modem from fax to data after every
> > call. First answers in fax - no connect? - then it hangs up and sets
> > itself up for data. Next time the phone rings - it is set to data.
> > The nest time - it is still set to data but gets no connect, it will
> > switch to fax. This way you *can* do both but the switch time is still
> > done by *failing* to make a connect. If you ran data, the next fax call
> > will fail. If you run fax, the next data call will fail.
> >
> > With Adaptive Answer, the modem is supposed to tell faxgetty what kind
> > of call it is getting. As far as I know, USR may or may not work this
> > correctly.
> >
> > Your best bet is to set the modem to do Adaptive Answer with FULL
> > logging turned on and see what it sends you if you get a fax call.
> > Then call in with data and see what you get with a data call. You
> > should be able to discern some small diofference. If not, you are
> > SOL - or the setup of the modem is wrong.
>
> Ok, I now think I've got it.
> It took me one weekend to figure out, though :-/
>
> I am now using the following strings:
>
> GettyArgs: "-r -b -s %s %l"
> ModemType: Class1 # use class 1 interface
> ModemRate: 38400 # DCE-DTE communication rate
> ModemFlowControl: rtscts # Hardware flow control assumed
> #
> ModemNoFlowCmd: AT&H0&I0&R1 # setup modem for no flow
> control
> ModemHardFlowCmd: AT&H1&I0&R2 # setup modem for hardware flow
> control
> ModemSoftFlowCmd: AT&H2&I2&R2 # setup modem for software flow
> control
> #
> ModemSetupDTRCmd: ATS13=1&D2 # setup so DTR drop resets modem
> ModemSetupDCDCmd: AT&C1 # setup so DCD reflects carrier
> (or not)
> ModemResultCodesCmd: ATQ0X4 # enable extended result codes
> #
> # The next line seems to be necessary to tell the modem to hangup an
> # inactivity line, as it once kept a closed line open for 8 hours,
> # which never got a proper connect from the dialing in data modem !
> # So here we hang up after 4 minutes of inactivity
> ModemResetCmds: ATS19=255
> #
> AdaptiveAnswer: yes # enable adaptive answer
> AnswerRotary: "fax data" # answer for fax, then data
> ModemAnswerFaxCmd: ATS27=8S56=0+FCLASS=1;A # default is to answer
> as fax
> ModemAnswerDataCmd: ATS27=1S56=16+FCLASS=0;A # hangup and answer as
> data
> Class1RecvIdentTimer: 10000 # timeout fax answer in 10 secs
> #
>
> As you might see, I am now using Class 1 and adaptive answer, as the
> lines:
>
> ModemType: Class2.0
> ModemSetupAACmd: AT+FAA=1
>
> Never worked out. Maybe my sportster 28800 v34 simply does not work for
> adaptive
> answer in class 2.0.... *SIGH*
>
> But now the modem picks up, tries to answer in fax and if that fails,
> switches to a data modulation tone and connects to the data mode, all in
> one
> session.
>
> Somehow the line ATS27=8S56=0 is necessary for the FAX mode for this
> modem,
> just as ATS27=1S56=16 is necessary for incoming DATA calls...
> I always used the modem in the first mode before, as I was only
> originating
> data calls and never saw a problem in there. But this option needs to be
> changed - the specific entrys are "shaping" 2100 Hz response tone
> setting/ITU,
> I really dont know what this is related to but now it works at least.
>
> And I do not cry for the Class 2.0 support which has now been thrown
> over board
> although it worked for most incoming/outgoing faxes, but I also
> already saw some faxes which did not come through in 2.0 and they all
> looked like
> this one, having multiple documents in them, not only one document with
> multiple pages:
>
> Jun 14 15:15:09.74: [ 1878]: SESSION BEGIN 00000043 498932158643
> Jun 14 15:15:09.74: [ 1878]: <-- [4:ATA\r]
> Jun 14 15:15:17.11: [ 1878]: --> [4:+FCO]
> Jun 14 15:15:17.11: [ 1878]: ANSWER: FAX CONNECTION
> Jun 14 15:15:17.11: [ 1878]: RECV FAX: begin
> Jun 14 15:15:18.75: [ 1878]: --> [27:+FTI:" Seagate Technology"]
> Jun 14 15:15:18.75: [ 1878]: REMOTE TSI "Seagate Technology"
> Jun 14 15:15:19.18: [ 1878]: --> [20:+FCS:1,3,0,2,0,0,0,0]
> Jun 14 15:15:19.27: [ 1878]: REMOTE wants 9600 bit/s
> Jun 14 15:15:19.27: [ 1878]: REMOTE wants page width 1728 pixels in 215
> mm
> Jun 14 15:15:19.27: [ 1878]: REMOTE wants unlimited page length
> Jun 14 15:15:19.27: [ 1878]: REMOTE wants 7.7 line/mm
> Jun 14 15:15:19.27: [ 1878]: REMOTE wants 1-D MR
> Jun 14 15:15:19.36: [ 1878]: --> [2:OK]
> Jun 14 15:15:19.36: [ 1878]: <-- [7:AT+FDR\r]
> Jun 14 15:15:21.33: [ 1878]: --> [20:+FCS:1,3,0,2,0,0,0,0]
> Jun 14 15:15:21.33: [ 1878]: REMOTE wants 9600 bit/s
> Jun 14 15:15:21.33: [ 1878]: REMOTE wants page width 1728 pixels in 215
> mm
> Jun 14 15:15:21.33: [ 1878]: REMOTE wants unlimited page length
> Jun 14 15:15:21.33: [ 1878]: REMOTE wants 7.7 line/mm
> Jun 14 15:15:21.33: [ 1878]: REMOTE wants 1-D MR
> Jun 14 15:15:23.47: [ 1878]: --> [7:CONNECT]
> Jun 14 15:15:23.47: [ 1878]: RECV: begin page
> Jun 14 15:15:23.47: [ 1878]: RECV: send trigger 022
> Jun 14 15:15:23.47: [ 1878]: <-- data [1]
> Jun 14 15:15:57.21: [ 1878]: RECV: 2165 total lines, 0 bad lines, 1
> consecutive
> bad lines
> Jun 14 15:15:57.21: [ 1878]: --> [17:+FPS:1,2174,0,0,0]
> Jun 14 15:15:58.47: [ 1878]: --> [6:+FET:1]
> Jun 14 15:15:58.47: [ 1878]: RECV recv EOM (more documents)
> Jun 14 15:15:58.47: [ 1878]: --> [2:OK]
> Jun 14 15:15:58.47: [ 1878]: RECV send MCF (message confirmation)
> Jun 14 15:15:58.47: [ 1878]: RECV FAX (00000043): from Seagate
> Technology, page
> 1 in 0:39, INF, 7.7 line/mm, 1-D MR
> Jun 14 15:15:58.47: [ 1878]: RECV FAX (00000043): recvq/fax00016.tif
> from Seagat
> e Technology, route to <unspecified>, 1 pages in 0:41
> Jun 14 15:15:58.48: [ 1878]: <-- [7:AT+FDR\r]
> Jun 14 15:16:09.06: [ 1878]: --> [7:+FHS:70]
> Jun 14 15:16:09.06: [ 1878]: REMOTE HANGUP: Unspecified Receive Phase B
> error (c
> ode 70)
> Jun 14 15:16:09.06: [ 1878]: RECV FAX (00000043): recvq/fax00017.tif
> from Seagat
> e Technology, route to <unspecified>, 0 pages in 0:11
> Jun 14 15:16:09.06: [ 1878]: RECV FAX: Unspecified Receive Phase B error
> Jun 14 15:16:09.06: [ 1878]: RECV FAX: bin/faxrcvd "recvq/fax00016.tif"
> "ttyS0"
> "00000043" ""
> Jun 14 15:16:09.55: [ 1878]: RECV FAX (00000043): session with Seagate
> Technolog
> y terminated abnormally: Unspecified Receive Phase B error
> Jun 14 15:16:09.55: [ 1878]: RECV FAX: bin/faxrcvd "recvq/fax00017.tif"
> "ttyS0"
> "00000043" "Unspecified Receive Phase B error"
> Jun 14 15:16:10.52: [ 1878]: RECV FAX: end
> Jun 14 15:16:10.52: [ 1878]: SESSION END
>
> The relevant part seems to be the line
> Jun 14 15:15:58.47: [ 1878]: RECV recv EOM (more documents)
> as this looks like the sending fax is sending several documents in one
> session and
> the sportster doesn't seem to be able to handle that in class 2.0
>
> If I try to get the exactly same document from Seagate fax server
> (Thanks
> go to Seagate for this excellent testing opportunity ;-))) )
> but now in Class 1, I gett the following result:
>
> Jun 16 00:58:08.92: [ 2216]: SESSION BEGIN 00000065 498932158643
> Jun 16 00:58:08.92: [ 2216]: <-- [24:ATS27=8S56=0+FCLASS=1;A\r]
> Jun 16 00:58:14.31: [ 2216]: --> [7:CONNECT]
> Jun 16 00:58:14.31: [ 2216]: ANSWER: FAX CONNECTION
> Jun 16 00:58:14.31: [ 2216]: RECV FAX: begin
> Jun 16 00:58:14.31: [ 2216]: <-- data [23]
> Jun 16 00:58:14.31: [ 2216]: <-- data [2]
> Jun 16 00:58:15.96: [ 2216]: --> [7:CONNECT]
> Jun 16 00:58:15.96: [ 2216]: <-- data [10]
> Jun 16 00:58:15.96: [ 2216]: <-- data [2]
> Jun 16 00:58:16.77: [ 2216]: --> [2:OK]
> Jun 16 00:58:16.86: [ 2216]: <-- [9:AT+FRH=3\r]
> Jun 16 00:58:17.88: [ 2216]: --> [7:CONNECT]
> Jun 16 00:58:18.55: [ 2216]: --> [2:OK]
> Jun 16 00:58:18.55: [ 2216]: REMOTE TSI "Seagate Technology"
> Jun 16 00:58:18.55: [ 2216]: <-- [9:AT+FRH=3\r]
> Jun 16 00:58:18.74: [ 2216]: --> [7:CONNECT]
> Jun 16 00:58:18.99: [ 2216]: --> [2:OK]
> Jun 16 00:58:18.99: [ 2216]: REMOTE wants 9600 bit/s
> Jun 16 00:58:18.99: [ 2216]: REMOTE wants page width 1728 pixels in 215
> mm
> Jun 16 00:58:18.99: [ 2216]: REMOTE wants unlimited page length
> Jun 16 00:58:18.99: [ 2216]: REMOTE wants 7.7 line/mm
> Jun 16 00:58:18.99: [ 2216]: REMOTE wants 1-D MR
> Jun 16 00:58:18.99: [ 2216]: RECV training at v.29 9600 bit/s
> Jun 16 00:58:18.99: [ 2216]: <-- [10:AT+FRM=96\r]
> Jun 16 00:58:19.39: [ 2216]: --> [7:CONNECT]
> Jun 16 00:58:20.94: [ 2216]: RECV: TCF 1859 bytes, 1% non-zero, 1828
> zero-run
> Jun 16 00:58:20.96: [ 2216]: --> [10:NO CARRIER]
> Jun 16 00:58:20.96: [ 2216]: DELAY 75 ms
> Jun 16 00:58:21.05: [ 2216]: <-- [9:AT+FTH=3\r]
> Jun 16 00:58:21.17: [ 2216]: --> [7:CONNECT]
> Jun 16 00:58:21.17: [ 2216]: <-- data [3]
> Jun 16 00:58:21.17: [ 2216]: <-- data [2]
> Jun 16 00:58:22.38: [ 2216]: --> [2:OK]
> Jun 16 00:58:22.38: [ 2216]: TRAINING succeeded
> Jun 16 00:58:22.38: [ 2216]: <-- [10:AT+FRM=96\r]
> Jun 16 00:58:23.44: [ 2216]: --> [7:CONNECT]
> Jun 16 00:58:23.44: [ 2216]: RECV: begin page
> Jun 16 00:58:57.21: [ 2216]: RECV: 2165 total lines, 0 bad lines, 1
> consecutive
> bad lines
> Jun 16 00:58:57.21: [ 2216]: RECV: end page
> Jun 16 00:58:57.21: [ 2216]: --> [10:NO CARRIER]
> Jun 16 00:58:57.21: [ 2216]: <-- [9:AT+FRH=3\r]
> Jun 16 00:58:58.10: [ 2216]: --> [7:CONNECT]
> Jun 16 00:58:58.24: [ 2216]: --> [2:OK]
> Jun 16 00:58:58.24: [ 2216]: RECV recv EOM (more documents)
> Jun 16 00:58:58.24: [ 2216]: <-- [9:AT+FTH=3\r]
> Jun 16 00:58:58.35: [ 2216]: --> [7:CONNECT]
> Jun 16 00:58:58.35: [ 2216]: <-- data [3]
> Jun 16 00:58:58.35: [ 2216]: <-- data [2]
> Jun 16 00:58:59.56: [ 2216]: --> [2:OK]
> Jun 16 00:58:59.56: [ 2216]: RECV send MCF (message confirmation)
> Jun 16 00:58:59.58: [ 2216]: RECV FAX (00000065): from Seagate
> Technology, page
> 1 in 0:37, INF, 7.7 line/mm, 1-D MR
> Jun 16 00:58:59.58: [ 2216]: RECV FAX (00000065): recvq/fax00034.tif
> from Seagat
> e Technology, route to <unspecified>, 1 pages in 0:45
> Jun 16 00:58:59.60: [ 2216]: <-- [9:AT+FRH=3\r]
> Jun 16 00:59:06.59: [ 2216]: --> [0:]
> Jun 16 00:59:06.77: [ 2216]: MODEM <Empty line>
> Jun 16 00:59:06.77: [ 2216]: <-- data [1]
> Jun 16 00:59:06.77: [ 2216]: --> [2:OK]
> Jun 16 00:59:06.77: [ 2216]: <-- data [23]
> Jun 16 00:59:06.77: [ 2216]: <-- data [2]
> Jun 16 00:59:09.77: [ 2216]: --> [0:]
> Jun 16 00:59:09.77: [ 2216]: MODEM <Empty line>
> Jun 16 00:59:09.77: [ 2216]: DELAY 1500 ms
> Jun 16 00:59:11.28: [ 2216]: <-- [9:AT+FTH=3\r]
> Jun 16 00:59:11.39: [ 2216]: --> [7:CONNECT]
> Jun 16 00:59:11.39: [ 2216]: <-- data [23]
>
> Jun 16 00:59:11.39: [ 2216]: <-- data [2]
> Jun 16 00:59:13.13: [ 2216]: --> [7:CONNECT]
> Jun 16 00:59:13.13: [ 2216]: <-- data [10]
> Jun 16 00:59:13.13: [ 2216]: <-- data [2]
> Jun 16 00:59:13.94: [ 2216]: --> [2:OK]
> Jun 16 00:59:13.94: [ 2216]: <-- [9:AT+FRH=3\r]
> Jun 16 00:59:15.05: [ 2216]: --> [7:CONNECT]
> Jun 16 00:59:15.72: [ 2216]: --> [2:OK]
> Jun 16 00:59:15.72: [ 2216]: REMOTE TSI "Seagate Technology"
> Jun 16 00:59:15.72: [ 2216]: <-- [9:AT+FRH=3\r]
> Jun 16 00:59:15.91: [ 2216]: --> [7:CONNECT]
> Jun 16 00:59:16.16: [ 2216]: --> [2:OK]
> Jun 16 00:59:16.16: [ 2216]: REMOTE wants 9600 bit/s
> Jun 16 00:59:16.16: [ 2216]: REMOTE wants page width 1728 pixels in 215
> mm
> Jun 16 00:59:16.16: [ 2216]: REMOTE wants unlimited page length
> Jun 16 00:59:16.16: [ 2216]: REMOTE wants 3.85 line/mm
> Jun 16 00:59:16.16: [ 2216]: REMOTE wants 1-D MR
> Jun 16 00:59:16.16: [ 2216]: RECV training at v.29 9600 bit/s
> Jun 16 00:59:16.16: [ 2216]: <-- [10:AT+FRM=96\r]
> Jun 16 00:59:16.57: [ 2216]: --> [7:CONNECT]
> Jun 16 00:59:18.11: [ 2216]: RECV: TCF 1858 bytes, 2% non-zero, 1814
> zero-run
> Jun 16 00:59:18.13: [ 2216]: --> [10:NO CARRIER]
> Jun 16 00:59:18.13: [ 2216]: DELAY 75 ms
> Jun 16 00:59:18.22: [ 2216]: <-- [9:AT+FTH=3\r]
> Jun 16 00:59:18.34: [ 2216]: --> [7:CONNECT]
> Jun 16 00:59:18.34: [ 2216]: <-- data [3]
> Jun 16 00:59:18.34: [ 2216]: <-- data [2]
> Jun 16 00:59:19.55: [ 2216]: --> [2:OK]
> Jun 16 00:59:19.55: [ 2216]: TRAINING succeeded
> Jun 16 00:59:19.55: [ 2216]: <-- [10:AT+FRM=96\r]
> Jun 16 00:59:20.69: [ 2216]: --> [7:CONNECT]
> Jun 16 00:59:20.69: [ 2216]: RECV: begin page
> Jun 16 00:59:34.81: [ 2216]: RECV: 1103 total lines, 0 bad lines, 0
> consecutive
> bad lines
> Jun 16 00:59:34.81: [ 2216]: RECV: end page
> Jun 16 00:59:34.81: [ 2216]: --> [10:NO CARRIER]
> Jun 16 00:59:34.81: [ 2216]: <-- [9:AT+FRH=3\r]
> Jun 16 00:59:35.72: [ 2216]: --> [7:CONNECT]
> Jun 16 00:59:35.86: [ 2216]: --> [2:OK]
> Jun 16 00:59:35.86: [ 2216]: RECV recv MPS (more pages, same document)
> Jun 16 00:59:35.86: [ 2216]: <-- [9:AT+FTH=3\r]
> Jun 16 00:59:35.97: [ 2216]: --> [7:CONNECT]
> Jun 16 00:59:35.97: [ 2216]: <-- data [3]
> Jun 16 00:59:35.97: [ 2216]: <-- data [2]
> Jun 16 00:59:37.18: [ 2216]: --> [2:OK]
> Jun 16 00:59:37.18: [ 2216]: RECV send MCF (message confirmation)
> Jun 16 00:59:37.18: [ 2216]: RECV FAX (00000065): from Seagate
> Technology, page
> 1 in 0:38, INF, 3.85 line/mm, 1-D MR
> Jun 16 00:59:37.18: [ 2216]: <-- [10:AT+FRM=96\r]
> Jun 16 00:59:38.30: [ 2216]: --> [7:CONNECT]
> Jun 16 00:59:38.30: [ 2216]: RECV: begin page
> Jun 16 00:59:54.02: [ 2216]: RECV: 1103 total lines, 0 bad lines, 0
> consecutive
> bad lines
> Jun 16 00:59:54.02: [ 2216]: RECV: end page
> Jun 16 00:59:54.02: [ 2216]: --> [10:NO CARRIER]
> Jun 16 00:59:54.02: [ 2216]: <-- [9:AT+FRH=3\r]
> Jun 16 00:59:54.95: [ 2216]: --> [7:CONNECT]
> Jun 16 00:59:55.08: [ 2216]: --> [2:OK]
> Jun 16 00:59:55.08: [ 2216]: RECV recv EOP (no more pages or documents)
> Jun 16 00:59:55.08: [ 2216]: <-- [9:AT+FTH=3\r]
> Jun 16 00:59:55.19: [ 2216]: --> [7:CONNECT]
> Jun 16 00:59:55.19: [ 2216]: <-- data [3]
> Jun 16 00:59:55.19: [ 2216]: <-- data [2]
> Jun 16 00:59:56.40: [ 2216]: --> [2:OK]
> Jun 16 00:59:56.40: [ 2216]: RECV send MCF (message confirmation)
> Jun 16 00:59:56.40: [ 2216]: RECV FAX (00000065): from Seagate
> Technology, page
> 2 in 0:19, INF, 3.85 line/mm, 1-D MR
> Jun 16 00:59:56.40: [ 2216]: RECV FAX (00000065): recvq/fax00035.tif
> from Seagat
> e Technology, route to <unspecified>, 2 pages in 0:57
> Jun 16 00:59:56.40: [ 2216]: <-- [9:AT+FRH=3\r]
> Jun 16 00:59:57.49: [ 2216]: --> [7:CONNECT]
> Jun 16 00:59:57.63: [ 2216]: --> [2:OK]
> Jun 16 00:59:57.63: [ 2216]: RECV FAX: bin/faxrcvd "recvq/fax00034.tif"
> "ttyS0"
> "00000065" ""
> Jun 16 00:59:58.09: [ 2216]: RECV FAX: bin/faxrcvd "recvq/fax00035.tif"
> "ttyS0"
> "00000065" ""
> Jun 16 00:59:58.49: [ 2216]: RECV FAX: end
> Jun 16 00:59:58.49: [ 2216]: SESSION END
>
> This time everything came through fine...
>
> So this is the reason why I think the Class 2.0 fax support in my
> sportster is
> broken, and I dont think anyone in this list will say somthing other as
> nobody seems
> to know about these phase B errors, as I look through the mailing list
> archives... :-(
>
> For everyone wanting to know my firmware of my modem, its
> Product type Germany
> External
> Options
> V32bis,V.FC,V.34
> Fax Options Class 1/Class
> 2.0
> Clock Freq
> 20.16Mhz
> Eprom
> 256k
> Ram
> 32k
>
> Supervisor date
> 04/06/95
> DSP date
> 03/31/95
>
> Supervisor rev
> 049-6.0
> DSP rev
> 11.3
>
> I hope I may help someone whith all this data, as I was very unhappy to
> get
> so few responses to MY questions, which were very specific AFTER I
> already
> read the FAQs and helpfiles/manuals.
>
> It seems to me that either
> 1. there are not many people in this list who know a lot about Hylafax
> and the related modems
> 2. There may be a lot but hey all are not very helpful or eager to help
> newbies like me, even if they try to read everything befor asking
> questions.
>
> I have to say the available manuals say a lot, but also a lot of the
> specific and difficult setups lack a lot of examples and direct answers,
> there is too much of vaguely stated assuments in there, which is not
> very helpful.
>
> I cannot believe there are not more examples for the configuration.
> maybe one should collect some once.
>
> This is the only good example I know of Gert Doering's mgetty and
> sendfax
> package, which HAS a lot of example configurations. But I switched to
> Hylafax
> because mgetty+sendfax lacks something like rotary answer, which was
> very
> important for me...
>
> regards and sorry for the lengthy mail...
> Thomas.
--
Thomas Kuerten - beim Pfarracker 29 - 85716 Unterschleissheim - Germany
-URL-: http://www.leo.org/~kuerten/
Email: kuerten@leo.org (at home), thomas@tekelec.de (at Work)
Phone: +49 (0)89 321 58644
