And maybe other TCP params that I have in the kamailio config : # life time of TCP connection when there is no traffic # - a bit higher than registration expires to cope with UA behind NAT tcp_connection_lifetime=3620 tcp_connect_timeout=1 tcp_keepcnt = 10
tcp_keepidle = 10 tcp_send_timeout=3 De : sr-users-boun...@lists.sip-router.org [mailto:sr-users-boun...@lists.sip-router.org] De la part de Laurent Schweizer Envoyé : mardi 9 septembre 2014 15:38 À : mico...@gmail.com; Kamailio (SER) - Users Mailing List Objet : Re: [SR-Users] TCP SYN only regarding error , yes I have a lot of error regarding SDP and a few regarding TCP. for the SDP , initially I have think that I call rtpproxy_offer / rtpproxy_answer for a request that don't have any SDP but all rtpproxy method have a check with has_body("application/sdp") Sep 9 15:26:31 ch38 kamailio[24730]: ERROR: <core> [parser/sdp/sdp.c:213]: Invalid payload location Sep 9 15:26:31 ch38 kamailio[24730]: ERROR: <core> [parser/sdp/sdp.c:229]: Invalid payload location Sep 9 15:26:31 ch38 kamailio[24730]: ERROR: <core> [parser/sdp/sdp.c:213]: Invalid payload location Sep 9 15:26:31 ch38 kamailio[24730]: ERROR: <core> [parser/sdp/sdp.c:229]: Invalid payload location Sep 9 15:26:31 ch38 kamailio[24730]: ERROR: <core> [parser/sdp/sdp.c:213]: Invalid payload location Sep 9 15:26:37 ch38 kamailio[24842]: ERROR: <core> [tcp_read.c:270]: error reading: Connection reset by peer (104) Sep 9 15:26:37 ch38 kamailio[24842]: ERROR: <core> [tcp_read.c:882]: ERROR: tcp_read_req: error reading Sep 9 15:26:37 ch38 kamailio[24709]: ERROR: <core> [parser/sdp/sdp.c:213]: Invalid payload location Sep 9 15:26:37 ch38 kamailio[24709]: ERROR: <core> [parser/sdp/sdp.c:213]: Invalid payload location Sep 9 15:26:37 ch38 kamailio[24709]: ERROR: <core> [parser/sdp/sdp.c:229]: Invalid payload location Sep 9 15:26:37 ch38 kamailio[24709]: ERROR: <core> [parser/sdp/sdp.c:213]: Invalid payload location Sep 9 15:26:37 ch38 kamailio[24709]: ERROR: <core> [parser/sdp/sdp.c:229]: Invalid payload location Sep 9 15:26:37 ch38 kamailio[24709]: ERROR: <core> [parser/sdp/sdp.c:213]: Invalid payload location Sep 9 15:26:38 ch38 kamailio[24831]: ERROR: <core> [tcp_read.c:270]: error reading: Connection timed out (110) Sep 9 15:26:38 ch38 kamailio[24831]: ERROR: <core> [tcp_read.c:882]: ERROR: tcp_read_req: error reading Sep 9 15:26:42 ch38 kamailio[24806]: ERROR: <core> [parser/sdp/sdp.c:213]: Invalid payload location Sep 9 15:26:42 ch38 kamailio[24806]: ERROR: <core> [parser/sdp/sdp.c:213]: Invalid payload location Sep 9 15:26:42 ch38 kamailio[24806]: ERROR: <core> [parser/sdp/sdp.c:229]: Invalid payload location Sep 9 15:26:42 ch38 kamailio[24806]: ERROR: <core> [parser/sdp/sdp.c:213]: Invalid payload location Sep 9 15:26:42 ch38 kamailio[24806]: ERROR: <core> [parser/sdp/sdp.c:229]: Invalid payload location Sep 9 15:26:42 ch38 kamailio[24806]: ERROR: <core> [parser/sdp/sdp.c:213]: Invalid payload location Sep 9 15:26:43 ch38 kamailio[24786]: ERROR: <core> [parser/sdp/sdp.c:213]: Invalid payload location Sep 9 15:26:43 ch38 kamailio[24786]: ERROR: <core> [parser/sdp/sdp.c:213]: Invalid payload location Sep 9 15:26:43 ch38 kamailio[24786]: ERROR: <core> [parser/sdp/sdp.c:229]: Invalid payload location Sep 9 15:26:43 ch38 kamailio[24786]: ERROR: <core> [parser/sdp/sdp.c:213]: Invalid payload location Sep 9 15:26:43 ch38 kamailio[24786]: ERROR: <core> [parser/sdp/sdp.c:229]: Invalid payload location Sep 9 15:26:43 ch38 kamailio[24786]: ERROR: <core> [parser/sdp/sdp.c:213]: Invalid payload location Sep 9 15:26:53 ch38 kamailio[24714]: ERROR: <core> [parser/sdp/sdp.c:213]: Invalid payload location Sep 9 15:26:53 ch38 kamailio[24714]: ERROR: <core> [parser/sdp/sdp.c:213]: Invalid payload location Sep 9 15:26:53 ch38 kamailio[24714]: ERROR: <core> [parser/sdp/sdp.c:229]: Invalid payload location Sep 9 15:26:53 ch38 kamailio[24714]: ERROR: <core> [parser/sdp/sdp.c:213]: Invalid payload location Sep 9 15:26:53 ch38 kamailio[24714]: ERROR: <core> [parser/sdp/sdp.c:229]: Invalid payload location Sep 9 15:26:53 ch38 kamailio[24714]: ERROR: <core> [parser/sdp/sdp.c:213]: Invalid payload location Sep 9 15:27:06 ch38 kamailio[24746]: ERROR: <core> [parser/sdp/sdp.c:213]: Invalid payload location Sep 9 15:27:06 ch38 kamailio[24742]: ERROR: <core> [parser/sdp/sdp.c:213]: Invalid payload location Sep 9 15:27:06 ch38 kamailio[24865]: ERROR: <core> [tcp_main.c:4137]: connect 77.29.142.196:49927 failed Sep 9 15:27:06 ch38 kamailio[24865]: ERROR: <core> [tcp_main.c:4137]: connect 77.29.142.196:49927 failed De : Daniel-Constantin Mierla [mailto:mico...@gmail.com]<mailto:[mailto:mico...@gmail.com]> Envoyé : mardi 9 septembre 2014 15:18 À : Laurent Schweizer; Kamailio (SER) - Users Mailing List Objet : Re: [SR-Users] TCP SYN only Ahh, overlooked in your previous email -- the numbers reported by sockstats were close to the default value for max connections, so it was my first thought. Do you get any error messages in syslog from kamailio? Cheers, Daniel On 09/09/14 15:16, Laurent Schweizer wrote: Yes I set tcp_max_connections=104096 Laurent De : Daniel-Constantin Mierla [mailto:mico...@gmail.com] Envoyé : mardi 9 septembre 2014 15:09 À : Laurent Schweizer; Kamailio (SER) - Users Mailing List Objet : Re: [SR-Users] TCP SYN only Hello, have you increased the max connections limit? - http://www.kamailio.org/wiki/cookbooks/devel/core#tcp_max_connections The PKG_MEM_POOL_SIZE is more or less same as -m parameter, so you don't need to change the sources if you need higher value. Cheers, Daniel On 09/09/14 14:57, Laurent Schweizer wrote: Hi, Yes I check them, the only 2 point that I have actually not tested is to change : - You might have to decrease TCP_BUF_SIZE to a smaller value (e.g 8K) - You might want to increase PKG_MEM_POOL_SIZE (for large queues) I'm using Kamailio 3.2.1 I have set: tcp children to 50 tcp_max_connections=104096 started wit -m 4096 -M 64 with sockstat I have: sockets: used 2171 TCP: inuse 913 orphan 1 tw 4 alloc 939 mem 29 UDP: inuse 440 mem 372 UDPLITE: inuse 0 RAW: inuse 1 FRAG: inuse 0 memory 0 BR Laurent De : sr-users-boun...@lists.sip-router.org<mailto:sr-users-boun...@lists.sip-router.org> [mailto:sr-users-boun...@lists.sip-router.org] De la part de Daniel-Constantin Mierla Envoyé : mardi 9 septembre 2014 14:46 À : Kamailio (SER) - Users Mailing List Objet : Re: [SR-Users] TCP SYN only Hello, have you checked the file in the sources located at doc/tcp_tunning.txt? Cheers, Daniel On 09/09/14 14:40, Laurent Schweizer wrote: Dear all, Since few weeks I have more and more TCP issue, I can see that sometimes the client send a TCP SYN but never get any response. 106.123315 62.12.179.104 -> X.X.X.X TCP 39174 > sip [SYN] Seq=0 Win=4380 Len=0 MSS=1380 TSV=4294942209 TSER=0 WS=1 109.124384 62.12.179.104 -> X.X.X.X TCP 39174 > sip [SYN] Seq=0 Win=4380 Len=0 MSS=1380 TSV=4294942510 TSER=0 WS=1 111.202946 62.12.179.104 -> X.X.X.X TCP 4993 > sip [SYN] Seq=0 Win=4380 Len=0 MSS=1380 TSV=4294942717 TSER=0 WS=1 114.204707 62.12.179.104 -> X.X.X.X TCP 4993 > sip [SYN] Seq=0 Win=4380 Len=0 MSS=1380 TSV=4294943018 TSER=0 WS=1 I have found on internet many doc regarding TCP and max connection issue and I have already done change in sysctl (see below) to increase the number of tcp connection but seems still not ok. Any idea ? Best regards Laurent net.ipv4.ip_forward = 0 net.ipv4.conf.default.rp_filter = 1 net.ipv4.conf.default.accept_source_route = 0 kernel.sysrq = 0 kernel.core_uses_pid = 1 net.ipv4.tcp_syncookies = 0 net.bridge.bridge-nf-call-ip6tables = 0 net.bridge.bridge-nf-call-iptables = 0 net.bridge.bridge-nf-call-arptables = 0 kernel.msgmnb = 65536 kernel.msgmax = 65536 kernel.shmmax = 68719476736 kernel.shmall = 4294967296 net.ipv4.tcp_timestamps = 1 net.ipv4.tcp_fin_timeout = 30 net.ipv4.tcp_keepalive_time = 1200 net.ipv4.tcp_max_syn_backlog = 8192 net.ipv4.tcp_max_tw_buckets = 5000 fs.file-max = 2097152 net.ipv4.ip_local_port_range = 2000 65535 net.ipv4.tcp_max_tw_buckets = 1440000 net.ipv4.tcp_tw_recycle = 1 net.ipv4.tcp_tw_reuse = 1 net.core.somaxconn = 65536 net.core.netdev_max_backlog = 65536 _______________________________________________ SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org<mailto:sr-users@lists.sip-router.org> http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users -- Daniel-Constantin Mierla http://twitter.com/#!/miconda<http://twitter.com/#%21/miconda> - http://www.linkedin.com/in/miconda Next Kamailio Advanced Trainings 2014 - http://www.asipto.com Sep 22-25, Berlin, Germany -- Daniel-Constantin Mierla http://twitter.com/#!/miconda<http://twitter.com/#%21/miconda> - http://www.linkedin.com/in/miconda Next Kamailio Advanced Trainings 2014 - http://www.asipto.com Sep 22-25, Berlin, Germany -- Daniel-Constantin Mierla http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda Next Kamailio Advanced Trainings 2014 - http://www.asipto.com Sep 22-25, Berlin, Germany
_______________________________________________ SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
