[arm-allstar] ARM-allstar Digest, Vol 71, Issue 24

Tue Apr 14 13:44:27 EDT 2020

Mike,

 No, not at all. It just calls a different context in extensions.conf
checks for ban entries and then calls the original radio-secure.

*73 Doug, WA3DSP*
*http://wa3dsp.org <http://wa3dsp.org>*

On Tue, Apr 14, 2020 at 1:36 PM "Mike Zolna - KD6RFJ via ARM-allstar" <
arm-allstar at hamvoip.org> wrote:

> Thanks Doug. Sure does. By changing the context from "radio-secure" to
> either blacklist or whitelist, am I giving up any functionality from the
> "radio-secure" context removal? I know you can only specify one of the
> three.
>
> Mike Zolna
> KD6RFJ
> 520.481.9991
> KD6RFJ at gmail.com
>
>
> On Tue, Apr 14, 2020 at 9:00 AM <arm-allstar-request at hamvoip.org> wrote:
>
> > Send ARM-allstar mailing list submissions to
> >         arm-allstar at hamvoip.org
> >
> > To subscribe or unsubscribe via the World Wide Web, visit
> >         http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar
> > or, via email, send a message with subject or body 'help' to
> >         arm-allstar-request at hamvoip.org
> >
> > You can reach the person managing the list at
> >         arm-allstar-owner at hamvoip.org
> >
> > When replying, please edit your Subject line so it is more specific
> > than "Re: Contents of ARM-allstar digest..."
> >
> >
> > Today's Topics:
> >
> >    1. Re: Restarting Asterisk Loop (Doug Crompton)
> >    2. Blacklist/Whitelist Question Perm vs. Temp? (Mike Zolna - KD6RFJ)
> >    3. Re: Blacklist/Whitelist Question Perm vs. Temp? (Doug Crompton)
> >    4. Controlling two nodes via Supermon (Mike Sullivan)
> >    5. Forecast.sh delay or pause if repeater is busy (David Panscik)
> >    6. Help with Script (Darrell Black)
> >
> >
> > ----------------------------------------------------------------------
> >
> > Message: 1
> > Date: Mon, 13 Apr 2020 18:31:31 -0400
> > From: Doug Crompton <wa3dsp at gmail.com>
> > To: ARM Allstar <arm-allstar at hamvoip.org>
> > Subject: Re: [arm-allstar] Restarting Asterisk Loop
> > Message-ID:
> >         <CAMp6vstbep7X1NZpQAnu=
> > PBu4wgtsdHKeOqti3A2Cfmc64Uz4Q at mail.gmail.com>
> > Content-Type: text/plain; charset="UTF-8"
> >
> > Kip,
> >
> >  You can now avoid that problem using the nptee script. This allows lame
> > and broadcastify to run independently from hamvoip so restarting manually
> > or via an update would not be effected. See the nptee howto at
> hamvoip.org
> > .
> >
> > *73 Doug, WA3DSP*
> > *http://wa3dsp.org <http://wa3dsp.org>*
> >
> > On Mon, Apr 13, 2020 at 5:33 PM "Kipton Moravec via ARM-allstar" <
> > arm-allstar at hamvoip.org> wrote:
> >
> > > Yes. I believe that was the problem.  I had not bothered to remember to
> > > change the menu to use the restart in the broadcastify.com
> > > documentation. And I am guessing the pointer to the update script uses
> > > the original restart also.
> > >
> > > Reboot fixed the problem, and using the other restart did not cause it
> > > to happen.
> > >
> > > I still have a lot to learn.
> > >
> > > Thanks,
> > >
> > > Kip
> > >
> > > On 4/13/20 2:28 PM, "Bryan St Clair via ARM-allstar" wrote:
> > > > Perform a system restart yet?
> > > >
> > > > Streaming audio?
> > > >
> > > > On Mon, Apr 13, 2020, 12:20 "Kipton Moravec via ARM-allstar" <
> > > > arm-allstar at hamvoip.org> wrote:
> > > >
> > > >> I decide to Perform a System Update. It appears there was an update.
> > > >>
> > > >> It looks like it got into a loop restarting Asterisk.
> > > >>
> > > >> I went to /var/log/asterisk/messages and copied the last few lines
> of
> > > >> the messages.log
> > > >>
> > > >>
> > > >> [Apr 13 13:34:57] NOTICE[333] dnsmgr.c: host '
> > register.allstarlink.org'
> > > >> changed from 178.32.160.85 to 192.83.199.4
> > > >> [Apr 13 13:35:35] WARNING[350] chan_iax2.c: REGISTER-LOG: Sending
> > > >> registration request for '501620'
> > > >> [Apr 13 13:35:35] WARNING[342] chan_iax2.c: REGISTER-LOG: registry
> > > >> rereqquest
> > > >> [Apr 13 13:36:25] WARNING[349] chan_iax2.c: REGISTER-LOG: Sending
> > > >> registration request for '501620'
> > > >> [Apr 13 13:36:25] WARNING[346] chan_iax2.c: REGISTER-LOG: registry
> > > >> rereqquest
> > > >> [Apr 13 13:37:16] WARNING[342] chan_iax2.c: REGISTER-LOG: Sending
> > > >> registration request for '501620'
> > > >> [Apr 13 13:37:16] WARNING[347] chan_iax2.c: REGISTER-LOG: registry
> > > >> rereqquest
> > > >> [Apr 13 13:38:06] WARNING[346] chan_iax2.c: REGISTER-LOG: Sending
> > > >> registration request for '501620'
> > > >> [Apr 13 13:38:06] WARNING[350] chan_iax2.c: REGISTER-LOG: registry
> > > >> rereqquest
> > > >> [Apr 13 13:38:56] WARNING[347] chan_iax2.c: REGISTER-LOG: Sending
> > > >> registration request for '501620'
> > > >> [Apr 13 13:38:56] WARNING[349] chan_iax2.c: REGISTER-LOG: registry
> > > >> rereqquest
> > > >> [Apr 13 13:39:47] WARNING[350] chan_iax2.c: REGISTER-LOG: Sending
> > > >> registration request for '501620'
> > > >> [Apr 13 13:39:47] WARNING[342] chan_iax2.c: REGISTER-LOG: registry
> > > >> rereqquest
> > > >> [Apr 13 13:40:37] WARNING[349] chan_iax2.c: REGISTER-LOG: Sending
> > > >> registration request for '501620'
> > > >> [Apr 13 13:40:37] WARNING[346] chan_iax2.c: REGISTER-LOG: registry
> > > >> rereqquest
> > > >> [Apr 13 13:41:27] WARNING[342] chan_iax2.c: REGISTER-LOG: Sending
> > > >> registration request for '501620'
> > > >> [Apr 13 13:41:27] WARNING[347] chan_iax2.c: REGISTER-LOG: registry
> > > >> rereqquest
> > > >> [Apr 13 13:42:18] WARNING[346] chan_iax2.c: REGISTER-LOG: Sending
> > > >> registration request for '501620'
> > > >> [Apr 13 13:42:18] WARNING[350] chan_iax2.c: REGISTER-LOG: registry
> > > >> rereqquest
> > > >> [Apr 13 13:43:16] WARNING[349] chan_iax2.c: REGISTER-LOG: Sending
> > > >> registration request for '501620'
> > > >> [Apr 13 13:43:16] WARNING[346] chan_iax2.c: REGISTER-LOG: registry
> > > >> rereqquest
> > > >> [Apr 13 13:44:06] WARNING[342] chan_iax2.c: REGISTER-LOG: Sending
> > > >> registration request for '501620'
> > > >> [Apr 13 13:44:07] WARNING[348] chan_iax2.c: REGISTER-LOG: registry
> > > >> rereqquest
> > > >> [Apr 13 13:44:57] WARNING[346] chan_iax2.c: REGISTER-LOG: Sending
> > > >> registration request for '501620'
> > > >> [Apr 13 13:44:57] WARNING[350] chan_iax2.c: REGISTER-LOG: registry
> > > >> rereqquest
> > > >> [Apr 13 13:45:47] WARNING[348] chan_iax2.c: REGISTER-LOG: Sending
> > > >> registration request for '501620'
> > > >> [Apr 13 13:45:47] WARNING[349] chan_iax2.c: REGISTER-LOG: registry
> > > >> rereqquest
> > > >> [Apr 13 13:46:37] WARNING[350] chan_iax2.c: REGISTER-LOG: Sending
> > > >> registration request for '501620'
> > > >> [Apr 13 13:46:38] WARNING[342] chan_iax2.c: REGISTER-LOG: registry
> > > >> rereqquest
> > > >> [Apr 13 13:47:28] WARNING[349] chan_iax2.c: REGISTER-LOG: Sending
> > > >> registration request for '501620'
> > > >> [Apr 13 13:47:28] WARNING[346] chan_iax2.c: REGISTER-LOG: registry
> > > >> rereqquest
> > > >> [Apr 13 13:48:18] WARNING[342] chan_iax2.c: REGISTER-LOG: Sending
> > > >> registration request for '501620'
> > > >> [Apr 13 13:48:18] WARNING[348] chan_iax2.c: REGISTER-LOG: registry
> > > >> rereqquest
> > > >> [Apr 13 13:49:08] WARNING[346] chan_iax2.c: REGISTER-LOG: Sending
> > > >> registration request for '501620'
> > > >> [Apr 13 13:49:08] WARNING[350] chan_iax2.c: REGISTER-LOG: registry
> > > >> rereqquest
> > > >> [Apr 13 13:49:57] NOTICE[333] dnsmgr.c: host '
> > register.allstarlink.org'
> > > >> changed from 192.83.199.4 to 178.32.160.82
> > > >> [Apr 13 13:49:59] WARNING[348] chan_iax2.c: REGISTER-LOG: Sending
> > > >> registration request for '501620'
> > > >> [Apr 13 13:49:59] WARNING[349] chan_iax2.c: REGISTER-LOG: registry
> > > >> rereqquest
> > > >> [Apr 13 13:50:49] WARNING[350] chan_iax2.c: REGISTER-LOG: Sending
> > > >> registration request for '501620'
> > > >> [Apr 13 13:50:50] WARNING[342] chan_iax2.c: REGISTER-LOG: registry
> > > >> rereqquest
> > > >> [Apr 13 13:51:14] NOTICE[2265] dnsmgr.c: Managed DNS entries will be
> > > >> refreshed every 300 seconds.
> > > >> [Apr 13 13:51:14] WARNING[2265] manager.c: Unable to bind socket:
> > > >> Address already in use
> > > >> [Apr 13 13:51:18] NOTICE[2347] dnsmgr.c: Managed DNS entries will be
> > > >> refreshed every 300 seconds.
> > > >> [Apr 13 13:51:18] WARNING[2347] manager.c: Unable to bind socket:
> > > >> Address already in use
> > > >> [Apr 13 13:51:22] NOTICE[2356] dnsmgr.c: Managed DNS entries will be
> > > >> refreshed every 300 seconds.
> > > >> [Apr 13 13:51:22] WARNING[2356] manager.c: Unable to bind socket:
> > > >> Address already in use
> > > >> [Apr 13 13:51:26] NOTICE[2365] dnsmgr.c: Managed DNS entries will be
> > > >> refreshed every 300 seconds.
> > > >> [Apr 13 13:51:26] WARNING[2365] manager.c: Unable to bind socket:
> > > >> Address already in use
> > > >> [Apr 13 13:51:30] NOTICE[2374] dnsmgr.c: Managed DNS entries will be
> > > >> refreshed every 300 seconds.
> > > >> [Apr 13 13:51:30] WARNING[2374] manager.c: Unable to bind socket:
> > > >> Address already in use
> > > >>
> > > >> So what do I do?
> > > >> Where do I look for what is wrong?
> > > >>
> > > >> Kip
> > > >>
> > > >> _______________________________________________
> > > >>
> > > >> 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/4 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/4 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/4 web page - http://hamvoip.org
> >
> >
> > ------------------------------
> >
> > Message: 2
> > Date: Mon, 13 Apr 2020 15:53:53 -0700
> > From: Mike Zolna - KD6RFJ <kd6rfj at gmail.com>
> > To: Mike Zolna - KD6RFJ via ARM-allstar <arm-allstar at hamvoip.org>
> > Subject: [arm-allstar] Blacklist/Whitelist Question Perm vs. Temp?
> > Message-ID:
> >         <
> > CAJ+F70A-3b+_FsMsJJX0Sf5hB4-bUGr+KK7W5gLukVJAxuyfzQ at mail.gmail.com>
> > Content-Type: text/plain; charset="UTF-8"
> >
> > I've read the how to and not getting temporary vs. permanent
> instantiation
> > of declaring a node ban or allow. Does the IAX modification piece make it
> > permanent along with the node-ban-allow.sh scrip? If one wants it to be
> > temporary, just run the script?
> >
> > Mike Zolna
> > KD6RFJ
> > 520.481.9991
> > KD6RFJ at gmail.com
> >
> >
> > ------------------------------
> >
> > Message: 3
> > Date: Mon, 13 Apr 2020 19:21:54 -0400
> > From: Doug Crompton <wa3dsp at gmail.com>
> > To: ARM Allstar <arm-allstar at hamvoip.org>
> > Subject: Re: [arm-allstar] Blacklist/Whitelist Question Perm vs. Temp?
> > Message-ID:
> >         <CAMp6vstFv1XdzHo5=
> > j5uSDznS4YqX-61vm_C_q1FaNhieyoqdA at mail.gmail.com>
> > Content-Type: text/plain; charset="UTF-8"
> >
> > Mike,
> >
> >  There is no permanent vs. temporary.  You need to setup the config files
> > as per the howto but you only have to add the contexts if they are not
> > already there. We added them to the download firmware at hamvoip.org
> last
> > year so anyone that started a node with that new download code would have
> > the scripts already installed in the config files. Older versions would
> > need to install them. So check and make sure you don't already have them.
> >
> > So once they are in place you have the choice of white or black listing a
> > node number. It has to be one or the other. This depends on which
> context=
> > you set in iax.conf. White listing means only the nodes specified can
> > connect. Black listing means the nodes listed cannot connect. Then you
> can
> > either use Supermon or the node-ban-allow.sh script to add or delete a
> node
> > number. Once you add it it is in a sense permanent until you delete it
> even
> > through a reboot. You can also add a short comment to the database as to
> > why you took that action.
> >
> > Does that answer your question?
> >
> > *73 Doug, WA3DSP*
> > *http://wa3dsp.org <http://wa3dsp.org>*
> >
> > On Mon, Apr 13, 2020 at 7:12 PM "Mike Zolna - KD6RFJ via ARM-allstar" <
> > arm-allstar at hamvoip.org> wrote:
> >
> > > I've read the how to and not getting temporary vs. permanent
> > instantiation
> > > of declaring a node ban or allow. Does the IAX modification piece make
> it
> > > permanent along with the node-ban-allow.sh scrip? If one wants it to be
> > > temporary, just run the script?
> > >
> > > Mike Zolna
> > > KD6RFJ
> > > 520.481.9991
> > > KD6RFJ at gmail.com
> > > _______________________________________________
> > >
> > > 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/4 web page - http://hamvoip.org
> > >
> >
> >
> > ------------------------------
> >
> > Message: 4
> > Date: Tue, 14 Apr 2020 02:57:02 -0400
> > From: Mike Sullivan <kn4imu at gmail.com>
> > To: ARM Allstar <arm-allstar at hamvoip.org>
> > Subject: [arm-allstar] Controlling two nodes via Supermon
> > Message-ID:
> >         <CAKoU=
> > 5ciRvS2vqneG4WCoig+1LKCCjFB4G5Z+eP9Y+-J6QadAA at mail.gmail.com>
> > Content-Type: text/plain; charset="UTF-8"
> >
> > I'm wanting to add the ability to control a neighboring club's repeater
> > from our node's Supermon panel (I manage both nodes). What's the easiest
> > way to add it into the Supermon panel? I know that there is a separate
> port
> > for web access. Just want to make sure I don't miss anything.
> >
> > Mike
> >
> >
> > ------------------------------
> >
> > Message: 5
> > Date: Tue, 14 Apr 2020 13:36:38 +0000 (UTC)
> > From: David Panscik <dpanscik at yahoo.com>
> > To: arm-allstar at hamvoip.org
> > Subject: [arm-allstar] Forecast.sh delay or pause if repeater is busy
> > Message-ID: <808668815.269919.1586871398979 at mail.yahoo.com>
> > Content-Type: text/plain; charset=UTF-8
> >
> > Howdy.
> > I have a crontab set to fire Forecast.sh a few times a day.
> > The script downloads the weather report from the National Weather Service
> > and puts the report on the air.? Its a fairly lengthy report taking
> > approximately two minutes to transmit.
> > Is there a way to make weather.sh to wait to broadcast if the repeater is
> > busy?
> > Ideally I would like the script to pause until the repeater has not been
> > used for at least 60 seconds.
> > Is there a way to do this?
> > Thanks!*73*
> > DavidKN6GUW
> >
> > ------------------------------
> >
> > Message: 6
> > Date: Tue, 14 Apr 2020 10:31:27 -0400
> > From: Darrell Black <gigahacker at gmail.com>
> > To: ARM Allstar <arm-allstar at hamvoip.org>
> > Subject: [arm-allstar] Help with Script
> > Message-ID:
> >         <CAC23xXA9upbF2MT2u=
> > pZxJHFj7tjotfFDEaUdmn8QzxSZ6YjTQ at mail.gmail.com>
> > Content-Type: text/plain; charset="UTF-8"
> >
> > I know this has been answered 1000's times but it just does not seem to
> > work for me. Below is my simple script.
> >
> > #!/bin/bash
> > crontab /etc/asterisk/local/cron_skywarn.txt
> > \cp -f /etc/asterisk/rpt_skywarn.conf /etc/asterisk/rpt.conf
> > sleep 1
> > sudo asterisk -rx "rpt reload"
> > sleep 5
> > sudo asterisk -rx "rpt localplay 50165 /etc/asterisk/sounds/wx"
> >
> >
> > I have verified  that the crontab is replaced and that works
> > I have verified that the rpt.conf is replaced with the new file
> >
> > What is not happening is I do not think the rpt.conf is being read in.
> >
> > The file is replaced however the CT does not change. I have the
> following:
> > NORMAL
> >
> > ; COURTESY TONE MAPPING
> > unlinkedct=ct1
> > remotect=ct3
> > linkunkeyct=ct8
> >
> > SKYWARN
> >
> > unlinkedct=ct5
> > remotect=ct5
> > linkunkeyct=ct5
> >
> > ct5 = iSW
> >
> > ct5 is never used.....Note the repeater is ALWAYs linked to a hub.
> >
> > Any help please
> > --
> >
> > Darrell Black
> >
> > (517) 917-2226
> > GigaHacker at gmail.com
> > http://www.linkedin.com/in/darrellblack
> >
> >
> > 73 de W8DSB
> > "In God we trust, all others we monitor"
> >
> > GMRS WRDE739
> >
> >
> > ------------------------------
> >
> > Subject: Digest Footer
> >
> > _______________________________________________
> > ARM-allstar mailing list
> > ARM-allstar at hamvoip.org
> > http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar
> >
> >
> > ------------------------------
> >
> > End of ARM-allstar Digest, Vol 71, Issue 24
> > *******************************************
> >
> _______________________________________________
>
> 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/4 web page - http://hamvoip.org
>