I wouldn't use the overloaded silliness of Dayton as a good example of how things are supposed to work.
About all Dayton traffic is good for showing, is that there are times when you should *shut the Gateway DOWN* during events. Better yet, it shows that the software lacks the ability to block calls to a PARTICULAR MODULE. Wouldn't that be nice? A local module and a module that has access to the Gateway? There's a lot of things still missing in the D-STAR Gateway software... if you ask me. It's at "nice beta test" stage, or "just barely release-quality code", really. I'm not even sure I believe the latter yet. As far as your notes about moving from repeater to repeater not working well for callsign routing in Atlanta, that should be #1 on Icom's list of things to fix, we all hope... You could tackle it by using different callsigns yourself for each repeater you use... if you have people locally who are savvy enough to figure that out. "Switching repeaters, call me back with my "A" callsign. Next repeater, call me with "B", or just hit one-touch on this transmission... I already changed over." Etc. It's still quite "do-able" but not pretty. Nate WY0X On Mar 29, 2009, at 6:54 PM, Woodrick, Ed wrote: > Callsign routing works ONLY if the user hasn't recently changed > repeaters. Might not be a problem in WA, but in Atlanta we've got a > number of repeaters and users commonly move back and forth between > them. I regularly use 3 different repeaters and if I'm driving > through town, add a couple of more. > > I'm not talking about normal operations, I'm talking about the > original scenario where there were a number of D-STAR repeaters and > users were spread across them. > > I listened to the repeater at the Dayton Hamfest last year. Since > linking wasn't commonly available then, stations were callsign > routing in. And trust me, they didn "go away after awhile" You > couldn't hold a local conversation because remote stations kept > barging in. > > Ed WA4YIH > > From: dstar_digital@yahoogroups.com [mailto:dstar_digital@yahoogroups.com > ] On Behalf Of John D. Hays > Sent: Saturday, March 28, 2009 11:33 PM > To: dstar_digital@yahoogroups.com > Subject: [DSTAR_DIGITAL] Callsign Routing (Was: Obfuscation of > Callsigns) > > Woodrick, Ed wrote: > > > > But if you are in the middle of a public service event, then there's > > often a bunch of traffic occurring on the channels. And if you > return > > the call, you have to hope that the one-touch worked, and that no > > additional traffic started on the other repeater. And then you've > got > > to remember to switch back when finished. > > Sure that's not much when you are sitting down, with the radio or HT > > in front of you. But if you are driving down the road or shadowing > an > > event official as the run all over the place, it just isn't the > > easiest thing to do. > > > > Remember, that in this hobby there are a LOT of people who have > > problems figuring out how to get PL turned on. > > > > Ed WA4YIH > > > > > > > > > > Chances are if nobody can get back to the remote station, he'll just > go > away after a couple of calls. (For an event, you should have a net > control, who is capable of handling this situation, and/or turn off > the > gateway until its over.) Most repeaters are so quiet that the chance > of > a "barge in" from a remote station is almost negligible. Callsign > routing is a good technology if you are looking for a specific > station. > > It's part of the design and protocol of D-STAR. If you use the mode, > you should know how to use callsign routing and deal with the > occasional > "visitor" -- if you just want audio linking, there are plenty of > choices. > > -- > John D. Hays > Amateur Radio Station K7VE <http://k7ve.ampr.org> > PO Box 1223 > Edmonds, WA 98020-1223 > VOIP/SIP: j...@hays.org<mailto:john%40hays.org> > <sip:j...@hays.org<mailto:john%40hays.org > >> > Phone: 206-801-0820 > 801-790-0950 > Fax: 866-309-6077 > Email: j...@hays.org<mailto:john%40hays.org> > <mailto:j...@hays.org<mailto:john%40hays.org > >> > > [Non-text portions of this message have been removed] > > [Non-text portions of this message have been removed] > > > -- Nate Duehr n...@natetech.com ------------------------------------ Please TRIM your replies or set your email program not to include the original message in reply unless needed for clarity. ThanksYahoo! Groups Links <*> To visit your group on the web, go to: http://groups.yahoo.com/group/dstar_digital/ <*> Your email settings: Individual Email | Traditional <*> To change settings online go to: http://groups.yahoo.com/group/dstar_digital/join (Yahoo! ID required) <*> To change settings via email: mailto:dstar_digital-dig...@yahoogroups.com mailto:dstar_digital-fullfeatu...@yahoogroups.com <*> To unsubscribe from this group, send an email to: dstar_digital-unsubscr...@yahoogroups.com <*> Your use of Yahoo! Groups is subject to: http://docs.yahoo.com/info/terms/