- App_rpt-users - lists.keekles.org

Config Allmon
by Brian Schmidt 27 Jan '17

27 Jan '17

New to Allstar and still working out the bug. End users a seeing a random TX from my node. I don't see the TX LED light up on my ARS USB FOB so I was trying to config Allmon but can't find and current docs on the net for the most current Allstar version I am using. Got this version from Steve Zingman a couplke weeks ago. Any help would be greatly appreciated. Thanks Brian KE0HZX

2 1

Probably an old tired discussion about voiceover repeater ID
by John Griffith 26 Jan '17

26 Jan '17

About two years ago I enquired if anyone knew of a fix to make the repeater ID with only CW if there was a transmission in progress, and answer was it was a bug they haven’t fixed yet. Currently on my repeater, if my wife’s melodial voice starts the repeater ID and someone keys up during it, the morse ID’er comes on as it should. But if there’s a long transmission in progress, and it comes time to ID, it doesn’t use the CW, rather my wife rudely talks over the speaker. Is there a fix for that yet? Thank you. John Griffith N7OKN Mesa, AZ

1 0

ARIB (Analog Radio Interface Board)
by Monty 26 Jan '17

26 Jan '17

Hello Everyone, Does anyone still have a ARIB they would care to part with? I'm experimenting with some T1 circuits with a FXS Channel Bank and would like to try it with App_rpt. Thanks, Monty

1 0

AllStarLink status
by Steve Zingman 25 Jan '17

25 Jan '17

It's been about 1 month since Jim's passing. I want to update everyone as to the status of AllStarLink now and going forward. Let me say first, AllStarLink will continue to thrive and move into the future. The steps we have taken, and will take, guarantee that. Never again will any one person have to scramble to pay a server bill, add to the DNS or renew the domain name. Our first step was to identify the hosts and domains involved in the infrastructure of ASL. We have done that. I have implemented a monitoring system to notify us when we have a problem with a host. The monitoring as of today is a basic available / not available system. I am adding the monitoring of services specific to the host. That can be HTTP, IAX, SIP, CPU load, Disk in use etc. At a later date, I will make a page available to all that can be checked for overall health of the entire ASL infrastructure. The servers need rebuilding. The services need redistribution. Standards need to be set. This will take time. Mission critical servers will have a hot backup. In case of failure a standby server will take over until repairs can be made. All servers will have a offsite cold backup. Data will be daily coped to a remote storage array. We are moving all services off of ohnosec.org. Thanks to Steve R for keeping it going through the transition. The first step is move the maillist app_rpt-users. It has been migrated to lists.allstarlink.org. The archives are intact and old archives from lists.illiana.net from Dec 2005 to Oct 2008 were added. For the time being, mail sent to app_rpt-users(a)ohnosec.org will go to the new list. An existing user on on the ohnosec list is valid with his existing password and subscription on app_rpt-users(a)allstarlink.org. A message posted to app_rpt-users(a)allstarlink.org will appear on the archive <http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users> A message posted to app_rpt-users(a)ohnosec.org will also appear on the archive <http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users> The archive on <http://ohnosec.org/pipermail/app_rpt-users/> will not be updated by any posts. The main website allstarlink.org is being rewritten. It is a slow tedious project. Great attention is being paid to the look, feel and consistency. As with all thing ASL, the source will be archived and available. The next thing to move will be the Drupal (Knowledge Base) We may move this to a wiki or some other form that lends itself better to being updated by the community. I have copied the source code repository from SVN to github. This is the complete source code repository with history. Any changes to the official source code will happen on github. Moving from SVN to git will allow more people to contribute ideas and fixes in the future. The github repository is at <https://github.com/AllStarLink> There are of course off site backups done daily. A small group of professionals are starting to review the code. The first step will be to add comments and documentation. We need a better base of information to carry this forward. LOTS more on this to come. A not for profit organization has been created. For the first year, we are keeping the directors to a minimum. I do not want a large unwieldy group trying to manage things. I do not want to have to try to "turn a battle ship" just to get something done. AllStarLink Inc. will hold the domain name, pay for server space and handle any other administrative tasks that are needed. More to follow... 73, Steve N4IRS -- "Real programmers use vi, that's why I use nano"

6 7

Announcements
by Brian Burton 25 Jan '17

25 Jan '17

