dan@asihub.UUCP (Dan O'Neill) (06/09/89)
Since there seems to be a great number of Ultrix users who need
configuration information for Telebit TrailBlazers, I offer the
following information as a working example.
--------------------- Background information ---------------------
The information presented is used on a MicroVAX II running under
Ultrix 3.0 with two Telebit TrailBlazer Plus modems. I believe these
are the original TrailBlazer models, so this information may not apply
to newer TrailBlazers.
We are currently communicating with two other Unix sites in fast or
PEP mode and are achieving transfer rates between 6000 and 8500
bits/second. We are able to generate and answer calls in PEP (FAST)
mode.
------------------- end background information -------------------
-------------------------- /etc/acucap ---------------------------
#
# Telebit Trailblazer Plus, autobaud
#
telebit|tbauto|trailblazer-auto|Telebit Trailblazer in auto mode S50=0:\
:cr:hu:ls:re:\
:ss=AAATZ\r\dAT &F S7=80 S45=0 S51=5 S52=2 S53=2 S54=3 S58=2 S64=1\
S66=1 S92=1 S111=30 Q6 X3 M0 &W\r\d:\
:sr=OK:sd#250000:di=A\dA\dATS50=0DT:dt=\r:\
:dd#50000:fd#50:rs=,:os=CONNECT:ds=\d+++\dATZ\r:ab=\d+++\dATZ\r:
#
# Telebit Trailblazer Plus, call in PEP mode
#
telebit-PEP|tb-PEP|trailblazer-PEP|Telebit Trailblazer in PEP mode S50=255:\
:cr:hu:ls:re:\
:ss=AAATZ\r\dAT &F S7=80 S45=0 S51=5 S52=2 S53=2 S54=3 S58=2 S64=1\
S66=1 S92=1 S111=30 Q6 X3 M0 &W\r\d:\
:sr=OK:sd#250000:di=A\dA\dATS50=255DT:dt=\r:\
:dd#50000:fd#50:rs=,:os=CONNECT:ds=\d+++\dATZ\r:ab=\d+++\dATZ\r:
----------------------- end of /etc/acucap -----------------------
--------------- Description of switch settings -------------------
&F - reset to factory defaults
S7=80 - wait 80 seconds for a valid carrier tone
S45=0 - disable remote access (this is the default, but we want to make sure)
S51=5 - talk to the local DTE (computer) at 19200 baud
S52=2 - Modem disconnects and saved configuration parameters
are reloaded when DTR is turned off (toggled).
S53=2 - DSR is ON only when DCD is ON. DCD is on when the carrier is
detected.
S54=3 - Pass BREAK's through the modem transparently.
S58=2 - use hardware flow control between modem and local DTE.
S64=1 - ignore characters sent from DTE while dialing or answering
a call.
S66=1 - regardless of the baud rate of the modem to modem connection,
the baud rate between the modem and the local DTE remains
fixed at the rate specified by S51. (19200 baud in this example)
S92=1 - answer incoming calls in the following order:
V.22bis, 212A, 103, PEP
This allows the Telebit to answer non-PEP (telebit fast mode)
modems before answering a Telebit PEP tone.
S111=30 - enables UUCP "g" protocol support in the TrailBlazer.
Q6 - silences the modem when an inbound call arrives. This prevents
getty battles between the RING result code and getty's echo
of the same.
X3 - sets the result codes to MNP/PEP Extended.
M0 - turns off the speaker.
&W - writes these new values to the EEPROM. This saves the new values
as the modem's power on defaults from now until you change them
again.
------------------ end of switch descriptions --------------------
------------------------- /etc/L-devices -------------------------
ACU ttyd4 ttyd4 19200 telebit-PEP
ACU ttyd4 ttyd4 2400 telebit
---------------------- end of /etc/L-devices ---------------------
---------------------------- /etc/ttys ---------------------------
ttyd4 "/etc/getty std.19200" dialup on modem shared # oldname=tty04, telebit
------------------------- end of /etc/ttys -----------------------
With these entries we are able to perform the following functions:
- originate a call at 2400 baud
- originate a call in PEP mode
- answer a call at 1200 baud
- answer a call at 2400 baud
- answer a call in PEP mode
The difference between the "telebit" and "telebit-PEP" /etc/acucap
entries is in the "si" entry. To generate a PEP mode call, use the
telebit-PEP acucap entry. This entry sets the S50 register to 255
prior to dialing. This instructs the modem to only recognize a PEP
tone and ignore all other modem tones. The "telebit" entry sets S50
to zero so that the modem will respond to the first compatible carrier
tone. It is important that S50 not be saved as 255 with the &W0
command. We want the default state of the modem to be "answer any
carrier tone".
For example, lets set up a machine named "harp" that has two way uucp
communications with sites "emerald" and "shamrock". Emerald has a
TrailBlazer configured as specified in this document and shamrock has
some kind of 2400 baud modem.
Your (harp's) /var/uucp (/usr/lib/uucp) L.sys file might contain:
emerald Any ACU 19200 5553456 (expect/send login sequence)
shamrock Any ACU 2400 5552376 (expect/send login sequence)
The /var/uucp/L.sys file on "emerald" might contain:
harp Any ACU 19200 5551245 (expend/send login sequence)
and on "shamrock":
harp Any ACU 2400 5551245 (expend/send login sequence)
Using the settings given here, your Telebit will answer calls from
either "emerald" or "shamrock" (PEP carrier, 2400 baud carrier
respectively). It will generate a PEP mode call when calling
"emerald" and a 2400 baud call to "shamrock".
In order for your modem to answer an incoming call in PEP mode, the
caller must force their modem to call in PEP, S50=255. Your modem
will send out the V.22bis, 212A and 103 carrier tones before sending
out the PEP carrier to the calling modem. If the caller has S50 set
to 255, their modem will only respond to the PEP tone.
This configuration works well for us. If I have made some mistakes or
could some how improve this configuration, I would appreciate the
input. Good luck.
--
Dan O'Neill dan@asihub.uucp {uunet|ncr-sd}!asihub!dan
Automated Systems, Inc. San Diego R&D