Hi all,
On Sat, 31 Jul 1999, Riley Williams wrote:
> > Hi all, as I will be working in Germany for the next year, no
> > that doesn't mean you wont hear from me !,
Would be bad, if German e-mail wouldn't make it around the world. Buh! Now
how did I get here? :)
> > I've come across a problem common to linux node, jnos, tnos and
> > fbb and probally a few more as well. All of the above check for
> > valid callsigns , ie 6 characters and a number in it somewhere.
Everybody seems to have implemented his own algorhythm. Some use more
rules than just a number *somewhere*.
> > now how about the following
>
> > dc/g8jvm
>
> > a perfectly valid callsign but the "/" is not accepted or any
> > other delimiter.
G8JVM with a CEPT class 2 license in Germany.
I *have* seen people here using a slash in their AX25-ID, as well as my
kernel-AX25 sending out NULL-Calls (strange, absolutely nothing in the
callsign field, but it worked). But it sure isn't normal and supposedly
depends on each node's AX25-routines.
> Also note that the following is a perfectly valid callsign which also
> doesn't fit in the AX.25 spcification:
>
> PA/GM7GOD/MM
>
> That is the callsign that *I* would have to use if operating from a
> ship sailing in tidal waters claimed by the Netherlands.
AFAIK, this callsign is *not* valid. If the waters are claimed by a
country (xx mile zone), you are IN that country an *not* /MM. So it's
either GM7GOD/MM *or* PA/GM7GOD/p or /m or whatever.
> > So it looks like the only way around this is to apply to the
> > German PTT for a true reciprocal licence , and you know how
> > pedantic the Germans can be !.
Hmm...
> My understanding is that the convention used to deal with this problem
> in the CEPT case is to just use your home callsign without any of the
> prefixes or suffixes.
That is exactly as I have done on the one or other holiday... just using
DL1NC and (just in case) sending a beacon every 10 minutes containing my
complete callsign and QTH. If anybody wants to know more, they can connect
me and ask.
> > Or is it a case of so what we'll just wait til some country uses
> > 7 char callsigns, well that may not be too far off.
>
> Examples have been in use for many years - any UK special event
> callsign with more than one digit in it is likely to qualify. In fact,
> I believe there's been a case of GB100xxxx being issued, which is 9
> characters as it stands.
It's pretty vague, but I remember some line requiring every valid callsign
to follow this scheme: one letter or number, then one letter, then one
number and following it 2 or 3 letters (or was is 1..3 letters?). Anyway,
by this rule most US callsigns would be invalid (e.g. N9KBK), but would
anybody care?
> To be honest, the AX.25 specification needs SERIOUS revision in this
> area, to allow for callsigns of any length or pattern to be used.
> However, it needs to be done in a manner compatible with the current
> standard.
Not only this are needs revision...
> > An help with this one would be very appreciated , especially
> > from anyone in the Munich area who could help with a reciprocal
> > call.
>
> Scotland is a little too far from the Munich area for me to be able to
> help, I'm afraid. Sorry.
Wuerzburg (JN49VS) is a couple hundred kms to the northwest, but contact
me, if you need any help. There also should be a lot of hams in the Munich
area who can help. Or check the DARC-homepage at http://www.darc.de. Or
the RSGB should also have information available.
73, Robert
--
Robert Steinhaeusser, DL1NC/N9KBK
Was "DL1NC" heisst? Alles ueber Amateurfunk auf
http://www.wuerzburg.de/darc-b17/
