Timewave DSP-232, Operating Manual

Page: 73 / 271

Chapter 5 Packet Operation
GATE>USER (RR) USER-15>REMOTE [I]:
hello.
REMOTE>USER-15 (RR)
REMOTE>USER-15 [I]:
Yes?
GATE>USER [I]: USER-15>REMOTE (RR)
Yes?
USER>GATE (RR)
Once the connection is established with the destination station, the node notifies the user that the
connection has been made then goes from the “Command” mode into the “Converse” mode. Now,
whatever the user sends goes to the destination station as data instead of to the node as a
command.
Normally, when someone disconnects from your node, no link will remain. However, if a user
adds the word
STAY
as the last argument in a Connect request, (e.g.,
C callsign STAY
), the user
will remain connected to your node even after disconnecting from the destination station.
If the connect attempt to the destination station retries out or is busy, your node sends the user a
Retry count exceeded
or
(Remote) busy
message, but remains connected to the user
even if STAY wasn’t entered.
D(isconnect)
(to cancel a connect attempt.) Since the source station remains in the Command mode until the
connection to the destination station is established, there’s no need for the user to wait for your
node to cycle through a full number of retries to attempt a connection—the user can send your
node a Disconnect request which cancels the Connect request the same way it would in a TNC’s
Command mode. (The user stays connected to your node even if
STAY wasn’t used in the
original Connect command.) The Disconnect command may be used at any time before the
connection is established, regardless of any preceding commands.
Once a connection is established and your node is in the Converse mode, the user can end the
connection either by sending a B(ye) command to the destination station if that station supports it,
or by issuing a Disconnect request to the user’s own TNC. If the user disconnects from your node
this way, it’ll force your node to disconnect the destination station.
J(heard)
Your node sends its MHEARD list to the user: A maximum of eighteen stations are kept in the
JHEARD
list.
L(isten)
The node toggles packet monitoring on or off.
N(odes)
Your node sends the user a list of nodes heard. The format is the same as that of the JHEARD
command, the difference being that a callsign is put in the Nodes list only if the monitored packet
was a UI frame with a PID of CF (NET/ROM) or CD (IP). A maximum of ten stations are kept in
the Nodes list. You clear the nodes list and the
MHEARD
list simultaneously with the same
command, MHEARD % .
S(end)
Your node responds with. . .
+++ Sending. To end, type ’=’.
. . . and sends all subsequent data in the broadcast mode “unproto.” The data characters are held
until the user sends a (
RETURN ), whereupon the held data is broadcast.
In all operating modes, the user can stop sending unproto by sending the “=” character—the node
will then issue a command prompt. The “=” character shouldn’t be used within the user’s
broadcast text.
5-12 September, 05