[arm-allstar] Schedule issue with Allstar Pi

[Doug Crompton]

Jeff,

  I will have to let someone else answer that. In all the years I have used
Allstar and all the nodes I have I have never used the internal scheduler
or for that matter macros other than to test. To me it is more logical to
have those things outside of Allstar. Obviously others would have different
opinions. To me scripting is fun and it allows you to build up a library of
functions independent of editing an rpt.conf file.

The scheduler is nothing more than a built-in cron with a few less
features. You have the option of how to do it. I would be curious if what
you are trying to do works when using a script. All you have to do is write
one as I described and run it manually to see if it works. If it runs
manually it will work with a cron.

Also you might send your exact scheduler syntax with the node connection
that is not working so we can see anything that might be wrong. Remember
you have to pad the echolink node connection and precede with a *33



*73 Doug*

*WA3DSP*

*http://www.crompton.com/hamradio <http://www.crompton.com/hamradio>*

On Tue, Nov 8, 2016 at 3:05 PM, Jeff Savasta <jeff.savasta at gmail.com> wrote:

> Doug,
> Thanks so much for the quick response.
>
> I guess what I am trying to understand is why the scheduler would not work
> with this and if it does not work is it because its a rasp pi thing?
>
> With that being said, does the scheduler work on its own for anything else
> or do I need to write crons for everything? Perhaps its just a Echolink
> issue?
>
> My buddy Bob, W2YMM is helping me along with this and has really held my
> hand. I am lucky to have him.
>
> Thanks Doug for the great work you have done. I love the rasp pi version!
> Jeff :)
>
> On Tue, Nov 8, 2016 at 2:34 PM, Doug Crompton via arm-allstar <
> arm-allstar at hamvoip.org> wrote:
>
>> Jeff,
>>
>>  I put out programming info yesterday on this forum about using a cron job
>> to perform commands at specific times. See the prior message. Here is is a
>> brief refresher...
>>
>> Create a script file. Call it whatever you want. Put it in
>> /etc/asterisk/local. Make it executable
>> 'chmod 750 filename'
>>
>> The script would look like this. Go to the directory and use 'nano
>> filename' to create -
>>
>> #!/bin/bash
>> # connect to some echolink node
>> /usr/sbin/asterisk -rx "rpt fun <your_node> *33<echo_link_node>"
>> # end script
>>
>> Do not enter the < or >, replace with node number, Leave quotes
>> ex: /usr/sbin/asterisk -rx "rpt fun 40000 *33147090"
>>
>> See rules for echolink node numbers -
>>
>> http://ohnosec.org/drupal/node/56
>>
>> type the script name at the Linux prompt to execute manually and test. Use
>> the full pathname -  /etc/asterisk/local/given_filename
>>
>> Typical cron entry - enter with 'crontab -e'  to edit,  'crontab -l' to
>> list
>>
>> 50 13 * * 3 /etc/asterisk/local/some_echolink_connect
>>
>> Assuming the above script is called some_echolink_connect (you would name
>> it your choice) this would run the script on Wednesday (third day of week)
>> at 13:50 hours - 1:50 PM.
>>
>> Goggle cron for more info.
>>
>> Likewise another script to disconnect and appropriate cron entry.
>>
>>
>>
>>
>> *73 Doug*
>>
>> *WA3DSP*
>>
>> *http://www.crompton.com/hamradio <http://www.crompton.com/hamradio>*
>>
>> On Tue, Nov 8, 2016 at 10:58 AM, Jeff Savasta via arm-allstar <
>> arm-allstar at hamvoip.org> wrote:
>>
>> > Hello All,
>> >
>> > I have a slight schedule issue using the schedule scripting in the Pi.
>> >
>> > I made a macro to connect to a certain Echolink conference. For
>> arguments
>> > sake its *522. It works fine when I bring it up with the DTMF pad on the
>> > HT.
>> >
>> > I then scheduled the macro via the scheduler in rpt.conf  to connect to
>> a
>> > specific Echolink node on a certain date and time every week. The entry
>> is
>> >
>> > 22=57 19 * * 1
>> >
>> > This in fact tells the Pi to connect every Monday night at 1957 hrs via
>> > that macro.
>> >
>> > The problem is that I hear the Pi attempt the connect as Allison
>> announces
>> > it but instead of saying connected, it says connection failed. If I
>> connect
>> > via Allmon or DTMF, it works fine???
>> >
>> > My buddy advised that he had a similar problem and had to schedule a
>> cron
>> > job to successfully execute the command? Anybody know why that would be
>> the
>> > case and if it is, what is the scheduler good for?
>> >
>> > Also, if I need to use a cron job to do this, where can i find
>> programming
>> > information to do this? I am unfamiliar with it?
>> >
>> > Thanks all,
>> >
>> > Jeff
>> > _______________________________________________
>> >
>> > arm-allstar mailing list
>> > arm-allstar at hamvoip.org
>> > http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar
>> >
>> > Visit the BBB and RPi2/3 web page - http://hamvoip.org
>> >
>> >
>> _______________________________________________
>>
>> arm-allstar mailing list
>> arm-allstar at hamvoip.org
>> http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar
>>
>> Visit the BBB and RPi2/3 web page - http://hamvoip.org
>>
>
>