Anyone else down?

[dbmaven]

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

[digger16309]

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

Same here this morning but VPanel still shows me as registered even though I am really not.

The pissed off factor is starting to rise now....

[VOIPoTim]

Same here this morning but VPanel still shows me as registered even though I am really not.

The pissed off factor is starting to rise now....

When you say you're really not what's happening? All the graphs look fine on our end so there aren't any system-wide issues that we can tell.

Did all of this start for you when the firmware was upgraded the other day?

[VOIPoTim]

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

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?

[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.

[VOIPoTim]

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]

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

[sr98user]

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]

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]

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.