I have recently been aware of some carrier Non-Disclosure Agreements under which the outage, and any information related to its cause and/or resolution, would be covered. In other words, speaking publicly about the situation could be considered to be breach of contract. The content of these Non-Disclosure Agreements themselves may be covered under said NDAs. As a result, some of us who might otherwise talk about a given outage, in a forum such as this, or to a reporter, might avoid doing so. Because it can be hard to keep track of NDA provisions, one would not be blamed for creating a corporate disclosure policy that held carrier information to the standard in the "highest" NDA, so as to avoid employees having to track individual NDAs. Annoying? Yes. Commercially reasonable? Also yes. -jbn On Fri, Apr 19, 2013 at 1:10 PM, PE <peeip989 at gmail.com> wrote:
How can it be that there was such a far reaching outage (in our rep's words, "catastrophic") yet I cannot find any news whatsoever about it and there was very, very little on the likes of Twitter. Anyone know of any news outlets that said anything?
On Thu, Apr 18, 2013 at 5:40 PM, David Thompson <dthompson at esi-estech.com>wrote:
Yes I can definitely confirm that this morning Verizon was having problems completing SIP calls.
David Thompson Network Services Support Technician (O) 858.357.8794 (F) 858-225-1882 (E) dthompson at esi-estech.com (W) www.esi-estech.com
*From:* VoiceOps [mailto:voiceops-bounces at voiceops.org] *On Behalf Of *Jared Geiger *Sent:* Thursday, April 18, 2013 10:52 AM *To:* VoiceOps *Subject:* [VoiceOps] Verizon SIP issues
Did anyone else have problems with inbound Verizon SIP numbers for about the past 30 minutes? Outbound calls were working fine.
~Jared
_______________________________________________ VoiceOps mailing list VoiceOps at voiceops.org https://puck.nether.net/mailman/listinfo/voiceops
_______________________________________________ VoiceOps mailing list VoiceOps at voiceops.org https://puck.nether.net/mailman/listinfo/voiceops