From sos@sokhapkin.dyndns.org Fri Oct 29 17:54:57 2010
From: Sergey Okhapkin <sos@sokhapkin.dyndns.org>
To: sr-users@lists.kamailio.org
Subject: [SR-Users] NAT ping replies
Date: Fri, 29 Oct 2010 11:55:35 -0400
Message-ID: <201010291155.35920.sos@sokhapkin.dyndns.org>
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="===============1743578380=="

--===============1743578380==
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable

Kamailio 3.1 log is filled with lines like

Oct 29 03:32:46 west /usr/local/sbin/kamailio[632]: INFO: <script>: incoming =

reply from udp:188.62.4.186:65333 SIP/2.0 404 Not Found  Via: SIP/2.0/UDP=20
204.74.213.5:5060;branch=3D0  From: <sip:pinger(a)sip.callwithus.com>;tag=3D3=
993f0c =20
To: <sip:188.62.4.186:65333>  Call-ID: aff32da5-89ef0136-71dc8c5(a)204.74.213=
.5 =20
CSeq: 1 OPTIONS  Content-Length: 0
Oct 29 03:32:46 west /usr/local/sbin/kamailio[632]: INFO: <core>=20
[forward.c:774]: broken reply to forward - no 2nd via

Shouldn't replies to NAT ping messages be silently dropped like in 1.4?


--===============1743578380==--