So, I travel. A lot. Im a hotshot driver, delivering coast to coast and border to border. The yl (of 7 years) works a weird mix of day and night shifts. The times when she and I are awake, I try to spend time with her and the family via radio. Me on echolink, her on a local rig on the side stand next to her recliner.
I have a back yard repeater up (Motorola R100) a URIx, and connect to a RPi3B. I have echolink pointing to the main node in rpt.conf.
What I would like to do is disconnect the repeater from asterisk/allstar but leave echolink up and use allstar to connect elsewhere, without the radio interrupting her sleep, due to unknown schedule changes.
So, recap…
I want to be able to
leave allstar running
turn the repeater on/off
connect on echolink and have the node connected to somewhere else.
I just want to be able to turn on/off information getting passed on the local repeater, connected to allstar.
I’m thinking I could add a couple of nodes, make 29655 the ‘main’ node, then a private node for the repeater and another for echolink. That way, 29655 will be connected elsewhere, I can connect to it via echolink, and the repeater wont be connected, until I send the command (via an ssh phone app).
Yep, that’s the way to do it. Add another node (public or private) and attach Echolink to it. Then you can turn Echolink on and off by connecting to the added node.
delivering coast to coast and border to border. The yl (of 7
years) works a weird mix of day and night shifts. The times
when she and I are awake, I try to spend time with her and the
family via radio. Me on echolink, her on a local rig on the side
stand next to her recliner.
I have a back yard repeater up (Motorola R100) a
URIx, and connect to a RPi3B. I have echolink pointing to the
main node in rpt.conf.
What I would like to do is disconnect the
repeater from asterisk/allstar but leave echolink up and use
allstar to connect elsewhere, without the radio interrupting
her sleep, due to unknown schedule changes.
So, recap…
I want to be able to
leave allstar running
turn the repeater on/off
3) connect on echolink and have the node
connected to somewhere else.
I just want to be able to turn on/off
information getting passed on the local repeater, connected to
allstar.
I'm *thinking* I could add a couple of nodes,
make 29655 the ‘main’ node, then a private node for the
repeater and another for echolink. That way, 29655 will be
connected elsewhere, I can connect to it via echolink, and the
repeater wont be connected, until I send the command (via an
ssh phone app).
_______________________________________________
App_rpt-users mailing list
To unsubscribe from this list please visit and scroll down to the bottom of the page. Enter your email address and press the "Unsubscribe or edit options button"
You do not need a password to unsubscribe, you can do it via email confirmation. If you have trouble unsubscribing, please send a message to the list detailing the problem.
So if I understand this correctly you want to keep a node running but disable
the transmitter, from a remote node. Lets say your node is 100, and the
remote is 105. You're local to 105.
Use cop,4 to proxy your commands, typical this is mapped to *4
1. connect node 100 to node 40821: *4-100-*3-40821
Means send *3-40821 to node 100
2. disable node 100 using cop, 3, say mapped to *876 DTMF
*4-100-*876
This will send *876 to the node 100 and disable it.
Once the node is disabled anyone connected through it will remain connected,
but no new connections will be permitted.
If you want to just disable the transmitter using a relay you can do the same
with GPIO as well.
The other option here is to setup a pseudo node as a hub and just connect
everything to that.
···
On 5/31/19 5:02 PM, ARS W5OMR wrote:
So, recap...
I want to be able to
1) leave allstar running
2) turn the repeater on/off
3) connect on echolink and have the node connected to somewhere else.
I just want to be able to turn on/off information getting passed on the
local repeater, connected to allstar.
