They each have their purpose, we just need better gateway software. -- John D. Hays 206-801-0820 Sent from my iPhone
On May 15, 2009, at 20:28, "Woodrick, Ed" <ewoodr...@ed-com.com> wrote: > > > > > Easy solution, stop callsign routing. Use repeater linking instead. > Problem solved. > > Ed WA4YIH > > From: dstar_digital@yahoogroups.com [mailto:dstar_digital@yahoogroups.com > ] On Behalf Of Nate Duehr > Sent: Friday, May 15, 2009 2:29 PM > To: dstar_digital@yahoogroups.com > Subject: Re: 880 vs 800 (was: Re: [DSTAR_DIGITAL] Signal Distance) > > Case in point: D-Plus linking is great, but it wasn't implemented in a > way to avoid the problems associated with mixing it with callsign > routing. I callsign route to a repeater that's involved in a D-Plus > link and (in my opinion) "bad" things happen. > > A sure sign that an attempt to make an already-working system > "easier", > actually makes it harder in the corner-cases, but "easier" in the > general sense. > > Not trying to embarass anyone, but here's another example: I had an > e-mail today from one of our local leadership people saying, "Please > keep Port B clear for an event tomorrow." Okay, well.. let me explain > here... in a callsign-routed "always on" network, there's no > "keeping it > clear" unless you want me to kill off D-Plus and the Gateway for ALL > of > the modules... your Net Controller instead NEEDS to know how to > reply to > a link made inbound from somewhere else and politely disconnect it, or > respond to an interloping Dongle user, or how to hit the one-touch and > reply to a callsign-routed "CQ" and explain there's a Net going on. > The > network is ALWAYS on in D-STAR... unless you're directing me to shut > down the Gateway... was my reply... > > That's my opinion anyway... "Power to the people" so to speak. LOL! > > Nate WY0X > -- > Nate Duehr > n...@natetech.com > > [Non-text portions of this message have been removed] > > [Non-text portions of this message have been removed]
