16 Feb
2018
16 Feb
'18
9:06 p.m.
Wondering if you actually read properly my previous response. There is
no "nat=yes" in Route params because the call (via initial INVITE) is
not marked as natted -- look at what is sent to the network for the
initial INVITE in the Record-Route header.
Daniel
On 16.02.18 10:45, Pau Giralt wrote:
These are the complete logs for the previous call:
[...]
As you can see check_route_param(): params are <;transport=tcp;lr>
2018-02-15 18:16 GMT+01:00 Daniel-Constantin Mierla <miconda(a)gmail.com
<mailto:miconda@gmail.com>>:
Based on the logs, there is no check_route_param() executed.
Actually, it is an initial INVITE, doesn't have a to-tag, so there
is no Route header added previously by kamailio where
check_route_param() can work on.
Looking at the headers, this initial INVITE has Via and Contact
with public addresses (maybe UA is using stun), only the SDP seems
to have carrier grand nat address. You have to adjust the
parameter for nat_uac_test() in order to detect it is a natted call.
Cheers,
Daniel
On 15.02.18 15:35, Pau Giralt wrote:
--
Daniel-Constantin Mierla
www.twitter.com/miconda -- www.linkedin.com/in/miconda
Kamailio Advanced Training - March 5-7, 2018, Berlin - www.asipto.com
Kamailio World Conference - May 14-16, 2018 - www.kamailioworld.com
My kamailio version is:
version: kamailio 4.4.6 (x86_64/linux) becbde
flags: STATS: Off, USE_TCP, USE_TLS, USE_SCTP, TLS_HOOKS,
DISABLE_NAGLE, USE_MCAST, DNS_IP_HACK, SHM_MEM, SHM_MMAP,
PKG_MALLOC, Q_MALLOC, F_MALLOC, TLSF_MALLOC, DBG_SR_MEMORY,
USE_FUTEX, FAST_LOCK-ADAPTIVE_WAIT, USE_DNS_CACHE,
USE_DNS_FAILOVER, USE_NAPTR, USE_DST_BLACKLIST, HAVE_RESOLV_RES
ADAPTIVE_WAIT_LOOPS=1024, MAX_RECV_BUFFER_SIZE 262144, MAX_LISTEN
16, MAX_URI_SIZE 1024, BUF_SIZE 65535, DEFAULT PKG_SIZE 8MB
poll method support: poll, epoll_lt, epoll_et, sigio_rt, select.
id: becbde
compiled on 08:18:45 Jul 3 2017 with gcc 5.4.0
I've pasted the logs below.
( ... )
[...]
Thanks!
2018-02-15 15:02 GMT+01:00 Daniel-Constantin Mierla
<miconda(a)gmail.com <mailto:miconda@gmail.com>>:
Hello,
first, what is the version of kamailio?
Then, can you load debugger module and set cfgtrace=1, then
send here all log messages for a case exposing this issue? It
should show what actions are executed from config.
Cheers,
Daniel
On 15.02.18 12:08, Pau Giralt wrote:
--
Daniel-Constantin Mierla
www.twitter.com/miconda <http://www.twitter.com/miconda> --
www.linkedin.com/in/miconda <http://www.linkedin.com/in/miconda>
Kamailio Advanced Training - March 5-7, 2018, Berlin - www.asipto.com
<http://www.asipto.com>
Kamailio World Conference - May 14-16, 2018 - www.kamailioworld.com
<http://www.kamailioworld.com>
Hi!
I'm working with kamailio and rtpproxy.
When I configure the clients to send sip messages through
TCP adding the ";transport=tcp" in the sip message the
rtpproxy is not working anymore.
The code is never passing the point pasted below, inside
route[NATMANAGE] in kamailio.cfg
|if (!(isflagset(FLT_NATS) || isbflagset(FLB_NATB))) return; |
Therefore, |rtpproxy_manage("co");| is never reached.
Could it be a parsing problem? (
|check_route_param("nat=yes")| )
The config file is exactly the same as the one provided in
the kamailio repository (the default one)
Thanks!
_______________________________________________
Kamailio (SER) - Users Mailing List
sr-users(a)lists.kamailio.org <mailto:sr-users@lists.kamailio.org>
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
<https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users>
--
Daniel-Constantin Mierla
www.twitter.com/miconda <http://www.twitter.com/miconda> --
www.linkedin.com/in/miconda <http://www.linkedin.com/in/miconda>
Kamailio Advanced Training - March 5-7, 2018, Berlin - www.asipto.com
<http://www.asipto.com>
Kamailio World Conference - May 14-16, 2018 - www.kamailioworld.com
<http://www.kamailioworld.com>