[99128] in North American Network Operators' Group
Re: Using Mobile Phone email addys for monitoring
daemon@ATHENA.MIT.EDU (Duane Waddle)
Thu Sep 6 17:48:15 2007
Date: Thu, 6 Sep 2007 16:27:09 -0500
From: "Duane Waddle" <duane.waddle@gmail.com>
To: nanog@merit.edu
In-Reply-To: <Pine.LNX.4.44.0709061339020.28859-100000@samwise.w-link.net>
Errors-To: owner-nanog@merit.edu
------=_Part_87569_1491320.1189114029499
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
On 9/6/07, Rick Kunkel <kunkel@w-link.net> wrote:
[snip]
We've traditionally used mobile phone email addresses for system
> notifications, but over the past 6-12 months, it seems to have become
> increasingly sketchy.
[snip]
Is SMTP to a mobile phone a fundamentally flawed way to do this?
>
> Anyone else have any issues, past or present, with this kind of thing?
We tend to avoid the whole SMTP mess and deliver messages to mobiles and
pagers via a modem and the provider's TAP gateway. It works quite well with
Verizon and AT&T/Cingular, but I've no experience with T-Mobile. It also
avoids the whole mess of failing to alert when your monitoring box has a bad
NIC, cable, switchport, etc - of course considering that you trade those for
problems with a serial port, cable, modem, or phone line... But it gives us
a big (and perhaps false) warm fuzzy that our alerting is 'out of band'
relative to our upstream Internet connections.
The folks at Avtech have a nice index of TAP gateway numbers at
http://www.avtech.com/Support/TAP/index.htm
Hope you find this useful...
--D
------=_Part_87569_1491320.1189114029499
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
<br><div><span class="gmail_quote">On 9/6/07, <b class="gmail_sendername">Rick Kunkel</b> <<a href="mailto:kunkel@w-link.net">kunkel@w-link.net</a>> wrote:</span><br><div><br>[snip] <br></div><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
We've traditionally used mobile phone email addresses for system<br>notifications, but over the past 6-12 months, it seems to have become<br>increasingly sketchy.</blockquote><div><br>[snip] <br></div><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Is SMTP to a mobile phone a fundamentally flawed way to do this?<br><br>Anyone else have any issues, past or present, with this kind of thing?</blockquote><div><br><br>We tend to avoid the whole SMTP mess and deliver messages to mobiles and pagers via a modem and the provider's TAP gateway. It works quite well with Verizon and AT&T/Cingular, but I've no experience with T-Mobile. It also avoids the whole mess of failing to alert when your monitoring box has a bad NIC, cable, switchport, etc - of course considering that you trade those for problems with a serial port, cable, modem, or phone line... But it gives us a big (and perhaps false) warm fuzzy that our alerting is 'out of band' relative to our upstream Internet connections.
<br><br>The folks at Avtech have a nice index of TAP gateway numbers at <a href="http://www.avtech.com/Support/TAP/index.htm">http://www.avtech.com/Support/TAP/index.htm</a> <br></div><br>Hope you find this useful...<br><br>
--D<br></div><br><br>
------=_Part_87569_1491320.1189114029499--
