<div dir="ltr"><div class="gmail_default" style="font-family:arial,helvetica,sans-serif">Daniel,</div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif">Just to make sure: did you try to define the "listen" parameters explicitly? The problem happens only when <span style="font-family:Arial,Helvetica,sans-serif">the "listen" parameters are</span></div>defined in the Kamailio configuration<span class="gmail_default" style="font-family:arial,helvetica,sans-serif">. When the "listens" are not configured then everything works correctly.</span><div><span class="gmail_default" style="font-family:arial,helvetica,sans-serif">So, the problem happens when it is necessary to configure not standard ports for the particular interface(s) ... </span><br><br></div><div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif">Thank you,</div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif">Leonid</div><br></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Wed, Aug 14, 2019 at 4:11 PM Daniel-Constantin Mierla <<a href="mailto:miconda@gmail.com">miconda@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div bgcolor="#FFFFFF">
<p>Hello,</p>
<p>I tried to reproduce a while ago on a system with many network
interfaces, but all was fine. I guess it has to do with network/ip
routing configuration there.<br>
</p>
<p>Open the issue, maybe other people will give some input based on
their experience.</p>
<p>Cheers,<br>
Daniel<br>
</p>
<div class="gmail-m_6645075114557351239moz-cite-prefix">On 14.08.19 13:37, Leonid Fainshtein
wrote:<br>
</div>
<blockquote type="cite">
<div dir="ltr">
<div class="gmail_default" style="font-family:arial,helvetica,sans-serif">Hello Daniel,</div>
<div class="gmail_default" style="font-family:arial,helvetica,sans-serif">Should I open a
bug regarding this issue?</div>
<div class="gmail_default" style="font-family:arial,helvetica,sans-serif"><br>
</div>
<div>
<div dir="ltr" class="gmail-m_6645075114557351239gmail_signature"><span class="gmail_default" style="font-family:arial,helvetica,sans-serif">Thank you</span>,<br>
Leonid</div>
</div>
</div>
<br>
<div class="gmail_quote">
<div dir="ltr" class="gmail_attr">On Sun, Jul 21, 2019 at 1:26
PM Leonid Fainshtein <<a href="mailto:leonid.fainshtein@xorcom.com" target="_blank">leonid.fainshtein@xorcom.com</a>>
wrote:<br>
</div>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div dir="ltr">
<div class="gmail_default" style="font-family:arial,helvetica,sans-serif">Hello
Daniel,</div>
<div class="gmail_default" style="font-family:arial,helvetica,sans-serif">The traces
and the simplified config file can be downloaded by using
the link below:</div>
<div class="gmail_default" style="font-family:arial,helvetica,sans-serif"><br>
</div>
<div class="gmail_default" style="font-family:arial,helvetica,sans-serif"><a href="http://updates.xorcom.com/~xorcom/2019-jul-21.tar.gz" target="_blank">http://updates.xorcom.com/~xorcom/2019-jul-21.tar.gz</a><br>
</div>
<div class="gmail_default" style="font-family:arial,helvetica,sans-serif"><br>
</div>
<div class="gmail_default" style="font-family:arial,helvetica,sans-serif">Regarding
to an IP route from the local IP <span style="font-family:Arial,Helvetica,sans-serif">appearing
in Record-Route to the target IP. I don't have a special
route for it. But the </span><span style="font-family:Arial,Helvetica,sans-serif">net.ipv4.ip_forward
is enabled in the system.</span></div>
<div class="gmail_default" style="font-family:arial,helvetica,sans-serif"><span style="font-family:Arial,Helvetica,sans-serif">Anyway,
I'm sending you IP addresses and the current routing
table:</span></div>
<div class="gmail_default" style="font-family:arial,helvetica,sans-serif"><span style="font-family:Arial,Helvetica,sans-serif"> </span></div>
<div class="gmail_default"><font face="courier new,
monospace"># ip a<br>
2: ens32: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu
1500 qdisc fq_codel state UP group default qlen 1000<br>
link/ether 00:0c:29:ad:af:e9 brd ff:ff:ff:ff:ff:ff<br>
inet <a href="http://192.168.9.103/20" target="_blank">192.168.9.103/20</a>
brd 192.168.15.255 scope global dynamic ens32<br>
valid_lft 116999sec preferred_lft 116999sec<br>
inet6 fe80::20c:29ff:fead:afe9/64 scope link <br>
valid_lft forever preferred_lft forever<br>
3: lxdbr0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu
1500 qdisc noqueue state UP group default qlen 1000<br>
link/ether fe:d8:26:e7:21:dc brd ff:ff:ff:ff:ff:ff<br>
inet <a href="http://10.28.80.1/24" target="_blank">10.28.80.1/24</a> scope global
lxdbr0<br>
valid_lft forever preferred_lft forever<br>
inet6 fe80::501d:dbff:fe72:876e/64 scope link <br>
valid_lft forever preferred_lft forever<br>
5: vethHT3VX5@if4:
<BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc
noqueue master lxdbr0 state UP group default qlen 1000<br>
link/ether fe:d8:26:e7:21:dc brd ff:ff:ff:ff:ff:ff
link-netnsid 0<br>
inet6 fe80::fcd8:26ff:fee7:21dc/64 scope link <br>
valid_lft forever preferred_lft forever<br>
<br>
</font></div>
<div class="gmail_default"><font face="courier new,
monospace"># ip r<br>
default via 192.168.0.1 dev ens32 proto dhcp src
192.168.9.103 metric 100 <br>
<a href="http://10.28.80.0/24" target="_blank">10.28.80.0/24</a> dev lxdbr0
proto kernel scope link src 10.28.80.1 <br>
<a href="http://192.168.0.0/20" target="_blank">192.168.0.0/20</a> dev ens32
proto kernel scope link src 192.168.9.103 <br>
192.168.0.1 dev ens32 proto dhcp scope link src
192.168.9.103 metric 100 <br>
</font></div>
<div>
<div dir="ltr" class="gmail-m_6645075114557351239gmail-m_389457387969098912m_-4896604996342057643gmail_signature"><br>
</div>
<div dir="ltr" class="gmail-m_6645075114557351239gmail-m_389457387969098912m_-4896604996342057643gmail_signature"><span class="gmail_default" style="font-family:arial,helvetica,sans-serif">Thank
you</span>,<br>
Leonid</div>
</div>
<br>
</div>
<br>
<div class="gmail_quote">
<div dir="ltr" class="gmail_attr">On Sun, Jul 21, 2019 at
9:35 AM Daniel-Constantin Mierla <<a href="mailto:miconda@gmail.com" target="_blank">miconda@gmail.com</a>> wrote:<br>
</div>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div dir="ltr">
<div>Can you load debugger module and enable cfgtrace to
see the actions executed in config file for such
INVITE - reproduce and send the log messages. Might be
an effect of something done there.</div>
<div><br>
</div>
<div>Did I asked if you have IP route from the local IP
appearing in Record-Route to the target IP address?
Kamailio has the rule of trying to reuse first the
local ip where the request was received also for
sending out.<br>
</div>
</div>
<br>
<div class="gmail_quote">
<div dir="ltr" class="gmail_attr">On Thu, Jul 18, 2019
at 2:09 PM Leonid Fainshtein <<a href="mailto:leonid.fainshtein@xorcom.com" target="_blank">leonid.fainshtein@xorcom.com</a>>
wrote:<br>
</div>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div dir="ltr">
<div class="gmail_default" style="font-family:arial,helvetica,sans-serif">Yes,
I have.</div>
<div class="gmail_default" style="font-family:arial,helvetica,sans-serif"><br>
</div>
<div>
<div dir="ltr" class="gmail-m_6645075114557351239gmail-m_389457387969098912gmail-m_-4896604996342057643gmail-m_-2005229189514266957gmail-m_-5021230384019393008gmail_signature">Best
regards,<br>
Leonid Fainshtein<br>
Xorcom Ltd</div>
</div>
<br>
</div>
<br>
<div class="gmail_quote">
<div dir="ltr" class="gmail_attr">On Thu, Jul 18,
2019 at 9:31 AM Daniel-Constantin Mierla <<a href="mailto:miconda@gmail.com" target="_blank">miconda@gmail.com</a>>
wrote:<br>
</div>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div dir="ltr">
<div>Hello,</div>
<div>traveling, so not much time available ...</div>
<div>I looked over the logs when expected socket
is not used, I couldn't spot any message about
selecting the socket, so there is a route from
them "wrong" socket to the destination.</div>
<div><br>
</div>
<div>Do you have "mhomed=1" in kamailio.cfg?</div>
<div><br>
</div>
<div>Cheers,<br>
</div>
<div>Daniel<br>
</div>
</div>
<br>
<div class="gmail_quote">
<div dir="ltr" class="gmail_attr">On Wed, Jul
17, 2019 at 5:27 PM Leonid Fainshtein <<a href="mailto:leonid.fainshtein@xorcom.com" target="_blank">leonid.fainshtein@xorcom.com</a>>
wrote:<br>
</div>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div dir="ltr">
<div dir="ltr">
<div class="gmail_default" style="font-family:arial,helvetica,sans-serif">Dear
Daniel,</div>
<div class="gmail_default" style="font-family:arial,helvetica,sans-serif">Did
you have a chance to check the traces?</div>
<div class="gmail_default" style="font-family:arial,helvetica,sans-serif"><br>
</div>
<div>
<div dir="ltr" class="gmail-m_6645075114557351239gmail-m_389457387969098912gmail-m_-4896604996342057643gmail-m_-2005229189514266957gmail-m_-5021230384019393008gmail-m_5493832268194904826gmail-m_-180027646461052478gmail_signature">Best
regards,<br>
Leonid<br>
</div>
</div>
</div>
<br>
<div class="gmail_quote">
<div dir="ltr" class="gmail_attr">On Wed,
Jul 10, 2019 at 9:15 AM Leonid
Fainshtein <<a href="mailto:leonid.fainshtein@xorcom.com" target="_blank">leonid.fainshtein@xorcom.com</a>>
wrote:<br>
</div>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Hello
Daniel,<br>
The requested traces can be downloaded
by using the link below:<br>
<br>
<a href="http://updates.xorcom.com/~xorcom/kam-tcp-problem.tar.gz" rel="noreferrer" target="_blank">http://updates.xorcom.com/~xorcom/kam-tcp-problem.tar.gz</a><br>
<br>
I don't use the force send socket option
and doesn't route out via<br>
dispatcher in this particular call flow.<br>
I found that the problem happens only
when the "listen" parameters are<br>
defined in the Kamailio configuration.<br>
Thus the server where I made the tests
have the following IPs configured:<br>
<br>
2: ens32:
<BROADCAST,MULTICAST,UP,LOWER_UP>
mtu 1500 qdisc fq_codel<br>
state UP group default qlen 1000<br>
link/ether 00:0c:29:ad:af:e9 brd
ff:ff:ff:ff:ff:ff<br>
inet <a href="http://192.168.9.103/20" rel="noreferrer" target="_blank">192.168.9.103/20</a>
brd 192.168.15.255 scope global dynamic
ens32<br>
3: lxdbr0:
<BROADCAST,MULTICAST,UP,LOWER_UP>
mtu 1500 qdisc noqueue<br>
state UP group default qlen 1000<br>
link/ether fe:d8:26:e7:21:dc brd
ff:ff:ff:ff:ff:ff<br>
inet <a href="http://10.28.80.1/24" rel="noreferrer" target="_blank">10.28.80.1/24</a>
scope global lxdbr0<br>
<br>
The request is accepted on 10.28.80.1
and forwarded from 192.168.9.103<br>
<br>
If I define:<br>
listen=udp:<a href="http://10.28.80.1:5060" rel="noreferrer" target="_blank">10.28.80.1:5060</a><br>
listen=tcp:<a href="http://10.28.80.1:5060" rel="noreferrer" target="_blank">10.28.80.1:5060</a><br>
listen=udp:<a href="http://192.168.9.103:5060" rel="noreferrer" target="_blank">192.168.9.103:5060</a><br>
listen=tcp:<a href="http://192.168.9.103:5060" rel="noreferrer" target="_blank">192.168.9.103:5060</a><br>
<br>
Then the problem occurs. Ref. files
syslog-bad.log and bad.cap.<br>
If I remove all of the 'listen'
parameters then the forwarded INVITE<br>
request is built properly. Ref. files
syslog-good.log and good.cap<br>
<br>
Best regards,<br>
Leonid Fainshtein<br>
Xorcom Ltd<br>
<br>
Best regards,<br>
Leonid Fainshtein<br>
Xorcom Ltd<br>
<br>
<br>
On Tue, Jul 9, 2019 at 9:53 AM
Daniel-Constantin Mierla<br>
<<a href="mailto:miconda@gmail.com" target="_blank">miconda@gmail.com</a>>
wrote:<br>
><br>
> Hello,<br>
><br>
> set debug = 3 in kamailio cfg and
reproduce this case. Send here all the<br>
> log messages printed by kamailio
from the moment it receives the request<br>
> till it sends it out.<br>
><br>
> Some further questions:<br>
><br>
> - do you use any force send
socket option?<br>
> - do you route out via
dispatcher? If yes, is the socket
attribute set?<br>
><br>
> Cheers,<br>
> Daniel<br>
><br>
> On 08.07.19 21:23, Leonid
Fainshtein wrote:<br>
> > Hello,<br>
> > The source address is correct:
192.168.0.31. I see it in tcpdump and<br>
> > also in sngrep.<br>
> ><br>
> > Thank you,<br>
> > Leonid<br>
> ><br>
> > On Mon, Jul 8, 2019 at 9:02 PM
Daniel-Constantin Mierla<br>
> > <<a href="mailto:miconda@gmail.com" target="_blank">miconda@gmail.com</a>>
wrote:<br>
> >> Hello,<br>
> >><br>
> >> when you look at the
network traffic 9e.g., with ngrep,
sngrep, ...)<br>
> >> what is shown as source
address for outbound leg?<br>
> >><br>
> >> Cheers,<br>
> >> Daniel<br>
> >><br>
> >> On 08.07.19 19:21, Leonid
Fainshtein wrote:<br>
> >>> I just found Daniel's
response to a similar question (ref.:<br>
> >>> <a href="https://lists.kamailio.org/pipermail/sr-users/2019-February/104853.html" rel="noreferrer" target="_blank">https://lists.kamailio.org/pipermail/sr-users/2019-February/104853.html</a>):<br>
> >>><br>
> >>> "check the routing
rules/table of the operating systems,
there should be<br>
> >>> some differences
between the two servers.<br>
> >>> If you mhomed=1 and an
unexpected interface is used for routing
out the<br>
> >>> traffic, it means that
the operating system has internal
routing rules that<br>
> >>> allow going from that
interface to the target address."<br>
> >>><br>
> >>> Don't see anything
suspicious in my server routing table:<br>
> >>><br>
> >>> default via
192.168.0.1 dev eno1 proto static<br>
> >>> <a href="http://10.159.65.0/24" rel="noreferrer" target="_blank">10.159.65.0/24</a>
dev lxdbr0 proto kernel scope link src
10.159.65.1<br>
> >>> <a href="http://172.200.4.0/24" rel="noreferrer" target="_blank">172.200.4.0/24</a>
dev eno1 proto kernel scope link src
172.200.4.1<br>
> >>> <a href="http://192.168.0.0/20" rel="noreferrer" target="_blank">192.168.0.0/20</a>
dev eno1 proto kernel scope link src
192.168.0.31<br>
> >>><br>
> >>> The request is
received on the lxdbr0 interface
(10.159.65.1) and sent<br>
> >>> out from the eno1
interface (192.168.0.31).<br>
> >>> I even tried to delete
the default route but nothing helped.
The<br>
> >>> request is sent out
with 10.159.65.1 in the via and
Record-Route<br>
> >>> fields...<br>
> >>><br>
> >>> Best regards,<br>
> >>> Leonid<br>
> >>><br>
> >>> On Thu, Jul 4, 2019 at
6:20 PM Leonid Fainshtein<br>
> >>> <<a href="mailto:leonid.fainshtein@xorcom.com" target="_blank">leonid.fainshtein@xorcom.com</a>>
wrote:<br>
> >>>> Hi,<br>
> >>>> Kamailio server
has two legs that are connected to
different networks.<br>
> >>>> I'm using Kamailio
v.5.2.3 and the "enable_double_rr" is
implicitly set to "1".<br>
> >>>> The leg "A" IP
address is 10.159.65.1<br>
> >>>> The leg "B" IP
address is 192.168.0.31<br>
> >>>> The call is
initiated from 10.159.65.18<br>
> >>>><br>
> >>>> According to the
"rr" module documentation, function
record_route()<br>
> >>>> should insert two
"Record_Route" header fields when a
request is<br>
> >>>> accepted on one
leg is should go out via the second leg.
This works as<br>
> >>>> expected in case
of UDP protocol:<br>
> >>>><br>
> >>>> INVITE <a href="http://sip:2000@192.168.6.106:5460" target="_blank">sip:2000@192.168.6.106:5460</a>;transport=UDP
SIP/2.0<br>
> >>>> Record-Route:
<a class="gmail-m_6645075114557351239moz-txt-link-rfc2396E"><sip:192.168.0.31;r2=on;lr;did=e2c.a191></a><br>
> >>>> Record-Route:
<a class="gmail-m_6645075114557351239moz-txt-link-rfc2396E"><sip:10.159.65.1;r2=on;lr;did=e2c.a191></a><br>
> >>>> Via: SIP/2.0/UDP<br>
> >>>>
192.168.0.31;branch=z9hG4bKcfa5.d64ecbd87d5315b5993c4ccf16f86537.0<br>
> >>>> Via: SIP/2.0/UDP
10.159.65.18:5060;rport=5060;branch=z9hG4bK3a9e9a4d<br>
> >>>><br>
> >>>> But when the TCP
protocol is used then the outbound
message looks like this:<br>
> >>>><br>
> >>>> INVITE <a href="http://sip:2005@192.168.0.178:35058" target="_blank">sip:2005@192.168.0.178:35058</a>;transport=tcp
SIP/2.0<br>
> >>>> Record-Route:
<a class="gmail-m_6645075114557351239moz-txt-link-rfc2396E"><sip:10.159.65.1;transport=tcp;lr;did=bb6.7dc1></a><br>
> >>>> Via: SIP/2.0/TCP<br>
> >>>>
10.159.65.1;branch=z9hG4bKc85a.14afc3867dd3220826f9b9940f78168f.0;i=3<br>
> >>>> Via: SIP/2.0/TCP
10.159.65.18:5060;rport=58616;branch=z9hG4bK1469331f<br>
> >>>><br>
> >>>> There are two
problems there:<br>
> >>>> a) only one
Record-Route with leg is inserted<br>
> >>>> b) the added "Via"
header field contains the leg "A" IP
address<br>
> >>>> instead of
expected leg "B" IP address
(192.168.0.31). In the LAN<br>
> >>>> trace I see that
in reality the message was sent from leg
"B".<br>
> >>>><br>
> >>>> Is it a bug?<br>
> >>>><br>
> >>>> Best regards,<br>
> >>>> Leonid Fainshtein<br>
> >>>
_______________________________________________<br>
> >>> Kamailio (SER) - Users
Mailing List<br>
> >>> <a href="mailto:sr-users@lists.kamailio.org" target="_blank">sr-users@lists.kamailio.org</a><br>
> >>> <a href="https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users" rel="noreferrer" target="_blank">https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users</a><br>
> >> --<br>
> >> Daniel-Constantin Mierla
-- <a href="http://www.asipto.com" rel="noreferrer" target="_blank">www.asipto.com</a><br>
> >> <a href="http://www.twitter.com/miconda" rel="noreferrer" target="_blank">www.twitter.com/miconda</a>
-- <a href="http://www.linkedin.com/in/miconda" rel="noreferrer" target="_blank">www.linkedin.com/in/miconda</a><br>
> >><br>
> --<br>
> Daniel-Constantin Mierla -- <a href="http://www.asipto.com" rel="noreferrer" target="_blank">www.asipto.com</a><br>
> <a href="http://www.twitter.com/miconda" rel="noreferrer" target="_blank">www.twitter.com/miconda</a>
-- <a href="http://www.linkedin.com/in/miconda" rel="noreferrer" target="_blank">www.linkedin.com/in/miconda</a><br>
><br>
</blockquote>
</div>
</div>
</blockquote>
</div>
<br clear="all">
<br>
-- <br>
<div dir="ltr" class="gmail-m_6645075114557351239gmail-m_389457387969098912gmail-m_-4896604996342057643gmail-m_-2005229189514266957gmail-m_-5021230384019393008gmail-m_5493832268194904826gmail_signature">
<div dir="ltr">
<div>
<div dir="ltr">
<div>Daniel-Constantin Mierla - <a href="http://www.asipto.com" target="_blank">http://www.asipto.com</a></div>
<div><a href="http://twitter.com/#!/miconda" target="_blank">http://twitter.com/#!/miconda</a>
- <a href="http://www.linkedin.com/in/miconda" target="_blank">http://www.linkedin.com/in/miconda</a></div>
</div>
</div>
</div>
</div>
</blockquote>
</div>
</blockquote>
</div>
<br clear="all">
<br>
-- <br>
<div dir="ltr" class="gmail-m_6645075114557351239gmail-m_389457387969098912gmail-m_-4896604996342057643gmail-m_-2005229189514266957gmail_signature">
<div dir="ltr">
<div>
<div dir="ltr">
<div>Daniel-Constantin Mierla - <a href="http://www.asipto.com" target="_blank">http://www.asipto.com</a></div>
<div><a href="http://twitter.com/#!/miconda" target="_blank">http://twitter.com/#!/miconda</a>
- <a href="http://www.linkedin.com/in/miconda" target="_blank">http://www.linkedin.com/in/miconda</a></div>
</div>
</div>
</div>
</div>
</blockquote>
</div>
</blockquote>
</div>
</blockquote>
<pre class="gmail-m_6645075114557351239moz-signature" cols="72">--
Daniel-Constantin Mierla -- <a class="gmail-m_6645075114557351239moz-txt-link-abbreviated" href="http://www.asipto.com" target="_blank">www.asipto.com</a>
<a class="gmail-m_6645075114557351239moz-txt-link-abbreviated" href="http://www.twitter.com/miconda" target="_blank">www.twitter.com/miconda</a> -- <a class="gmail-m_6645075114557351239moz-txt-link-abbreviated" href="http://www.linkedin.com/in/miconda" target="_blank">www.linkedin.com/in/miconda</a></pre>
</div>
</blockquote></div>