Asterisk

check_asterisk_ami

Description:

Plugin to check Asterisk using AMI,

Current Version

1.1.0.6

Last Release Date

2011-09-08

Compatible With

  • Nagios 3.x
  • Nagios XI

Owner

License

GPL


Nagios CSP

Meet The New Nagios Core Services Platform

Built on over 25 years of monitoring experience, the Nagios Core Services Platform provides insightful monitoring dashboards, time-saving monitoring wizards, and unmatched ease of use. Use it for free indefinitely.

Monitoring Made Magically Better

  • Nagios Core on Overdrive
  • Powerful Monitoring Dashboards
  • Time-Saving Configuration Wizards
  • Open Source Powered Monitoring On Steroids
  • And So Much More!
Project Files
Project Notes
Plugin to check Asterisk via AMI Currently has the following information channels in use calls active number of IAX2 peers number of SIP peers Requires manager.conf user with access to: write:system,command Returns performance data for statistics. requires netcat and uses utils.sh check_asterisk_ami v1.1.0.6 (nagios-plugins 1.4.15) The nagios plugins come with ABSOLUTELY NO WARRANTY. You may redistribute copies of the plugins under the terms of the GNU General Public License. For more information about these matters, see the file named COPYING. Nagios Plugin to check Asterisk using AMI Usage: check_asterisk_ami [-H hostname] [-q query] [-u username] [-p password] [-P port] [-w warning] [-c critical] -H Hostname -q Command to query -u AMI Username -p AMI Password -P (optional) AMI PORT -w (optional) warning threshold -c (optional) critical threshold SupportedCommands: channels (check number of current channels in-use) calls (check number of current calls) sippeers (check number of current calls) iaxpeers (check number of current calls) Usage: check_asterisk_ami --help Usage: check_asterisk_ami --version Asterisk Call Status Check. Jason Rivers 2011
Reviews (2) Add a Review
Nice one, some typos ...
by bendler, April 30, 2016
Does _not_ work as expected because of some typos in the source. Replace all STATUS_ and STATU_ with STATE_, then exit codes are correct again. At the end, remove the equals-sign (=) in exit=$STATE_WARNING - now the exit codes should respect warning/critical states.
For those who care: in the section "channels", messages are still using "calls" - enough room for confusion.
Helpful? Yes  No 
very good.
by 808blogger, September 30, 2011
Works exactly as described.

Would have 5 stars if the netcat path was either autodetermined or a variable so that i didn't have to change it in the code.

combine with pnp4nagios for some nice graphs.
0 of 1 found this review helpful.
Helpful? Yes  No 1
Add a Review

You must be logged in to submit a review.

Thank you for your review!

Your review has been submitted and is pending approval.

Recommend

To:


From:


Thank you for your recommendation!

Your recommendation has been sent.

Project Stats
Rating
4 (3)
Favorites
0
Views
94,784