No More Connections Allowed.

Home » Asterisk Users » No More Connections Allowed.
Asterisk Users 8 Comments

Hello,

I have strange situation with Asterisk 1.8.18.0 , randomly i got this message in cli:

“WARNING[15925] asterisk.c: No more connections allowed”

All connections freeze and all extensions doesn’t work anymore. Is any bug or is any setting that can solve this problem?

Thank you.

Jonson. http://mobile-sip.tel/

8 thoughts on - No More Connections Allowed.

  • Jonson Player wrote:

    Hola,

    This message is output when the number of Asterisk consoles (asterisk -r instances) has reached the limit. This limit is 128 by default which is quite a lot. Are you doing something that would cause a lot? Could they be hanging around by mistake?

    This definitely shouldn’t happen but it would be useful to know exactly what you are doing with the system. Answering my questions above is a good start.

    Cheers,

  • You’ve exceeded the allowed maximum number of simultaneous remote console connections (128). While it may be a bit aggressive to have it kill all current connected consoles, its also a bit excessive to have
    128 connected remote consoles.

    While the behaviour may not be entirely desirable, this isn’t so much a bug as a limitation of the system.

  • You’ve exceeded the allowed maximum number of simultaneous remote console connections (128). While it may be a bit aggressive to have it kill all current connected consoles, its also a bit excessive to have
    128 connected remote consoles.

    While the behaviour may not be entirely desirable, this isn’t so much a bug as a limitation of the system.

  • Hello Josua,

    Thank you for this answers:

    First of all, yes i run in crontab at 15 min an analyzing script which collect show sip channels with asterisk -rx . This could be my problem… I think that this commands could remain stalled and doesn’t logout after execution of command.

    A friend of main told me that i could put in asterisk init script the following command: ulimit -HSn 135535

    You think is useful?

    Another abortion could be to make something with manager /AMI scripts like that: http://ofps.oreilly.com/titles/9780596517342/asterisk-AMI.html

    What is your advice? I need this analyzing script to monitor when i have strange rise of use channels to prevent attacks or brute force.

  • Hello Danny,

    Could you tell me how can i put time out at execution of remote commands with asterisk -rx “show sip channels”. I think that is my problem… after i execute asterisk -rx commands something remain stalled and somehow i think that could block my asterisk… I mean all new connections couldn’t be made anymore and the old active peers is nonfunctional and logged off, and the strangest thing is that i go on asterisk -rvc and i tap sip show peers i seen old active peers logged in… is clear that asterisk is freezed somehow and i need some workaround at this situation.

    Thank you.

  • Hello Matthew,

    Could I rise with some option the number of simultaneous console? I don’t have simultaneous console but is good to know in case i didn’t get any other workaround to fix this problem.

    Thank you.

  • No, you don’t need your script for this.

    Prevent attacks by using fail2ban to block brute force attacks using iptables, securing your server at the OS level, and NEVER EVER EVER let leave the web GUI for FreePBX open to the internet. I’m sure others have more suggestions.

    Over the years 100% of successful attacks against our Asterisk/FreePBX servers (we have 20 or 30 servers) used the FreePBX GUI to get access to the server. We use very complex passwords for SIP accounts and use a non-default password for the Polycom provisioning user.

    —–Original Message—

  • My suggestion would be to issue a “core restart when convenient” around midnight, assuming your installation doesn’t do 24/7 calls.

    From: asterisk-users-bounces@lists.digium.com
    [mailto:asterisk-users-bounces@lists.digium.com] You’ve exceeded the allowed maximum number of simultaneous remote console connections (128). While it may be a bit aggressive to have it kill all current connected consoles, its also a bit excessive to have
    128 connected remote consoles.

    While the behaviour may not be entirely desirable, this isn’t so much a bug as a limitation of the system.