Hi all,
Currently trying to use Kamailio as a passthrough to some FreeSWITCH boxes.
When receiving an invite from FreeSWITCH which contains a Route header including received information, example below;
Route: sip:201@10.10.2.5:5072;lr;received=sip:[PUBLIC_IP]:45126
When using loose_route() Kamailio still send the invite to the rfc1918 address instead of the received IP:PORT in the Route header.
Am I misunderstanding how this should work?
Hello,
On 01/08/16 14:14, Luke Milbourne wrote:
if you use path module, have you enabled the option to use the received parameter?
https://www.kamailio.org/docs/modules/stable/modules/path.html#idp38033932
Cheers, Daniel
Hi Daniel,
Yep, I've got the below in my kamailio.cfg
modparam("path", "use_received", 1)
Kind regards, Luke
On 1 August 2016 at 13:25, Daniel-Constantin Mierla miconda@gmail.com wrote:
Is it correct to use loose_route() along side the path module?
On 1 August 2016 at 13:33, Luke Milbourne luke.milbourne@gmail.com wrote:
Hi All,
I've been going through my script against other examples on the internet and cannot see any differences, also changing use_received between 1 and 0 makes no different.
Kamailio still uses the Contact header instead of the Route header.
If any one has any suggestions it would be very much appreciated, but I'll continue going through the config line by line.
Kind regards, Luke
On 1 August 2016 at 13:46, Luke Milbourne luke.milbourne@gmail.com wrote:
Luke,
This is actually the behavior I would expect, though admittedly I've never tried to rely on received= parameter routing for requests (I wasn't aware that was something that should be supported).
However, you're probably better of addressing your NAT issues in a different part of your request lifecycle. Could you share a bit more about the setup you're using here? Is this Freeswitch dialing out to a registered endpoint? Where are registrations being handled? How is FS creating the route headers?
If you just start with a layout if your infrastructure it'll probably answer all those questions and we can come up with a solution from there.
Best, Colin
On Mon, Aug 1, 2016 at 11:57 AM Luke Milbourne luke.milbourne@gmail.com wrote:
Hello,
yes, loose_route() should be used there. Can you add a log message and print $ru and $du before and after loose_route() in config and then send the result to this mailing list?
Btw, what version of Kamailio are you using?
Cheers, Daniel
On 01/08/16 14:46, Luke Milbourne wrote:
Morning Gents,
Firstly, thanks for taking the time to reply :)
Kamailio is doing the NAT detection and simply acting as a passthrough to FreeSWITCH (which handles all SIP registrations etc).
Will setup the log lines shortly and share the results.
kamailio -V outputs;
version: kamailio 4.3.4 (x86_64/linux) 83e842 flags: STATS: Off, USE_TCP, USE_TLS, USE_SCTP, TLS_HOOKS, USE_RAW_SOCKS, DISABLE_NAGLE, USE_MCAST, DNS_IP_HACK, SHM_MEM, SHM_MMAP, PKG_MALLOC, DBG_QM_MALLOC, 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: 83e842 compiled on 18:22:39 Jan 26 2016 with gcc 4.9.2
Kind regards, Luke - Chicane Support
On 2 August 2016 at 07:52, Daniel-Constantin Mierla miconda@gmail.com wrote:
I added the below xlog lines into my script:
xlog("L_NOTICE", "Before loose_route: $si -> $ru - $du\n"); xlog("L_NOTICE", "Before record_route: $si -> $ru - $du\n"); xlog("L_NOTICE", "After both: $si -> $ru - $du\n");
Which generated the below output in syslog:
Aug 2 09:46:11 ip-10-10-2-5 /sbin/kamailio[529]: NOTICE: <script>: Before loose_route: 10.10.0.25 -> sip:201@192.168.1.114:5062 - <null> Aug 2 09:46:11 ip-10-10-2-5 /sbin/kamailio[529]: NOTICE: <script>: Before record_route: 10.10.0.25 -> sip:201@192.168.1.114:5062 - <null> Aug 2 09:46:11 ip-10-10-2-5 /sbin/kamailio[529]: NOTICE: <script>: After both: 10.10.0.25 -> sip:201@192.168.1.114:5062 - <null>
Seems that the destination URI is never set, the Route header is below:
Route: sip:201@10.10.2.5:5072;lr;received=sip:[PUBLIC_IP]:45126
The use_received modparam for path is also set to 1.
Any idea's/suggestions are greatly appreciated :)
Kind regards, Luke
On 2 August 2016 at 09:40, Luke Milbourne luke.milbourne@gmail.com wrote:
Hi Daniel,
I've added some more logging and can see loose_route() is returning -1 - route calculation has been unsuccessful.
Is there a way of finding out why this is the case?
Kind regards, Luke
On 2 August 2016 at 09:49, Luke Milbourne luke.milbourne@gmail.com wrote:
Hello,
set debug=3 in kamailio.cfg and look at log messages in syslog.
If you find it too verbose, use dispatcher module and set debug level only for core and rr modules to 3.
Cheers, Daniel
On 03/08/16 13:22, Luke Milbourne wrote:
-
Colin Morelli -
Daniel-Constantin Mierla -
Luke Milbourne