Printable View
We're currently seeing internal latency at one of our datacenters (The Planet) in Dallas which is causing some of our servers to have issues connecting to our core database servers.
The Planet is working to correct these network issues as quickly as possible.
These are located in a "high priority" zone of their newest facility so we expect network conditions to return to normal very shortly.
This looked like it had subsided earlier, but has returned.
Here is an example of what we're seeing internally:
1 81.83.84ae.static.theplanet.com (174.132.131.129) 12.887 ms 12.961 ms 13.026 ms
2 e1.fe.5746.static.theplanet.com (70.87.254.225) 0.378 ms 0.433 ms 0.494 ms
3 92.fe.5746.static.theplanet.com (70.87.254.146) 1544.017 ms 1544.252 ms 1544.461 ms
It's very intermittent and one trace will be all less than 1ms and then this. The Planet assures us they are working to clear this up as quickly as possible.
We don't know at this point, but it's potentially related to some type of network attack with effects flowing over into other customers.
Yeah…. A very clear-cut, distinct and detailed answer from Timothy, just as usual. What else to expect? And the problems go on… and on… and on…. and on…. (this is with regard to my PAP2T lost registration today http://forums.voipo.com/showpost.php...8&postcount=77 ). One issue it heroically fixed and another one starts. You know, Tim, people like the way you explain why they got a service interruption. So, please, keep talking.
Very nice stason99. Maybe VOIP isn't for you. It is the Internet you know.
So, if the PAP2 is completely unregistered, rebooting probably won't change that, correct?
Just leave it alone and it will register when it can connect ?
Well, it'll attempt to re-register every 5 minutes.Quote:
Originally Posted by dbmaven
If you reboot it before then it's possible it'll register right then vs waiting the entire window.
Well, it'll attempt to re-register every 5 minutes.Quote:
Originally Posted by dbmaven
If you reboot it before then it's possible it'll register right then vs waiting the entire window.
We're at about 98% of the registrations before this was detected and they're still increasing every minute so it seems to be clear now.
QFT . I am glad I am not the only one annoyed by this guys replies.Quote:
Originally Posted by scott2020
Well - it's certainly been trying - unsuccessfully - since
Last Registration At: 3/30/2009 21:29:26
Current Time: 3/30/2009 22:25:34
Go ahead and try a reboot then. It shouldn't be that long.Quote:
Originally Posted by dbmaven
pop back up yet?
Quote:
Originally Posted by dbmaven
Registration Retry Interval is 30 seconds. If it loses registration then it will try every 30 seconds. Unless the adapter does not know it lost registartion and thinks its online.
My line 1 is registered, but line 2 is not. Also, outbound calling issue - after about 30-45 seconds, it cuts the call off and goes to fast busy. Related?
Likely, yes.Quote:
Originally Posted by dmbmar
Go ahead and reboot if you're still seeing this and then update your ticket if it does not resolve it.
Is another side effect of this calls either say "Thank you" then hangup right after dialing or maximum call length 30 seconds?
It was not a matter of 5 minutes. It was at least 6 hours, people! Please, understand that.
Sorry if you felt my reply was rude. All I wanted was to get an explanation if it was ever possible to get a smooth service. I finally got a PAP2T, and I spent some money on a router. And I spent lots of time configuring it. Also, I was told (oh.. and You, Xponder1 told me that) that my registration issues will be fixed once I get a PAP2T and a router. And here I am, just after 4 days of running on PAP2T, loosing registration for the nearly whole day. What reaction do you expect from me? Just put yourself in my situation. Everyone here praises Timothy but actually the company’s service is far from yearning much praises. Nearly every day there are new issues coming in. After all, I’m helping YOU, VOIPo, to fix your issues. Seems like not much people here even care to point at these problems. Or, afraid maybe?
Internet? No. My internet is fine. It’s VOIPo. When you have to sit next to you ATA and pull the power cord every day VOIPo is not gonna be for you either.Quote:
Originally Posted by scott2020
If they can't connect to the core outbound routing servers, it's possible yes.Quote:
Originally Posted by dcurrey
Rebooted at 8:40 MDT. No help. Line 1 does not register. Line 2 does. Ticket updated.
Also tested outbound call - fails at about 45 seconds - goes to fast busy. Inbound appears to be normal.
No - a reboot of the PAP2 did nothing.Quote:
Originally Posted by VOIPoJustin
I bounced my network, then rebooted the PAP2 and it registered.
Reboot and try now (or wait until it re-provisions every hour). I think I see what happened with yours. The update changed your SIP ports to new default ones. We've restored all SIP ports to what they were before.Quote:
Originally Posted by dmbmar
Will reboot shortly and update thread and ticket.
I'll just let your comment stand for itself as an indication you obviously don't even understand the point of Tim's post regarding the Dallas latency. Again, it's the Internet, not necessarily VOIPo, and these things will happen with VOIP. Sorry for your recent troubles, but people need to understand the Internet is far from perfect, filled with hackers, script kiddies, and other trash, and you need to accept the good with the bad. I won't clog this thread with any further comment.Quote:
Originally Posted by stason99
Will reboot shortly and update thread and ticket.
Update. After reboot, outbound calling issue appears to be resolved. However, only one line (line2) is registered. Half way home.
I thought you meant my ISP. So replied with that in mind as my ISP seems very stable. Anyway, Tim said that if there’s any issues with registration, PAP2T should reconnect themselves. That supposed to be the main advantage over HT502s.Quote:
Originally Posted by scott2020
Dmbmar...Are you still having an issue with your lines? I am having the same issue with only line 2 active. Still waiting to hear back on my ticket.
Yes, same issue. Line 2 registers, line 1 does not. All else appears to be working normally.
Well at least I know I'm not the only one :p
Looks like right after I typed that line 1 came back online so (fingers crossed) all appears to be back to normal now.
Nice. Still no luck here, but I know they are working on it. Since I have 1 line, not that concerned. Yet.
Now it works!
Sometime overnight - both lines failed to register - I have no idea if this was related to the internal latency issue or not.Quote:
Originally Posted by dbmaven
The reboot did nothing, had to bounce my network again.
If anyone else is continuing to have issues with one line registering please update your ticket or PM me your account # to investigate.