Send VoiceOps mailing list submissions to
[email protected]
To subscribe or unsubscribe via the World Wide Web, visit
https://puck.nether.net/mailman/listinfo/voiceops
or, via email, send a message with subject or body 'help' to
[email protected]
You can reach the person managing the list at
[email protected]
When replying, please edit your Subject line so it is more specific
than "Re: Contents of VoiceOps digest..."
Today's Topics:
1. Re: Odd "TOS violation" op intercept? (April Jones)
----------------------------------------------------------------------
Message: 1
Date: Sun, 26 May 2013 18:11:07 -0600
From: April Jones <[email protected]>
To: [email protected]
Subject: Re: [VoiceOps] Odd "TOS violation" op intercept?
Message-ID:
<CA+vTEYbjky91SyMjD2L0p=rlp-x5yfyzxqmi5dp8jd3cyth...@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"
No, none of my vendors shared the information nor did I find a common
thread on my own. The reports subsided mid-week as everyone slowly routed
away. The suspects were Google Voice, MagicJack (Ymax), and apparently
CenturyLink though that last one would really surprise me.
It's issues like these that can make or break my trust with vendors and
determine which routing groups, if any, they are placed in. I have some
customers who would pull traffic immediately upon receiving such an
intercept message, and I can't really fault them for doing so. At the same
time, the trouble seemed to be so widespread that the nonchalance some
customers and vendors exhibited in dealing with it was kind of refreshing.
It was treated as more of a "yup, telecom" moment than Verizon outages.
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<https://puck.nether.net/pipermail/voiceops/attachments/20130526/30cda423/attachment-0001.html>
------------------------------
Subject: Digest Footer
_______________________________________________
VoiceOps mailing list
[email protected]
https://puck.nether.net/mailman/listinfo/voiceops
------------------------------
End of VoiceOps Digest, Vol 47, Issue 18
****************************************
