Busy Signal Outgoing Calls

**VOIPoTim** · 01-22-2015 05:26 PM

Originally Posted by chevyman

now i'm having problems with sip7! can't make any calls and registration is flaky.

I just did a trace of sip and sip7 and they are both going to chicago to some company liquidweb.com and not to texas as its been for years, did Voipo change servers?

Can you guys verify if you are having issues now?

We think we tracked it down and had an attack on our network that we believe has been firewalled out for good now.

Please let us know if you're seeing normal service or or still having issues.

**GreenLantern** · 01-22-2015 05:50 PM

Originally Posted by VOIPoTim

Can you guys verify if you are having issues now?

We think we tracked it down and had an attack on our network that we believe has been firewalled out for good now.

Please let us know if you're seeing normal service or or still having issues.

It has improved, but is still not back to normal.

I'm still getting some "unreachable" and "lagged" results on both servers, especially SIP7.

Example from right now...

sip 7 LAGGED (2405 ms)
sip OK (465 ms)
other provider 1 OK (25 ms)
other provider 2 OK (26 ms)

**GreenLantern** · 01-22-2015 04:15 PM

yes, looks like they've remapped SIP to the north server, in Michigan I think.

whoever was attacking the texas server must have started hitting the michigan one too.

**GreenLantern** · 01-22-2015 06:06 PM

texas server is also still lagging bad.

sip LAGGED (3178 ms)

**VOIPoBrandon** · 01-22-2015 09:38 PM

Hello,

Please advise if you are not seeing this issue completely resolved at this point, thank you!

**chevyman** · 01-23-2015 01:08 AM

Originally Posted by VOIPoBrandon

Hello,

Please advise if you are not seeing this issue completely resolved at this point, thank you!

do you mean the busy signal on sip.voipwelcome.com & sip7.voipwelcome.com for the last week or what happen Today?

**VOIPoTim** · 01-23-2015 12:14 PM

Originally Posted by chevyman

do you mean the busy signal on sip.voipwelcome.com & sip7.voipwelcome.com for the last week or what happen Today?

Everything should be back to normal on them. We mitigated what looked like an attack on them earlier in the week and discovered an issue with some users that were using TCP to register with instead of UDP and that was causing issues since TCP held all the packets and released them at once causing issues and delays for everyone. We disabled TCP registrations because everyone should be using UDP.

Between blocking the attack and disabling TCP registrations (which were causing a quasi-attack on their own), everything appears completely stable on our end now.

Reseller support load is now drastically lower than it has been all week with only some typical support issues that seem unrelated.

Greenlantern - We are looking at your ticket, but everything looks fine on our end. We even did a test on your accounts by registering to them and they worked fine. Brandon will get in touch with you.

Also worth noting...we've noticed on a few users that if their device is sending too much info in the headers it can cause the MTU to be too big in the headers and cause issues. We control this on our ATAs to limit the amount of info they send but if you have BYOD devices configured to send things like codecs we don't support, a name in the from header, etc it could push it over the MTU limit in the headers and cause a busy signal or call failure.

**chevyman** · 01-24-2015 05:07 PM

Originally Posted by VOIPoTim

Also worth noting...we've noticed on a few users that if their device is sending too much info in the headers it can cause the MTU to be too big in the headers and cause issues. We control this on our ATAs to limit the amount of info they send but if you have BYOD devices configured to send things like codecs we don't support, a name in the from header, etc it could push it over the MTU limit in the headers and cause a busy signal or call failure.

I TOO have been asking for configuration setting to set my customer's ATAs, I have posted here and ask in trouble tickets But over the years I never get the answers, like it's Top Secret! and over this last week i have been looking at other providers, which they all list the settings for there systems.

Like on 'sip' if i do *21 or *20 i get "busy signal" but the command goes through anyway. But if i change to 'sip7' without changing any settings and do the *21 or *20 i get the response "Thank You" every time.

So TIM when is Voipo going to give resellers the configuration settings needed to support there customers!

**VOIPoTim** · 01-24-2015 05:24 PM

Originally Posted by chevyman

I TOO have been asking for configuration setting to set my customer's ATAs, I have posted here and ask in trouble tickets But over the years I never get the answers, like it's Top Secret! and over this last week i have been looking at other providers, which they all list the settings for there systems.

Like on 'sip' if i do *21 or *20 i get "busy signal" but the command goes through anyway. But if i change to 'sip7' without changing any settings and do the *21 or *20 i get the response "Thank You" every time.

So TIM when is Voipo going to give resellers the configuration settings needed to support there customers!

Just contact reseller@voipo.com with any questions you have and we'll be happy to help.

In terms of my post above about codecs, we only support the G.711 codec so it's best to disable any others on your device so it doesn't even attempt to negotiate anything else.

**GreenLantern** · 01-23-2015 03:01 PM

Hi Tim,

Thanks for all the hard work you guys did the last few days. It was rough sledding, but things look great right now.

Any idea if/why these attacks are intentionally targeting voipo?

Great info on the MTU limits. We'll know now to look for extraneous info like extra codecs, names, etc. in case BYOD users add any of that.

Thanks again, and now everyone go perform your preferred good luck rituals.