[aprssig] Echolink/IRLP objects for the mobile

[Robert Bruninga]

EchoLink/IRLP for the APRS mobile:

I am told that most local EchoLink nodes are OPEN and use the
same standard Access method....  Just used DTMF to dial the
desired Node anywhere in the world, and the link comes up.
Press # and it goes down.  Thus talking voice to any other Ham
operator is even simpler than using an Autopatch.  (6 digits
instead of 10)

So, I am gungho on getting these local OPEN EchoLink and IRLP
objects out to the mobile operator.  After a lot of learning
last week we figured out how to do it simply and effectively.
Just put them in the (now 3 slots for this purpose) in the local
digi as noted in the original email below.

But I was surprised when I was rejected by a digi operator that
would not support EchoLink at all, and only IRLP.  I thought
this battle was over long ago, and that the two are getting
along quite well.  I know there is a bias against all the
non-radio Shack-potato's on EchoLink (same problem with
shack-potato's on APRS), but, then this initiative to get these
objects on APRS has nothing to do with the shack-potatos, only
on-air ooperation.  We are only interested in OPEN Echolink
Repeaters or links.  Can someone enlightmen me if this
anti-echolink bias is still pervasive?

Bob, Wb4APR

> -----Original Message-----
> From: aprssig-bounces at tapr.org 
> [mailto:aprssig-bounces at tapr.org] On Behalf Of Robert Bruninga
> Sent: Thursday, July 23, 2009 5:56 PM
> To: 'TAPR APRS Mailing List'
> Subject: [aprssig] Immediate Local Object Solution!
> 
> A SOLUTION!
> 
> OK, Here is an easy way to get this info (EchoLink objects)
out.
> Now.
> 
> Each KPC-3+ and many other TNC DIGI's have 3 or 4 LOCATION
TEXTS
> plus one BEACON Text.  Under the New-N Paradigm, we used up
all
> of the LOCATION texts for the digi's proportional pathing
> beacon, and reserved the Btext for the LOCAL-FREQ-OBJECT.
> 
> Now that everyone has more or less bought into the New-N
> paradigm, we can relax the Proportional Pathing and free up
more
> of those Ltexts for such use as the local Echolink Objects.
SO
> how about this.
> 
> 1) We significanly reduce proportional pathing from all digis.
> 2) The digi will beacon every 10 minutes DIRECT and a single 2
> hops every hour.
> 3) This frees up 2 Ltexts for EchoLink or other important
> objects
> 4) The Btext is still used for the local voice freq object
> DONE
> 
> This way, it is a WIN-WIN-WIN-WIN-WIN situation:
> 1) We get the local data locally DIRECT
> 2) The DIGI only injects local-info on a clear channel
> 3) This data will not collide with any other packets
> 4) This info will not SPAM areas where the objects have no
value
> 5) It forces us to identify the BEST objects and not SPAM all
> ego repeaters
> 6) It avoids asking for any changes to the APRS-IS
> 
> The only problems are:
> A) Absentee digipeater sysops
> B) It took years just to get them to change to New-N settings
> C) The Echolink node status is not live
> D) We loose the 30 minute 1 hop digi beacon
> 
> I ask that ONLY ECHOLINK repeaters and links that are OPEN and
> use the standard Echolink signaling convention without any
> access codes be so beaconed.  This fullfils the original
> objective.  For the mobile, any where, any time, if he sees an
> Echolink node on his radio, he can call home, or do a voice
link
> to anyone anywhere else on the planet.  
> 
> The standard is to simply announce your intentions, dial the
> node you want to link to, and talk.  When done, # down.
> 
> Can we all move out on this?
> 
> And while we are at it, GET THOSE LOCAL FREQ OBJECTS in there
> too.
> 
> AND get rid of those home station SPAM objects that are
> transmitted over thousands of square miles.
> 
> Unless there are objections, Ill start modifying the New-N
pages
> immediately..
> 
> Bob, Wb4APR
> 
> 
> _______________________________________________
> aprssig mailing list
> aprssig at tapr.org
> https://www.tapr.org/cgi-bin/mailman/listinfo/aprssig
>