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

[David McGough]

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
>