Order Tray | Contact Us | Home | SIG Lists

[aprssig] APRS Field Events

Curt, WE7U archer at eskimo.com
Wed Oct 19 15:00:28 UTC 2005

On Mon, 17 Oct 2005, Robert Bruninga wrote:

> >>> "Curt, WE7U" <archer at eskimo.com> 10/17/05 3:09 PM >>>
> >> Here is the list of recommended calls:
> >>
> >FOUR-H will get igated to RF fine as a 3rd-party
> >packet, but nobody can send that call out directly
> >on RF as it's not a legal AX.25 callsign...
> >Same goes for REDCROSS  [ too long]
> But in most code, it doesnt matter.  It is sent
> in MSG format which doesnt use any of the
> AX.25 fields.  At least APRSdos doesnt care.
> We better check other codes though...

Perhaps I'm a bit confused on this issue...   If two stations were
talking, one using the callsign REDCROSS, and another using WE7U-7,
then they could communicate if the REDCROSS station were directly on
the internet.  The WE7U-7 station could be on either internet or RF.

If the REDCROSS station however were on RF, whether going through an
igate to get to WE7U-7 or communicating directly on RF between them,
the two could not talk.  WE7U-7 could send a msg to REDCROSS, but
REDCROSS could not send a message to WE7U-7 due to the excessive
length of the "callsign".  That's what I was getting at.

  WE7U-7>APRS::REDCROSS :Test Msg{00}
  REDCROSS>APRS::WE7U-7   :ack{00}

See the problem?  That second packet cannot happen as "REDCROSS" is
longer than six chars + SSID.

Curt, WE7U.   APRS Client Comparisons: http://www.eskimo.com/~archer
"Lotto:    A tax on people who are bad at math." -- unknown
"Windows:  Microsoft's tax on computer illiterates." -- WE7U
"The world DOES revolve around me:  I picked the coordinate system!"

More information about the aprssig mailing list