I am looking for a way that a user on a repeater, say Node “A”, can issue a command that will connect/disconnect a link on Node B. I’ve seen the propagatedtmf command, not sure if that’s taking me in the right direction. Is this possible?
Thx. Adrian.
VE7NZ
Adrian,
The way this is done is by connecting to the node in ‘command mode’
The way to do that is similar to connecting to it in any other mode…
*4xxxxx
This will give you a number of minutes to issue commands on the command connected node and timeout on inactivity
or by manually issuing a # will drop command mode control.
Mike, is there a way of sending DTMF via iaxRPT so it goes to a connected node?
Thanks,
Bob
K6ECM
Bob,
The short answer is…
Outside of the method listed above (*4xxxx), there is no other method provided. With exception to command line options.
And not sure, but I don’t think you can *4 a private node if that was in your thinking.
But I have never tried this with an unregistered NNX node (would be private) as I don’t have one. But perhaps a option to try if that was your route.
For all/others to understand,
Technically, you are not passing DTMF AUDIO between the nodes, but numbers/commands on IAX.
IAXrpt only sends commands/numbers in the iax, not audio. Even nodes that would send the iax info downstream, without that downstream node in command mode, it would be ignored as it should.
Command mode says accept commands from this node as local.
You should visualize this by example in a command line instruction to a node. Because that is so similar to what it actually is. And perhaps that can be your solution. Command line actions directly to the node or scripted from the node you control.
Asterisk has a set of rules of it’s own and our app_rpt is basically a hack into asterisk, you can’t always get what you want and keep system integrity/stability over a wide network.
Years ago, I had built a ‘dtmf regenerator dialplan’ to control a hardwired controller listening on the output of a node, but I have not located that old script/dialplan. Perhaps next winter I will re-write and post it, but little need for anyone anymore.
This winter is dedicated to new stuff from old wishlists. LOL But be my guest to make one.
But I did had to change the command structure of the hard wired system so commands could not be accepted and confused by any connected node. And that is the thing that made it a hazardous utility.
At the time I did this, there were not even 1000 nodes and only 60% of them were registered in use and active and most of them were repeaters or hubs. Very few personal simplex nodes.
Imagine now just some of the 10K+ personal Pi users executing things like this without thinking about downstream implications while connected to large hubs. Food for thought anyway.
A check today showed 6500+ reg’d/active nodes.