[SR-Users] TCP SYN only

Discussion:

Laurent Schweizer

2014-09-09 12:40:15 UTC

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

Daniel-Constantin Mierla

2014-09-09 12:46:09 UTC

Permalink

Hello,

have you checked the file in the sources located at doc/tcp_tunning.txt?

Cheers,
Daniel

Post by Laurent Schweizer
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
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users

--
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

Laurent Schweizer

2014-09-09 12:57:39 UTC

Permalink

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-bounces-cR8azDVoa3IcDhw6gZKtMWD2FQJk+8+***@public.gmane.org [mailto:sr-users-***@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-cR8azDVoa3IcDhw6gZKtMWD2FQJk+8+***@public.gmane.org<mailto:sr-users-cR8azDVoa3IcDhw6gZKtMWD2FQJk+8+***@public.gmane.org>

http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users

--

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

Daniel-Constantin Mierla

2014-09-09 13:09:08 UTC

Permalink

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

Post by Laurent Schweizer
Hi,
- 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)
Im using Kamailio 3.2.1
tcp children to 50
tcp_max_connections=104096
started wit -m 4096 -M 64
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
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
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
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://www.linkedin.com/in/miconda
Next Kamailio Advanced Trainings 2014 - http://www.asipto.com
Sep 22-25, Berlin, Germany

Laurent Schweizer

2014-09-09 13:16:30 UTC

Permalink

Yes I set tcp_max_connections=104096

Laurent

De : Daniel-Constantin Mierla [mailto:miconda-***@public.gmane.org]
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-bounces-cR8azDVoa3IcDhw6gZKtMWD2FQJk+8+***@public.gmane.org<mailto:sr-users-bounces-***@public.gmane.orgp-router.org> [mailto:sr-users-bounces-cR8azDVoa3IcDhw6gZKtMWD2FQJk+8+***@public.gmane.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-cR8azDVoa3IcDhw6gZKtMWD2FQJk+8+***@public.gmane.org<mailto:sr-users-cR8azDVoa3IcDhw6gZKtMWD2FQJk+8+***@public.gmane.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://www.linkedin.com/in/miconda

Next Kamailio Advanced Trainings 2014 - http://www.asipto.com

Sep 22-25, Berlin, Germany

Daniel-Constantin Mierla

2014-09-09 13:18:29 UTC

Permalink

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

Post by Laurent Schweizer
Yes I set tcp_max_connections=104096
Laurent
*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
Hi,
- 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)
Im using Kamailio 3.2.1
tcp children to 50
tcp_max_connections=104096
started wit -m 4096 -M 64
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
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
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
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

Laurent Schweizer

2014-09-09 13:38:10 UTC

