Neal, I think you have a typo below.. Should it not be *4XXXXXX? That is what I have to do to get the remote command back.. Once I have control, I tried *3xxxxx to connect a node , or even *81 to force time announce, but neither work. So I presume there is a permissions issue or something else I am doing wrong? From: Neal Garbenis [mailto:njgarbenis@gmail.com] Sent: Wednesday, July 27, 2011 9:08 PM To: Lu Vencl Cc: <app_rpt-users@ohnosec.org> Subject: Re: [App_rpt-users] Remote commands Lu I am no expert but I do use the remote command often. First you need to be connected to the node that you want to control. Then dial *xxxxxx (the node you want to control). You will then hear a very overdriven audio file that says remote command. From that point on you are controlling that node you can (connect,disconnect, etc). To exit remote comand mode hit the # sign. Hope this helps Neal NG8Y Sent from my iPhone On Jul 27, 2011, at 8:52 PM, "Lu Vencl" <vencl@att.net> wrote: Ok, I know this is a newbie question, but I searched everywhere I know and I can’t find an example nor figure this out.. I need to understand the proper command structure or procedure of *4 remote command. Example, I want to issue a command to one of my nodes from another node. How do I do this? I tried the following example from my node 27870 KA4EPS-R-Margate*CLI> rpt fun 27870 *427869*81# I thought that this command would allow me to announce the time on node 27869 while entering this on the 27870 node.. Is this not possible? Another example, let’s say I want 27869 to connect to 27875 would I want to dial over the air on (node 27870) *427869*327875# ? Thanks again for your help.. I am just not getting anywhere with it. Lu, KA4EPS _______________________________________________ App_rpt-users mailing list App_rpt-users@ohnosec.org http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users

Yes – once you hear the announcement, it should work. If it is working, the machine you are talking to will stay continuously keyed up. If the machine you are trying to command is not in the right command state (user functions disabled, for example) that would likely block you from executing anything. Ken PS: I replaced the recording with a much nicer sounding one J From: app_rpt-users-bounces@ohnosec.org [mailto:app_rpt-users-bounces@ohnosec.org] On Behalf Of Neal Garbenis Sent: Wednesday, July 27, 2011 9:24 PM To: Lu Vencl Cc: <app_rpt-users@ohnosec.org> Subject: Re: [App_rpt-users] Remote commands Lu Yes I did have a typo sorry. Once you have control everything should work. Neal Sent from my iPhone On Jul 27, 2011, at 9:15 PM, "Lu Vencl" <vencl@att.net> wrote: Neal, I think you have a typo below.. Should it not be *4XXXXXX? That is what I have to do to get the remote command back.. Once I have control, I tried *3xxxxx to connect a node , or even *81 to force time announce, but neither work. So I presume there is a permissions issue or something else I am doing wrong? From: Neal Garbenis [mailto:njgarbenis@gmail.com] Sent: Wednesday, July 27, 2011 9:08 PM To: Lu Vencl Cc: <app_rpt-users@ohnosec.org> Subject: Re: [App_rpt-users] Remote commands Lu I am no expert but I do use the remote command often. First you need to be connected to the node that you want to control. Then dial *xxxxxx (the node you want to control). You will then hear a very overdriven audio file that says remote command. From that point on you are controlling that node you can (connect,disconnect, etc). To exit remote comand mode hit the # sign. Hope this helps Neal NG8Y Sent from my iPhone On Jul 27, 2011, at 8:52 PM, "Lu Vencl" <vencl@att.net> wrote: Ok, I know this is a newbie question, but I searched everywhere I know and I can’t find an example nor figure this out.. I need to understand the proper command structure or procedure of *4 remote command. Example, I want to issue a command to one of my nodes from another node. How do I do this? I tried the following example from my node 27870 KA4EPS-R-Margate*CLI> rpt fun 27870 *427869*81# I thought that this command would allow me to announce the time on node 27869 while entering this on the 27870 node.. Is this not possible? Another example, let’s say I want 27869 to connect to 27875 would I want to dial over the air on (node 27870) *427869*327875# ? Thanks again for your help.. I am just not getting anywhere with it. Lu, KA4EPS _______________________________________________ App_rpt-users mailing list App_rpt-users@ohnosec.org http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users

Lu, Not sure if you actually got everything answered but from the command line this is how you would do it... Lets say I am node 2337 and I want to control 2340. First I would connect to the node rpt fun 2337 *32340

From 2337 I would issue rpt fun 2337 *42340 (THis forces all the command sent on 2337 to forward over to 2340)

