[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Email to text - vtext.com blacklisting ip



This subject pops up every 6 months and it's a problem that can be solved
100 ways. One way we did it at Team Cymru was install a foxbox sms gateway
in our datacenter. It was a pain to get working, (mainly due to some
miscommunication with the Italian support team), but one we got past a few
problems it works flawlessly for all alerts. If alerts are unack'd for a
specific amount of time, escalation alerts go out via email-to-sms AND SMS
to a broader group to ensure someone gets the message.

Thanks,
Scott

On Wed, Aug 17, 2016 at 5:31 AM, Dovid Bender <dovid at telecurve.com> wrote:

> We use Zang.io and are very happy. Be careful when using long codes (10
> digit numbers) as if you send too many messages out in a day (500+) the
> larger carriers such as Verizon will start blocking you. As Jeff mentioned
> if your monitoring tool is onsite and the internet goes down then it's
> worthless. In our case it's in another DC so if everything goes down we
> still get alerts. You can also try twilio and telnyx.
>
>
> On Tue, Aug 16, 2016 at 7:33 PM, Sam Norris <Sam at sandiegobroadband.com>
> wrote:
>
> > Same boat...  We are sending messages to PHONENUMBER at vtext.com and
> getting
> > bouncebacks or lost items.  I assume its because some limits are now
> being
> > put
> > into place.  We are a Verizon subscriber so I am paying, it is not a free
> > service.  But .... I am totally up for paid services if you can recommend
> > some
> > that will reliably get us texts to our verizon phones.
> >
> > Sam
> >
> >
> > > -----Original Message-----
> > > From: NANOG [mailto:nanog-bounces at nanog.org] On Behalf Of Ryan,
> Spencer
> > > Sent: Tuesday, August 16, 2016 4:17 PM
> > > To: Josh Luthman; Mike
> > > Cc: NANOG list
> > > Subject: RE: Email to text - vtext.com blacklisting ip
> > >
> > > I agree. Pay Pager duty or a SMS gateway with a SLA. Relying on  the
> free
> > service
> > > for anything critical is asking for trouble.
> > >
> > >
> > >
> > > Sent from my Verizon, Samsung Galaxy smartphone
> > >
> > >
> > > -------- Original message --------
> > > From: Josh Luthman <josh at imaginenetworksllc.com>
> > > Date: 8/16/16 6:09 PM (GMT-05:00)
> > > To: Mike <mike-nanog at tiedyenetworks.com>
> > > Cc: NANOG list <nanog at nanog.org>
> > > Subject: Re: Email to text - vtext.com blacklisting ip
> > >
> > > If it's critical I'd suggest a service than can depended on...
> > >
> > > Josh Luthman
> > > Office: 937-552-2340
> > > Direct: 937-552-2343
> > > 1100 Wayne St
> > > Suite 1337
> > > Troy, OH 45373
> > >
> > > On Aug 16, 2016 5:45 PM, "Mike" <mike-nanog at tiedyenetworks.com> wrote:
> > >
> > > > Hi,
> > > >
> > > >
> > > >     I have a server that monitors my network and issues text messages
> > if
> > > > there are events of note that require human intervention. There is
> some
> > > > process filtering that ensures it also is not able to issue more
> than 1
> > > > alert maximum per 5 minutes, to ensure it doesn't flood pagers with
> > > > messages all screaming the sky is falling when things are not going
> > well.
> > > > Recently however, this server is no longer able to deliver messages
> to
> > > > vtext.com - it gets nothing but 554 errors:
> > > >
> > > >
> > > > telnet 69.78.67.53 25
> > > > Trying 69.78.67.53...
> > > > Connected to 69.78.67.53.
> > > > Escape character is '^]'.
> > > > 554 txslspamp10.vtext.com
> > > > Connection closed by foreign host.
> > > >
> > > > Granted on some days during challenging times it can send 30 or 40
> > > > messages before we get to it and get it squelched / silenced, but
> it's
> > > > otherwise reasonably well behaved IMHO and I don't think we are any
> > heavy
> > > > volume sender. So I am trying to figure out why it's blacklisted then
> > and
> > > > am rolling snake eyes.  If anyone who is an admin for verizon or who
> > has
> > > > any insight to share I'd certainly appreciate it. Email to text is a
> > > > critical function we depend on.
> > > >
> > > >
> > > > Thank you.
> > > >
> > > >
> > > >
> >
> >
>



-- 
Scott