[arm-allstar] Allmon
Pierre Martel
petem001 at gmail.com
Mon May 1 22:17:03 EST 2017
make totally sens.. but one thing i,ve seen that make a lot of problem is
port redirection to different port.
like you redirect port 5000 to the local machine 192.xxx.xxx.xxx but to the
port 5001 , just an exemple. some router will let you do it but the
software sometimes wont like it much...
Le lun. 1 mai 2017 à 22:53, "Doug Crompton via arm-allstar" <
arm-allstar at hamvoip.org> a écrit :
> Larry,
>
> Is that really true or only if you are trying to access via port forward?
> I though that internally the IP address and port would point it to the
> right server and only if you were going to port forward would you need
> different ports because you obviously cannot port forward to the same port
> to two different IP's.
>
>
> *73 Doug*
>
> *WA3DSP*
>
> *http://www.crompton.com/hamradio <http://www.crompton.com/hamradio>*
>
> On Mon, May 1, 2017 at 6:46 PM, "larry via arm-allstar" <
> arm-allstar at hamvoip.org> wrote:
>
> > Doug and Ken
> > If on the same LAN you cannot have both ports 5038 on 2 different
> servers.
> > Reconfig the node being monitored to a different port and leave the
> server
> > running allmon (the Pi node) set to 5038.
> >
> > Dont know if it makes any difference to ALLMON But when on the same LAN
> > you still need each node configured in each others rpt.conf
> > In order for them to connect to each other.
> >
> > Larry - N7FM
> >
> > -------- Original message --------
> > From Doug Crompton via arm-allstar <arm-allstar at hamvoip.org>
> > Date: 05/01/2017 2:43 PM (GMT-08:00)
> > To ARM Allstar <arm-allstar at hamvoip.org>
> > Cc Doug Crompton <wa3dsp at gmail.com>
> > Subject Re: [arm-allstar] Allmon
> >
> > Ken,
> >
> > At this point I can't offer you anything more. If you are doing what you
> > say you are doing it looks right. I have no idea what is happening. It
> > should work. I have never had a problem connecting to the manager.
> >
> > I can only offer you that I could login and look around. I would need
> your
> > ssh port if other than 222 and your login password to both allstar
> servers
> > as well as there local IP addresses. If you decide to do that send a
> > personal email and we can take this off the forum.
> >
> >
> >
> > *73 Doug*
> >
> > *WA3DSP*
> >
> > *http://www.crompton.com/hamradio <http://www.crompton.com/hamradio>*
> >
> > On Mon, May 1, 2017 at 3:29 PM, "Ken via arm-allstar" <
> > arm-allstar at hamvoip.org> wrote:
> >
> > > Hi Doug,
> > > Yes my node is on a BBB and Allmon is on my Raspberry pi web server
> > > I had the ip address set to 127.0.0.1
> > >
> > > I have changed the ip address in Allmon.ini to 192.168.1.74 which is
> the
> > > BBB
> > > ip address, port is 5038, uncommented 0.0.0.0 in the manager.conf file
> > >
> > > It still won't connect, it logs on ok but will not connect to asterick
> > > manager
> > > Sorry to be hogging the list
> > > Regards Ken
> > >
> > > -----Original Message-----
> > > From: arm-allstar [mailto:arm-allstar-bounces at hamvoip.org] On Behalf
> Of
> > > "Doug Crompton via arm-allstar"
> > > Sent: 01 May 2017 19:44
> > > To: ARM Allstar <arm-allstar at hamvoip.org>
> > > Cc: Doug Crompton <wa3dsp at gmail.com>
> > > Subject: Re: [arm-allstar] Allmon
> > >
> > > Ken,
> > >
> > > Somehow I think there is a misunderstanding here. Is the node you
> listed
> > > 28468 on a BBB? Assuming that and this code is on the RPI then it would
> > not
> > > work - if the node you want to look at is on a different server you
> have
> > to
> > > use the IP address, port and credentials for that servers manager in
> the
> > > node settings in allmon.ini. Larry documented that in a separate
> message.
> > > In addition you need to uncomment the bindaddr=0.0.0.0 in the
> > manager.conf
> > > file on the BBB.
> > >
> > >
> > >
> > > *73 Doug*
> > >
> > > *WA3DSP*
> > >
> > > *http://www.crompton.com/hamradio <http://www.crompton.com/hamradio>*
> > >
> > > On Mon, May 1, 2017 at 2:16 PM, "Ken via arm-allstar" <
> > > arm-allstar at hamvoip.org> wrote:
> > >
> > > > Hi Both,
> > > >
> > > > Here is a copy of my Allmon.ini and manager files.
> > > > As far as I can see they are the same as your files, I just have one
> > > > node
> > > >
> > > > Regards
> > > > Ken
> > > >
> > > > <?php
> > > > [About]
> > > > url=about.php
> > > > [28468]
> > > > host=127.0.0.1:5038
> > > > user=admin
> > > > passwd=xxxxxxx
> > > > menu=yes
> > > > hideNodeURL=no
> > > > ?>
> > > >
> > > > ;
> > > > ; AMI - The Asterisk Manager Interface ; ; Third party application
> > > > call management support and PBX event supervision ; ; This
> > > > configuration file is read every time someone logs in ; ; Use the
> > > > "manager list commands" at the CLI to list available manager commands
> > > > ; and their authorization levels.
> > > > ;
> > > > ; "manager show command <command>" will show a help text.
> > > > v;
> > > > ;
> > > > ; ---------------------------- SECURITY NOTE
> > > > ------------------------------
> > > > -
> > > > ; Note that you should not enable the AMI on a public IP address. If
> > > > needed, ; block this TCP port with iptables (or another FW software)
> > > > and reach it ; with IPsec, SSH, or SSL vpn tunnel. You can also make
> > > > the manager ; interface available over http if Asterisk's http server
> > > > is enabled in ; http.conf and if both "enabled" and "webenabled" are
> > > > set to yes in ; this file. Both default to no. httptimeout provides
> > > > the maximum ; timeout in seconds before a web based session is
> > > > discarded. The ; default is 60 seconds.
> > > > ;
> > > > [general]
> > > > displaysystemname = yes
> > > > enabled = yes
> > > > ;webenabled = yes
> > > > port = 5038
> > > >
> > > > ;httptimeout = 60
> > > > ; a) httptimeout sets the Max-Age of the http cookie ; b) httptimeout
> > > > is the amount of time the webserver waits
> > > > ; on a action=waitevent request (actually its httptimeout-10)
> > > > ; c) httptimeout is also the amount of time the webserver keeps
> > > > ; a http session alive after completing a successful action
> > > >
> > > > bindaddr = 127.0.0.1 ; Local interface only!
> > > > ;bindaddr = 0.0.0.0 ; Not secure
> > > > ;
> > > > ;displayconnects = yes
> > > > ;
> > > > ; Add a Unix epoch timestamp to events (not action responses) ;
> > > > ;timestampevents = yes
> > > >
> > > > [admin]
> > > > secret =xxxxxx
> > > > read = all,system,call,log,verbose,command,agent,user,config
> > > > write = all,system,call,log,verbose,command,agent,user,config
> > > >
> > > >
> > > >
> > > > -----Original Message-----
> > > > From: arm-allstar [mailto:arm-allstar-bounces at hamvoip.org] On Behalf
> > > > Of "Doug Crompton via arm-allstar"
> > > > Sent: 01 May 2017 17:25
> > > > To: ARM Allstar <arm-allstar at hamvoip.org>
> > > > Cc: Doug Crompton <wa3dsp at gmail.com>
> > > > Subject: Re: [arm-allstar] Allmon
> > > >
> > > > Would you not also have to allow general access to the manager(s) on
> > > > the various servers? The accessing system has to use the port and IP
> > > > address of the manager on the system you want to monitor. Thus I
> think
> > > > you would need to setup the manager.conf on the monitored system to
> > > > allow access. In that case the line bindaaddr=0.0.0.0 would need to
> be
> > > uncommented on his BBB.
> > > >
> > > > The manager is not very secure but unless you port forward it -
> > > > typically
> > > > 5038 - and you are behind a router and use it only locally it should
> > > > not be a problem.
> > > >
> > > > [general]
> > > >
> > > > displaysystemname =
> > > > yes
> > > > enabled =
> > > > yes
> > > > ;webenabled =
> > > > yes
> > > > port =
> > > > 5038
> > > >
> > > >
> > > > ;httptimeout =
> > > > 60
> > > > ; a) httptimeout sets the Max-Age of the http cookie ; b) httptimeout
> > > > is the amount of time the webserver waits
> > > > ; on a action=waitevent request (actually its
> > > > httptimeout-10)
> > > > ; c) httptimeout is also the amount of time the webserver keeps
> > > > ; a http session alive after completing a successful
> > > > action
> > > >
> > > >
> > > > bindaddr = 127.0.0.1 ; Local interface
> > > > only!
> > > > ;bindaddr = 0.0.0.0 ; Not secure
> > > > ;
> > > >
> > > >
> > > >
> > > > *73 Doug*
> > > >
> > > > *WA3DSP*
> > > >
> > > > *http://www.crompton.com/hamradio <http://www.crompton.com/hamradio
> >*
> > > >
> > > > On Mon, May 1, 2017 at 12:02 PM, "Larry via arm-allstar" <
> > > > arm-allstar at hamvoip.org> wrote:
> > > >
> > > > > Hi ken.
> > > > >
> > > > > Here is a sample of my "allmon.ini.php" this needs to be on the
> > > > > server that is doing the node monitoring of other nodes.
> > > > >
> > > > > This server monitors a group of my other nodes. I thought it might
> > > > > help with an example of what the Allmon2 server needs in order to
> > > > > log into the other nodes Asterick manager.
> > > > >
> > > > > I have removed the password but it needs to match the Asterisk
> > > > > Manager login you set on each of the other node if on different
> > > servers.
> > > > > Also ... Each server needs to have its own port number assigned as
> > > > > you will note in the "host" settings below.
> > > > >
> > > > > Doug was correct in his reply I just thought a picture of the
> > > > > process might help.
> > > > >
> > > > > Larry - N7FM
> > > > > ----------------------------------
> > > > > File: allmon.ini.php
> > > > >
> > > > > <?php
> > > > > [About]
> > > > > url=about.php
> > > > > [41880]
> > > > > host=127.0.0.1:5038
> > > > > user=admin
> > > > > passwd=xxxxxx
> > > > > menu=yes
> > > > > hideNodeURL=no
> > > > >
> > > > > :[41879]
> > > > > ;host=192.168.9.38:5033
> > > > > ;user=admin
> > > > > ;passwd=xxxxxx
> > > > > ;menu=nyes
> > > > > ;hideNodeURL=no
> > > > >
> > > > > [28162]
> > > > > host=192.168.9.68:5037
> > > > > user=admin
> > > > > passwd=xxxxxx
> > > > > menu=nyes
> > > > > hideNodeURL=no
> > > > >
> > > > > [28358]
> > > > > host=192.168.9.68:5037
> > > > > user=admin
> > > > > passwd=xxxxxxx
> > > > > menu=no
> > > > > hideNodeURL=no
> > > > >
> > > > > [41473]
> > > > > host=192.168.9.68:5037
> > > > > user=admin
> > > > > passwd=xxxxxxxx
> > > > > menu=nyes
> > > > > hideNodeURL=no
> > > > >
> > > > > [29018]
> > > > > host=192.168.9.50:5036
> > > > > user=admin
> > > > > passwd=
> > > > > menu=no
> > > > > hideNodeURL=no
> > > > >
> > > > >
> > > > >
> > > > >
> > > > > On 05/01/2017 05:58 AM, "Ken via arm-allstar" wrote:
> > > > >
> > > >
> > > > 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
> _______________________________________________
>
> 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