[arm-allstar] Logging Echolink connects

[Doug Crompton]

Rick,

The very best way to solve your problem is to run Supermon with the
smlogger activated. This is all described in the Supermon setup howto at
the hamvoip.org website. It is easy to setup. Then all actions Allstar,
Echolink, or IRLP are logged to /var/log/asterisk/connectlog. You could
then grep from there. Remember however that logs are volatile so if you
want to keep them through a reboot you need to copy them off. Supermon is
also an excellent way to view and manage your nodes.


*73 Doug*

*WA3DSP*

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



On Mon, Apr 9, 2018 at 12:42 PM, "Rick Harkins via arm-allstar" <
arm-allstar at hamvoip.org> wrote:

> We'd like to log all Echolink connects. The default verbosity (3) doesn't
> seem to drop the connect message into /var/log/asterisk/messages.
>
> If I start the CLI with a verbosity of 4, I see a nice connect message.
>
> I'm thinking that if I can run asterisk with a verbosity of 4, then those
> connect messages will get dropped in the log file and I can grep them out.
>
> Is the the best way? Where do I change the default verbosity level for the
> main asterisk process?
>
> Thanks!
>
> Rick Harkins WØYGH
> Lee's Summit, MO
> _______________________________________________
>
> 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