[arm-allstar] Image update 12/10/17

Tue Dec 12 00:06:56 EST 2017

It will automount. Whatever the flash drive name is will show up in /media
with the ls command. If you want to make a specific folder, after you've
navigated and changed directories until you're on your flash drive, you
type "mkdir (directory name)".

You need to edit two commented out lines in your rpt.conf file in
/etc/asterisk with nano. Scroll down until you see audio something. I'm
doing this from memory.

After you remove the ; from the two lines, you need to enter the path to
your external drive in the line that is where the path goes. I removed the
example and put /media/256GB/dvr as my path. Your drive will be named
different. You need to check what your naming is before editing your
rpt.conf with nano.

Also, the info that was mentioned about 0 for off and 1 for on, it needs to
be changed to =1 for audio recording. You must also add a line with the
mentioned command after the two stanzas with the audio commented out lines.

The pi will create another folder on your drive with your node number. All
the files will be dumped there. They are time stamped to the second as
their file name. My 256GB flash drive is formatted in exfat. The pi sees
the files but windows 10 does not see them. I will attempt to put the flash
drive on my ubuntu machine tomorrow, to see if it sees the files created.
The pi sees them but windows doesn't. I don't know why yet.

I know this is not a good newbie howto, and I'm going all from memory on
how I finally got it to work. Also, if your flash drive has a distinctive
led flash pattern when it is idle, and when it is being accessed, my
samsung flash drive acted like it was idle, even though when I ssh into the
node, and did a ls command, wav files were piling up in the directory. Like
I said, I'll test tomorrow to see if the files are good, or even there, on
a Linux machine with a gui.

On Dec 11, 2017 11:44 PM, Steve Agee via arm-allstar <
arm-allstar at hamvoip.org> wrote:

