Both my boxes just went down...no registration..
Printable View
Both my boxes just went down...no registration..
I'm not at home to confirm, but vPanel says no devices registered.
OK now....after a power reboot..
Yep. The daily VOIPo problem. Only 2 lights on the adapter...rebooted, again...seems registered. Who knows how long for.
Tried calling an 866 number this morning and it would not go through on VOIPo.
OK, I give up. Bailing as soon as I can get another provider and port out. Sorry, no more "tickets".
My PAP2 just went down 2 minutes ago..
Yup. I'm down as well. Just power-cycled, and seem to have re-registered.
My papt just lost registration.
I had to reboot for the 1st time. :eek:
Hey guys -- looks like there was a load issue on sip.voipwelcome.com, looks like a possible loop like scenario, if your device lost connection, it should automatically reconnect within 5 minutes. We have corrected this and rebalanced the load, thanks and sorry for any inconvenience!
________
Creampie Porn
Just a sidenote...this loop is a prime and timely example of why we're ending BYOD support.
BYOD users can easily cause a lot of issues like this and do so on a regular basis when they misconfigure things like Asterisk no matter how many safeguards you put in place. Today is was an SPA3000.
If we wouldn't have allowed BYOD, this would not have happened.
My wife was just trying to call my sister back and was about to throw the phone through the TV. 4 dials out, nothing. I was wondering why my parents called my cell phone earlier.
I am on east01 and I don't believe my ATA went down.
Never noticed anything (looks fine here at this moment!)
EDIT:
If you want BYOD, (and its not cost prohibitive)
perhaps they could be on their own server? (sandbox)
Or perhaps they could graduate from a sandbox?
Just dreaming up options ... you don't really need to be all things to everyone!
I'm totally down right now - and vPanel will not load.
And I'm on EAST01
This is my EXACT problem. First noticed it today but it dates back to yesterday upon further review.
PAP2T shows as registered - does not lose registration according to VPanel.
But the 2 phone lights go out and there is no dial tone or incoming.
Then everything works, then it doesn't, over and over - without losing registration.
Reboot changes nothing.
Ticket submitted but PAP2T is registered so.....
WAF (Wife Aggravation Factor) very high.
I just had a quick outage around 7:30 PM Eastern. Couldn't get to voice mail with 123 or *123, then no dial tone then couldn't get to vpanel . Now, all seems to be ok.
We have seen several cases of massive floods of traffic causing latency a few times tonight. The Planet is working to control it with firewalls.
traceroute to 174.132.131.132 (174.132.131.132), 30 hops max, 40 byte packets
1 41.38.344a.static.theplanet.com (74.52.56.65) 916.325 ms 916.529 ms 916.741 ms
2 91.fe.5746.static.theplanet.com (70.87.254.145) 0.474 ms 0.460 ms 0.659 ms
3 e2.fe.5746.static.theplanet.com (70.87.254.226) 0.895 ms 0.896 ms 0.885 ms
We are seeing another huge flood of traffic in which is causing major network latency. This is similar to last night.
traceroute to 174.132.131.132 (174.132.131.132), 30 hops max, 40 byte packets
1 41.38.344a.static.theplanet.com (74.52.56.65) 916.325 ms 916.529 ms 916.741 ms
2 91.fe.5746.static.theplanet.com (70.87.254.145) 0.474 ms 0.460 ms 0.659 ms
3 e2.fe.5746.static.theplanet.com (70.87.254.226) 0.895 ms 0.896 ms 0.885 ms
They're working to firewall it now.
I'm in Southern California.
Both lines lost registration at around 4:30pm PDT with a status of "Can't connect to login server" on the PAP2T status page. I could not get to vPanel.
THe PAP2T was able to re-register on it's own within 5 to 10 minutes. And I could then get into vPanel.
Tim,
I'm not up on the technical stuff. Why does that cause the two phone lights on my PAP2T to keep going out?
It looks like someone does not want our service to stay up and just keeps sending these floods of traffic (almost to the point of being a DOS attack).
We're evaluating putting in some more powerful hardware firewalls tonight.
If you think you are being attacked, check out:
http://www.stopddos.org/
These guys are sharp and in most cases can identify the source of an active attack within minutes.
FWIW, I did not notice any outage, the Zoom indicates that it's happy with all appropriate lights lit and I still have service; no reboot was required, so I would guess no outage occurred here. It's still set to register to the default sip.voipwelcome.com, where ever that puts me at a given moment.
Please do not shoot all the BYOD users. If you believe there is a problem my equipment, simply turn me off and send me note to fix it! I listen well to criticism before counter-attacking! ;-)
My lights on the PAP2 never went off, but the service was going to dead air, the CP showed the device connected.
Maybe a denial of service, how about all of the obviously fake profiles that were being generated and finally had to be brought to Voipo's attention?
I noticed no devices registered around 4:20 pm and my pap2t showed can't logon to server. However, I left it alone and pap2t re-registered within a few minutes. Everything works fine. Didn't miss a call.
I believe I am on sip. I am a light footprint. :) I check and double check and then check here and BBR if something is not right. I always figure it will correct itself if left alone.
Forum users wouldn't have anything to do with the other portions of the service. They're not even in the same datacenters.
The attacks do seem to be under control, but we're working on making some changes tonight to beef up our protection since they do seem to come back.
Even more interesting in where we think they originate, but this isn't really the place to go into that.
I know that, but all of a sudden there are an influx here and now you are being targeted. Either a huge coincidence....
They can't really be that stupid if that is what you are inferring....
Not being as technical as some, I have heard of a BYOD loop before but don't really know too much about it.
Sounds like a denial of service attack to me.
Someone with nothing better to do is sitting in a irc chat room with 1000's of bots typing commands like !pingfast (insert one of voipo's many ips here)
I have been in several bot net channels. Used to run a large irc network. Had more than one guys bot net put out of commission permanently. You really should not be able to tell where its originating because they would just be infected pc's. Unless they are morons using dos software on their own pc's (most are smarter than that).
Wish they would really crack down on that stuff. The FBI seems to only focus on the people who profit from it. Good luck fighting them off.
I don't know if this mess is still going on or not.
But I can't stay registered at all.
If I reboot my router, then re-apply power to the PAP2, both lines register.
On the first re-registration (260 secs?) both fail - lights out - vPanel empty.
I'm going to submit a ticket - but I can't reboot or do anything until tomorrow night - because I don't have time to mess with it in the AM.
Edit: Ticket opened - HEK-343939: Complete Registration failure
Would this DDOS attack in theory affect people that are not having their audio relayed though the Voipo servers? I would think in theory it shouldn't.