Anyone else down?

**VOIPoTim** · 04-02-2009 07:31 AM

Originally Posted by ptrowski

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.

Yes. All the signaling would still have to go through our network to establish the calls, so major latency there would cause an issue.

**ptrowski** · 04-02-2009 07:32 AM

Ah ok. I am a better resource manager than VoIP engineer.

**sr98user** · 04-02-2009 07:36 AM

Originally Posted by ptrowski

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.

I am on east01 and my audio is not relayed through Voipo servers. My ATA did not go down yesterday and when people had problems, I tried making some outgoing calls and it worked fine. ATA and vPanel showed I was registered. I am not sure if this was isolated to the Dallas servers.

**ptrowski** · 04-02-2009 07:39 AM

Originally Posted by sr98user

I am on east01 and my audio is not relayed through Voipo servers. My ATA did not go down yesterday and when people had problems, I tried making some outgoing calls and it worked fine. ATA and vPanel showed I was registered. I am not sure if this was isolated to the Dallas servers.

That's why I asked as I am supposed to be on East01 also and I was getting dead air.

**VOIPoTim** · 04-02-2009 07:43 AM

Originally Posted by ptrowski

That's why I asked as I am supposed to be on East01 also and I was getting dead air.

We're showing you're using a HT502 on Central02 in Dallas.

**ptrowski** · 04-02-2009 07:52 AM

Originally Posted by VOIPoTim

We're showing you're using a HT502 on Central02 in Dallas.

That must be because I took the pap2 out and put the 502 back in after the wife was done giving me dirty looks.

**dbmaven** · 04-02-2009 10:55 AM

Originally Posted by VOIPoTim

We're not even seeing attempts from your account at all which is very odd.

I know in the past you mentioned having to reboot your router for it to connect, have you tried that time time?

Every time I reboot the router, it registers successfully. At the first expiration (which looks like 250+ seconds) - *BAM* = FAIL. Cannot connect to registration server (or whatever the exact message is in the PAP2 status page), and vPanel shows nothing.

My ticket update by support shows a suspicion that this was related to issues at your datacenter.

I will reboot everything tonight when I get home and we'll go from there.

Brandon also indicated that he was reviewing my router logs (from the earlier ticket) and (paraphrased) 'was seeing some very weird things'....

If it's all related to issues at your data center I'll be happy. For most of the prior week - it just worked. No port forwarding or anything at all in the router setup - almost an 'out of the box' router config - which is the way it should be...

VOIPoLukeBotha · 04-02-2009 11:58 AM

Hi guys,

There was a network failure earlier which affected registrations - This has since been resolved.

More information regarding the network failure can be found using the URL listed below:

http://forums.voipo.com/showthread.p...1222#post11222

If you're still experiencing any issues please direct a ticket to the Support department by emailing support@voipo.com.

We'll gladly look into this for you.

Thanks

**Dave_N** · 04-02-2009 12:20 PM

Originally Posted by dbmaven

Every time I reboot the router, it registers successfully. At the first expiration (which looks like 250+ seconds) - *BAM* = FAIL. Cannot connect to registration server (or whatever the exact message is in the PAP2 status page), and vPanel shows nothing.

My ticket update by support shows a suspicion that this was related to issues at your datacenter.

I will reboot everything tonight when I get home and we'll go from there.

Brandon also indicated that he was reviewing my router logs (from the earlier ticket) and (paraphrased) 'was seeing some very weird things'....

If it's all related to issues at your data center I'll be happy. For most of the prior week - it just worked. No port forwarding or anything at all in the router setup - almost an 'out of the box' router config - which is the way it should be...

I can confirm this behavior as well. Prior to this week, it was just working, didn't have to port forward on my router or anything. As of late Tuesday, things got bad again. Unfortunately, there were "two changes". The firmware upgrade and the network instability. I also was usually connected after the reboot and then unable to connect. This of course led me to reconfigure my router for the port forwarding recommended. Change #3. As of now things are working but the WAI (and index of the current Wife Acceptance Factor) is at a new low and the installation might not survive another extended outage.

**dbmaven** · 04-02-2009 06:39 PM

Originally Posted by VOIPoLuke

Hi guys,

There was a network failure earlier which affected registrations - This has since been resolved.

More information regarding the network failure can be found using the URL listed below:

http://forums.voipo.com/showthread.p...1222#post11222

If you're still experiencing any issues please direct a ticket to the Support department by emailing support@voipo.com.

We'll gladly look into this for you.

Thanks

HEK-343939