*BSD News Article 28644


Return to BSD News archive

Xref: sserve comp.mail.uucp:12182 comp.os.386bsd.questions:9394
Newsgroups: comp.mail.uucp,comp.os.386bsd.questions
Path: sserve!newshost.anu.edu.au!munnari.oz.au!metro!news.cs.su.oz.au!harbinger.cc.monash.edu.au!msuinfo!agate!howland.reston.ans.net!usc!elroy.jpl.nasa.gov!grian!pelican!pete
From: pete@pelican.com (Pete Carah)
Subject: Re: taylor-uucp-1.04 and Worldblazer modem
References: <CMxJnt.17v@luva.stgt.sub.org>
Organization: Pete's news server
Date: Tue, 22 Mar 1994 17:02:51 GMT
Message-ID: <Cn2sor.1sF@pelican.com>
Lines: 87

In article <CMxJnt.17v@luva.stgt.sub.org>,
Michael Giegerich <migieger@luva.stgt.sub.org> wrote:

>I changed my ZyXEL modem yesterday against a Worldblazer...
>I set the WB to use factory default #9 (at &f9) which is
>for IBM PC/MAC with HW flow control (RTS/CTS).

>---------- snip ---------- snip ---------- snip ---------- snip ----------
>chat "" ATZ\r\d\c OK ATDP\T CONNECT
>---------- snip ---------- snip ---------- snip ---------- snip ----------

>---------- snip ---------- snip ---------- snip ---------- snip ----------
>uucico delos - (1994-03-19 15:32:06.35 280) DEBUG: fcsend: Writing "ATZ\r" sleep
>uucico delos - (1994-03-19 15:32:08.36 280) DEBUG: icexpect: Looking for 2 "OK"
>uucico delos - (1994-03-19 15:32:08.36 280) DEBUG: icexpect: Got "a(k\177
>---------- snip ---------- snip ---------- snip ---------- snip ----------
I'll have to look at work; we are using a WB with Taylor 1.04 (under
ESIX 4.0.4, not freebsd).  One impression I have is that the WB doesn't
like lots of things piled together at 38.4kb (though that isn't your
problem here).  Another is that it was a  LOT of trouble getting a
modem config that worked, and I've forgotten to print it out.
Once I had a config that worked for HDB, it worked for Taylor also.

excerpts from:
========================dial========================
chat-fail BUSY
chat-fail NO\sDIAL\sTONE
chat-fail NO\sCARRIER
chat-fail VOICE
chat-7-bit

dialer Modemx
chat "" \M\c

dialer TelebitFast
chat "" \M\c "" ATE1M0\r\c OK\r ATS50=255S52=1S111=30S58=4\r\c OK\r ATDT\T\r\c CONNECT \m\c
dialer Telebit
chat "" \M\c "" AT\r\c OK ATE1M0\r\c OK ATDT\T\r\c CONNECT \m\c
dialer Telebit9
chat "" \M\c "" ATE1M0S50=6\r\c OK ATDT\T\r\c CONNECT \m\c
dialer Telebit12
chat "" \M\c "" ATE1M0\r\c OK\r ATS50=2S94=0S180=0\r\c OK\r ATDT\T\r\c CONNECT \m\c
=============================port===================================
port ACU
type modem
device term/02h
baud 19200
dialer Telebit

port ACU9
type modem
device term/02h
baud 19200
dialer Telebit9

port ACU12
type modem
device term/02h
baud 19200
dialer Telebit12

port ACUp
type modem
device term/02h
baud 19200
dialer TelebitFast
=======================================================================
The real problem is the initial config; I didn't use any factory defaults
since we were doing bidirectional; none of them work right as is.
I'll try to get a AT&V from the modem and list it here...

It isn't cooperating...  I've had lots of trouble getting local
control of the modem.

I do remember using Q2 or Q9 (don't remember which modem that was; it
gives result codes only when commanded and not on dial-in.)
and &C1&D3 (CD follows real connect state and modem resets on DTR drop)
(both those are IMPORTANT if bidirectional use is planned); baud rate
locked at 19200 (esix doesn't like 38k; freebsd does).
There were other changes; you want to completely disable MNP mode if
you will be dealing with any unix systems at the called end.  V.42/V.42bis
is OK.  You may want to disable the escape character '+'.  (done by
setting it to 128).  Don't make the escape guard time 0; telebit takes
that literally and if the esc is then defined it'll hang up on you if
any text has 3 plusses in it.

-- Pete