I would then get the audio file telling me it was working. Then I would just issues commands as normal in the same fashion. Say I wanted to connect 2340 to the Wan repeater system. I would issue rpt fun 2337 *32135. This would be controlling node 2340. It will continue to do so until I issue the #. (rpt fun 2337 #) Corey N3FE ________________________________ From: app_rpt-users-bounces@ohnosec.org [app_rpt-users-bounces@ohnosec.org] On Behalf Of Lu Vencl [vencl@att.net] Sent: Wednesday, July 27, 2011 11:09 PM To: Ken Cc: <app_rpt-users@ohnosec.org> Subject: Re: [App_rpt-users] Remote commands It was my bad. I did not realize that I had to be actually connected to the node first. I thought you could control without being connected. Sent from my iPhone, Lu Vencl On Jul 27, 2011, at 9:29 PM, "Ken" <ke2n@cs.com<mailto:ke2n@cs.com>> wrote: Yes – once you hear the announcement, it should work. If it is working, the machine you are talking to will stay continuously keyed up. If the machine you are trying to command is not in the right command state (user functions disabled, for example) that would likely block you from executing anything. Ken PS: I replaced the recording with a much nicer sounding one :) From: app_rpt-users-bounces@ohnosec.org<mailto:app_rpt-users-bounces@ohnosec.org> [mailto:app_rpt-users-bounces@ohnosec.org] On Behalf Of Neal Garbenis Sent: Wednesday, July 27, 2011 9:24 PM To: Lu Vencl Cc: <app_rpt-users@ohnosec.org<mailto:app_rpt-users@ohnosec.org>> Subject: Re: [App_rpt-users] Remote commands Lu Yes I did have a typo sorry. Once you have control everything should work. Neal Sent from my iPhone On Jul 27, 2011, at 9:15 PM, "Lu Vencl" <<mailto:vencl@att.net>vencl@att.net<mailto:vencl@att.net>> wrote: Neal, I think you have a typo below.. Should it not be *4XXXXXX? That is what I have to do to get the remote command back.. Once I have control, I tried *3xxxxx to connect a node , or even *81 to force time announce, but neither work. So I presume there is a permissions issue or something else I am doing wrong? From: Neal Garbenis [mailto:njgarbenis@gmail.com] Sent: Wednesday, July 27, 2011 9:08 PM To: Lu Vencl Cc: <<mailto:app_rpt-users@ohnosec.org>app_rpt-users@ohnosec.org<mailto:app_rpt-users@ohnosec.org>> Subject: Re: [App_rpt-users] Remote commands Lu I am no expert but I do use the remote command often. First you need to be connected to the node that you want to control. Then dial *xxxxxx (the node you want to control). You will then hear a very overdriven audio file that says remote command. From that point on you are controlling that node you can (connect,disconnect, etc). To exit remote comand mode hit the # sign. Hope this helps Neal NG8Y Sent from my iPhone On Jul 27, 2011, at 8:52 PM, "Lu Vencl" <<mailto:vencl@att.net>vencl@att.net<mailto:vencl@att.net>> wrote: Ok, I know this is a newbie question, but I searched everywhere I know and I can’t find an example nor figure this out.. I need to understand the proper command structure or procedure of *4 remote command. Example, I want to issue a command to one of my nodes from another node. How do I do this? I tried the following example from my node 27870 KA4EPS-R-Margate*CLI> rpt fun 27870 *427869*81# I thought that this command would allow me to announce the time on node 27869 while entering this on the 27870 node.. Is this not possible? Another example, let’s say I want 27869 to connect to 27875 would I want to dial over the air on (node 27870) *427869*327875# ? Thanks again for your help.. I am just not getting anywhere with it. Lu, KA4EPS _______________________________________________ App_rpt-users mailing list <mailto:App_rpt-users@ohnosec.org>App_rpt-users@ohnosec.org<mailto:App_rpt-users@ohnosec.org> <http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users>http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users -- This message was scanned and is believed to be clean. Click here to report this message as spam.<http://simba.repeater.net:8080/cgi-bin/learn-msg.cgi?id=C8C872221.A7176>

On 7/28/11 10:04 AM, Lu Vencl wrote:

Hi Corey,

Yea, I just thought that I could issue commands to another node without actually connecting to it.. I would have thought there would be a way to do this in the background (short from SSHing into the box) so you would not have to go through the actual connect process, but the current method is just fine.. I just did not understand it for some reason at first that you had to connect.

I suppose I could create some sort of macro to login to the boxes and perform the intended commands, just got to learn how to do all of that when I get some time..

Thanks and 73

Lu, KA4EPS

That's what the XXX=cmd,/some/were/in/your/filesystem comes in handy, where XXX=some DTMF command, and /.... is a script you run. You can have asterisk execute shell commands as the target of a DTMF sequence. For instance: in rpt.conf in the functions stanza, I have lines thus: (note, 123/124 is a placeholder for the purposes of this discussion) [functions] ... 123=cmd,/etc/asterisk/scripts/nodexup.sh 124=cmd,/etc/asterisk/scripts/nodexdown.sh ... and in a scripts directory I've created under /etc/asterisk there's a shell script called nodexup.sh: #!/bin/bash /usr/sbin/asterisk -rx "rpt cmd myhubnode ilink 3 nodex" with a chmod of 755, owned by whomever owns the asterisk daemon. To write the node down script, cp nodexup.sh nodexdown.sh, change the 3 to a 1, save, check the permissions, and restart asterisk. Now, if you have multiple nodes running on the same instantiation of asterisk (as I do), I have them all pointing to a common function stanza (I know, I should separate them out...), so, from any of my nodes I can DTMF 123 (not really this sequence), and it will link myhubnode to some nodex and take it down if I send the complimentary sequence. I can still do the *4myhubnode*3nodex# if I want, but, having *123# to press correctly is a lot less liable to fat-fingering or going into brain fade on the DTMF pad on the HT or mobile than the extended sequence. Yeah, it means you have to figure out just what you want to do, but, the ability to execute not only macros, but shell scripts from the daemon is a powerful (and dangerous) thing. You can still do the long sequence if you need something for ad-hoc, but for normal ops, making up a script to do it for you is a time/stress/fatfinger prevention/ease of ops technique. By the by, you can also execute the shell script from the command line, too...;) Just my opinion, maybe this answers your question. However, if you're looking for automatic connect on reboot/restart...look at the startup_marcro line in the rpt.conf for the node.... -- Bryan In this world, you must be oh so smart or oh so pleasant. Well, for years I was smart. I recommend pleasant. You may quote me.