From khorsmann@gmail.com Thu Jul 4 15:58:25 2019 From: Karsten Horsmann To: sr-users@lists.kamailio.org Subject: Re: [SR-Users] kamailio as UAC and NAPTR / sendsocket question Date: Thu, 04 Jul 2019 15:58:10 +0200 Message-ID: In-Reply-To: MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============1009146200==" --===============1009146200== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Hi Frederico and Daniel. Today i found also the "tcp_reuse_port" documentation. Thanks Federico for the hint. With that paramenter to yes - i have still the issue that kamailio generates on force_send_socket or $fs (which is the same IMHO at the end) generates UDP. It forced the right IP but the transport is wrong. Without tcp_reuse_port it was the same stuff. I also tried a new listen param like "listen tcp:212.zz.xx.ab:8000" and point it to that direction. $fs and force_send_socket seems to be working with ip in that case. At the bottom I xlogged the du prameter. It feels like an special special corner case with naptr overwrite, uac and empty du tcp. $fs=3D"212.zz.xx.ab" 13:07:35.839094 IP (tos 0x10, ttl 64, id 62416, offset 0, flags [none], proto UDP (17), length 472) 212.zz.xx.ab.sip > 217.0.26.67.sip: [bad udp cksum 0x9796 -> 0x68cb!] SIP, length: 444 REGISTER sip:sip-trunk.telekom.de SIP/2.0 Via: SIP/2.0/UDP 212.zz.xx.ab;branch=3Dz9hG4bKc689.5afe94c5000000000000000000000000.0;i=3D0 To: From: ;tag=3D0e37b8f111de3a41f982d1e82cae2fe3-b388 CSeq: 10 REGISTER Call-ID: 547d384144e9b23e-7166(a)212.zz.xx.ab Max-Forwards: 70 Content-Length: 0 User-Agent: SBC-OS Contact: Expires: 360 Jul 4 13:10:01 siptrunk1 /usr/sbin/kamailio[9380]: INFO: