[FADCA] Fw: [telpac-paclink] Digest Number 170

[bud thompson]

Deltona
Tuesday Oct 5 0700

(NOTE: To the best of my knowledge the KF4SIR telpac node is no longer on 
the air.)

There is no need to register Paclink stations on the FADA data base - these 
are classified as user terminal node devices and cannot even accept an 
incoming connect request.  Many Paclink stations would be portable for 
tactical operations and not always associated with a specific LAN.

What local and district EMCOMMs planners could use eventually would be a 
list of all permanently assigned tactical e-mail addresses in the State, but 
I see that as an ARES management function rather than a FADCA function.  It 
is likely WL2K will eventually manage/publish a national list of permanently 
assigned tactical e-mail addresses of which those in Florida would be a 
subset.

Most Paclink stations and Telpac nodes will be AGW PE compliant and could 
have the AGW Digi set up.  If the Paclink user leaves his/her computer on 
24/7 it is recommended the AGW Digi be set up - then that digi should be 
registered.  We have a real potential problem with getting a lot of this 
stuff registered by well-meaning hams who want to try these things out- 
register them- then take them off the air!  (See REF below)

To be useful a registered Telpac node or digi must be on 24/7.  I see no 
value in registering a Telpac node that is not.  The digi should be ON for 
all Telpac nodes. (See REF below)

We definitely need a comprehensive master list of Florida Telpac nodes, PMBO 
packet ports, and EMCOMMs PMBOs that may otherwise may be reached through a 
Telpac node.  The EMCOMMs PMBOs will be those that 'hubb' messages for local 
users when the associated Telpac node no longer has an internet connection. 
It could be beneficial for our FADCA list to include HF PMBOs, but those 
could be simply marked as "HF" with a permanent reference link to the 
winlink.org QRG list which is meticulously maintained and updated by WL2K. 
FADCA doesn't coordinate those frequencies anyway.

In my Lessons Learned from the recent hurricanes (If You Want to Hear God 
Laugh . . .)  I recommended some sweeping additions to the Pacllink user 
program to facilitate more automatic connections to Telpac nodes and PMBOs 
on packet.  (See Appendix 1 of Lessons Learned)... If implemented, this will 
require detailed information on all Telpac nodes and PMBO packet ports in 
the state to not only be available, but be up to date.  More on that later 
if the WL2K Development Teams sees merit.

REF:
The list of all 364 Telpac and packet PMBO ports is presently available at 
http://winlink.org/status/TelpacEx.aspx.  Maybe it would be easier to just 
work with this list which would ensure the FADCA information being up to 
date.  I counted 33 in Florida - almost ten percent of the total.

In your browser, the list can be sorted by call, city, grid square etc. - 
I'll make some comments/recommendations to the WL2K Development Team.  I see 
that sorting by grid square would put most, but not all, of the Florida 
Telpac nodes together in the list (though some do not include "FL" - the 
state is not a separate field in the registration process, but if the 
registrants would use the comma separator (some have not), the state 
information might be available for what ever purpose.

I see a bunch of Telpac nodes in the Orange/Seminole County area that I was 
not aware of!!!! I don't find all those calls on the heard list of the 
Orlando switch, but it might not seem them all until we move it.  My guess 
is that some hams play around with the new ideas, register a Telpac, then 
take it off w/o deleting it from the WL2K registry.  WL2K will have to get a 
handle on this or the Telpac registry will be of little value - especially 
in an emergency.

Russ/Free - What if when a new telpac / PMBO packet node in Florida is 
registered with winlink an e-mail with the data is automatically sent to 
FADCA in an e-mail?  I don't know if that can be set up, but I can sure 
recommend it.  Not likely the data could be re-shuffled/organized, so you'd 
have to work with the format that is available.

bud



----- Original Message ----- 
From: "Chuck Hast" <wchast at gmail.com>
To: "Florida Amateur Digital Communication Association" 
<fadca at mailman.qth.net>
Sent: Monday, October 04, 2004 23:43
Subject: Re: [FADCA] Fw: [telpac-paclink] Digest Number 170


> On Mon, 4 Oct 2004 22:54:53 -0400, Russell Oder <oderr at bellsouth.net> 
> wrote:
>> I have not received any submissions for Telpac, Paclink, PMBOs or other
>> stations for theFADCA database.  As soon as everyone can recover from the
>> hurricanes, please start sending the applications for coordintaion so we 
>> can
>> get the database cleared of non working and up-to-date on the new and
>> working devices.
>>
>> Here is what is on the web site now (formatting does not come over from 
>> the
>> web site.):
>>
>>                              TELP
>> N4KOX  Telp Y Russell Oder       Orange Park          144.930 7
>> KC4OUA Telp Y William Guthrie    Jacksonville         145.010 7
>> KF4SIR TelP Y KF4SIR             Winter Park          145.07  5
>> W1NPR  Telp Y W1NPR              Englewood            145.09  6
>>
>> I appended this message to a Winlik reflector entry that has a good link 
>> to
>> Kentucky EMCOMMS display.
>
> Here in Tampa we will follow what we have established years ago for 
> services.
> The TelPac node will hang off of a switch, I will supply the address
> for the node
> as soon as we get it up, but it should be a 8132xx address. It will be 
> available
> from anywhere on the network of course. So any user port on our network 
> will
> view it as one of the network services rather than a standalone device.
> _______________________________________________
> FADCA mailing list
> FADCA at mailman.qth.net
> http://mailman.qth.net/mailman/listinfo/fadca
>