I think the issue there is simply that the majority of people just don’t do
Callsign Routing, and depend on DPlus routing instead on the K5TIT network.
So while this is a good technical solution, the knowledge and ability to do
it seems to be sliding away.  I suspect its not something that newcomers pay
a lot of attention to either. It’s a shame really, but having the ability to
reduce the “lag” in synchronising between callsigns as they move from
Repeater to Repeater is a valuable one. It just feels like its arrived too
late. If this was around near the beginning of the WW expansion of the
D-Star network, perhaps we wouldn’t have needed DPlus. Or perhaps DPlus and
Reflectors would have taken a different direction. So the ability to
Callsign Route and exchange information across Networks on a Routing basis
is a very positive development, but its just the lack of routing that’s
probably having the biggest impact on it. Who knows, but I also like the
Callsign Squelch feature in the radios. And again, because people don’t
route directly, or callsign route, it’s a feature rendered useless in the
radios.

 

Difficult to see how you increase uptake, DPlus and the Reflectors just seem
to be a lot easier in comparison to Direct Routing. I do accept that there
may be areas of the world where this might be the preferred way of doing
things, but none spring to mind as I write this, notwithstanding those who
currently have it installed on their repeaters.

 

Dex

M0TMX

 

From: [email protected] [mailto:[email protected]]
On Behalf Of john_ke5c
Sent: 30 July 2010 15:44
To: [email protected]
Subject: [DSTAR_DIGITAL] Re: Please help me support D-Star ...

 

  

> Just waiting for the "Open vs Closed" debate to start (again!) 

For callsign routing there wouldn't have to be a debate if folks would
utilize ircddb:

http://db0fhn.efi.fh-nuernberg.de/doku.php?id=projects:dstar:ircddb

Only a handful of gateways on all systems have installed it, however:

http://ircddb.net/

Maybe it's a start.

73--John



Reply via email to