[arm-allstar] Echolink connects on Version 1.5 as seen on CLI had a surprising improvement

[Pierre Martel]

forgot to add that if you have 2 node you need to put it in both node
stanza if you wish to record each node audio.

and it will also record the audio file under a directory that is your node
number


2017-02-21 15:03 GMT-05:00 Pierre Martel <petem001 at gmail.com>:

> Hi Stanley you can already record to an exernal hard disk all the audio
>  activity of your node
>
> In rpt.conf in the node stanza just had this:
>
> archivedir = /etc/asterisk/record
>
> this would record all activity to the /etc/asterisk/record/ directory.
>
> you can mount your usb hard disk to where you want and point to it in the
> archivedir option. could be /media/usb/asteriskarchive/
>
> fit the path to your need
>
> Pierre VE2PF
>
>
> 2017-02-21 8:53 GMT-05:00 "Stanley Stanukinos via arm-allstar" <
> arm-allstar at hamvoip.org>:
>
>> David, on the logging a request from me if possible is to log to an
>> external USB hard drive. Also make it where it is a menu option to turn on
>> and off. My thought on this is if the drive dies/crashes it is not a big
>> loss. Some of the laptop drives have dropped drastically in price and the
>> solid state drive have gotten cheaper as well. I would also like to capture
>> the audio if possible from what I have read about on the PC based systems.
>>
>> I know a wish list.
>>
>> Thanks to you, Doug and the team for all the development work.
>>
>> Stan
>>
>> Sent from my iPhone
>>
>> > On Feb 20, 2017, at 10:23 PM, David McGough via arm-allstar <
>> arm-allstar at hamvoip.org> wrote:
>> >
>> >
>> > Hi Tom,
>> >
>> > Thanks for the positive feedback!!
>> >
>> > There are a handful of memory corruption bugfixes in the updated V1.5
>> > echolink driver which improve stability and functionality. Several of
>> > these fixes are in the echolink nodelist management code, which would
>> > cause crashes in certain situations.
>> >
>> > Currently, I don't think "normal" echolink connects/disconnects get
>> > logged in any of the Asterisk logs. Improved logging is one area Doug &
>> I
>> > have already discussed, and is desirable.  We'll work on this for a
>> future
>> > release.
>> >
>> > 73, David KB4FXC
>> >
>> >
>> >
>> >> On Mon, 20 Feb 2017, "Tom Whiteside via arm-allstar" wrote:
>> >>
>> >> To get my feet wet, converted one of our four Allstar nodes over to
>> the new
>> >> version recently - started with the one we use for Echolink and Zoiper
>> >> connects.   We always have a number of Echolink connects during a
>> local net
>> >> and I took the opportunity to watch the activity using the CLI menu
>> item.
>> >> To my happy surprise, it now actually shows the callsigns and names
>> for for
>> >> Echolink connects versus only showing the proxy server used in 1.2.
>> >>
>> >>
>> >>
>> >> Version 1.5 has been working flawlessly so far and with this nice added
>> >> surprise!   Is this user log information logged somewhere?
>> >>
>> >>
>> >>
>> >> Tom N5TW
>> >>
>> >> _______________________________________________
>> >>
>> >> 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
>>
>
>