[FADCA] Quick connect for TelPac

[bud thompson]

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" <wb4moz@adelphia.net>
To: "FADCA" <fadca@mailman.qth.net>
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
> FADCA@mailman.qth.net
> http://mailman.qth.net/mailman/listinfo/fadca
>