> Date: Tue, 3 Aug 1999 23:30:46 +0200 (CEST)
> From: Michele A Debandi <[EMAIL PROTECTED]>
> Subject: Re: CEPT callsigns
> [...]
> My explanation: due the fact that IEEE 802 adresses aren't for free
> (you have to pay the right to register a block of addr
Riley Williams wrote:
> My understanding is that both Spain and Greece have stated that they
> expect to run out of callsigns with three letter suffixes by 2002, and
> that they propose to issue callsigns with four letter suffixes unless
> additional prefixes are made available.
This is completl
On Tue, Aug 03, 1999 at 06:50:15PM -0500, Nate Bargmann wrote:
>
> P.S. Who "owns" the AX.25 protocol, and what is the process of fixing it
> and having those changes recognized by major organizations like ARRL and
> TAPR (or do they matter anymore?)?
ARRL turned it over to TAPR. I'm not really
On 03-Aug-99 Walter Koch wrote:
>>The requirement to comply with the regulations is
>>that the FULL BASE CALLSIGN be inserted in the address field.
>
Sorry, this is a) off topic and b) national.
Riley, please would quote the paragraph in BR68 and/or WT acts which
demonstrate the assertion you
Riley Williams wrote:
> My understanding is that both Spain and Greece have stated that they
> expect to run out of callsigns with three letter suffixes by 2002, and
> that they propose to issue callsigns with four letter suffixes unless
> additional prefixes are made available. I also understand
Moin,
> > Just put GB50BO in the callsign field...
>Thereby contravening the regulations in just about EVERY country
ok. bad example. Use GB50?? in the callfield. Or the callsign of the
original operator. Or, or, or...
> > But those celebration-callsigns are IMHO rare and therefore a
> > mino
> "Riley" == Riley Williams <[EMAIL PROTECTED]> writes:
Riley> My understanding is that both Spain and Greece have stated
Riley> that they expect to run out of callsigns with three letter
Riley> suffixes by 2002, and that they propose to issue callsigns
Riley> with four letter
On Tue, 3 Aug 1999, Robin Gilks wrote:
> Have looked long and hard through BR68 I can't find ANYTHING that
> even mentions AX25 never mind that a callsign MUST be used as
> a part of the protocol.
>
> Do not confuse station identification (necessary by MORSE in the UK)
> with the particular digi
> Date: Tue, 3 Aug 1999 12:17:29 +0100 (GMT)
> From: Riley Williams <[EMAIL PROTECTED]>
> Subject: Re: CEPT callsigns
> [...]
> Put bluntly, anybody following Walter's suggestion had better ensure
> that the 'shortened form' they use has NEVER be
Hi Tomi.
> I tried to keep my hands out of this but... :-)
>>> Just put GB50BO in the callsign field...
>> Thereby contravening the regulations in just about EVERY country
>> I've ever operated in! Certainly, doing that is against the
>> British regulations, the US regulations, the Canadi
Hi Robin.
Please advise how one would put the callsign GB50BOB into
a packet radio transceiver then?
>>> I do not like to cite my cites but:
>> just using DL1NC and (just in case) sending a beacon every 10
>> minutes containing my complete callsign and QTH. If anybod
Hi Andrew.
>>> Just put GB50BO in the callsign field...
>> Thereby contravening the regulations in just about EVERY country
>> I've ever operated in! Certainly, doing that is against the
>> British regulations, the US regulations, the Canadian
>> regulations, the French regulations...should
I tried to keep my hands out of this but... :-)
> > Just put GB50BO in the callsign field...
>
> Thereby contravening the regulations in just about EVERY country I've
> ever operated in! Certainly, doing that is against the British
> regulations, the US regulations, the Canadian regulations, t
- Original Message -
From: Riley Williams <[EMAIL PROTECTED]>
To: Walter Koch <[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>
Sent: 03 August 1999 10:35
Subject: Re: CEPT callsigns
> Hi Walter.
>
> >> Please advise how one would put the callsign
On Tue, 3 Aug 1999, Riley Williams wrote:
> > Just put GB50BO in the callsign field...
>
> Thereby contravening the regulations in just about EVERY country I've
> ever operated in! Certainly, doing that is against the British
> regulations, the US regulations, the Canadian regulations, the Fre
Hi Walter.
>> Please advise how one would put the callsign GB50BOB into a
>> packet radio transceiver then?
> I do not like to cite my cites but:
just using DL1NC and (just in case) sending a beacon every 10
minutes containing my complete callsign and QTH. If anybody
w
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
Hi Walter.
>>> 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.
> No. It is IMO not necessary to put your whole callsign into the
> address fields.
Please advise how one would put the callsign GB5
Moin,
>On Sat, 31 Jul 1999, Riley Williams wrote:
>> 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.
No. It is IMO not necessary to put your whole callsign into the
adressfields. Exactly as dl1nc wrote:
>
Hi Dirk.
>> In fact, the HDLC standard on which it is based already defines
>> how such a system is to be handled, and precicely what should
>> occur under all possible scenarios, so there's very little to be
>> agreed on other than precicely what is meant by "Extended mode"
>> as opposed to
On 01-Aug-99 Riley Williams wrote:
> In fact, the HDLC standard on which it is based already defines how
> such a system is to be handled, and precicely what should occur under
> all possible scenarios, so there's very little to be agreed on other
> than precicely what is meant by "Extended mode"
What is this all about?
When I travel I just use my license - No one in the UK even cares.
So much junk mail over one issue.
(Filter On)
> Remember that marine and amateur licences include several clauses that
> conflict, giving different requirements. This is presumably one of
> them.
>
> > .
Hi Geoff.
>> 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.
> Are you ce
When I first returned to the UK from the US (where I was first licenced), my
reciprical call was
g0/n6lyt, so I had to just use n6lyt for packet, but did id with g0/n6lyt.
-- John Melton g0orx/n6lyt
On Sat, 31 Jul 1999, Riley Williams wrote:
> 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 th
Hi Thomas.
>> ie. bit 0 is set to say this is the end of the address field -
>> by this means, AX25 (and X25 on which it is based) already
>> support variable length address fields.
>> That most implementations don't support it is another matter
>> entirely!!!
> Well, this is not exactly
Hi Robin.
>> 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.
>> My suggestion would be to make it dynamic to suit th
Hello Riley,
> >> 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.
On Sat, Jul 31, 1999 at 01:40:08PM +0100, Robin Gilks wrote:
> ie. bit 0 is set to say this is the end of the address field -
> by this means, AX25 (and X25 on which it is based) already
> support variable length address fields.
>
> That most implementations don't support it is another matter
> e
Hi here is the form you need to apply for a German license.
73
Wayne
N1WPN
I used to be DA2YD
mstr_antrag.doc
There was a ham with a French callsign running a BBS in Texas. He just
used his F callsign for connecting and beaconed an I.D. with the w5/, as
I recall. This may have been confusing to some, but is legal in the
U.S., possibly elsewhere.
Bob
On Sat, Jul 31, 1999 at 09:25:54AM +0100, richard bo
Hi Robert.
>> 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, th
- Original Message -
From: Riley Williams <[EMAIL PROTECTED]>
To: Richard Bown <[EMAIL PROTECTED]>
Cc: Linux Ham Radio <[EMAIL PROTECTED]>
Sent: 31 July 1999 13:02
Subject: Re: CEPT callsigns
[snip]
> To be honest, the AX.25 specification needs SERIOUS revisi
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 proble
Hi Richard.
> Hi all, as I will be working in Germany for the next year, no
> that doesn't mean you wont hear from me !,
Chuckle...
> 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 c
On Sat, 31 Jul 1999, richard bown wrote:
> now how about the followingdc/g8jvm a perfectly valid callsign
> but the "/" is not accepted or any other delimiter.
Isn't the ax25 protocol itself limited to 6 chars in the call?? I havent
seen any tnc/programs that supports more than 6 chars
On 31-Jul-99 richard bown wrote:
> 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 German s
> can be !.
> Or is it a case of so what we'll just wait til some country uses 7 char
> callsigns, well that may not
37 matches
Mail list logo
