[aprssig] APRS Calling

[Robert Bruninga]

John,

The proposal to Kenwood and Yaesu is to use the same format for the
FREQ-IN-MESSAGE format as in the STATION or OBJECT formats.  No reason to
re-invent the wheel.  No, it is not a conversational message in human
form, but someone who receives it can cleary see all he needs.

Message from someone..... QSY 147.105MHz T141 +600 ... Joe

Means to call Jo on that freq, tone and offset.  All we do to make it a
message is to p ut "QSY " in front of it.  Im doing this from memeory, but
somewhere I have a spec that nails it down...

Bob, Wb4APR

-----Original Message-----
From: aprssig-bounces at tapr.org [mailto:aprssig-bounces at tapr.org] On Behalf
Of John Gorkos
Sent: Monday, October 22, 2012 12:04 PM
To: Andrew P.; aprssig at tapr.org
Subject: Re: [aprssig] APRS Calling

The message sent to the originating station looks something like this:
String.format("CALL %s on %3.3f MHz T%-3s %s node %d", bestTarget, freq,
tone, type,
            nodeId);


Or, CALL W1XYZ on 146.820 Mhz T141.3 Echolink node 12345
So, assuming it's a standard EchoLink node, you would usually use the
standard "#node-number" format.
If you're using a "closed" system that requires an access code (like my
local IRLP node), you're pretty much SOL unless you know the codes.


On 10/22/12 11:53 AM, "Andrew P." <andrewemt at hotmail.com> wrote:

>Just out of curiosity, what would make the Echolink/IRLP/AllLink nodes
>actually connect to each other, too? Even if the the two end-point radios
>did QSY to the locally appropriate frequencies, etc., what makes those
>two repeaters talk to each other? Or would one of the radio operators
>have to tone-command the linked repeater to bring up the link?
>
>Andrew Pavlin, KA2DDO
>------Original Message------
>From: John Gorkos
>To: aprssig at tapr.org
>Sent: Oct 22, 2012 8:46 AM
>Subject: Re: [aprssig] APRS Calling
>
>
>
>
>On 10/21/12 4:29 PM, "Robert Bruninga" <bruninga at usna.edu> wrote:
>
>>
>>The FREQ-QSY Format is already there.  The radios will do the
>>one-button QSY, and it will all work, just as you have suggested.
>
>Actually, this is where things fall apart.  The radios will not recognize
>a FREQ object to QSY to in a message, which is critical to the whole "One
>button tune" concept.  This is where AVRS currently falls down. The
>process should be:   N1ABC sends an APRS message to AVRS with the
callsign
>of the person he wants to have a voice contact with (W1XYZ).  AVRS finds
>that person (who has to be running an APRS system) and finds the closest
>echolink/allstar/irlp nodes to both N1ABC and W1XYZ.  AVRS then sends a
>message to W1XYZ with the QSY information, and a note saying N1ABC is
>looking to talk to you.  W1XYZs radio ACKs that message bck to AVRS, and
>then AVRS sends a message back to N1ABC with QSY information and the node
>number of the node that W1XYZ is now listening to.  In the perfect world,
>the two users would hit the "TUNE" button, and the radio would auto-QSY
to
>that frequency.  Unfortunately, no radio on the market parses QSY data
>from MESSAGES, so the system falls down right there.  The users need to
>manually change frequencies, offsets, and set up the tone squelch for the
>internet link frequency.  Hence, AVRS is about as useful as a screen door
>on a submarine.  The system is still up and running, and get occasional
>hits, but there's too much manual diddling to make it as effective as
>D-STAR or DMR.
>
>John Gorkos
>AB0OO
>
>
>
>_______________________________________________
>aprssig mailing list
>aprssig at tapr.org
>https://www.tapr.org/cgi-bin/mailman/listinfo/aprssig
>
>
>Sent from my Verizon Wireless BlackBerry



_______________________________________________
aprssig mailing list
aprssig at tapr.org
https://www.tapr.org/cgi-bin/mailman/listinfo/aprssig