[arm-allstar] Autopatch CT & ARRL news

Sun May 22 18:07:59 EST 2016

Hi Doug, I would like to take your offer for some setup help with the
playnews script, thank you very much for the generous offer. Will put a
call out for you on 27225.

On the autopatch thing, agree it is a bit antiquated
   Our area, Northern Alabama, has great cell phone coverage. But it is
also prone to periodically getting torn up by tornadoes. The last major
weather event we experience was in April of 2011, urban Huntsville was
without power or internet for two weeks and without cell phone service for
a full week.
The repeater I am building with Allstar/Autopatch is destined for
installation at a DoD facility on Redstone Arsenal (in Huntsville). This
facility enjoys a hardened/armored T3 line and superb backup power
infrastructure. During the April 2011 event the power and internet at this
facility was uninterrupted.
Would like to have the autopatch available for the local ARES/RACES amateur
radio community for the inevitability of another April 2011 event.
I agree that the CT over the autopatch is not that important, am not going
to worry about it anymore.

--
Robert Conklin
*N4WGY <http://qrz.com/db/N4WGY>*

On Sun, May 22, 2016 at 4:02 PM, Doug Crompton via arm-allstar <
arm-allstar at hamvoip.org> wrote:

> Robert,
>
>  On the playnews script. It is not hard to implement. I can help if you
> want. Let me know what you were having problems with.
>
> The problem with using a direct feed as you mentioned is that there is no
> timing included. The playnews script stops every 2.5 minutes for 20 seconds
> to allow system reset and so other nodes can send commands if necessary.
> You can customize the messages if desired.
>
> You would have to manually add your own timing and breaks for ID's. On a
> connected network assume timeouts are at about 3 minutes.
>
> For the autopatch, first of all that is something that is rarely used
> anymore except maybe in an emergency. Don't you have a cellphone and
> service where you live? Unless you live out in the sticks where cell
> coverage is sparse I would recommend not using it.
>
> If you must use it I would just explain as soon as the person answers that
> it is a one way conversation and to use over.
>
>
>
> *73 DougWA3DSPhttp://www.crompton.com/hamradio
> <http://www.crompton.com/hamradio>*
>
>
> ------------------------------
> Date: Sun, 22 May 2016 12:52:33 -0500
> To: arm-allstar at hamvoip.org
> Subject: Re: [arm-allstar] Autopatch CT & ARRL news
> From: arm-allstar at hamvoip.org
> CC: n4wgy.ham at gmail.com
>
> I am genuinely appreciative of everyone's time. Thank you!
>
> Explanation:
> Have observed that few people realize or remember that with most equipment
> an autopatch call is a half duplex conversation.
> Even if I state we are conversing at half duplex at the beginning of the
> autopatch conversation, doubles happen frequently.
> Am thinking that If I could tell folks I am calling via autopatch and that
> they should not to talk til after they hear the CT beep & say "over" after
> their piece is said, this would maybe reduce doubles.
>
> Changing the noct=1 to noct=0 enables CT to be heard on the RF side during
> an autopatch qso, but does not propagate the CT to the telephone. Don't
> know what to do next.
>
> In regards to the Scripts "how to" for setting up an automated ARL news
> feed on my node; I have been trying to implement with no success yet, but
> that's almost certainly my lack of experience. I am not proficient in
> implementing or manipulating code.
> Was wondering if there was a simpler way by possibly using the echolink
> news feeds from the ARRL.
> I will keep hammering at it, success is inevitable with persistance.
>
> Thank you all very much for your advise!
>
> --
> Robert Conklin
> *N4WGY <http://qrz.com/db/N4WGY>*
>
> On Sat, May 21, 2016 at 11:32 PM, Mark Johnston via arm-allstar <
> arm-allstar at hamvoip.org> wrote:
>
> I have not setup a ct for autopatch but I believe the line in rpt.conf
> similar to:
>
>
> 6=autopatchup,context=to-callcentric,noct=1,farenddisconnect=1,dialtime=20000
> change noct=1 to noct=0 or remove that portion, and reload config..
>
>
>
>
>
> "Got Root?"
>
> How many software engineers does it take to change a light bulb?
> *None. It's a hardware problem.*
>
>
> Unix is user friendly. It's just very particular about who it's friends
> are.
> WINDOWS: Will Install Needless Data On Whole System
> MICROSOFT: Most Intelligent Customers Realize Our Software Only Fools
> Teenagers.
>
>
> A ntennas
> P oorly
> P laced
> L acks
> E ngineering
>
> The best way to accelerate a computer running Windows is at 9.81 m/s².
>
> *"I get paid to support Windows, I use Linux to get work done."*
>
>
> On Sat, May 21, 2016 at 8:45 PM, Robert Conklin via arm-allstar <
> arm-allstar at hamvoip.org> wrote:
>
> Hello, hope everyone is well.
> I regards to autopatch, how would I propagate a courtesy tone from the
> radio user unkeying to the phone user?
> Also wondering if it would be possible to set up a cron job to play the
> ARRL news from the W1AWBDCT echolink node, or is there a better way to do
> this?
> Thank you for any advise!
> --
> Robert Conklin
> *N4WGY <http://qrz.com/db/N4WGY>*
>
> _______________________________________________
>
> arm-allstar mailing list
> arm-allstar at hamvoip.org
> http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar
>
> Visit the BBB and RPi2 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 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 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 web page - http://hamvoip.org
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.hamvoip.org/pipermail/arm-allstar/attachments/20160522/66a3375b/attachment-0001.html>