[arm-allstar] Public/Private node connection(s)

Doug Crompton wa3dsp at gmail.com
Wed Aug 29 19:29:30 EDT 2018


Ian,

  There would be no difference public or private as far as management. It
sounds like you are not connecting to the private node servers manager with
supermon - thus the "could not connect to Asterisk manager"  message.  Make
sure the server you cannot connect to has the bindaddr=0.0.0.0 NOT
127.0.0.1  in /etc/asterisk/manager.conf and that the password (secret) in
manager.conf matches the entry in your allmon.ini file for supermon.
Restart Asterisk when you make changes.


*73 Doug*

*WA3DSP*

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

On Wed, Aug 29, 2018 at 7:22 PM "Ian via ARM-allstar" <
arm-allstar at hamvoip.org> wrote:

> Hello,
>
> I have downloaded and updated to the most recent version and I would
> like to know if I have Supermon configured correctly.
>
> I have three RPI's and a x86 on my network.
>
> Two Rpi's and the x86 are public nodes and one Rpi is private nodes.
>
> In my main Supermon menu I have added a drop down with public nodes and
> private nodes.
>
> Clicking on the public nodes shows my public nodes status ( except the
> x86 - I'm not bothered about this at the moment )
>
> Clicking on the private nodes give a " could not connect to Asterisk
> manager " prompt.
>
> If I log into Supermon, select a public node and then select connect to
> a private node, I have a connection showing the private node status.
>
> Is this the correct operation ?  eg: private node status only available
> after login to Supermon ?
>
> Regards,
> Ian..
> _______________________________________________
>
> 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
>


More information about the arm-allstar mailing list