From owner-freebsd-isp@FreeBSD.ORG Thu Jun 1 19:42:56 2006 Return-Path: X-Original-To: freebsd-isp@freebsd.org Delivered-To: freebsd-isp@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4E93716B479 for ; Thu, 1 Jun 2006 19:42:56 +0000 (UTC) (envelope-from lambert@lambertfam.org) Received: from sysmon.tcworks.net (sysmon.tcworks.net [65.66.76.4]) by mx1.FreeBSD.org (Postfix) with ESMTP id A274143D45 for ; Thu, 1 Jun 2006 19:42:54 +0000 (GMT) (envelope-from lambert@lambertfam.org) Received: from sysmon.tcworks.net (localhost [127.0.0.1]) by sysmon.tcworks.net (8.13.1/8.13.1) with ESMTP id k51Jgrl8048687 for ; Thu, 1 Jun 2006 14:42:53 -0500 (CDT) (envelope-from lambert@lambertfam.org) Received: (from lambert@localhost) by sysmon.tcworks.net (8.13.1/8.13.1/Submit) id k51JgroZ048686 for freebsd-isp@freebsd.org; Thu, 1 Jun 2006 14:42:53 -0500 (CDT) (envelope-from lambert@lambertfam.org) X-Authentication-Warning: sysmon.tcworks.net: lambert set sender to lambert@lambertfam.org using -f Date: Thu, 1 Jun 2006 14:42:53 -0500 From: Scott Lambert To: freebsd-isp@freebsd.org Message-ID: <20060601194253.GA42904@sysmon.tcworks.net> Mail-Followup-To: freebsd-isp@freebsd.org References: <20060601152435.GC51255@ns2.wananchi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20060601152435.GC51255@ns2.wananchi.com> User-Agent: Mutt/1.5.9i Subject: Re: Mass SMS X-BeenThere: freebsd-isp@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Internet Services Providers List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 01 Jun 2006 19:42:56 -0000 On Thu, Jun 01, 2006 at 06:24:35PM +0300, Odhiambo Washington wrote: > I have a few hundred VIP clients (yes, some are more VIP than others) > who I'd like to notify, via SMS, whenever we have any network problem > and also immediately such a problem is resolved. I would use Nagios, ports/net-mgmt/nagios, http://www.nagios.org/, and setup a contact for each VIP. Then you can notify only the VIPs that are affected by a particular problem. For example: if some of your VIPs are in Washington State, they probably don't want to know about problems in Virginia.... They might even get mad at you if you sent them notifications for issues they don't care about, especially at 2am. You can define contact groups for Washington, Virginia and global. Contacts can exist in more than one contact group. The only hard part is generating the config file. But that should be easily scripted since Nagios can use multiple config files. Acknowledgements that a techincian is working on the problem are sent as notifications to all contacts by default. For SMS notification without just using someone else's e-mail<-->SMS gateway, use QPage, ports/comms/qpage, http://www.qpage.org/. However, some companies are beginning to charge for modem access to their SMS gateways. The e-mail<-->SMS gateways are great so long as not all of your connections to the Internet are down. There are other options for SMS, whichever option you pick should be possible to tie into Nagios. -- Scott Lambert KC5MLE Unix SysAdmin lambert@lambertfam.org