> Doug,
>
> Thanks for the reminder on this. How about a quick crash course "how to"
> on this. I insert a USB stick. Will Debian then auto mount it, or is human
> intervention required, and once mounted, how do I point the recorded audio
> to the USB stick please?
>
> N5ZUA
>
> On 12/11/2017 10:40 PM, "Doug Crompton via arm-allstar" wrote:
>
>> And remember and I can't emphasize this enough - DO NOT even think of
>> archiving to the SD card!!! If you use archive use a USB stick, hard or SS
>> drive, or sshfs, samba, to another computer.
>>
>>
>> *73 Doug*
>>
>> *WA3DSP*
>>
>> *http://www.crompton.com/hamradio <http://www.crompton.com/hamradio>*
>>
>>
>> On Mon, Dec 11, 2017 at 10:34 PM, "David McGough via arm-allstar" <
>> arm-allstar at hamvoip.org> wrote:
>>
>> BTW, if you need to convert the .pcm container into a .wav container, so
>>> that you can play the file with most software, use sox:
>>>
>>> sox -t ul -c 1 -r 8000 -U "filename.pcm" "filename.wav"
>>>
>>>
>>> 73, David KB4FXC
>>>
>>>
>>>
>>> On Mon, 11 Dec 2017, "David McGough via arm-allstar" wrote:
>>>
>>>
>>>> Hi Terry,
>>>>
>>>> As of the 12/10 update there are now 3 settings related to saving audio
>>>> and telemetry files:
>>>>
>>>> archivedir=<path to archived files>
>>>> ;; No changes, works as previously
>>>>
>>>> archiveaudio=[0|1]
>>>> ;; == 0 means save telemetry log only
>>>> ;; == 1 means telemetry log and audio files
>>>> ;; default value is: 1
>>>> ;; No changes, works as previously
>>>>
>>>>
>>>> archivetype=[gsm|pcm]
>>>> ;; == gsm means to save a gsm encoded .wav file
>>>> ;; == pcm means to save a ulaw encoded .pcm file
>>>> ;; default value is: gsm
>>>> ;; Newly added feature
>>>>
>>>>
>>>> This new archivetype parameter allows the AllStar user a way to save
>>>> very
>>>> high quality ulaw audio, rather than the mediocre sounding gsm encoded
>>>> audio, should it be needed for any reason---such as analysis when there
>>>>
>>> is
>>>
>>>> an interference source getting into a repeater.
>>>>
>>>>
>>>> 73, David KB4FXC
>>>>
>>>>
>>>>
>>>> On Mon, 11 Dec 2017, "Terry Bethlehem via arm-allstar" wrote:
>>>>
>>>> Did you mean archiveaudio=0 for off (text) and archiveaudio=1 for on
>>>>>
>>>> (wav)?
>>>
>>>> On Dec 10, 2017 11:56 PM, Doug Crompton via arm-allstar <
>>>>> arm-allstar at hamvoip.org> wrote:
>>>>>
>>>>> A new update dated 12/10/17 has been released that includes a couple
>>>>>
>>>> of new
>>>
>>>> commands for the rpt.conf file. Install this update using the ADMIN
>>>>>
>>>> menu
>>>
>>>> selection 1. These commands if used need to be manually entered into
>>>>>
>>>> the
>>>
>>>> file.
>>>>>
>>>>> Startup_macro_delay
>>>>>
>>>>> The existing startup_macro command allows you to run Asterisk/Allstar
>>>>> commands at boot and is typically used to connect to a node or nodes as
>>>>> part of the startup process. This is often used with a fixed, mobile,
>>>>>
>>>> or
>>>
>>>> portable node to initiate Allstar commands like connecting to other
>>>>>
>>>> nodes
>>>
>>>> without operator intervention at boot.
>>>>>
>>>>> The problem with this command is that if you use it to connect and you
>>>>>
>>>> have
>>>
>>>> not received connection information for the node you wish to connect to
>>>>> prior to executing the command it will be ignored and never executed.
>>>>>
>>>> If
>>>
>>>> routing information for the node you were connecting to was hard coded
>>>>>
>>>> in
>>>
>>>> rpt.conf this would not be a problem but it would almost always not be
>>>>>
>>>> the
>>>
>>>> case for nodes outside of your local purview with public IP addresses.
>>>>>
>>>> For
>>>
>>>> rpt_extnodes file lookup it would generally not be updated in time for
>>>>>
>>>> the
>>>
>>>> connect to complete and even in the upcoming quicker DNS lookup it
>>>>>
>>>> could
>>>
>>>> still require some amount of delay.
>>>>>
>>>>> In order to alleviate this problem a startup_macro_delay command has
>>>>>
>>>> been
>>>
>>>> added. This command if you intend to use it should be added to your
>>>>> rpt.conf file on a line before or after the startup_macro command.
>>>>>
>>>> This is
>>>
>>>> on a per node basis so be sure to add it to all node stanzas that you
>>>>>
>>>> want
>>>
>>>> to apply it to. The default delay value if not in rpt.conf is 0 or no
>>>>> delay. The delay is entered in seconds from 0-120.
>>>>>
>>>>> startup_macro_delay=10  ; 10 second delay before executing the startup
>>>>>
>>>> macro
>>>
>>>> The delay would probably be in the area of 5-20 seconds but for the
>>>>> rpt_extnodes file lookup it could exceed this in some instances. Some
>>>>> experimentation for a minimum reliable number is required. There is no
>>>>> danger in setting this too long, it will just take longer to execute at
>>>>> startup.
>>>>>
>>>>> Another command has been added to allow a format type specification
>>>>>
>>>> for the
>>>
>>>> archivedir command called archivetype
>>>>>
>>>>> archivetype=[gsm|pcm] parameter.
>>>>>
>>>>> This is the format that is used to archive voice data to a hard or
>>>>>
>>>> solid
>>>
>>>> state drive. The default if not defined is gsm which is the current
>>>>>
>>>> default
>>>
>>>> in Allstar. Setting the format to pcm gives greater fidelity but at the
>>>>> expense of requiring greater storage space for the files. Never
>>>>>
>>>> archive to
>>>
>>>> your SD card. Use a USB stick, hard drive, SSD, or remote storage for
>>>>> archiving.  Use the archivedir=<dir> command to set the directory path
>>>>>
>>>> for
>>>
>>>> archiving and the archiveaudio=0|1 command to turn On/Off the
>>>>>
>>>> archiving of
>>>
>>>> audio. With audio off only text archiving is stored.
>>>>>
>>>>> Both the startup_macro_delay and the archivetype commands are on a per
>>>>>
>>>> node
>>>
>>>> basis. They can be defined and assigned different values in each node
>>>>>
>>>> on
>>>
>>>> your server.
>>>>>
>>>>> Information on version updates is available from a link on the
>>>>>
>>>> hamvoip.org
>>>
>>>> web page or directly at this URL -
>>>>>
>>>>> https://hamvoip.org/local/allstar_version.php
>>>>>
>>>>>
>>>>> *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
>>>>> _______________________________________________
>>>>>
>>>>> 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
>