Permalink

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:miconda-***@public.gmane.org]
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:miconda-***@public.gmane.org]
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-bounces-cR8azDVoa3IcDhw6gZKtMWD2FQJk+8+***@public.gmane.org<mailto:sr-users-bounces-***@public.gmane.orgp-router.org> [mailto:sr-users-bounces-cR8azDVoa3IcDhw6gZKtMWD2FQJk+8+***@public.gmane.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-cR8azDVoa3IcDhw6gZKtMWD2FQJk+8+***@public.gmane.org<mailto:sr-users-cR8azDVoa3IcDhw6gZKtMWD2FQJk+8+***@public.gmane.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

Laurent Schweizer

2014-09-09 14:02:11 UTC

Permalink

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-bounces-cR8azDVoa3IcDhw6gZKtMWD2FQJk+8+***@public.gmane.org [mailto:sr-users-***@lists.sip-router.org] De la part de Laurent Schweizer
Envoyé : mardi 9 septembre 2014 15:38
À : miconda-***@public.gmane.org; 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:miconda-***@public.gmane.org]<mailto:[mailto:miconda-***@public.gmane.org]>
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:miconda-***@public.gmane.org]
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-bounces-cR8azDVoa3IcDhw6gZKtMWD2FQJk+8+***@public.gmane.org<mailto:sr-users-bounces-***@public.gmane.orgp-router.org> [mailto:sr-users-bounces-cR8azDVoa3IcDhw6gZKtMWD2FQJk+8+***@public.gmane.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-cR8azDVoa3IcDhw6gZKtMWD2FQJk+8+***@public.gmane.org<mailto:sr-users-cR8azDVoa3IcDhw6gZKtMWD2FQJk+8+***@public.gmane.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

Laurent Schweizer

2014-09-09 15:36:28 UTC

Permalink

Hello,

I have check again the log file and I see other error tcp error reading and parsing ...

Any idea ?

Laurent

9 17:27:10 ch38 kamailio[24845]: ERROR: registrar [save.c:506]: invalid cseq for aor <90756153105>
Sep 9 17:27:12 ch38 kamailio[24845]: ERROR: registrar [save.c:506]: invalid cseq for aor <90756153105>
Sep 9 17:27:13 ch38 kamailio[24859]: ERROR: <core> [tcp_read.c:270]: error reading: Connection reset by peer (104)
Sep 9 17:27:13 ch38 kamailio[24859]: ERROR: <core> [tcp_read.c:882]: ERROR: tcp_read_req: error reading
Sep 9 17:27:15 ch38 kamailio[24845]: ERROR: registrar [save.c:506]: invalid cseq for aor <90756153105>
Sep 9 17:27:20 ch38 kamailio[24845]: ERROR: registrar [save.c:506]: invalid cseq for aor <90756153105>
Sep 9 17:27:20 ch38 kamailio[24801]: ERROR: <core> [parser/sdp/sdp.c:213]: Invalid payload location
Sep 9 17:27:20 ch38 kamailio[24801]: ERROR: <core> [parser/sdp/sdp.c:213]: Invalid payload location
Sep 9 17:27:20 ch38 kamailio[24801]: ERROR: <core> [parser/sdp/sdp.c:229]: Invalid payload location
Sep 9 17:27:20 ch38 kamailio[24801]: ERROR: <core> [parser/sdp/sdp.c:213]: Invalid payload location
Sep 9 17:27:20 ch38 kamailio[24801]: ERROR: <core> [parser/sdp/sdp.c:229]: Invalid payload location
Sep 9 17:27:20 ch38 kamailio[24801]: ERROR: <core> [parser/sdp/sdp.c:213]: Invalid payload location
Sep 9 17:27:24 ch38 kamailio[24845]: ERROR: registrar [save.c:506]: invalid cseq for aor <90756153105>
Sep 9 17:27:29 ch38 kamailio[24845]: ERROR: registrar [save.c:506]: invalid cseq for aor <90756153105>
Sep 9 17:27:33 ch38 kamailio[24845]: ERROR: registrar [save.c:506]: invalid cseq for aor <90756153105>
Sep 9 17:27:49 ch38 kamailio[24717]: ERROR: <core> [parser/sdp/sdp.c:213]: Invalid payload location
Sep 9 17:27:49 ch38 kamailio[24717]: ERROR: <core> [parser/sdp/sdp.c:213]: Invalid payload location
Sep 9 17:27:49 ch38 kamailio[24717]: ERROR: <core> [parser/sdp/sdp.c:229]: Invalid payload location
Sep 9 17:27:49 ch38 kamailio[24717]: ERROR: <core> [parser/sdp/sdp.c:213]: Invalid payload location
Sep 9 17:27:49 ch38 kamailio[24717]: ERROR: <core> [parser/sdp/sdp.c:229]: Invalid payload location
Sep 9 17:27:49 ch38 kamailio[24717]: ERROR: <core> [parser/sdp/sdp.c:213]: Invalid payload location
Sep 9 17:27:51 ch38 kamailio[24821]: ERROR: <core> [tcp_read.c:270]: error reading: Connection reset by peer (104)
Sep 9 17:27:51 ch38 kamailio[24821]: ERROR: <core> [tcp_read.c:882]: ERROR: tcp_read_req: error reading
Sep 9 17:27:56 ch38 kamailio[24851]: ERROR: <core> [parser/msg_parser.c:710]: ERROR: parse_msg: message=<-mvuayf9nj9qk#015#012CSeq: 5307 REGISTER#015#012Max-Forwards: 70#015#012Contact: <sip:90735616896-***@public.gmane.org:3361;transport=tcp;line=yrw5xkcx>;reg-id=1;q=1.0;+sip.instance="<urn:uuid:e3669128-6208-48f5-8d49-0004134B05A7>";audio;mobility="fixed";duplex="full";description="snom821";actor="principal";events="dialog";methods="INVITE,ACK,CANCEL,BYE,REFER,OPTIONS,NOTIFY,SUBSCRIBE,PRACK,MESSAGE,INFO"#015#012User-Agent: snom821/8.7.3.16#015#012Allow-Events: dialog#015#012X-Real-IP: 192.168.105.253#015#012Supported: path, gruu#015#012Expires: 600#015#012Content-Length: 0#015#012#015#012>
Sep 9 17:27:56 ch38 kamailio[24851]: ERROR: <core> [receive.c:144]: ERROR: receive_msg: parse_msg failed
Sep 9 17:28:03 ch38 kamailio[24817]: ERROR: <core> [tcp_read.c:270]: error reading: Connection timed out (110)
Sep 9 17:28:03 ch38 kamailio[24817]: ERROR: <core> [tcp_read.c:882]: ERROR: tcp_read_req: error reading
Sep 9 17:28:08 ch38 kamailio[24823]: ERROR: <core> [tcp_read.c:270]: error reading: Connection reset by peer (104)
Sep 9 17:28:08 ch38 kamailio[24823]: ERROR: <core> [tcp_read.c:882]: ERROR: tcp_read_req: error reading
Sep 9 17:28:09 ch38 kamailio[24865]: ERROR: <core> [tcp_main.c:4322]: connect 212.147.50.253:19614 failed (timeout)
Sep 9 17:28:10 ch38 kamailio[24865]: ERROR: <core> [tcp_main.c:4322]: connect 212.147.50.253:19614 failed (timeout)
Sep 9 17:28:11 ch38 kamailio[24865]: ERROR: <core> [tcp_main.c:4322]: connect 212.147.50.253:19614 failed (timeout)
Sep 9 17:28:13 ch38 kamailio[24850]: ERROR: registrar [save.c:506]: invalid cseq for aor <90756153105>
Sep 9 17:28:13 ch38 kamailio[24850]: ERROR: registrar [save.c:506]: invalid cseq for aor <90756153105>
Sep 9 17:28:14 ch38 kamailio[24850]: ERROR: registrar [save.c:506]: invalid cseq for aor <90756153105>
Sep 9 17:28:15 ch38 kamailio[24865]: ERROR: <core> [tcp_main.c:4322]: connect 212.147.50.253:19614 failed (timeout)
Sep 9 17:28:16 ch38 kamailio[24850]: ERROR: registrar [save.c:506]: invalid cseq for aor <90756153105>
Sep 9 17:28:19 ch38 kamailio[24802]: ERROR: <core> [parser/sdp/sdp.c:213]: Invalid payload location
Sep 9 17:28:19 ch38 kamailio[24802]: ERROR: <core> [parser/sdp/sdp.c:213]: Invalid payload location
Sep 9 17:28:19 ch38 kamailio[24802]: ERROR: <core> [parser/sdp/sdp.c:229]: Invalid payload location
Sep 9 17:28:19 ch38 kamailio[24802]: ERROR: <core> [parser/sdp/sdp.c:213]: Invalid payload location
Sep 9 17:28:19 ch38 kamailio[24802]: ERROR: <core> [parser/sdp/sdp.c:229]: Invalid payload location
Sep 9 17:28:19 ch38 kamailio[24802]: ERROR: <core> [parser/sdp/sdp.c:213]: Invalid payload location
Sep 9 17:28:21 ch38 kamailio[24850]: ERROR: registrar [save.c:506]: invalid cseq for aor <90756153105>
Sep 9 17:28:21 ch38 kamailio[24865]: ERROR: <core> [tcp_main.c:4322]: connect 212.147.50.253:19614 failed (timeout)
Sep 9 17:28:22 ch38 kamailio[24865]: ERROR: <core> [tcp_main.c:4322]: connect 212.147.50.253:19614 failed (timeout)
Sep 9 17:28:23 ch38 kamailio[24714]: ERROR: <core> [parser/sdp/sdp.c:213]: Invalid payload location
Sep 9 17:28:23 ch38 kamailio[24714]: ERROR: <core> [parser/sdp/sdp.c:213]: Invalid payload location
Sep 9 17:28:23 ch38 kamailio[24714]: ERROR: <core> [parser/sdp/sdp.c:229]: Invalid payload location
Sep 9 17:28:23 ch38 kamailio[24714]: ERROR: <core> [parser/sdp/sdp.c:213]: Invalid payload location
Sep 9 17:28:23 ch38 kamailio[24714]: ERROR: <core> [parser/sdp/sdp.c:229]: Invalid payload location
Sep 9 17:28:23 ch38 kamailio[24714]: ERROR: <core> [parser/sdp/sdp.c:213]: Invalid payload location
Sep 9 17:28:25 ch38 kamailio[24865]: ERROR: <core> [tcp_main.c:4322]: connect 212.147.50.253:19614 failed (timeout)
Sep 9 17:28:25 ch38 kamailio[24850]: ERROR: registrar [save.c:506]: invalid cseq for aor <90756153105>
Sep 9 17:28:28 ch38 kamailio[24865]: ERROR: <core> [tcp_main.c:4322]: connect 212.147.50.253:19614 failed (timeout)
Sep 9 17:28:29 ch38 kamailio[24850]: ERROR: registrar [save.c:506]: invalid cseq for aor <90756153105>
Sep 9 17:28:31 ch38 kamailio[24737]: ERROR: <core> [tcp_main.c:700]: ERROR: wbufq_add(702 bytes): write queue full or timeout (32406, total 32406, last write 2 s ago)
Sep 9 17:28:31 ch38 kamailio[24737]: ERROR: tm [../../forward.h:170]: msg_send: ERROR: tcp_send failed
Sep 9 17:28:31 ch38 kamailio[24737]: ERROR: tm [t_fwd.c:1385]: ERROR: t_send_branch: sending request on branch 0 failed
Sep 9 17:28:31 ch38 kamailio[24737]: ERROR: sl [sl_funcs.c:282]: ERROR: sl_reply_error used: Unfortunately error on sending to next hop occurred (477/SL)
Sep 9 17:28:31 ch38 kamailio[24865]: ERROR: <core> [tcp_main.c:3595]: handle_ser_child: ERROR: received CON_ERROR for 0x7fa32b835390 (id 173139), refcnt 2, flags 0x3096
Sep 9 17:28:32 ch38 kamailio[24865]: ERROR: <core> [tcp_main.c:4322]: connect 212.147.50.253:19614 failed (timeout)
Sep 9 17:28:33 ch38 kamailio[24850]: ERROR: registrar [save.c:506]: invalid cseq for aor <90756153105>
Sep 9 17:28:34 ch38 kamailio[24865]: ERROR: <core> [tcp_main.c:4322]: connect 212.147.50.253:19614 failed (timeout)
Sep 9 17:28:43 ch38 kamailio[24763]: ERROR: <core> [parser/sdp/sdp.c:213]: Invalid payload location

De : sr-users-bounces-cR8azDVoa3IcDhw6gZKtMWD2FQJk+8+***@public.gmane.org<mailto:sr-users-bounces-***@public.gmane.orgp-router.org> [mailto:sr-users-bounces-cR8azDVoa3IcDhw6gZKtMWD2FQJk+8+***@public.gmane.org]<mailto:[mailto:sr-users-bounces-cR8azDVoa3IcDhw6gZKtMWD2FQJk+8+***@public.gmane.org]> De la part de Laurent Schweizer
Envoyé : mardi 9 septembre 2014 16:02
À : Kamailio (SER) - Users Mailing List; miconda-***@public.gmane.org<mailto:***@gmail.com>
Objet : Re: [SR-Users] TCP SYN only

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-bounces-cR8azDVoa3IcDhw6gZKtMWD2FQJk+8+***@public.gmane.org<mailto:sr-users-bounces-***@public.gmane.orgp-router.org> [mailto:sr-users-bounces-cR8azDVoa3IcDhw6gZKtMWD2FQJk+8+***@public.gmane.org]<mailto:[mailto:sr-users-bounces-cR8azDVoa3IcDhw6gZKtMWD2FQJk+8+***@public.gmane.org]> De la part de Laurent Schweizer
Envoyé : mardi 9 septembre 2014 15:38
À : miconda-***@public.gmane.org<mailto:miconda-***@public.gmane.org>; 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

Daniel-Constantin Mierla

2014-09-10 16:29:28 UTC

Permalink

Hello,

the logs on tcp are mostly about the remote closing the connection. So
nothing wrong about tcp reported by kamailio.

Maybe you can look at the tcp connections details via rpc commands and
see if you can spot a reason there:
-
http://www.kamailio.org/docs/docbooks/devel/rpc_list/rpc_list.html#core.tcp_info

You can run them via kamcmd.

Cheers,
Daniel

Post by Daniel-Constantin Mierla
Hello,
I have check again the log file and I see other error tcp error
reading and parsing
Any idea ?
Laurent
invalid cseq for aor <90756153105>
invalid cseq for aor <90756153105>
error reading: Connection reset by peer (104)
ERROR: tcp_read_req: error reading
invalid cseq for aor <90756153105>
invalid cseq for aor <90756153105>
Sep 9 17:27:20 ch38 kamailio[24801]: ERROR: <core>
[parser/sdp/sdp.c:213]: Invalid payload location
Sep 9 17:27:20 ch38 kamailio[24801]: ERROR: <core>
[parser/sdp/sdp.c:213]: Invalid payload location
Sep 9 17:27:20 ch38 kamailio[24801]: ERROR: <core>
[parser/sdp/sdp.c:229]: Invalid payload location
Sep 9 17:27:20 ch38 kamailio[24801]: ERROR: <core>
[parser/sdp/sdp.c:213]: Invalid payload location
Sep 9 17:27:20 ch38 kamailio[24801]: ERROR: <core>
[parser/sdp/sdp.c:229]: Invalid payload location
Sep 9 17:27:20 ch38 kamailio[24801]: ERROR: <core>
[parser/sdp/sdp.c:213]: Invalid payload location
invalid cseq for aor <90756153105>
invalid cseq for aor <90756153105>
invalid cseq for aor <90756153105>
Sep 9 17:27:49 ch38 kamailio[24717]: ERROR: <core>
[parser/sdp/sdp.c:213]: Invalid payload location
Sep 9 17:27:49 ch38 kamailio[24717]: ERROR: <core>
[parser/sdp/sdp.c:213]: Invalid payload location
Sep 9 17:27:49 ch38 kamailio[24717]: ERROR: <core>
[parser/sdp/sdp.c:229]: Invalid payload location
Sep 9 17:27:49 ch38 kamailio[24717]: ERROR: <core>
[parser/sdp/sdp.c:213]: Invalid payload location
Sep 9 17:27:49 ch38 kamailio[24717]: ERROR: <core>
[parser/sdp/sdp.c:229]: Invalid payload location
Sep 9 17:27:49 ch38 kamailio[24717]: ERROR: <core>
[parser/sdp/sdp.c:213]: Invalid payload location
error reading: Connection reset by peer (104)
ERROR: tcp_read_req: error reading
Sep 9 17:27:56 ch38 kamailio[24851]: ERROR: <core>
600#015#012Content-Length: 0#015#012#015#012>
ERROR: receive_msg: parse_msg failed
error reading: Connection timed out (110)
ERROR: tcp_read_req: error reading
error reading: Connection reset by peer (104)
ERROR: tcp_read_req: error reading
connect 212.147.50.253:19614 failed (timeout)
connect 212.147.50.253:19614 failed (timeout)
connect 212.147.50.253:19614 failed (timeout)
invalid cseq for aor <90756153105>
invalid cseq for aor <90756153105>
invalid cseq for aor <90756153105>
connect 212.147.50.253:19614 failed (timeout)
invalid cseq for aor <90756153105>
Sep 9 17:28:19 ch38 kamailio[24802]: ERROR: <core>
[parser/sdp/sdp.c:213]: Invalid payload location
Sep 9 17:28:19 ch38 kamailio[24802]: ERROR: <core>
[parser/sdp/sdp.c:213]: Invalid payload location
Sep 9 17:28:19 ch38 kamailio[24802]: ERROR: <core>
[parser/sdp/sdp.c:229]: Invalid payload location
Sep 9 17:28:19 ch38 kamailio[24802]: ERROR: <core>
[parser/sdp/sdp.c:213]: Invalid payload location
Sep 9 17:28:19 ch38 kamailio[24802]: ERROR: <core>
[parser/sdp/sdp.c:229]: Invalid payload location
Sep 9 17:28:19 ch38 kamailio[24802]: ERROR: <core>
[parser/sdp/sdp.c:213]: Invalid payload location
invalid cseq for aor <90756153105>
connect 212.147.50.253:19614 failed (timeout)
connect 212.147.50.253:19614 failed (timeout)
Sep 9 17:28:23 ch38 kamailio[24714]: ERROR: <core>
[parser/sdp/sdp.c:213]: Invalid payload location
Sep 9 17:28:23 ch38 kamailio[24714]: ERROR: <core>
[parser/sdp/sdp.c:213]: Invalid payload location
Sep 9 17:28:23 ch38 kamailio[24714]: ERROR: <core>
[parser/sdp/sdp.c:229]: Invalid payload location
Sep 9 17:28:23 ch38 kamailio[24714]: ERROR: <core>
[parser/sdp/sdp.c:213]: Invalid payload location
Sep 9 17:28:23 ch38 kamailio[24714]: ERROR: <core>
[parser/sdp/sdp.c:229]: Invalid payload location
Sep 9 17:28:23 ch38 kamailio[24714]: ERROR: <core>
[parser/sdp/sdp.c:213]: Invalid payload location
connect 212.147.50.253:19614 failed (timeout)
invalid cseq for aor <90756153105>
connect 212.147.50.253:19614 failed (timeout)
invalid cseq for aor <90756153105>
ERROR: wbufq_add(702 bytes): write queue full or timeout (32406,
total 32406, last write 2 s ago)
msg_send: ERROR: tcp_send failed
t_send_branch: sending request on branch 0 failed
ERROR: sl_reply_error used: Unfortunately error on sending to next hop
occurred (477/SL)
handle_ser_child: ERROR: received CON_ERROR for 0x7fa32b835390 (id
173139), refcnt 2, flags 0x3096
connect 212.147.50.253:19614 failed (timeout)
invalid cseq for aor <90756153105>
connect 212.147.50.253:19614 failed (timeout)
Sep 9 17:28:43 ch38 kamailio[24763]: ERROR: <core>
[parser/sdp/sdp.c:213]: Invalid payload location
de* Laurent Schweizer
*Envoyé :* mardi 9 septembre 2014 16:02
*Objet :* Re: [SR-Users] TCP SYN only
# 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* Laurent Schweizer
*Envoyé :* mardi 9 septembre 2014 15:38
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 dont 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
error reading: Connection reset by peer (104)
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
error reading: Connection timed out (110)
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
connect 77.29.142.196:49927 failed
connect 77.29.142.196:49927 failed
_______________________________________________
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users

--
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

Camille Oudot

2014-09-09 13:18:35 UTC

Permalink

Le Tue, 9 Sep 2014 12:40:15 +0000,

Post by Laurent Schweizer
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 ?

Is your machine using netfilter's conntrack module? If yes, you might
have to raise the net.nf_conntrack_max value also.

Regards,

--
Camille

Laurent Schweizer

2014-09-09 13:29:20 UTC

Permalink

I don't have installed conntrack and /proc/net/ip_conntrack is not exsiting so I don't think that I'm using it .

Laurent

-----Message d'origine-----
De : sr-users-***@lists.sip-router.org [mailto:sr-users-***@lists.sip-router.org] De la part de Camille Oudot
Envoyé : mardi 9 septembre 2014 15:19
À : sr-***@lists.sip-router.org
Objet : Re: [SR-Users] TCP SYN only

Le Tue, 9 Sep 2014 12:40:15 +0000,

Post by Laurent Schweizer
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 ?

Is your machine using netfilter's conntrack module? If yes, you might have to raise the net.nf_conntrack_max value also.

Regards,

--
Camille

_______________________________________________
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-***@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users

Continue reading on narkive:

Search results for '[SR-Users] TCP SYN only' (Questions and Answers)

replies

How does a SYN attack deny service?

started 2006-10-12 20:40:42 UTC

internet

replies

what are the most important TCP/IP protocols?

started 2008-09-16 20:01:59 UTC

computer networking

replies

How to stop SYN FLOOD attacks?