[arm-allstar] Update V1.5.3-38 is out

Thu Aug 9 07:12:57 EDT 2018

Doug,

How does this impact those of us who are using a remote RF link to 
access our repeaters?

Mike
WM4B

On Thu, Aug 9, 2018 at 4:16 AM, "Doug Crompton via arm-allstar" wrote:

> There is a hamvoip update now available which adds the following 
> features.
> Use the ADMIN menu item 1 to update,
>
> An option has been added to the rxondelay command in 
> simpleusb-tune-menu.
> If the delay number is negative the delay time is only applied if the 
> node
> has transmitted
> (PTT asserted)
> prior to cos. This avoids the issue of the delayed cos causing a cut- 
> off
> of the beginning of a transmission when the node receives cos but that 
> cos
> is not immediately after a transmission from that node.  rxondelay 
> values
> are 20ms increments. Example:  rxondelay=10  is a 200ms delay with the
> delay added regardless of transmit state. rxondelay=-10 is a 200ms 
> delay
> but only after a prior transmission.
> rxondelay is the 'm' option in simpleusb-tune-menu. Unless you have a 
> need
> for this feature leave it at the '0' setting. Values can range from 
> -100 to
> +100. It now uses the hi-res timing so delay timing is accurate. 
> rxondelay
> is often used to eliminate keying loops when used with a repeater and 
> for
> "kerchunk" (very short keyup) elimination.
>
> It was determined that the one-way audio detection code that was 
> introduced
> in V1.5.3-29  was causing a disconnect when a user had remote base 
> enable
> d. A check is now made to not validate one way audio for remote base 
> nodes
> thus allowing them to operate normally.
>
> Awhile back we expressed our intent to remove the remote base code 
> from the
> image. Roughly 5% of the Allstar active users have remote base 
> activated.
> This is activated with a check-box at allstarlink,org in the node
> configuration area. Many or even most who have checked the remote base 
> box
> have done it by mistake and
> are not using what is defined as a remote base. If you have this 
> checked
> only one node can connect to you at a time. The theory being that this 
> node
> was controlling a remote radio and there could be only one controller 
> at a
> time. If you are not actually using the code to control a remote base 
> radio
> you do NOT need to have this turned on. Further the remote base code 
> in
> Allstar is somewhat flaky. Today the external hamlib programs are a 
> much
> better choice for remote radio control. hamlib is part of the hamvoip 
> code.
> Users should be aware that the remote base code will be removed from
> hamvoip in the near future and if you are currently using it to 
> control a
> remote radio you should investigate other means. This howto from the
> hamvoip.org web page explains a method to pass DTMF to any external 
> script
> or program and would be useful for this application -
>
> https://www.hamvoip.org/Allstar_extended_functions_using_autopatch.pdf
>
> We will have a more detailed howto on this soon. You can check if you 
> have
> you node set to remote base by doing a dns-query. If it has a 'y' at 
> the
> end it is set to remote base.
>
> dns-query 48598
> +OK|radio at 35.137.74.22:4569/48598,35.137.74.22,y
>
> Two new scripts -
>
> say-hamvoip-sys-update.sh
> <node>
>
>      This script allows a voice prompted system update. This is
> particularly useful for portable headless operation and also for our 
> many
> sight-impaired users.
> This script can be run manually but typically would be added as a DTMF
> command. The added node number is optional. If left off it uses the 
> first
> defined node - $NODE1
>
>  Example:  C2=cmd,/usr/local/sbin/say-hamvoip-sys-update.sh ; Update
> hamvoip with voice feedback, Play to first node
>
> truncate_log
> s.sh
>
>      This is a configurable script that truncates logs to avoid 
> conditions
> of full ramdisks on systems that have heavy use and rarely get 
> rebooted.
> The scripts default configuration limits the size (truncates) the 
> Asterisk
> message file and the httpd access and error logs. These are the files 
> that
> fill the most in normal use. You can optionally configure other files, 
> file
> maximum size, and comments written to the journal. This script is 
> typically
> run
> daily
> from a cron.
>
> 0
> 4
> 04 * * * /
> usr/local/sbin
> /truncate_logs
> .sh     ; execute log check at 4:04 AM
>
>
> Behind the scenes code is also part of this update to prepare for the 
> DNS
> and registration server update coming soon.
>
>
> *73 Doug*
>
> *WA3DSP*
>
> *http://www.crompton.com/hamradio <http://www.crompton.com/hamradio>*
> _______________________________________________
>
> 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