At 05:59 AM 4/9/2010, you wrote: >This is more a sign of really poor integration of the regular >features vs. the add-on features, than anything. If the two were >"aware" of each other in any way, a message could be sent back to >the user who is "barging" in saying the remote system is linked somewhere.
There's still the issue of local QSOs, source routing is still rather "blind" that way. Being one who did have to source route for a few months, as the only way to get out of the local area, I did get to learn that method. Also, things got tricky when we had people source routing from two different places, so which do you reply to? ;) Often this was because source routing was already in use with a couple of locals talking to one station, then someone else drops in. They get no busi indication, because they actually manage to time it for the break between transmissions (Murphy's Law). So, not all routing conflicts are with DPlus. Some are with local users, and some are with other source routed traffic, and sometimes you coincidentally time it so you manage to cause a bit of confusion. :D That said, there are a few scenarios where I will still use source routing. It's low overhead (no need to tear down a default link, establish a new link, then tear that down when you're done) and has some smarts for finding people. >Easy to fix, if Icom were really interested. They're not. And >D-PLUS can't do it all "alone" so to speak. It would require a new >release of Gateway software that had been built with linking in mind. That would help too, though being able to source route while a system is linked has its advantages too, like for that quick call - a couple of overs and you're gone type of thing (assuming the link itself is idle at the time). >As it stands today, two things must happen... Both common sense and basically what I do. >THE ONLY REASON you find callsign routing "a problem" is because >people refuse to learn it. Anyone that understands it, can deal >with it... including hitting their One-Touch button to route back to >the "interloper" and tell them what's happening. I agree here. >Trying to treat D-STAR like it wasn't source-routed and adding >software to make it act like an analog system, is what got us to >this so-called "problem" in the first place, not the other way around. Both methods have their place. Source routing works well for some scenarios, not for others. In particular, it doesn't handle large scale nets well (the multicast feature requires administrative intervention, and concentrates bandwidth use where it's least appropriate - at the end nodes). It does handle point to point traffic very well. 73 de VK3JED / VK3IRL http://vkradio.com
