On Tue, 19 May 2009 08:30:36 -0600, "Barry A. Wilson" <[email protected]> said:
> (NOTE: I know how we identify MYCALL has been left open to local > interpretation because there are a few operators here in Denver that like > to > play with erroneous MYCALL callsigns like RG8U or COAX because they > think > it is cute and as long as they ID in voice they feel using unassigned > calls > in digital is OK. ItÂ’s not their concern what gets routed and > retransmitted > by someone else remotely if on the Gateway. BAD PRACTICE? Some would say > yes. I personally will always interpret the rules along with good > amateur > practice to operate with the intent of the law and not necessarily how to > get around the rules so as to be cute.) [Sorry folks, going to go into a couple of local-only topics for a minute here, but Barry is always complaining about "RG8U" incessantly on the NATIONAL list, and he doesn't talk about it at all on the LOCAL list or even ask me or any of the other leadership team members who is doing it... so...] Barry, Watching you get all riled up about that fake callsign over and over again is quite entertaining. I know EXACTLY who set up a rig with RG8U back during system testing, and it's still floating around in the memory of that rig, and I think I know EXACTLY why they keep doing it... Hint: By now, it's just to annoy you. No one else cares. Get a clue. They happen to have donated over $2000 worth of gear and were instrumental in getting a repeater site -- without them, Colorado D-STAR wouldn't have won the RFP process from HRO or even been viable. You MIGHT want to ask locally before you rant for months about someone on the national list. Just seems like a good idea to me... but do what you like. To your point where you think they don't care about where they "route" to... you're forgetting that callsign can't route ANYWHERE because it's NOT REGISTERED. The dstarusers.org folks publicize non-registered transmissions without vetting them as even being valid Gateway users -- but that isn't my problem. I've already been shouted down by the mob here for wanting a way to ensure privacy at the Gateway (feed) end of that data, but the anti-privacy mob says that the whole world needs to know when we all key up, here in the U.S. Thus, a very strange U.S. Only requirement... I don't see any dstarusersjapan.org publication of all of their transmissions? Whatever. Publicizing every key-up without stripping the non-registered users is silly if the point is to foster activity -- since no one can call that callsign, and that callsign can't callsign route, command the Gateway D-Plus, etc. (I don't allow non-registered callsigns to command the links, ever since Robin added that feature... for example.) The only three places "RG8U" shows up: 1) On your rig locally. If you see it, you'll recognize the voice. 2) In the Gateway logs. I see those, and know who it is already. 3) Dstarusers.org because they insist on publishing it, even though it's not registered and couldn't route anywhere. You might want to stop attacking one of the group's benefactors on a national mailing list before you've even asked about it on the local list. (And at this point, it's so funny that you don't know who it is, we'll probably keep you in suspense! Hahaha!) Now back to something actually useful, hopefully... since this particular issue is a non-issue, other than it very CLEARLY proves that the so-called "callsign" field in D-STAR... isn't. It's just a network address, set by the user and utterly changeable. Only an operator's good-will keeps it set to a callsign, really. Relying on having a CALLSIGN in that field is silly in the extreme. It's nice if everyone does it, but the field itself and the technology really don't "care" what's in the rigs at all. It's just an alphanumeric field. No amount of wishful thinking will stop someone from copy-catting a callsign to gain access to routing... eventually. Nate WY0X -- Nate Duehr [email protected]
