On Friday 13 April 2007 13:38:21 Fredrik SM6VTT wrote:
> I agree!
> Its a big problem when users don't know the commands. It should be a
> standard for all nodes. At least connect and disconnect. Perhaps it could
> be changed in a config file? In a easy way... Then the sysop can change it
> to the same commands as in the windows version.
Yes, I realized that this would be a problem when I designed the DTMF command
system. The problem is that SvxLink is not just an EchoLink client. EchoLink
is just one of the voice services of the system. I didn't want to get caged
by the EchoLink DTMF command system. I wanted a more logical system. But of
course, it's only more logical if you know how it work.
For local users it's less of a problem. The real challenge is for unfrequent
users and users that pass by.
My original thoughts of how to remidi this situation was to have a good help
system. The current help system is quite basic and must be improved. This is
high on my TODO list. The identify DTMF command is *, just like in EchoLink.
That is no coincidence. My thought was that the identification message would
lead the user on the right track, directing them to the help system. That is
not so at the moment but that is quite easy to fix. Just add a message at the
end of the identification: "press zero hash for help".
This is what I plan to do with the help system:
* Drop the Help module. Make the help system a core function instead.
* The new help system should be consistent in use for both the core and the
* Command 0 should always give a short help message that is context related.
* Command 0n should give detailed help on function "n".
* A user passing through try a couple of EchoLink commands that fail.
* He know the *-command since it's the same in EchoLink. If I was looking for
an EchoLink or SvxLink node the *-command is what I would use to check if I'm
* When the node answers it identifies and ends the identidfication
with: "press zero hash for help".
* The user hopefully is smart enough to press 0#. The node say: "One -
Activate module Parrot, Two - Activate module EchoLink, Three - Activate
module voice mail. End all commands with a hash. Zero hash will always play a
context sensitive help message. Zero command number hash will play detailed
help on the given command number."
* The user now know how to activate the EchoLink module so he press 2#.
* Hopefully he have also got the message that 0# is worth remembering so he
press 0#. The node say: "One - Connection status, Two - Own node id, Three -
Random connect, Four - Reconnect, Five - Listen only, * - Connect by
callsign, Node id - connect to the specified EchoLink node".
* He get curious about the random connect feature so he press 03#. The link
say: "The random connect feature is used to connect to a random link,
repeater or conference. Three one - random link or repeater, Three two -
* And he also got the message that connecting to another EchoLink station is
done by entering the node id, just as in EchoLink. Hopefully he also remember
to press #.
Well, I think you've got it by now. I hope this will be enough for a user who
is totally unaware of the existance of SvxLink to at least get an EchoLink
connection established. Hopefully, by making good use of the help system, he
could also use the full power of SvxLink.
Another thing one might do to help EchoLink users, when in "idle mode", are
to automatically activate the EchoLink module and initiate a connect if a
command >= four digits in length is received. That is a step away from what I
think is a logic DTMF command system but if it help the users it might be
Another thing one might consider is to implement an EchoLink compatibility
mode where SvxLink behaves as close as possible to the original EchoLink
application. This would be the default mode. There would be a command to
switch the link into SvxLink mode when the other features are going to be
accessed. This is of course a much bigger job and I'm not sure I even like it
A comment about configurable commands, I don't like that idea of the same
reason as the one that started this discussion. All nodes should have the
same command set.
73 de SM0SVX / Tobias
> 73 de Fredrik SM6VTT
> ( Sysop node 211110, SK6DW-R http://www.sk6dw.se )
> >I agree, Birger. Users, especially those who are passing through and
> > have never used SVXlink, expect the DTMF functions to be the same as
> > what they use on all Echolink nodes. They have no way of knowing what
> > these different functions are. They even confuses those of us who have
> > SVXlink nodes but also use other's Echolink nodes.
> > Tim WB4BAH
> > Birger Olsson wrote:
> >>Nice work!
> >>But why not try to harmonize with the windows version and use the same
> >>commands? Its hard for users when every other link have different
> >>73 Birger, SM6VQJ
> Take Surveys. Earn Cash. Influence the Future of IT
> Join SourceForge.net's Techsay panel and you'll get the chance to share
> your opinions on IT & business topics through brief surveys-and earn cash
> Svxlink-devel mailing list