[Home]

Summary:ASTERISK-27587: Asterisk webrtc con JSSIP dont close connection
Reporter:VIP2PHONE INC (vip2phone)Labels:webrtc
Date Opened:2018-01-15 13:55:35.000-0600Date Closed:2018-01-15 15:55:02.000-0600
Priority:MajorRegression?
Status:Closed/CompleteComponents:Core/HTTP
Versions:14.5.0 14.6.2 Frequency of
Occurrence
Related
Issues:
Environment:Attachments:
Description:Greetings, we currently have the version of Asterisk 14.5.0 implemented, we use JSSIP as the base library for the Webrct webphone, initially it works correctly with a small number of extensions, but when we use a pbx with 100 extensions the response on port 8089 tcp of webrtc denies the connections, and the connections that existed begin to be lost.

We observe in the system message:

TCP: request_sock_TCP: Possible SYN flooding on port 8089. Sending cookies. Check SNMP counters.

Log Asterisk

http.c: HTTP session count exceeded 100 sessions.

We make the adjustment in the http.conf file

sessionlimit = 500

But the message Greetings, we currently have the version of Asterisk 14.5.0 implemented, we use JSSIP as the base library for the Webrct webphone, initially it works correctly with a small amount of extensions, but when we use a pbx with 100 extensions the answer on port 8089 tcp of webrtc denies the connections, and the connections that existed begin to get lost.

We observe in the system message:

TCP: request_sock_TCP: Possible SYN flooding on port 8089. Sending cookies. Check SNMP counters.

We modify

echo "4096"> / proc / sys / net / ipv4 / tcp_max_syn_backlog

Log Asterisk

http.c: HTTP session count exceeded 100 sessions.

We make the adjustment in the http.conf file

sessionlimit = 500

The error of SYN flooding persists, I clarify that the Firewall has blocked the external traffic so the connections to port 8089 are legitimate.

I can see that when executing the command.

netstat -anp | awk '{print $ 4 "" $ 6}' | grep '8089 ESTABLISHED' | wc -l

Shows values ​​below the 100 allowed sessions.

Verifying with netstat we find that there are more than 100 sessions in CLOSE_WAIT status, and do not finish the process by gluing the sessions until the SYN flooding error in Kernel happens.

What is the recommended configuration so that this situation does not occur as it becomes recurrent.

I appreciate any configuration parameter that helps us improve this instability in the system, thanks.
Comments:By: Asterisk Team (asteriskteam) 2018-01-15 13:55:36.379-0600

Thanks for creating a report! The issue has entered the triage process. That means the issue will wait in this status until a Bug Marshal has an opportunity to review the issue. Once the issue has been reviewed you will receive comments regarding the next steps towards resolution.

A good first step is for you to review the [Asterisk Issue Guidelines|https://wiki.asterisk.org/wiki/display/AST/Asterisk+Issue+Guidelines] if you haven't already. The guidelines detail what is expected from an Asterisk issue report.

Then, if you are submitting a patch, please review the [Patch Contribution Process|https://wiki.asterisk.org/wiki/display/AST/Patch+Contribution+Process].

By: Kevin Harwell (kharwell) 2018-01-15 15:46:38.250-0600

We appreciate the difficulties you are facing, however this does not appear to be a bug report and your request or comments would be better served in a different forum.

The Asterisk community provides support over IRC, mailing lists, and forums as described at http://asterisk.org/community. The Asterisk issue tracker is used specifically to track issues concerning bugs and documentation errors.

Please see the Asterisk Issue Guidelines [1] for instruction on the intended use of the Asterisk issue tracker.

Thanks!

[1] https://wiki.asterisk.org/wiki/display/AST/Asterisk+Issue+Guidelines



By: Kevin Harwell (kharwell) 2018-01-15 15:54:46.148-0600

Per the Asterisk versions page [1], the maintenance (bug fix) support for the Asterisk branch you are using has ended. For continued maintenance support please move to a supported branch of Asterisk. After testing with a supported branch, if you find this problem has not been resolved, please open a new issue against the latest version of that Asterisk branch.

Thanks!

[1] https://wiki.asterisk.org/wiki/display/AST/Asterisk+Versions