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. 360 outage? (Oren Yehezkely)
2. Re: 360 outage? (Shripal Daphtary)
3. Rejected port due to having other orders active on the
account (Carlos Alvarez)
4. Re: Sandy Watch (Hiers, David (DS))
5. Re: Rejected port due to having other orders active on the
account (michael sterl)
6. Re: Sandy Watch (Shripal Daphtary)
----------------------------------------------------------------------
Message: 1
Date: Wed, 31 Oct 2012 14:15:21 -0400
From: Oren Yehezkely <[email protected]>
To: "[email protected]" <[email protected]>
Subject: [VoiceOps] 360 outage?
Message-ID:
<cal+wrh+a70+g2rq0nwtqzdnw90vgrhz38kyx5ph3svz4nm8...@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Hello,
One of our ULC PeeringPartners (now Unipoint / PointOne) has some DIDs
with 360 networks.
In the last days those DIDs give a message that the number is 'unallocated'.
Does anybody have some information about a problem with one of those companies?
Thanks,
Oren
------------------------------
Message: 2
Date: Wed, 31 Oct 2012 14:25:46 -0400
From: Shripal Daphtary <[email protected]>
To: Oren Yehezkely <[email protected]>
Cc: "[email protected]" <[email protected]>
Subject: Re: [VoiceOps] 360 outage?
Message-ID: <[email protected]>
Content-Type: text/plain; charset="us-ascii"
We got this email, but this was supposed to be done tomorrow. 360 networks is
Texas right?
Please note, PointOne will be performing network maintenance on Thursday,
November 1, 2012, starting at 12:01 a.m. Central time. Beginning just after
midnight, the maintenance window is scheduled for three hours, ending at 3:01
a.m. Central time. During this maintenance window, DIDs in Texas LATAs 558,
564 and 568 will be intermittently without service. You are receiving this
notification because you have purchased numbers from PointOne in one or more of
these LATAs. The impact to service is not expected to be lengthy; instead,
during this three hour window, you can expect brief intervals where DIDs may
encounter intermittent unavailability. Our main NOCC contact number will also
be impacted by this maintenance. As a result, should you need to reach us
during the three hour maintenance window, you may instead contact our technical
support staff at 512-343-0630. We apologize for the inconvenience and will
work quickly to complete our maintenance activities in order to !
minimize impact to service. Please contact our Customer Care team
[email protected] or 512-628-0097 if you have any questions or need
additional details.
Sent from my mobile device.
On Oct 31, 2012, at 2:15 PM, Oren Yehezkely <[email protected]> wrote:
> Hello,
>
> One of our ULC PeeringPartners (now Unipoint / PointOne) has some DIDs
> with 360 networks.
>
> In the last days those DIDs give a message that the number is 'unallocated'.
>
> Does anybody have some information about a problem with one of those
> companies?
>
> Thanks,
>
> Oren
> _______________________________________________
> VoiceOps mailing list
> [email protected]
> https://puck.nether.net/mailman/listinfo/voiceops
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<https://puck.nether.net/pipermail/voiceops/attachments/20121031/14f0aa92/attachment-0001.html>
------------------------------
Message: 3
Date: Wed, 31 Oct 2012 17:03:25 -0700
From: Carlos Alvarez <[email protected]>
To: [email protected]
Subject: [VoiceOps] Rejected port due to having other orders active on
the account
Message-ID:
<CAFn1dUG4hLjAKx7QHdWQZmkRqVJxu_PAkEff850eegGwwPJ=v...@mail.gmail.com>
Content-Type: text/plain; charset="iso-8859-1"
This doesn't seem like a valid/legal reason to reject a port. Integra has
always done this with both our own account with them and any other accounts
we're porting from. If there is ANY open order on the account, they will
reject a port. This could be simply ordering some DIDs or doing another
port. In the current case, as has happened in the past, it's going to end
up costing an extra month on a PRI. Is this valid? Anyone have experience
getting them to see the error of their ways?
--
Carlos Alvarez
TelEvolve
602-889-3003
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<https://puck.nether.net/pipermail/voiceops/attachments/20121031/da297602/attachment-0001.html>
------------------------------
Message: 4
Date: Wed, 31 Oct 2012 19:34:38 -0500
From: "Hiers, David (DS)" <[email protected]>
To: Jared Geiger <[email protected]>, "[email protected]"
<[email protected]>
Subject: Re: [VoiceOps] Sandy Watch
Message-ID:
<81cdfc77fb2dc54db875d4f8ffc36ce01437822...@dsmail2he.ds.ad.adp.com>
Content-Type: text/plain; charset="us-ascii"
How are things going out there? We're seeing pretty broad failures in both
termination and origination with Verizon. If we route calls out Level3, we can
at least call out.
Thanks,
David
________________________________________
From: [email protected] [[email protected]] On Behalf
Of Jared Geiger [[email protected]]
Sent: Tuesday, October 30, 2012 2:35 PM
To: [email protected]
Subject: Re: [VoiceOps] Sandy Watch
Looks like TATA NYC1 and 2 came back up. Telia went down. Belgacom is
back up but taking the Washington -> Paris route instead of the NYC ->
London route.
Novatel in NYC went completely down. IPs aren't even being advertised in BGP.
On Tue, Oct 30, 2012 at 11:51 AM, Jared Geiger <[email protected]> wrote:
> We're connected to 2 others. The one in NJ seems up and we're
> connected to London as well. Looks like the path across the Atlantic
> is fine.
>
> On Tue, Oct 30, 2012 at 9:41 AM, Colin Brown <[email protected]> wrote:
>> If your connected with Tata hopefully your connected to at least one of the
>> 13 other gsxes they have.
>>
>> On Oct 30, 2012, at 9:34 AM, Jared Geiger <[email protected]> wrote:
>>
>>> 1) Looks like TATA NYC1 and NYC2 GSXes are down.
>>> 2) I got an email saying Telia only had 6 hours of power left at 6 AM
>>> Eastern, so they may go dark as well at noon.
>>> 3) Our IP routes to Belgacom are broken and die in NYC on nlayer,
>>> Cogent, and Abovenet.
>>> 4) Looks like Hypercube in NYC is down.
>>> 5) Reliance is going down in NYC
>>>
>>> It seems all of our other trunks are up.
>>>
>>> On Tue, Oct 30, 2012 at 2:37 AM, Hiers, David (DS) <[email protected]>
>>> wrote:
>>>> Nothing too surprising so far...
>>>>
>>>> There seems to be pretty strong correlation between flooded areas with no
>>>> electricity and unregistered devices. I probably don't need to drop a 650
>>>> into a fish tank to see if the issue is reproducible, but it is oddly
>>>> tempting.
>>>>
>>>>
>>>> David
>>>>
>>>>
>>>>
>>>> ________________________________________
>>>> From: [email protected] [[email protected]] On
>>>> Behalf Of Hiers, David (DS)
>>>> Sent: Monday, October 29, 2012 11:58 AM
>>>> To: [email protected]
>>>> Subject: [VoiceOps] Sandy Watch
>>>>
>>>> Hi,
>>>>
>>>> Is anyone seeing any storm related issues yet? I've got the expected drop
>>>> in calls as the NE shuts down, not much more on the radar.
>>>>
>>>> I'll be watching/updating this list (and outages) tonight for any
>>>> significant events.
>>>>
>>>> Thanks,
>>>>
>>>> David
>>>>
>>>> PS: Having your machines prepped for disaster is good, but what about
>>>> your people? All that expensive gear might not be not worth much if
>>>> you've got no one to operate it when the big one hits. After all, even
>>>> first responders don't respond if doing so would imperil their families...
>>>> are your people wired in to ready.gov?
>>>>
>>>>
>>>>
>>>> ________________________________
>>>>
>>>> ________________________________
>>>> This message and any attachments are intended only for the use of the
>>>> addressee and may contain information that is privileged and confidential.
>>>> If the reader of the message is not the intended recipient or an
>>>> authorized representative of the intended recipient, you are hereby
>>>> notified that any dissemination of this communication is strictly
>>>> prohibited. If you have received this communication in error, please
>>>> notify us immediately by e-mail and delete the message and any attachments
>>>> from your system.
>>>>
>>>>
>>>>
>>>> This message and any attachments are intended only for the use of the
>>>> addressee and may contain information that is privileged and confidential.
>>>> If the reader of the message is not the intended recipient or an
>>>> authorized representative of the intended recipient, you are hereby
>>>> notified that any dissemination of this communication is strictly
>>>> prohibited. If you have received this communication in error, please
>>>> notify us immediately by e-mail and delete the message and any attachments
>>>> from your system.
>>>>
>>>> _______________________________________________
>>>> VoiceOps mailing list
>>>> [email protected]
>>>> https://puck.nether.net/mailman/listinfo/voiceops
>>>
>>> _______________________________________________
>>> VoiceOps mailing list
>>> [email protected]
>>> https://puck.nether.net/mailman/listinfo/voiceops
>>
>> _______________________________________________
>> VoiceOps mailing list
>> [email protected]
>> https://puck.nether.net/mailman/listinfo/voiceops
_______________________________________________
VoiceOps mailing list
[email protected]
https://puck.nether.net/mailman/listinfo/voiceops
This message and any attachments are intended only for the use of the addressee
and may contain information that is privileged and confidential. If the reader
of the message is not the intended recipient or an authorized representative of
the intended recipient, you are hereby notified that any dissemination of this
communication is strictly prohibited. If you have received this communication
in error, please notify us immediately by e-mail and delete the message and any
attachments from your system.
------------------------------
Message: 5
Date: Wed, 31 Oct 2012 18:41:22 -0600
From: michael sterl <[email protected]>
To: Carlos Alvarez <[email protected]>
Cc: "[email protected]" <[email protected]>
Subject: Re: [VoiceOps] Rejected port due to having other orders
active on the account
Message-ID: <[email protected]>
Content-Type: text/plain; charset=us-ascii
This has always rejected ports from most carriers we have worked with. The
reason I believe is you can't have active orders on the same account (meaning
they can't manage multiple orders at one time ;) . Series approach.
michael sterl
(sent from the local ski lift)
On Oct 31, 2012, at 6:03 PM, Carlos Alvarez <[email protected]> wrote:
> This doesn't seem like a valid/legal reason to reject a port. Integra has
> always done this with both our own account with them and any other accounts
> we're porting from. If there is ANY open order on the account, they will
> reject a port. This could be simply ordering some DIDs or doing another
> port. In the current case, as has happened in the past, it's going to end up
> costing an extra month on a PRI. Is this valid? Anyone have experience
> getting them to see the error of their ways?
>
> --
> Carlos Alvarez
> TelEvolve
> 602-889-3003
>
>
> _______________________________________________
> VoiceOps mailing list
> [email protected]
> https://puck.nether.net/mailman/listinfo/voiceops
------------------------------
Message: 6
Date: Wed, 31 Oct 2012 20:43:37 -0400
From: Shripal Daphtary <[email protected]>
To: "Hiers, David (DS)" <[email protected]>
Cc: "[email protected]" <[email protected]>
Subject: Re: [VoiceOps] Sandy Watch
Message-ID: <[email protected]>
Content-Type: text/plain; charset="us-ascii"
Major issues out of 75 broad with Windstream paetec. We have had no did's
inbound from the for 24 hours. They are completely dark in that location. Mind
you they are not just ny did's. they're nationwide did's
First of two updates from Windstream all day
NY2 has been OOS since approx 8:30 last night. As a result of the storm surge
Monday night, basement of the building that NY2 & NY3 are in, flooded. Late
yesterday afternoon, the pump that moves diesel fuel from the basement to where
our generators are located on the 18th floor, failed. Shortly thereafter, our
generators ran out of fuel and shut down. Batteries to NY2 lasted 2+ hours
while we unsuccessfully brainstormed alternative solutions to getting fuel to
the 18th floor. Keep in mind, there is no power in this building and most if
not all of the emergency lighting is no out, so flashlights are primary
lighting. NY2 is also where majority of connectivity feeds through, to include
some connectivity to Newark, so when the batteries ran down, we lost not only
NY2, but effectively lost NY3 and some connectivity to Newark.
NY2 5E switch 16th floor
NY3 Soft switch 4th floor
Generators. 18th floor
Basement. Fuel tanks
We are currently working on 2 solutions in parallel:
1. Procuring a fuel lift pump and 200' of high pressure hose to pump our own
fuel from ground level to 18th floor generators. Prime and restart generators,
charge batteries for 30 min and begin rebooting equipment.
2. Contracted with local vendor to do something similar for us
Since they are both sub-optimal solutions, we are working both simultaneously
to improve of chances of success. Best case is early afternoon restoration.
Building management, who is responsible for providing fuel to us continues to
pump out the flooded basement in order to expose pumps, assess situation with
intent of permanent repair/replacement of the main pump
Sent from my mobile device.
On Oct 31, 2012, at 8:34 PM, "Hiers, David (DS)" <[email protected]> wrote:
> How are things going out there? We're seeing pretty broad failures in both
> termination and origination with Verizon. If we route calls out Level3, we
> can at least call out.
>
> Thanks,
>
> David
>
> ________________________________________
> From: [email protected] [[email protected]] On Behalf
> Of Jared Geiger [[email protected]]
> Sent: Tuesday, October 30, 2012 2:35 PM
> To: [email protected]
> Subject: Re: [VoiceOps] Sandy Watch
>
> Looks like TATA NYC1 and 2 came back up. Telia went down. Belgacom is
> back up but taking the Washington -> Paris route instead of the NYC ->
> London route.
>
> Novatel in NYC went completely down. IPs aren't even being advertised in BGP.
>
> On Tue, Oct 30, 2012 at 11:51 AM, Jared Geiger <[email protected]> wrote:
>> We're connected to 2 others. The one in NJ seems up and we're
>> connected to London as well. Looks like the path across the Atlantic
>> is fine.
>>
>> On Tue, Oct 30, 2012 at 9:41 AM, Colin Brown <[email protected]> wrote:
>>> If your connected with Tata hopefully your connected to at least one of the
>>> 13 other gsxes they have.
>>>
>>> On Oct 30, 2012, at 9:34 AM, Jared Geiger <[email protected]> wrote:
>>>
>>>> 1) Looks like TATA NYC1 and NYC2 GSXes are down.
>>>> 2) I got an email saying Telia only had 6 hours of power left at 6 AM
>>>> Eastern, so they may go dark as well at noon.
>>>> 3) Our IP routes to Belgacom are broken and die in NYC on nlayer,
>>>> Cogent, and Abovenet.
>>>> 4) Looks like Hypercube in NYC is down.
>>>> 5) Reliance is going down in NYC
>>>>
>>>> It seems all of our other trunks are up.
>>>>
>>>> On Tue, Oct 30, 2012 at 2:37 AM, Hiers, David (DS) <[email protected]>
>>>> wrote:
>>>>> Nothing too surprising so far...
>>>>>
>>>>> There seems to be pretty strong correlation between flooded areas with no
>>>>> electricity and unregistered devices. I probably don't need to drop a
>>>>> 650 into a fish tank to see if the issue is reproducible, but it is oddly
>>>>> tempting.
>>>>>
>>>>>
>>>>> David
>>>>>
>>>>>
>>>>>
>>>>> ________________________________________
>>>>> From: [email protected] [[email protected]] On
>>>>> Behalf Of Hiers, David (DS)
>>>>> Sent: Monday, October 29, 2012 11:58 AM
>>>>> To: [email protected]
>>>>> Subject: [VoiceOps] Sandy Watch
>>>>>
>>>>> Hi,
>>>>>
>>>>> Is anyone seeing any storm related issues yet? I've got the expected
>>>>> drop in calls as the NE shuts down, not much more on the radar.
>>>>>
>>>>> I'll be watching/updating this list (and outages) tonight for any
>>>>> significant events.
>>>>>
>>>>> Thanks,
>>>>>
>>>>> David
>>>>>
>>>>> PS: Having your machines prepped for disaster is good, but what about
>>>>> your people? All that expensive gear might not be not worth much if
>>>>> you've got no one to operate it when the big one hits. After all, even
>>>>> first responders don't respond if doing so would imperil their
>>>>> families... are your people wired in to ready.gov?
>>>>>
>>>>>
>>>>>
>>>>> ________________________________
>>>>>
>>>>> ________________________________
>>>>> This message and any attachments are intended only for the use of the
>>>>> addressee and may contain information that is privileged and
>>>>> confidential. If the reader of the message is not the intended recipient
>>>>> or an authorized representative of the intended recipient, you are hereby
>>>>> notified that any dissemination of this communication is strictly
>>>>> prohibited. If you have received this communication in error, please
>>>>> notify us immediately by e-mail and delete the message and any
>>>>> attachments from your system.
>>>>>
>>>>>
>>>>>
>>>>> This message and any attachments are intended only for the use of the
>>>>> addressee and may contain information that is privileged and
>>>>> confidential. If the reader of the message is not the intended recipient
>>>>> or an authorized representative of the intended recipient, you are hereby
>>>>> notified that any dissemination of this communication is strictly
>>>>> prohibited. If you have received this communication in error, please
>>>>> notify us immediately by e-mail and delete the message and any
>>>>> attachments from your system.
>>>>>
>>>>> _______________________________________________
>>>>> VoiceOps mailing list
>>>>> [email protected]
>>>>> https://puck.nether.net/mailman/listinfo/voiceops
>>>>
>>>> _______________________________________________
>>>> VoiceOps mailing list
>>>> [email protected]
>>>> https://puck.nether.net/mailman/listinfo/voiceops
>>>
>>> _______________________________________________
>>> VoiceOps mailing list
>>> [email protected]
>>> https://puck.nether.net/mailman/listinfo/voiceops
>
> _______________________________________________
> VoiceOps mailing list
> [email protected]
> https://puck.nether.net/mailman/listinfo/voiceops
>
>
> This message and any attachments are intended only for the use of the
> addressee and may contain information that is privileged and confidential. If
> the reader of the message is not the intended recipient or an authorized
> representative of the intended recipient, you are hereby notified that any
> dissemination of this communication is strictly prohibited. If you have
> received this communication in error, please notify us immediately by e-mail
> and delete the message and any attachments from your system.
>
> _______________________________________________
> VoiceOps mailing list
> [email protected]
> https://puck.nether.net/mailman/listinfo/voiceops
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<https://puck.nether.net/pipermail/voiceops/attachments/20121031/4657783e/attachment.html>
------------------------------
_______________________________________________
VoiceOps mailing list
[email protected]
https://puck.nether.net/mailman/listinfo/voiceops
End of VoiceOps Digest, Vol 40, Issue 32
****************************************
