13 Nov
2019
13 Nov
'19
12:36 a.m.
Back to this one, somehow it got on the side with busy end of summer and autumn ...
I tried to reproduce, but I couldn't get the same result. In my case it worked fine
with the current master branch. I made the following minimal config:
```
#!KAMAILIO
debug=3
children=4
mhomed=1
listen=tcp:192.168.56.1:5060
listen=tcp:127.0.0.1:5060
loadmodule "tm.so"
loadmodule "sl.so"
loadmodule "corex.so"
loadmodule "pv.so"
loadmodule "textops.so"
loadmodule "rr.so"
request_route {
if(is_method("INVITE")) {
record_route();
}
$du = "sip:192.168.56.1:5080;transport=tcp";
t_relay();
}
```
The INVITE was sent to 127.0.0.1:5060 and the outgoing one from kamailio had two
Record-Route headers:
```
INVITE sip:test@kamailio.org SIP/2.0
Record-Route:
<sip:192.168.56.1;transport=tcp;r2=on;lr;ftag=76ff7a07-c091-4192-84a0-d56e91fe104f>
Record-Route:
<sip:127.0.0.1;transport=tcp;r2=on;lr;ftag=76ff7a07-c091-4192-84a0-d56e91fe104f>
Via: SIP/2.0/TCP 192.168.56.1;branch=z9hG4bKac3f.6b055b9438495fd0fb5e6b08f07611d5.0;i=1
Via: SIP/2.0/UDP
192.168.178.8:5040;received=127.0.0.1;branch=z9hG4bKac3fd.jasefjsdfas;rport=54075
```
I also changed the order of listen parameters and the same result with two record-route
headers.
Can you test again with latest master and see if you get the same result like in the past?
If yes, are the two IP addresses assigned to different network interfaces/cards, or they
are assigned to the same network interface?
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/issues/2033#issuecomment-553126580