Busy Signal Outgoing Calls

[VOIPoBrandon]

Hello,

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

[chevyman]

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]

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]

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]

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.

[chevyman]

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.

So are they going to give a list of the configuration settings needed?

what about my question about the *21 or *20 issue?

[VOIPoTim]

So are they going to give a list of the configuration settings needed?

what about my question about the *21 or *20 issue?

In terms of * codes, that sounds like a DTMF setting where it's being recognized on one and not the other...just e-mail and ask support what you should have your DTMF set to...I'm honestly not sure which method we use...too technical for me.

In terms of other settings, I'm not sure what you're really needing. Your device may have lots of settings, but the ones ones that are rally needed are the SIP info, codec info, and DTMF info. There's nothing else really to provide since the rest are just built into the device and up to you whether you choose to use them or not. We can't get into all the special settings each device has since they have nothing to do with us or our service.

Just contact reseller support about the DTMF tone question and also if you have any specific questions about the basic settings and we'll be happy to help.