19 Nov
2014
19 Nov
'14
1:29 p.m.
Hello,
I reviewed the changelogs.
I can see the following updates that could change the previous behaviour:
commit 42897d422b60edeac393201326a3e71318445e62
Author: Daniel-Constantin Mierla <miconda(a)gmail.com>
Date: Mon Sep 22 22:04:39 2014 +0200
core: add received parameter to via if rport parameter is present
- required by RFC3581, section 4.
(cherry picked from commit a1e96cbd5a3b43598c59cb50693e6b739801b804)
commit a52c0024723a59d90c3c3966d5deadaf8b0d4440
Author: Daniel-Constantin Mierla <miconda(a)gmail.com>
Date: Sun Sep 28 12:48:53 2014 +0200
core: helper functions to get addr and port to be used in signaling from
socket info
(cherry picked from commit c725f1dec14863e069bfd1e5c26857a1005528d5)
But I can't explain why the same nat_uac_test doesn't behaves the same
between the two versions.
Regards,
Igor.
De : Igor Potjevlesch [mailto:igor.potjevlesch@gmail.com]
Envoyé : mardi 18 novembre 2014 14:00
À : amit(a)avhan.com; 'Kamailio (SER) - Users Mailing List'
Objet : RE: [SR-Users] Issue with 4.2.0 and nathelper and/or rtpproxy
Hi Amit,
The config is the same between the two version. Even this line.
Regards,
Igor.
De : sr-users-bounces(a)lists.sip-router.org
<mailto:sr-users-bounces@lists.sip-router.org>
[mailto:sr-users-bounces@lists.sip-router.org] De la part de Amit Patkar
Envoyé : mardi 18 novembre 2014 13:16
À : sr-users(a)lists.sip-router.org <mailto:sr-users@lists.sip-router.org>
Objet : Re: [SR-Users] Issue with 4.2.0 and nathelper and/or rtpproxy
Hi
You should compare this line in your configuration file.
if (nat_uac_test("18")) {
It may be using different parameters.
Regards,
Amit
On 11/18/2014 5:23 PM, Igor Potjevlesch wrote:
Hello,
I can reproduce the issue on a pre-production system.
So, I downgraded to 4.1.5.
Here is the difference:
The INVITE comes into NATDETECT:
route[NATDETECT] {
xlog("ENTERING NATDETECT routes\n");
#!ifdef WITH_NAT
force_rport();
if (nat_uac_test("18")) {
if (is_method("REGISTER")) {
fix_nated_register();
} else {
add_contact_alias();
}
setflag(FLT_NATS);
xlog("NAT_UAC_TEST OK\n");
}
#!endif
return;
}
With Kamailio 4.2.0, the NAT_UAC_TEST returns true whereas with 4.1.5
returns false.
I also look at the force_rport. Im not sure if its related, but with
4.2.0, the Via looks like:
Via: SIP/2.0/UDP
PST_GW:5060;received=PST_GW;rport=5060;branch=z9hG4bK-34d5-1416308856-4847-4
41\r\n
In 4.1.5:
Via: SIP/2.0/UDP
PST_GW:5060;rport=5060;branch=z9hG4bK-2e3d-1416311184-4886-146\r\n
The received parameters is not added. Note that PSTN_GW refers to a public
IP address (out of RFC1918 and Carrier Grade NAT).
Regards,
Igor.
De : Igor Potjevlesch [mailto:igor.potjevlesch@gmail.com]
Envoyé : mardi 18 novembre 2014 11:43
À : sr-users(a)lists.sip-router.org <mailto:users@lists.sip-router.org>
Objet : Issue with 4.2.0 and nathelper and/or rtpproxy
Hello,
Since I done the upgrade of Kamailio into 4.2.0, there are, at least, one
new case where the RTPProxy is launched.
When I got an INVITE from my PSTN Gateway, for unknown reason (and not for
all calls), Record-Route is append with nat=yes. I looked into an old trace
and this behaviour didnt exist.
What could have changed that can explain this?
Regards,
Igor.
_______________________________________________
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users(a)lists.sip-router.org <mailto:sr-users@lists.sip-router.org>
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users