[aprssig] APRS => Winlink Messaging

[Andrew Rich (Home)]

Interesting

I have been able to pluck email addresse form the IS stream. Anthing should 
be possible.

Do you want to go from mobile to email ? Is that the aim ?

Seems you might be heading for the need for a message type descriptor.

In mobile phone protocols we used to have message type descriptors.

Ie FAX EMAIL SMS PAGER message was the destination.

MSG002 might be email
MSG003 might be fax
MSG004 might be SMS
etc

Add new ones as different needs arrise.

I am just a bit worried by adding adhoc APRS triggers you might end up with 
a mess.

Perhaps comma's could be used to help tell the other end how to break up the 
data ?

Or perhaps a space would do the trick ?

I have been playing iwth the idea of messaging as well, I don't care where 
the packet came from, as long as the packet contains the right series of 
characters I can split up the data and act on it.






----------------------------------------------------------
Andrew Rich
Airways Technical Officer Grade 4
Surveillance - RADAR ADS-B
Amateur Radio Callsign VK4TEC
email: vk4tec at tech-software.net
web: www.tech-software.net
----- Original Message ----- 
From: "Bob Bruninga " <bruninga at usna.edu>
To: <aprssig at tapr.org>
Sent: Sunday, September 13, 2009 1:36 AM
Subject: [aprssig] APRS => Winlink Messaging


> We need an author:
>
> I was told that we cannot use APRS to send email to Winlink accounts from 
> the APRS mobiles because winkink needs a special SUBJECT line.  Therefore, 
> if I understand the problem correctly we cannot do this presently.  Here 
> is what we need:
>
> *** An engine (like the EMAIL engine) that monitors the APRS-IS for a 
> trigger ADDRESS, lets say "WLK".  If anyone uses their radio to send an 
> APRS message TO WLK then this happens:
>
> 1) The first word of the message is the CALLSIGN of the winlink addressee 
> (example:  WB4APR, we are here and ready at 1430. ).
>
> 2) The WLK engine takes this APRS message and creates an EMAIL of the 
> form:
>
> TO:    WB4APR at winlink.org
> FROM:  (your radio callsign)
> SUBJ:  //WLNK (or whatever the special format is)
> MESSAGE: we are here and ready at 1430.
>
> *** Message originated from station (your call)
> *** on the APRS system.  Location is now
> *** at this link (**** LINK to APRS-IS map display)
> *** To reply, reply to this message, though APRS
> *** is a live message system only, and will not
> *** be delivered unless station is currently active.
>
> They way it was explained to me, is that the above EMAIL is not accepted 
> by WINLINK system unless there is the special SUBJECT line (something like 
> above) to help guard against spam.  So that is why we cannot currently 
> send APRS messages to Winlink addresses because we do not have a subject 
> line.
>
> Notice that I did suggest that this "WLK" engine will accept REPLY 
> messages and will inject them back into the APRS-IS!  This should be safe, 
> since we have to assume that a callsign originator on WINLINK is a 
> licensed ham and his communication is legitimate.
>
> Again, I am not a WinLINK expert and I only heard about this issue second 
> hand, so I could be mistaken, and maybe there is already a workaround for 
> this issue..  If so, ignore me.
>
> If not, then, this is the kind of gizmo we need to add to the APRS quiver 
> so that we can be one step closer to the UNIVERSAL HAM RADIO TEXT 
> MESSAGING initiative where  we can message ANY HAM, ANYWHERE, using ANY 
> DEVICE, by callsign alone.  See Sept Issue of QST.
>
> Bob, Wb4APR
>
> _______________________________________________
> aprssig mailing list
> aprssig at tapr.org
> https://www.tapr.org/cgi-bin/mailman/listinfo/aprssig


--------------------------------------------------------------------------------



No virus found in this incoming message.
Checked by AVG - www.avg.com
Version: 8.5.409 / Virus Database: 270.13.92/2364 - Release Date: 09/11/09 
17:51:00