[arm-allstar] Auto connection if not in use

Mon Oct 15 10:00:43 EDT 2018

Matt,

There are several settings that effect telemetry. First of all  'rpt
localplay' NOT 'rpt playback' only sends to local RF not to other nodes
connected.

In rpt.conf -

holdofftelem=1 | 0        If 1 no telem on top of talking station, if 0
talks on top

telemnomdb=0      ; Overall reduction in telemetry level in dB
telemduckdb=-9     ; Telemetry level reduction with signal in dB

You should always add or insert some silence at the beginning of your
message. I would say 1-2 seconds. Without this the keyup time could cut off
the beginning.  /var/lib/asterisk/sounds/silence has multiple files of
seconds of silence. These can be converted to other formats if needed.

*73 Doug*

*WA3DSP*

*http://www.crompton.com/hamradio <http://www.crompton.com/hamradio>*

On Mon, Oct 15, 2018 at 9:23 AM "Matthew via ARM-allstar" <
arm-allstar at hamvoip.org> wrote:

> That seems to be working well. Thanks Doug.
>
> I have 2 small outstanding issues.
>
> 1. I only want the audio announcements to go out over local RF. At the
> moment, they play over the RF and the network side of things. IS there a
> setting I am missing to prevent play out over the network side?
>
> 2. Is there a way to get the audio files to play whilst the repeater is
> in use from the RF side?. At the moment, if I try and play an audio file
> whilst someone is using the repeater, it holds off until the user
> finishes and then plays out but I seem to miss the first few seconds of
> audio. I would like to be able to play the announcement over the top.
>
> Thanks,
>
> Matt
>
> "Doug Crompton via ARM-allstar" wrote on 14/10/2018 22:19:
> > Matt,
> >
> >   The proper way is   rpt localplay <node> <file>    So if it was node
> 40000
> > and the file was /etc/asterisk/local/test.gsm it would look like this -
> >
> > rpt localplay 40000 /etc/asterisk/local/test
> >
> > You do not put the extent on the file name.
> >
> > If you used playback instead of localplay it would go locally and to all
> > connected nodes.
> >
> > Also the file must be properly formatted for Allstar.   See the Text to
> > Speech Howto. At the end of that PDF is a SOX line to convert. I would
> > start out with a .wav file. Yoiu can either create it locally in yours or
> > others voice or cature one of the demo sites in computer voice.  Then
> > convert to a .ul file as shown in the howto.
> >
> >
> > *73 Doug*
> >
> > *WA3DSP*
> >
> > *http://www.crompton.com/hamradio <http://www.crompton.com/hamradio>*
> >
> >
> >
> > On Sun, Oct 14, 2018 at 4:25 PM "Matthew via ARM-allstar" <
> > arm-allstar at hamvoip.org> wrote:
> >
> >> Thanks Doug.
> >>
> >> That was my initial thought. Play a 10 minute, 5 minute and 1 minute
> >> warning and see how the users take to it.
> >>
> >> I seem to have a problem playing my voice files though. I have them
> >> saved as .gsm files in /var/lib/asterisk/sounds but if I try and play
> >> them from the Asterisk CLI, I get an error (I've replaced node number
> >> with 12345). The repeater keys up but no audio is played..
> >>
> >> rpt playback 12345 voice_test.gsm
> >> [Oct 14 21:14:24] WARNING[1944]: file.c:602 ast_openstream_full: File
> >> voice_test.gsm does not exist in any format
> >> [Oct 14 21:14:24] WARNING[1944]: file.c:912 ast_streamfile: Unable to
> >> open voice_test.gsm (format 0x44 (ulaw|slin)): No such file or directory
> >> [Oct 14 21:14:24] WARNING[1944]: app_rpt.c:7937 rpt_tele_thread:
> >> ast_streamfile failed on DAHDI/pseudo-1336827494
> >>       -- Hungup 'DAHDI/pseudo-1336827494'
> >>
> >> Am I missing something?
> >>
> >> Thanks,
> >>
> >> Matt
> >>
> >> "Doug Crompton via ARM-allstar" wrote on 14/10/2018 20:53:
> >>> Matt,
> >>>
> >>>    Anything is usually possible with some work but what you want to do
> is
> >>> probably not practical. I would think the best approach is to either
> >>> educate your users of the connection and time it will connect or you
> >> could
> >>> as I do here create a cron based announcement at 5 and 10 minutes
> before
> >>> the connect on the RF side that the connection will be taking place.
> >>> Something like "Attention the so and so net will connect in 10 minutes"
> >>> That way they are aware it is going to happen. If this is done on a
> >> regular
> >>> basis then it should not be a problem once they get use to it.
> >>>
> >>> Being able to detect usage would be tricky. You could check for PTT at
> >> the
> >>> time the connection was to take place but how do you know it was really
> >>> busy or just Id'ing. I suppose a more elaborate script could be written
> >> but
> >>> I would try the above approach first.
> >>>
> >>>
> >>> *73 Doug*
> >>>
> >>> *WA3DSP*
> >>>
> >>> *http://www.crompton.com/hamradio <http://www.crompton.com/hamradio>*
> >>>
> >>> On Sun, Oct 14, 2018 at 3:40 PM "Matthew via ARM-allstar" <
> >>> arm-allstar at hamvoip.org> wrote:
> >>>
> >>>> Hi all.
> >>>>
> >>>> I've been playing with connecting our stand alone repeater up to one
> of
> >>>> the AllStar hubs in the afternoons when the repeater is usually very
> >>>> quiet on local RF. I've got all of the cron entries sorted and
> >>>> everything works well. Before I make it all live, is there any way I
> can
> >>>> only get the script to run if there are no RF users on the repeater so
> >>>> it does not connect them up half way through a QSO? I already have
> voice
> >>>> announcements for 10 minutes, 5 minutes and 1 minute before the
> >>>> connection runs but it would be great to only allow the connection
> once
> >>>> the repeater has not been in use for x minutes.
> >>>>
> >>>> Failing that, is there a way to set up a short code that an RF user
> can
> >>>> dial to abort the auto connect before it runs? I could create a voice
> >>>> file that outputs something like 'dial *73 on your DTMF keypad to
> abort
> >>>> the connection'. I know I can do this once the repeater has connected
> >>>> but it would be a nice feature to be able to stop the connection.
> >>>>
> >>>> Is any of that possible?
> >>>>
> >>>> Thanks,
> >>>>
> >>>> Matt
> >>>> M0LMK
> >>>> _______________________________________________
> >>>>
> >>>> 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
> >>>>
> >>> _______________________________________________
> >>>
> >>> 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
> >> _______________________________________________
> >>
> >> 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
> >>
> > _______________________________________________
> >
> > 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
>
> _______________________________________________
>
> 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
>