[FADCA] Quick connect for TelPac

John H. Green [email protected]
Sat, 12 Apr 2003 13:08:21 -0400



  
  


Hi All

    I don't have a problem with using -6, well maybe a slight one. We have
a bbs (n4joa) using -6 now, but I think this can be moved.. If there are
no further comments I think I will get started making the changes. Now, the
question is what Telpac nodes are out there? 

Info is needed for the following that do not have a station listed:



Lan / City                              TelPac/WL2K Station
Arcadia / Brownsville

Boca Raton

Ft. Pierce

Lake Harbor

Lake Placid

Melbourne                            kn6kb
Okeechobee

Sarasota

Stuart

Vero Beach

West Palm Beach                kd4lxb-2


Please note - this list in not all inclusive, info is needed for other areas
also.

Station should have a good reliable connection into the network, preferably
at a high speed.



Bud, on your proposed lan frequency list you might include the TelPac station
and the quick connect..



Now, the discussion on additional quick connects:

Adding additional quick connects to fpac above ssid -15 will not be useable
from a users tnc. Most tnc's will not accept a connect request with -17 or
-a. This is built into ax25 protocol. Since Fpac already uses -0 to -6 (quick
connects) and -8, -9 -10 (switch call) this leave only 6 ssid's for possible
additional quick connects. Probably not enough for a busy EOC that has to
connect to a bunch of shelters and other EOC's.

    An alternate solution might be to use the FPAC quick connects for common
things like TelPac, local BBS's, etc. and move the other needs to the terminal
program in the EOC, Shelter, etc. A simple program like Packcom has up to
40 function key positions (F1, shift F1, Alt F1 and Cntrl F1-10). Windows
based terminal programs probably have even more. A cheat sheet could tell
the operator which key to use for a certain connection.  Using a standard
program, identical key assignments and a cheat sheet should make it easier
for the operators if they go to different location as needed.

My 3 cents :-)   (inflation,
you know)



73  John




bud thompson wrote:


  Deltona
Thursday April 9 0535EST

I agree on having a standard SSID for TelPac throughout the system.

We discussed this a year ago when KN6KB first set up the SMS node which
TelPac now transcends.  At that time we only had the one SMS node KN6KB on
the fledgling Melbourne FPAC switch and we decided on -4 ssid (W4MLB-4) as
the standard.   Changing a quick connect SSID in FPAC configuration is a no
brainer - except at Melbourne where we continue to not have site access, now
thanks to the War on Iraq!  Hopefully that will be short lived - both the
war and lack of site access.

I'm not particular at this time, but we might consider the standard for
TelPac as SSID -6 as that is the highest one available  therefore stands the
best chance of not getting in he way of some already established.

Here on the DeLand FPAC we already have SSIDs 0 through six assigned, but
only 0 through five are presently in use.  FPAC DOS presently restricts
SSIDs for quick connect to a total of six, -1 though -6.

Since we apparently cannot get any changes made to the FPAC DOS code -

What I propose is that when we move to LINUX FPAC we establish more alias
capability, which I naively assume could be done since LINUX programs/stuff
apparently can more readily be changed/modified at the user level.  We could
actually use mnemonics - as we will certainly run out of ssids in the long
run anyway.  That way we could use TELPAC or WL2K (which is where TelPac
leads), and others, such as EOC, DABBBS, etc. We could have as many as we
decided was reasonably, perhaps 16 or so.

Most Airmail mobiles (Sailors/RVers) who would be acquainted with WL2K would
be able to pick up this information on the Winlink web site - though it is
not yet there since we are still in testing phase. Eventually, this
information, along with the LAN frequencies could be set up as a WL2K
catalog that can be requested via radio link.

Additionally a link to the FADCA pages will be on the winlink web site and
the LAN frequencies can be determined from the interactive map.  I suggest
we also have a list of LAN frequencies available there in text form -

CITY   COUNTY    SWITCH CALL LAN FREQ

Good job, John.

bud N0IA
---------------------------------------------------------------------
"Are you still wasting your time with spam?...
There is a solution!"

Protected by GIANT Company's Spam Inspector
The most powerful anti-spam software available.
http://www.giantcompany.com


----- Original Message -----
From: "John H. Green" <[email protected]>
To: "FADCA" <[email protected]>
Sent: Wednesday, April 09, 2003 22:47
Subject: [FADCA] Quick connect for TelPac


  
  
    Hi All
    I would like to suggest that we set up a standard ssid at each FPAC
switch to connect to the nearest TelPac node. To open the discussion I
suggest we use -3. Thus, here in the West Palm area connecting to
k4pkt-3 would connect you to the kd4lxb-2 TelPac node. In the Stuart
area connecting to k1vao-3 could connect to a TelPac node in the Stuart
area or, utilizing the network, could connect to kd4lxb-2 in the West
palm area. And so on.. :-)
    Once we get this setup a traveling user would only need to watch the
beacon from the local switch to get the switch call (assuming they don't
already know it) and connect to callsign-3 to get the nearest TelPac
node. Of course, one still needs to find the local lan frequency - no
easy task since they were removed from the repeater directory. :-(

Present ssid use in South Fl.:
-0  co-located bbs, otherwise unused.
-1  Local bbs or as required locally.
-2  As required locally.
-3  Tampa Info Server (has been unavailable for over a year, network
into Tampa out)
-4  As required locally.
-5  As required locally.
-6  As required locally.

Thoughts anyone??

73  John  wb4moz


_______________________________________________
FADCA mailing list
[email protected]
http://mailman.qth.net/mailman/listinfo/fadca

    
  
  

_______________________________________________
FADCA mailing list
[email protected]
http://mailman.qth.net/mailman/listinfo/fadca

  








--- StripMime Report -- processed MIME parts ---
text/html (html body -- converted)
The reason this message is shown is because the post was in HTML
or had an attachment.  Attachments are not allowed.  To learn how
to post in Plain-Text go to: http://www.expita.com/nomime.html  ---