[nos-bbs] nos-bbs Digest, Vol 134, Issue 4 (fwd)
Maiko Langelaar
maiko at pcs.mb.ca
Thu Nov 19 14:23:45 EST 2015
Same here, I should have sent this to group as well, plus
an additional comment. I never had to use any scripts, the
JNOS itself did the necessary BW command, however as I noted
further below in my response to Gary, I only initiate the BW
command on an incoming request. So IF that is required to get
a response, then I've misplaced the command and maybe it should
be sent as soon as JNOS is connected to the command channel,
instead of waiting for a connect it may never get. Just a
thought, that's all.
I'll look through the logs when I have a free moment.
---------- Forwarded message ----------
Date: Wed, 18 Nov 2015 21:19:25 -0600 (CST)
From: Maiko Langelaar <maiko at pcs.mb.ca>
To: Gary White <garyrwhite52 at yahoo.com>
Subject: Re: [nos-bbs] nos-bbs Digest, Vol 134, Issue 4
> Looking at the logs with both JNOS initializing and RMS I
> created an expect script to to telnet into the control port
> and initialize the winmor TNC. I found out the minimum
> to get it to start answering incoming is to make sure
> Codec was false and sent a BW 500 command.
JNOS sends the BW 500 command automatically on incoming
connect, mind you if it's waiting for the incoming, then
maybe I should put the BW send right when JNOS initializes
the winmore tcp connection, instead of waiting for an
incoming. That's a good observation Gary.
> Seems JNOS does not recognize the RMS forward email command ...
It should.
> Attached are the logs and scripts.
I'll look at the logs when I have a free moment. This week is
very busy for me on all fronts. I'll see what I can do.
73 Maiko
More information about the nos-bbs
mailing list