VoIP Mailing List Archives

[nitesh.bansal at gmail...]

Hello all,


The question isn't directly related to Asterisk, but I'm looking for recommendations

for a monitoring tool to monitor the health of Asterisk instances running in Production.


Ideally, the tool should be able to generate monitoring traffic (OPTIONS ping or INVITE),

use the response/no response from Asterisk to store the health of an Asterisk instance running

somewhere in the DB.



Thanks,

Nitesh Bansal

[gr.sabery at gmail.com]

Hello,


For service monitoring you can use tools like sipsak in combination with Zabix or Zenoss. Also using Zenoss or Zabix you can monitor the health of your servers. This way you have both top-down and bottom-up monitoring. For monitoring call quality you can use tools like VoIP Monitor (it is not free).


Regards






On Tue, Sep 27, 2016 at 12:03 PM, Nitesh Bansal <nitesh.bansal@gmail.com (nitesh.bansal@gmail.com)> wrote:

[sysadmin at reed-media...]

Hello,
you can have a look on Homer
http://sipcapture.org/
regards


On 27/09/2016 10:39, Gholamreza Sabery wrote:

[nitesh.bansal at gmail...]

Thanks, I'm considering Homer, but I'm not sure if it can generate traffic on its own to check

the health of the service.


Regards,

Nitesh


On Tue, Sep 27, 2016 at 11:17 AM, sysadmin@reed-media.com (sysadmin@reed-media.com) <sysadmin@reed-media.com (sysadmin@reed-media.com)> wrote:

[sysadmin at reed-media...]

you have some tools listed here to generate traffic.
http://www.voip-info.org/wiki/view/How+To+Debug+and+Troubleshoot+VOIP
regards,

Jose


On 27/09/2016 11:44, Nitesh Bansal wrote:

[nrjchnd at gmail.com]

Homer for voip / flow capture




Smoke ping has a sip based server test feature in it as well

Sent from my iPhone

On 27 Sep. 2016, at 7:17 pm, "sysadmin@reed-media.com (sysadmin@reed-media.com)" <sysadmin@reed-media.com (sysadmin@reed-media.com)> wrote:

[joan.ayma at ackstorm.es]

If you only need graphing and history, munin plus plugins does well its job.


El 27/09/16 a les 12:34, Neeraj Chand ha escrit:

[asterisk at voipbusine...]

Hello;
    We’ve been using Nagios and a lot of customizations for the plugins for several years now to monitor over 1,000 metrics on each of our PBX’s. We’re in the process of GPL’ing the Asterisk plugins now. That gives us our core monitoring, notifications, event handlers, etc. To put it all together, instead of the standard static rrdtool graphs, which we thought would be a bottleneck and limit us, we’ve implemented a dynamic dashboarding system that we use to display the relevant data and to trivially create new dynamic dashboards in a matter of seconds. There is definitely no shortage of monitoring and NMS systems out there, but for us, we pretty much built this to monitor our Asterisk PBX’s. If you want to take a look at what we use, contact me offline.
Regards;
John V.
support@voipbusiness.us (support@voipbusiness.us)



From: asterisk-users-bounces@lists.digium.com [mailto:asterisk-users-bounces@lists.digium.com] On Behalf Of Nitesh Bansal
Sent: Tuesday, September 27, 2016 4:34 AM
To: Asterisk Users Mailing List - Non-Commercial Discussion; Asterisk Developers Mailing List
Subject: [asterisk-users] VoIP monitoring tools


Hello all,

The question isn't directly related to Asterisk, but I'm looking for recommendations

for a monitoring tool to monitor the health of Asterisk instances running in Production.

Ideally, the tool should be able to generate monitoring traffic (OPTIONS ping or INVITE),

use the response/no response from Asterisk to store the health of an Asterisk instance running

somewhere in the DB.



Thanks,

Nitesh Bansal

[nitesh.bansal at gmail...]

Hello,


Nagios is really a good tool, we are already using it to monitor Asterisk.

I'm looking for something which can monitor the Asterisk and store the information

somewhere in a DB, where I could retrieve it from Kamailio.

I need that information in Kamailio to make routing decisions.


Thanks,

Nitesh


On Tue, Sep 27, 2016 at 4:28 PM, Tech Support <asterisk@voipbusiness.us (asterisk@voipbusiness.us)> wrote: