<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
<html><head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<meta name="generator" content="Osso Notes">
<title></title></head>
<body>
<p>Using an automated telephone notification system is entirely feasible. There are many open source telephony solutions. (Or cheap commercial solutions based on those open source software)  Best know is probably Asterisk. Its quite flexible on how it can be used. You can create your own cutom scripting in Asterisk and even integrate text to speech software like flite. And you can use just about any method to connect into a phone network: VoIP connection or trunk, a T# trunck, POTS port etc. The non-VoIP method would require some modest extra hardware.  
<br>
<br>----- Original message -----
<br>> Greetings,
<br>>
<br>> Something occurred to me in reading this.
<br>>
<br>> Is there any reason why we can't use text-to-speech? I mean, have
<br>> Nagios call phones, and read the error, or play a pre-recorded error
<br>> message over the voice-line, and listen for a response? ("Hit 1 to
<br>> acknowledge you are on the problem, Hang up, or hit 2 to pass this on to
<br>> the next person in the tree." or the like.)
<br>>
<br>> Especially with VoIP so common nowadays ...
<br>>
<br>> Just thinking of the future,
<br>> -dkap
<br>>
<br>> On Thu, 2010-03-18 at 10:26 -0400, Ryan Pugatch wrote:
<br>> > Here is a summary of solutions mentioned in response to my posting to
<br>> > BBLISA and SAGE:
<br>> >
<br>> > - Dean Anderson mentions this article:
<br>> > <a href="http://www.linuxjournal.com/files/linuxjournal.com/ufiles/LJ191_UsingSMSforNagios.pdf">http://www.linuxjournal.com/files/linuxjournal.com/ufiles/LJ191_UsingSMSforNagios.pdf</a>
<br>> > which involves using an SMS device to interface with Nagios. The
<br>> > MultiTech device in the article is mentioned by Daniel Rich.
<br>> >
<br>> > - Lukas Karlsson uses QuickPage - <a href="http://www.qpage.org/">http://www.qpage.org/</a> with a modem and
<br>> > POTS line. There were a few others suggesting qpage as well.
<br>> >
<br>> > - Derek Balling suggests the Siemens TC65T - several others recommend
<br>> > using an old cell phone or modem to send the texts directly.
<br>> >
<br>> > - Jens Link and Daniel Rich mentioned the decreasing lack of support for
<br>> > TAP (and also lack of support for WCTP)
<br>> >
<br>> > - Several suggestions about having multiple types of notification in
<br>> > case one fails.
<br>> >
<br>> > - Brian de Smet suggests <a href="http://www.pagerduty.com">www.pagerduty.com</a> but Phil Pennock said his
<br>> > colleague had encountered some trouble with them.
<br>> >
<br>> > - A couple of people mentioned that AT&T has an enterprise paging option
<br>> > that gives you an SLA for your texts. <a href="http://enterprisepaging.com/faq.jsp">http://enterprisepaging.com/faq.jsp</a>
<br>> >
<br>> >
<br>> > I hope I didn't miss any of the suggestions.
<br>> >
<br>> > I think the route I am going to go is to grab a MultiTech iSMS and put
<br>> > it on to AT&T with an enterprise paging plan. Then I can have big
<br>> > brother use the API to send messages.
<br>> >
<br>> >
<br>> > Thanks all for your suggestions.
<br>> >
<br>> > Ryan
<br>> >
<br>> > _______________________________________________
<br>> > bblisa mailing list
<br>> > <a href="mailto:bblisa@bblisa.org">bblisa@bblisa.org</a>
<br>> > <a href="http://www.bblisa.org/mailman/listinfo/bblisa">http://www.bblisa.org/mailman/listinfo/bblisa</a>
<br>>
<br>> _______________________________________________
<br>> sage-members mailing list
<br>> <a href="mailto:sage-members@mailman.sage.org">sage-members@mailman.sage.org</a>
<br>> <a href="http://mailman.sage.org/mailman/listinfo/sage-members">http://mailman.sage.org/mailman/listinfo/sage-members</a>
<br><br></p>
</body>
</html>