Moin,
am / On Mon, 2 Aug 1999 13:04:49 +0100 (GMT), schriebst Du / you
wrote:
>Please advise how one would put the callsign GB50BOB into a packet
>radio transceiver then?
I do not like to cite my cites but:
[quoting dl1nc]
> >> 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.
Just put GB50BO in the callsign field, and setup a beacon explainig
"GB50BO = GB50BOB". But those celebration-callsigns are IMHO rare and
therefor a minor "problem" :-)
The field, in which the callsign is usally placed, is an adressfield,
needed to identify the sender, repeater and receiver uniquely. This
could also contain any other worldwide unique ID like your birthday
combined with your locator. The identifier is needed for protocol
purposes and not to identify the sender of the RF.
But we all have an unique callsign, so the callsign is a good choice
for those fields.
But this does not mean, that it is required to put any extension (e.g.
DC/ /mm /p /m /am /A) also into these fields.
Of course, your national PTT could have requested to put the whole
callsign including extension in the ax25.protocol. But if this would
be true, they could never have allowed ax.25...
> > AX25: DC/->DB0IZ-11 v /W0RLI*, /MM, DB0IZ-9 <C C P>
...
>Since the proposed solution just doesn't work,
it does :)
>but the problem definately isn't
>nonsense, as was quite evident prior to your missive !!!
s/nonsense/irrelevant to me/g
BTW: non fixed adress length in a protocol-field aren't funny, even in
software. Even the 0 to 8 digipeter adressfields are annoying. If this
would be combinined with length-infix callsignfields... And this only
for GB50BOB?
Gruss,
Walter
--
Walter Koch Hochdahl am Neandertal
http://www.hsp.de/~koch/ qrv:db0iz-9
[EMAIL PROTECTED] ham:dg9ep@db0iz
[EMAIL PROTECTED]
