well - still have "unable to authenticate" problem.  I did figure out that  allmon does not run unless you have the web page open on your browser.  I am assuming startup is when it reads the ini file (?) So any changes you make in allmon.ini get used next time you open the page.

 

Can I assume I do not need to pass the 5038 port through my router?  The allmon PC and the node server are behind the same router - same switch even.

 

I also am having a problem with the Admin access for the web page.  I made the user (not called admin this time) following the instructions, but when I try to login from the web page I get "sorry, login failed"

 

 

sigh

 

Ken

 

-----Original Message-----
From: Tim Sawyer <tim.sawyer@me.com>
To: Ken <ke2n@cs.com>
Sent: Tue, Oct 22, 2013 7:13 am
Subject: Re: [App_rpt-users] allmon

Sorry, I thought there was a sample manager.conf, here's one....

[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

displayconnects = no

;                                                                               

; Add a Unix epoch timestamp to events (not action responses)                   

;                                                                               

timestampevents = yes                                                          

                                                                                

[admin]                                                                         

secret = xxxxxxxxxxxxxxx ; your password

read = all,system,call,log,verbose,command,agent,user,config                    

write = all,system,call,log,verbose,command,agent,user,config    

;permit=127.0.0.1

;permit=192.168.0.0/255.255.255.0

;permit=192.168.21.0/255.255.255.0

--
Tim
:wq

On Oct 21, 2013, at 9:37 PM, Ken <ke2n@cs.com> wrote:

distro?

 

in https://github.com/tsawyer/allmon

 

there is no sample manager.conf

 

 

 Thanks

Ken

-----Original Message-----
From: Tim Sawyer <tim.sawyer@me.com>
To: Ken <ke2n@cs.com>
Cc: app_rpt-users <app_rpt-users@ohnosec.org>
Sent: Mon, Oct 21, 2013 11:06 pm
Subject: Re: [App_rpt-users] allmon

There is a sample manager.conf with the distro. Is that any help?

--
Tim
:wq

On Oct 21, 2013, at 2:05 PM, Ken <ke2n@cs.com> wrote:

trying allmon for the first time.

 

Instructions say to modify manager.conf but don't say what you actually have to do.

 

anyway, I took a shot at it and I am getting this on the asterisk node:

 

[Oct 21 16:58:04] NOTICE[4403]: manager.c:1034 authenticate: 192.168.1.203 failed to authenticate as 'admin'
  == Connect attempt from '192.168.1.203' unable to authenticate

 

yes I called the user 'admin'

 

any help?

also - to reload the manager.conf file, do I have to restart asterisk, or is there a smoother way?

 

Thanks

Ken

_______________________________________________
App_rpt-users mailing list
App_rpt-users@ohnosec.org
http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users