[App_rpt-users] Echolink Link Status

[K&R Yoksh]

Yes, this is what I was referring to...

TheLinkBox, TheBridge and RtpDir have all supported the Echolink AVRS 
system, so I was curious if App_rpt did as well..

73.
Kyle
K0KN

--- Original Message ---
Jim,

I believe what people are asking for is to have app_rpt send status updates 
when connects and disconnects occur.  Below is the format for echolink 
status reporting taken from Skip's WB6YMH source for thelinkbox. Looks like 
the connect message would be "=NNTECHTALK at 1530" for example. I assume the 
disconnect message would be " On @ 1545".


EchoLink sends a packet once every 10 minutes to aprs.echolink.org.  It also
sends a packet when the node status changes (i.e., when somebody connects or
disconnects, or the node comes online or goes offline).

The packet is an RTP control packet, and thus is sent to port 5199.

The CNAME portion is the node callsign (including -L/-R), followed by a
slash, followed by a "password", which is actually a hash of the callsign.
However, at this time, the password field is ignored by the server; a future
release of the server will verify the authenticity of the packet by its
source IP address.  So the callsign can be repeated in this second field.

The format of the LOC portion is as follows:


 )EL-nnnnnn!DDMM.HHNXDDDMM.HHW0PHGphgd/FFFFFF/PPPyyyyyyyyyyzzzzzzzz

 Where:

 nnnnnn           is the 6 character node Name or Callsign (right-padded
                  with spaces to 6 chars)
 DDMM.HHN DDDMM.HHW  is the LAT/LONG of the node, using degrees, minutes,
                     and 100ths of minutes, and E/W/N/S
X                    is the letter "E", for EchoLink
 0                   is a "zero",the ICON character
p                    is the power (encoded)
h                    is the antenna height (encoded)
g                    is the antenna gain (encoded)
d                    is the antenna directivity (encoded)
 FFFFFF              is the frequency in KHz
 /PPP                is the PL in whole number Hz
 yyyyyyyyyy          Second line on a D7 (11th to 20th on a D700)
 zzzzzzzz            last 8 not shown on a D7 but are on the D700

 Formats for the variable field YYYYYYYYYY and ZZZZZZZZ:

    Offline:    " Off @HHMM........"  can contain some comment
    On-Line:    " On @ HHMM........"  Time it returned to ON-Line
    Busy:       " Busy HHMM........"  Time it went busy
    Connected:  "=NNnnnnnnn at HHMM"  Shows call/Name of connection

The encoding of the p/h/g/d fields is as follows:

     DIGITS   0  1  2   3   4   5   6    7    8    9
     -------------------------------------------------------------------
     POWER    0, 1, 4,  9, 16, 25, 36,  49,  64,  81  watts  SQR(P)
     HEIGHT  10,20,40, 80,160,320,640,1280,2560,5120  feet   LOG2(H/10)
     GAIN     0, 1, 2,  3,  4,  5,  6,   7,   8,   9  dB
     DIR   omni,45,90,135,180,225,270, 315, 360,   .  deg    (D/45)

For example:   // )EL-K1RFD !4118.52NE07329.97W0PHG7430/144300/000 On @0444
Rdgfld

--
Tim
:wq

On Jan 20, 2011, at 8:08 AM, Tim Sawyer wrote:

> I suspect that the app_rpt echolink client is not reporting to the 
> mothership, not that the mothership is ignoring us. If that's the case, 
> maybe our exalted developer  would add echolink status reporting.
> --
> Tim
> :wq
>
> On Jan 20, 2011, at 7:16 AM, Bryan D. Boyle wrote:
>
>> We're not running Echolink software...so, while we're able to register 
>> our nodes, I'm thinking that the Echolink mother ship is studiously 
>> ignoring, for the sake of display, alternative software that speaks their 
>> language.
>