Page 1 of 1

Too many authhentication requestes a second?

PostPosted: Wed Mar 12, 2014 5:51 pm
by tgirl
Hi guys - first post...
Asterisk 1.8.23.0-1_centos5.go RPM with goautodial 3.3-1393218000 interface

We have just been through a minor trauma. We committed to using this autodialer last week and it was running ok. Then it stopped. We do not have much Linux experience and had a very stressful few hours while our staff stood around waiting.

It turned out that our SIP trunk had been disabled. When we spoke to our provider they said that we had been sending multiple requests to authenticate per second and their system had taken this as an attack.

Due to other stuff going on in the office, we forgot about this as the system was working fine after we changed it's IP address. However we had to reboot the server today and when it came up the voip trunk again got suspended. The provider told us it was the same as before and also told us that there was a setting in asterisk to adjust this.

Any ideas?
thx

Re: Too many authhentication requestes a second?

PostPosted: Wed Mar 12, 2014 6:18 pm
by mav2287
IP authentication would be my quick fix

Re: Too many authhentication requestes a second?

PostPosted: Wed Mar 12, 2014 6:26 pm
by tgirl
That would not stop the VOIP providers anti hack system from disabling that IP due to excessive authentication requests from it.

Re: Too many authhentication requestes a second?

PostPosted: Wed Mar 12, 2014 7:25 pm
by deficit
Actually IP auth would as you do not authenticate they just allow traffic from the IP address.. I would recommend changing providers.. Does your provider allow dialer short duration traffic??

Re: Too many authhentication requestes a second?

PostPosted: Wed Mar 12, 2014 9:10 pm
by williamconley
tgirl wrote:Hi guys - first post...
Asterisk 1.8.23.0-1_centos5.go RPM with goautodial 3.3-1393218000 interface

We have just been through a minor trauma. We committed to using this autodialer last week and it was running ok. Then it stopped. We do not have much Linux experience and had a very stressful few hours while our staff stood around waiting.

It turned out that our SIP trunk had been disabled. When we spoke to our provider they said that we had been sending multiple requests to authenticate per second and their system had taken this as an attack.

Due to other stuff going on in the office, we forgot about this as the system was working fine after we changed it's IP address. However we had to reboot the server today and when it came up the voip trunk again got suspended. The provider told us it was the same as before and also told us that there was a setting in asterisk to adjust this.

Any ideas?
thx

1) Welcome to the Party! 8-)

2) As you are obviously new here, I have some suggestions to help us all help you:

When you post, please post your entire configuration including (but not limited to) your installation method and vicidial version with build.

This IS a requirement for posting along with reading the stickies (at the top of each forum) and the manager's manual (available on EFLO.net, both free and paid versions)

You should also post: Asterisk version, telephony hardware (model number is helpful here), cluster information if you have one, and whether any other software is installed in the box. If your installation method is "from scratch" you must post your operating system and should also post the .iso version from which you installed your original operating system. If your installation is "Hosted" list the site name of the host.

If this is a "Cloud" or "Virtual" server, please note the technology involved along with the version of that techology (ie: VMware Server Version 2.0.2). If it is not, merely stating the Motherboard model # and CPU would be helpful.

Similar to This:

Vicibox X.X from .iso | Vicidial X.X.X-XXX Build XXXXXX-XXXX | Asterisk X.X.X | Single Server | No Digium/Sangoma Hardware | No Extra Software After Installation | Intel DG35EC | Core2Quad Q6600

3) Changing carriers would likely resolve your issue, but the question I have to ask is why your system would request registration more than ONCE. How many carriers did you set up in Vicidial to connect to the "carrier" and does more than one of them have a registration string (which should never be duplicated)?

4) In case I did not mention it, you MUST have more than one carrier if you intend to hire people whose paychecks (and family income) will depend upon this equipment working properly.

Please also be aware you are using "GoAutoDial" which is an installation ISO/CD installer for Vicidial. ViciBOX is another ISO/CD Installer for Vicidial (installs the same software without the pretty wizards in front of it ...). Some find the wizards useful, others find them to be "in the way" and obscure your view of Vicidial which is the software you are actually running. Not to mention the GoAutoDial logo everywhere and the confusion about the Version of Vicidial being run (as the word "version" seems to be moved away from the word "Vicidial" in many distros of Goautodial, LOL). It's a good stable install, though, and very useful for a single standalone server. But when you graduate to a cluster(multi-server) install because you have over 25 agents, it would be good to be running Vicibox already. :) FYI