* matthew zeier <[EMAIL PROTECTED]> [2007-09-06 23:39]:
> >It's more effective to spend the money on SMS messages. Mobile
> >providers are forced to use very aggressive anti spam measures, which
> >can add significant delays in message delivery.
> Recommendations on software and modems?
the UMTS
On 9/7/07, Alex Pilosov <[EMAIL PROTECTED]> wrote:
>
>
> * Purpose-made GSM/CDMA modems
> ** Software: same as above
> ** Manufacturers: Intercel, Sierra 750 (PCMCIA), Falcom Samba 75 (USB)
>
>
Does anyone have experience and/or opinion (positive or negative) with the
Multi-Tech cellular modems?
h
On Fri, 2007-09-07 at 19:54 -0400, Alex Pilosov wrote:
> As an experiment, I wanted to try to summarize all the answers given on
> this question, hope this helps someone.
>
> Suggestions given:
>
> * modem and TAP gateway
> ** TAP numbers at http://www.avtech.com/Support/TAP/index.htm
> ** So
As an experiment, I wanted to try to summarize all the answers given on
this question, hope this helps someone.
Suggestions given:
* modem and TAP gateway
** TAP numbers at http://www.avtech.com/Support/TAP/index.htm
** Software: sendpage or qpage
* Mobile phone with a serial port and AT com
On 9/6/07, Rick Kunkel <[EMAIL PROTECTED]> wrote:
> Hello folks,
>
> It seems especially prevalent when MANY things are sent at once; if, for
> example, a central piece fails, and dependent pieces suddenly fail as
> well.
I'd probably recommend implementing some sort of parent/child system
to red
Am 06.09.2007 um 23:22 schrieb matthew zeier:
Ken Simpson wrote:
It's more effective to spend the money on SMS messages. Mobile
providers are forced to use very aggressive anti spam measures, which
can add significant delays in message delivery.
Recommendations on software and modems?
gsmd
> Is SMTP to a mobile phone a fundamentally flawed way to do this?
Yes. It takes too long and nobody is responsible for making sure it is
fast.
SMS is better, even though it can also suffer from delays, because
somebody is in charge of making sure it is fast. The worst delays I
witnessed were o
> Ken Simpson wrote:
>
> > It's more effective to spend the money on SMS messages. Mobile
> > providers are forced to use very aggressive anti spam
> measures, which
> > can add significant delays in message delivery.
>
> Recommendations on software and modems?
We've been having fun with these
I would never trust SMTP for all the reasons already mentioned. Primarily
if my network is dead, I still want to get paged about it. Relying on the
import policy of another organization in the hostile port 25 environment is
also bad voodoo.
We've used a mix of TAP and SMS for many years with var
I used a wide range of alerting methods. The most reliable that I have
found (at least for Cingular/AT&T phones) has been TAP. Since this way the
monitoring server can have its own dedicated modem / phone line (separate
from the PBX). Thereby you no longer have to use any of the monitored
equipm
On Thu, Sep 06, 2007 at 06:04:44PM -0600, Jason J. W. Williams wrote:
> Hi All,
>
> Our experience with using the e-mail-to-SMS gateways provided by
> AT&T/Cingular and T-Mobile:
>
> AT&T: Messages come through with very little delay (even during alert
> storms).
As long as you're sourc
:> Some mobile phones you can talk to via AT commandset, either
:>via USB cable or something else. (eg: I have used a Nokia 6230 with usb
:>cable.. you can also use bluetooth). If you pay $5 or whatnot for unlimited
:>SMS on a el-cheapo plan, it might work better than using the SMTP gate
our.
-J
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of
Daniel Senie
Sent: Thursday, September 06, 2007 4:09 PM
To: Jared Mauch; matthew zeier
Cc: Rick Kunkel; nanog@merit.edu
Subject: Re: Using Mobile Phone email addys for monitoring
At 05:29 PM 9/6/2007, Jar
On Thu, Sep 06, 2007 at 05:51:38PM -0400, Alex Pilosov wrote:
[...]
> Analog modem and voice line and TAP software (like sendpage or qpage)
I like the TAP route with qpage.
I was starting to get spam via my provider's e-mail to SMS gateway. They were
kind enough to disable it, and we use TAP t
> Once upon a time, Duane Waddle <[EMAIL PROTECTED]> said:
> > 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.
>
> T-Mobil
> > It's more effective to spend the money on SMS messages. Mobile
> > providers are forced to use very aggressive anti spam measures, which
> > can add significant delays in message delivery.
>
> Recommendations on software and modems?
Easy enough to build, here's one I made earlier
http://www
On Sep 6, 2007, at 5:39 PM, Seth Mattinen wrote:
matthew zeier wrote:
> Anyone else have any issues, past or present, with this kind of
thing?
It takes ~ 7 minutes from the time Nagios sends an email sms to
AT&T to the time it hits my phone. I'm using
@mobile.mycingular.com because mmo
On Thu, 2007-09-06 at 14:12 -0700, matthew zeier wrote:
>
>
> > Anyone else have any issues, past or present, with this kind of thing?
>
>
> It takes ~ 7 minutes from the time Nagios sends an email sms to AT&T to
> the time it hits my phone. I'm using @mobile.mycingular.com because
> mmod
On Thu, Sep 06, 2007 at 01:46:18PM -0700, Rick Kunkel wrote:
[snip]
> Is SMTP to a mobile phone a fundamentally flawed way to do this?
Yes - think of the dependency chain involved. Years ago, hacking
hylafax (or similar DTMF sources) to dial directly to pagers was
a commonplace solution.
Cheer
GSM/GPRS modems are cheap; so are SMS messages. The answer should be
clear...
On 9/6/07, Matthew Palmer <[EMAIL PROTECTED]> wrote:
>
> The only
> thing I spec for SMS notifications is a GSM modem physically connected to
> the monitoring box. There's still points of failure, but they're a lot
> f
At 05:29 PM 9/6/2007, Jared Mauch wrote:
On Thu, Sep 06, 2007 at 02:12:34PM -0700, matthew zeier wrote:
>
>
>
> > Anyone else have any issues, past or present, with this kind of thing?
>
>
> It takes ~ 7 minutes from the time Nagios sends an email sms to
AT&T to the
> time it hits my phon
On 9/6/07, Todd Underwood <[EMAIL PROTECTED]> wrote:
> as much as i hate to say it, verizon has been extremely reliable on
> the smtp<->sms gateway. been using them for paging for 3 years or so
> now and never had a significant (detected) failure or latency.
>
> if you don't like this way of doi
> > Anyone else have any issues, past or present, with this kind of thing?
>
> It takes ~ 7 minutes from the time Nagios sends an email sms to AT&T to
> the time it hits my phone. I'm using @mobile.mycingular.com because
> mmode.com stopped working (which results in at least two txt pages vs
On Thu, Sep 06, 2007 at 02:22:10PM -0700, matthew zeier wrote:
> Ken Simpson wrote:
> >It's more effective to spend the money on SMS messages. Mobile
> >providers are forced to use very aggressive anti spam measures, which
> >can add significant delays in message delivery.
>
> Recommendations on
Once upon a time, Duane Waddle <[EMAIL PROTECTED]> said:
> 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.
T-Mobile dropped th
On Thu, 6 Sep 2007, matthew zeier wrote:
> Recommendations on software and modems?
Couple of options:
Dedicated cell phone connected via serial cable and gnokii-like software
Analog modem and voice line and TAP software (like sendpage or qpage)
Technically, SNPP is the appropriate solution, bu
On 9/6/07, Rick Kunkel <[EMAIL PROTECTED]> wrote:
> 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.
Rick,
I've had good results with vzw.blackberry.net (Verizon Wireless +
Blackberry)
matthew zeier wrote:
> Anyone else have any issues, past or present, with this kind of thing?
It takes ~ 7 minutes from the time Nagios sends an email sms to AT&T to
the time it hits my phone. I'm using @mobile.mycingular.com because
mmode.com stopped working (which results in at least
Is it flawed? It depends on your business requirements. If seconds,
milliseconds, or even microseconds matter to your mission critical apps
(think real-time trading networks) then you would want a 24x7 staffed
NOC using an enterpise monitoring system - something like Openview. You
wouldn't want
On Thu, Sep 06, 2007 at 01:46:18PM -0700, Rick Kunkel wrote:
> For instance, if an application fails to contact a certain service on a
> certain server, it sends an email (through it's own SMTP service, to avoid
> a chicken-and-egg prob if/when our main SMTP service fails) to
[...]
> Is SMTP to
matthew zeier wrote:
> Anyone else have any issues, past or present, with this kind of thing?
It takes ~ 7 minutes from the time Nagios sends an email sms to AT&T to
the time it hits my phone. I'm using @mobile.mycingular.com because
mmode.com stopped working (which results in at least
On Thu, Sep 06, 2007 at 02:12:34PM -0700, matthew zeier wrote:
>
>
>
> > Anyone else have any issues, past or present, with this kind of thing?
>
>
> It takes ~ 7 minutes from the time Nagios sends an email sms to AT&T to the
> time it hits my phone. I'm using @mobile.mycingular.com bec
On Thu, Sep 06, 2007 at 02:12:34PM -0700, matthew zeier wrote:
>
>
>
> > Anyone else have any issues, past or present, with this kind of
>thing?
as much as i hate to say it, verizon has been extremely reliable on
the smtp<->sms gateway. been using them for paging for 3 years or so
now and
On 9/6/07, Rick Kunkel <[EMAIL PROTECTED]> 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?
>
>
Ken Simpson wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
It takes ~ 7 minutes from the time Nagios sends an email sms to AT&T to
the time it hits my phone. I'm using @mobile.mycingular.com because
mmode.com stopped working (which results in at least two txt pages vs.
the one I was
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
> It takes ~ 7 minutes from the time Nagios sends an email sms to AT&T to
> the time it hits my phone. I'm using @mobile.mycingular.com because
> mmode.com stopped working (which results in at least two txt pages vs.
> the one I was used to).
>
>
On Sep 6, 2007, at 1:46 PM, Rick Kunkel wrote:
Is SMTP to a mobile phone a fundamentally flawed way to do this?
Yes, IMHO - too many things to fail, including potentially your own
DCN, the SMTP gateway service from the mobile operator, et. al.
I'd strongly recommend a direct NMS-to-SMS g
> Anyone else have any issues, past or present, with this kind of thing?
It takes ~ 7 minutes from the time Nagios sends an email sms to AT&T to
the time it hits my phone. I'm using @mobile.mycingular.com because
mmode.com stopped working (which results in at least two txt pages vs.
the
38 matches
Mail list logo