Thanks, Shadih. I agree with you that it's not a great idea (although with enough work and loving care, I think pagerduty.com is likely to be a hit), and I don't relish the idea of leaving voicemail messages for folks, but I'm going to at least give it a shot. I will also continue sending email notifications for every alert.
I learned long ago that even for text paging, it's always best to send an email copy of every text page -- it helps greatly to avoid folks blaming Nagios when the real problem is their carrier. Any other suggestions from anyone? -- Trever ---------------------------------------------------------------- From: shadih rahman [mailto:shadhi...@gmail.com] Sent: Tuesday, October 06, 2009 9:52 PM To: Furnish, Trever G Subject: Re: [Nagios-users] notify by telephone call? Twinkle has a command line and it should be easy to handle via script. However I have to say making a phone call for notification is not a good idea. People miss call all the time. Paging is much more reliable then placing a call.. That is just my two cents On Tue, Oct 6, 2009 at 8:42 PM, Furnish, Trever G <tgfurn...@herffjones.com> wrote: Can anyone whose already done this point me in the right direction for sending out notifications by reading the alerts into a phone call? The hard part isn't the text-to-speech (I'm assuming I can just use festival for that), or even a pre-recorded message. What's proving to be the hard part for me is figuring out how to reliably make a phone call. We have an existing VoIP phone system, including Cisco routers I could connect to using SIP... if I could find a good command-line SIP calling tool. I also don't want to create a notification method that causes Nagios to back up on notifications. The existing notification methods allow Nagios to quickly hand off notifications to other daemons that ensure reliable delivery (QuickPage, which is wonderful for sending SMS via TAP gateways, and sendmail, which of course handles sending out notifications by email). But I don't want to get distracted by this -- if I could just find a good command-line "place-a-call-and-play-some-audio-into-it" tool, I could wrap it easily in enough scripting to make it reliable. So far I've found notes on using vgetty (and I'm still reading through those), and I've found notes on doing this with Asterisk (but I don't have Asterisk and I hope it's an unneeded level of complexity). There are lots of graphical sip clients available, but I haven't found any others to use from the command-line yet. Suggestions? -- Trever Furnish, tgfurn...@herffjones.com Herff Jones, Inc. Systems Engineer Phone: 317.612.3519 Any sufficiently advanced technology is indistinguishable from Unix. ------------------------------------------------------------------------------ Come build with us! The BlackBerry(R) Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9 - 12, 2009. Register now! http://p.sf.net/sfu/devconference _______________________________________________ Nagios-users mailing list Nagios-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/nagios-users ::: Please include Nagios version, plugin version (-v) and OS when reporting any issue. ::: Messages without supporting info will risk being sent to /dev/null -- Cordially, Shadhin Rahman ------------------------------------------------------------------------------ Come build with us! The BlackBerry(R) Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9 - 12, 2009. Register now! http://p.sf.net/sfu/devconference _______________________________________________ Nagios-users mailing list Nagios-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/nagios-users ::: Please include Nagios version, plugin version (-v) and OS when reporting any issue. ::: Messages without supporting info will risk being sent to /dev/null