Your crontab thinks your script is located in /root. Your script is located in /etc/asterisk/scripts/####. you need to add the complete directory for the crontab to locate the script. AB3AA Brian On Jan 24, 2017 9:50 PM, <app_rpt-users-request(a)lists.allstarlink.org> wrote: Send App_rpt-users mailing list submissions to app_rpt-users(a)lists.allstarlink.org To subscribe or unsubscribe via the World Wide Web, visit http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users or, via email, send a message with subject or body 'help' to app_rpt-users-request(a)lists.allstarlink.org You can reach the person managing the list at app_rpt-users-owner(a)lists.allstarlink.org When replying, please edit your Subject line so it is more specific than "Re: Contents of App_rpt-users digest..." Today's Topics: 1. testing (Bryan Fields) 2. testing ohnosec (Bryan Fields) 3. test (Steve Zingman) 4. Test (Steve Zingman) 5. crontab schedule repeater announcements (DuaneVT .) 6. Re: crontab schedule repeater announcements (Apu) ---------------------------------------------------------------------- Message: 1 Date: Tue, 24 Jan 2017 18:45:54 -0500 From: Bryan Fields <Bryan(a)bryanfields.net> To: app_rpt-users(a)lists.allstarlink.org Subject: [App_rpt-users] testing Message-ID: <17c773f2-cfea-506e-5a81-8e2bf9131fee(a)bryanfields.net> Content-Type: text/plain; charset=windows-1252 please ignore -- Bryan Fields 727-409-1194 - Voice http://bryanfields.net ------------------------------ Message: 2 Date: Tue, 24 Jan 2017 20:03:46 -0500 From: Bryan Fields <Bryan(a)bryanfields.net> To: APP RPT <app_rpt-users(a)ohnosec.org> Subject: [App_rpt-users] testing ohnosec Message-ID: <53004182-6858-0f7a-a123-721a86aebdae(a)bryanfields.net> Content-Type: text/plain; charset=utf-8 ignore please -- Bryan Fields 727-409-1194 - Voice http://bryanfields.net ------------------------------ Message: 3 Date: Tue, 24 Jan 2017 20:33:09 -0500 From: Steve Zingman <szingman(a)msgstor.com> To: "app_rpt-users(a)ohnosec.org" <app_rpt-users(a)ohnosec.org> Subject: [App_rpt-users] test Message-ID: <15c33849-4f11-a047-abfb-5bd144768140(a)msgstor.com> Content-Type: text/plain; charset=utf-8; format=flowed Please ignore -- "Real programmers us vi, that's why I use nano" ------------------------------ Message: 4 Date: Tue, 24 Jan 2017 20:35:15 -0500 From: Steve Zingman <szingman(a)msgstor.com> To: app_rpt-users(a)lists.allstarlink.org Subject: [App_rpt-users] Test Message-ID: <3ca0a459-09c2-1dfb-966c-fb8002aa78bc(a)msgstor.com> Content-Type: text/plain; charset=utf-8; format=flowed Please ignore -- "Real programmers us vi, that's why I use nano" ------------------------------ Message: 5 Date: Tue, 24 Jan 2017 21:41:24 -0500 From: "DuaneVT ." <selkie2(a)comcast.net> To: app_rpt-users(a)ohnosec.org Subject: [App_rpt-users] crontab schedule repeater announcements Message-ID: <CABhxdJn3xJpyqVrSYsuYYKi8mcrX+U=U+fz4M1ANmdwwKGdvRA(a)mail.gmail.com> Content-Type: text/plain; charset="utf-8" I am having trouble getting crontab to schedule playing repeater announcements. I have successfully recorded IAX speech to "prompt01.gsm". I created a script /etc/asterisk/scripts/announcements01.sh. #!/bin/bash # Script plays prompt01 audio files over local node (repeater) PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin /usr/sbin/asterisk -rx "rpt localplay 42996 /etc/asterisk/scripts/prompt01" Via terminal, I can enter "announcements01" and hear the node play the repeater announcements. My crontab -e is: SHELL=/bin/bash PATH=~/sbin:/bin:/usr/sbin:/usr/bin:/etc/asterisk/scripts MAILTO=root HOME=/ # I have tried all the following script treatments! # m h dom mon dow command * * * * * ./announcements01 * * * * * ./announcements01.sh * * * * * . /announcements01.sh # dot space announcements01.sh * * * * * announcements01.sh # chmod u-x announcements01.sh (to make executable) ------------------------------------------------------------ ------------------------------------------------------- I have used the crontab to pass text to a file every minute..no problems; so cron is running. I am logged into ROOT. Any suggestions as to HOW to get crontab to run my announcements01.sh script would be MUCH appreciated! 73, Duane KA1LM

1 0

test
by Steve Zingman 25 Jan '17

25 Jan '17

Please ignore -- "Just say no to world domination"

1 0

crontab schedule repeater announcements
by DuaneVT . 25 Jan '17

25 Jan '17

I am having trouble getting crontab to schedule playing repeater announcements. I have successfully recorded IAX speech to "prompt01.gsm". I created a script /etc/asterisk/scripts/announcements01.sh. #!/bin/bash # Script plays prompt01 audio files over local node (repeater) PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin /usr/sbin/asterisk -rx "rpt localplay 42996 /etc/asterisk/scripts/prompt01" Via terminal, I can enter "announcements01" and hear the node play the repeater announcements. My crontab -e is: SHELL=/bin/bash PATH=~/sbin:/bin:/usr/sbin:/usr/bin:/etc/asterisk/scripts MAILTO=root HOME=/ # I have tried all the following script treatments! # m h dom mon dow command * * * * * ./announcements01 * * * * * ./announcements01.sh * * * * * . /announcements01.sh # dot space announcements01.sh * * * * * announcements01.sh # chmod u-x announcements01.sh (to make executable) ------------------------------------------------------------------------------------------------------------------- I have used the crontab to pass text to a file every minute..no problems; so cron is running. I am logged into ROOT. Any suggestions as to HOW to get crontab to run my announcements01.sh script would be MUCH appreciated! 73, Duane KA1LM

2 1

Test
by Steve Zingman 25 Jan '17

25 Jan '17

Please ignore -- "Real programmers us vi, that's why I use nano"

1 0

test
by Steve Zingman 25 Jan '17

25 Jan '17

Please ignore -- "Real programmers us vi, that's why I use nano"

1 0

testing ohnosec
by Bryan Fields 25 Jan '17

25 Jan '17

ignore please -- Bryan Fields 727-409-1194 - Voice http://bryanfields.net

1 0