Using command mode via a SHARI mode into an ALLSTAR repeater

I have searched a bit through the responses regarding this topic and poked around for an EXAMPLE.

I am able to put my SHARI NODE in COMMAND MODE using *4 node number. I get that far. I hear the mechanized voice “COMMAND MODE”. The commands I enter for the distant node do not seem to be working SO, what exactly qualifies as a properly formatted COMMAND that will work and in WHAT FORMAT ? * and the command ? I have some CUSTOM commands for my system and they are not being recognized when using COMMAND MODE through the Shari Node. *XXX (Not sharing the exact code for privacy sake) works fine on the input of the other node, my repeater.

Once you enter ‘command mode’ on some other node, all of your commands will be sent to that node and are therefore the same as if you were commanding the local node.
No special formatting is required.

But it might be important to first connect to the target node *3xxxxx and then command mode
(shortcut) *40
All of alison telemetry will come back to you as if you were on the local node.

If you are having a issue and understand all this,
the first look may be to watch asterisk in foreground and watch what is happening in real time.
asterisk -rvvv
Perhaps some of your dtmf is not being read or something simple like that.
But watching it live will give you some clue to the error.

The other thing to remember is that even in command mode, only that nodes command list are valid. You may not run commands from the local node and expect those to work on the remotely commanded node. They would need to be in the remotes command list only.

Hopefully that gets you somewhere.

I need to look on mine. I have a HF remote that I control from a 927 MHz repeater. I think the remote function list is in both rpt.conf files. But I can comment out those in the 927 radios allstar computer and see if I can still control the remote base. Is that the kind of scenario you have there or just non remote base commands… just added repeater command for the remote end? And yeah they all start with *…

My remote is off right now, I’m making an image of its drive for archiving at this moment

GeorgeC W2DB

Id like a bit more info on the “asterisk -rvvv” you suggested.

I assume this is a command for a BASH prompt, correct ?

where did you get this command and the switches ? I see if I type asterisk help it states use asterisk -r to “connect” Need to understand how to fully get into and out of a entered command before I attempt this

When you say command list, you are referring to what is configured in the rpt.conf file for the remote node, correct ?

Hey George !

The “remote” node is a repeater and I am trying to control it via my SHARI node

so in the rpt.conf, is there a “REMOTE” section to also populate with the custom control commands in order to do this via my SHARI node ? Have I got that correct ?

Try asterisk -help
Yes, from bash
The vvv is verbosity level from one v to 5 changes the detail depth. 3 v’s is common for most debugging.

Yes, the command list is that which you assign in rpt.conf
Each node has it’s own and when you enter command mode for a node,
only it’s commands are valid.
Not the commands of the node you are sending them from.

If you connect node A to node B in command mode,
you can only issue node B’s commands that it has in it’s files.
You couldn’t create a command in node A and expect to run it on node B
Command mode may be thought of as a command ‘PIPELINE’.
A pound ‘#’ will exit command mode. Or it will timeout after some amount of inactivity.

1 Like

See what Mike said, that’s the ticket

GeorgeC W2DB