[arm-allstar] New RPI2 version release

[Doug Crompton]

Another thing I thought of the stock image also has  holdofftelem=1  which means it will not send telemetry when a signal is present. If your COS line was somehow indicating a constant signal it would never send any telemetry. It would be queued up and sent as a batch when the COS line returned to the no signal state. I have seen this happen when the COS phase was reversed or a radio was turned off and still connected. You should have a radio connected and on at all times especially if you are connected somewhere else. If the radio is turned off and the COS line indicates a signal it could hang up the whole network. 

Setting holdofftelem=0 will allow the telemetry to be sent regardless of the COS state but it will also send messages over top of node voice.
I think an understanding of how these settings work should solve your problem.

73 Doug
WA3DSP
http://www.crompton.com/hamradio


From: doug at crompton.com
To: n7jys at yahoo.com
Date: Sat, 25 Jul 2015 18:15:46 -0400
CC: arm-allstar at hamvoip.org
Subject: Re: [arm-allstar] New RPI2 version release




The stock images have telemdefault=2 in rpt.conf which means announce connect or disconnect messages only when you send them and mute a short time after. So you will not hear other connect/disconnect messages once it mutes. On large connected systems having connect messages always on can be very annoying so that is why it is set to 2 by default. Setting it to 1 means connect/disconnect messages are always on. 

Perhaps setting it to 1 for awhile might solve your problem assuming you always want to hear the messages.

73 Doug
WA3DSP
http://www.crompton.com/hamradio


Subject: Re: [arm-allstar] New RPI2 version release
From: n7jys at yahoo.com
Date: Sat, 25 Jul 2015 15:40:15 -0500
To: doug at crompton.com

Sometimes when I enter a command I don't get a voice response and sometimes I do. Same thing happens with an incoming connection. Sometimes it announces it and sometimes it won't. So not sure what's causing it. I have not tried a nother install as everything is new. I'm using a DKM sound dongle.
Eric

Sent from my iPhone
On Jul 25, 2015, at 3:29 PM, Doug Crompton <doug at crompton.com> wrote:




Eric,

  I don't think we are going to make a July release but again I am hoping for mid August.

The problem you are experiencing is NOT a general RPi2 or BBB problem. I have not seen this in any other system I have operated nor have I had any other complaints.

Exactly what is happening?
73 Doug
WA3DSP
http://www.crompton.com/hamradio


Date: Sat, 25 Jul 2015 19:52:43 +0000
From: n7jys at yahoo.com
To: arm-allstar at hamvoip.org
Subject: [arm-allstar] New RPI2 version release

I am curious to know when the next  allstar version release for the RPI2 is going to happen. July was the indicated target month for this and we arenearing the end of July! Would like to see audio stability issues fixed.Very pleased  with version 1.0 rpi2 except for intermittent  audio from asterisk voice commands. (As in sometimes it works and sometimes it doesn't) Thanks for all your hard work! Eric (N7JYS)

Marshall's Communications
_______________________________________________

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/20150725/5f977365/attachment-0001.html>