Hello all. Been trying to remotely commands one of my nodes using *4 but the remote node does not seem to acknowledge the DTMF at all. I have both CLIs pulled up and see the local node decoding DTMF but the remote node shows nothing.
Searched around for a newer parameter I might be missing etc but no luck. Anyone using *4 these days for remote commands that has a tip?
Thanks. 73
Kyle
K0KN
Kyle, I have been using remote *4 commands. I can only send one command at a time, not a cascaded *4nnnnnn xxxyyy .
Tom / K5TRA
From: K0KN [email protected]
Sent: Friday, September 25, 2026 10:00 PM
To: [email protected]
Subject: AllStarLink Community Forum: *4 remote commands
Someone replied to a topic you are Watching.
|
K0KN
September 26
|
- | - |
Hello all. Been trying to remotely commands one of my nodes using *4 but the remote node does not seem to acknowledge the DTMF at all. I have both CLIs pulled up and see the local node decoding DTMF but the remote node shows nothing.
Searched around for a newer parameter I might be missing etc but no luck. Anyone using *4 these days for remote commands that has a tip?
Thanks. 73
Kyle
K0KN
Visit Topic or reply to this email to respond.
You are receiving this because you enabled mailing list mode.
To unsubscribe from these emails, click here.
By defualt that service is disabled on Nodes, you need to add this line to on the remote nodes you want to control. Be advised why this was disabled was, someone could control your node.
This needs to be added to the rpt.conf
remote_dtmf_allowed = 1
so first on the node that your node is connected to (or chain of one)you want to control you enter *4xxxxx X's is the remote node number, then any DTMF you do will be sent to the Node, but actually does not send DTMF tones, it uses the serial data connection you have between the 2 nodes via connection.
Correct me if I'm wrong, but isn't that a HamVoIP specific rpt.conf directive?
On Sep 26, 2026, at 17:44, Dale [email protected] wrote:
Someone replied to a topic you are Watching.
| N6ZCM
September 26 |
- | - |
By defualt that service is disabled on Nodes, you need to add this line to on the remote nodes you want to control. Be advised why this was disabled was, someone could control your node.
This needs to be added to the rpt.conf
remote_dtmf_allowed = 1
so first on the node that your node is connected to (or chain of one)you want to control you enter *4xxxxx X's is the remote node number, then any DTMF you do will be sent to the Node, but actually does not send DTMF tones, it uses the serial data connection you have between the 2 nodes via connection.
Visit Topic or reply to this email to respond.
You are receiving this because you enabled mailing list mode.
To unsubscribe from these emails, click here.
I dont know is it?
I have done this in ASL Version 2 Beta. Hamvoip is the first ones to implement default Off for Security reasons. ASL followed after that since it made sense IMHO.
Try it!
I did just the other day with one of our local repeaters. Default configuration. Was still able to send it remote commands from my node.
On Sep 26, 2026, at 20:11, Dale [email protected] wrote:
Someone replied to a topic you are Watching.
September 26 |
- | - |
I dont know is it?
I have done this in ASL Version 2 Beta. Hamvoip is the first ones to implement default Off for Security reasons. ASL followed after that since it made sense IMHO.
Try it!
Visit Topic or reply to this email to respond.
You are receiving this because you enabled mailing list mode.
To unsubscribe from these emails, click here.
