<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<p>Hello,</p>
<p>not sure I understood properly, but if you want to use port 5060
for both tcp and tls is not working. Better just use it for tls
only.</p>
<p>Cheers,<br>
Daniel<br>
</p>
<div class="moz-cite-prefix">On 29.03.19 03:26, Lợi Đặng wrote:<br>
</div>
<blockquote type="cite"
cite="mid:CAGsrq_u8YV3FPFVKqLk+L0dFAxfvyXELEKOmdCiqfE3JG3-9Pg@mail.gmail.com">
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
<div dir="ltr">Hi Joel, thanks for verification, it was ok to me
when using the default 5060 for udp/tcp with port omitted in the
RR, the calls should be routed properly.
<div>But it don't work if i use the same port 5060 for tls (i
know this is a bit weird, but i want to re-use the port due to
customer firewall restriction), the port is still omitted and
`ACK/BYE` routed wrongly to <b>MY_ADDR;transport=tls</b>
(5061).</div>
<div><br>
</div>
<div>I only want to make sure whether it is not able to
explicitly add 5060 port to the RR when using tls or i just
make it wrong with my configuration.</div>
<div><br>
</div>
<div>rgds,</div>
<div>
<div>
<div dir="ltr" class="gmail_signature"
data-smartmail="gmail_signature">
<div dir="ltr">
<div>
<div dir="ltr">
<div>
<div dir="ltr">
<div>
<div>Loi Dang Thanh<br>
</div>
Phone : +84. 774.735.448<br>
</div>
Email : <a
href="mailto:loi.dangthanh@gmail.com"
target="_blank" moz-do-not-send="true">loi.dangthanh@gmail.com</a><br>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
<br>
</div>
</div>
<br>
<div class="gmail_quote">
<div dir="ltr" class="gmail_attr">On Thu, Mar 28, 2019 at 10:19
PM Joel Serrano <<a href="mailto:joel@textplus.com"
moz-do-not-send="true">joel@textplus.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">By SIP definition if the port is the default
(5060 for udp/tcp, 5061 for tls) it's not mandatory, that's
why if you choose any other port you specifically see it in
the RR.
<div><br>
</div>
<div>
<div><br>
</div>
<div><br>
</div>
</div>
</div>
<br>
<div class="gmail_quote">
<div dir="ltr" class="gmail_attr">On Thu, Mar 28, 2019 at
3:30 AM Lợi Đặng <<a
href="mailto:loi.dangthanh@gmail.com" target="_blank"
moz-do-not-send="true">loi.dangthanh@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 dir="ltr">
<div dir="ltr">
<div dir="ltr">
<div dir="ltr">
<div dir="ltr">
<div dir="ltr">
<div dir="ltr">
<div dir="ltr">
<div>
<div>Hi all, i was using kamailio
4.2.1 located in 2 networks</div>
</div>
<blockquote class="gmail_quote"
style="margin:0px 0px 0px
0.8ex;border-left:1px solid
rgb(204,204,204);padding-left:1ex">listen
= tcp:MY_ADDR:5060 advertise
MY_ADDR:5060<br>
listen = tls:MY_ADDR:5061 advertise
PUBLIC_NAT_ADDR:5061</blockquote>
<div><br>
</div>
<div>
<div>when the call made from the
inside network to out side, running
`record_route()` resulted in 2
Record-Route headers added
(enable_double_rr=1)</div>
<div><br>
</div>
<blockquote class="gmail_quote"
style="margin:0px 0px 0px
0.8ex;border-left:1px solid
rgb(204,204,204);padding-left:1ex">Record-Route:
PUBLIC_NAT_ADDR:5061;transport=tls;lr<br>
Record-Route:
MY_ADDR;transport=tcp;lr</blockquote>
</div>
<div><br>
</div>
<div>
<div>That was totally fine omitting
the port in the first Record-Route
when using tcp (or udp) on the first
realm, but when i start switching to
tls, it caused trouble</div>
<div><br>
</div>
<blockquote class="gmail_quote"
style="margin:0px 0px 0px
0.8ex;border-left:1px solid
rgb(204,204,204);padding-left:1ex">Record-Route:
PUBLIC_NAT_ADDR:5061;transport=tls;lr<br>
Record-Route:
MY_ADDR;transport=tls;lr</blockquote>
</div>
<div><br>
</div>
<div>
<div>The client is then told to send
ACK/BYE to `MY_ADDR;transport=tls`
located at `MY_ADDR:5061` as per
rfc3263, then the call would failed.</div>
</div>
<div><br>
</div>
<div>
<div>I had another try with
`record_route_preset("PUBLIC_NAT_ADDR:5061;transport=tls",
"MY_ADDR:5060;transport=tls");`, it
really did add what i want with
explicit 5060 port on RR, `ACK/BYE`
travel on the correct path, but
`loose_route()` only consumes the
local `Route` header (it should
consume 2). So my assumption is to
stick with `record_route()` function
to make `loose_route()` work
properly.</div>
</div>
<div><br>
</div>
<div>
<div>I tried using another port on the
local realm, e.g: 5062 and the port
is explicitly added to the
Record-Route header
`MY_ADDR:5062;transport=tls;lr`</div>
<div>So is `5060` couldn't be
explicitly added to the inbound
Record-Route, or i just missed
something?</div>
</div>
<div><br>
</div>
<div>
<div>Any help will be appreciated.</div>
<div><br>
</div>
<div>P/S: I also tried 4.4.7 and it
still omit my 5060 port in the RR.</div>
<div><br>
</div>
<div>rgds,</div>
</div>
<div>
<div dir="ltr"
class="gmail-m_-8730375461263020956gmail-m_1449278207755631929gmail_signature">
<div dir="ltr">
<div>
<div dir="ltr">
<div>
<div dir="ltr">
<div>
<div>Loi Dang Thanh<br>
</div>
Phone : +84. 774.735.448<br>
</div>
Email : <a
href="mailto:loi.dangthanh@gmail.com"
target="_blank"
moz-do-not-send="true">loi.dangthanh@gmail.com</a><br>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
_______________________________________________<br>
Kamailio (SER) - Users Mailing List<br>
<a href="mailto:sr-users@lists.kamailio.org"
target="_blank" moz-do-not-send="true">sr-users@lists.kamailio.org</a><br>
<a
href="https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users"
rel="noreferrer" target="_blank" moz-do-not-send="true">https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users</a><br>
</blockquote>
</div>
_______________________________________________<br>
Kamailio (SER) - Users Mailing List<br>
<a href="mailto:sr-users@lists.kamailio.org" target="_blank"
moz-do-not-send="true">sr-users@lists.kamailio.org</a><br>
<a
href="https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users"
rel="noreferrer" target="_blank" moz-do-not-send="true">https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users</a><br>
</blockquote>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<pre class="moz-quote-pre" wrap="">_______________________________________________
Kamailio (SER) - Users Mailing List
<a class="moz-txt-link-abbreviated" href="mailto:sr-users@lists.kamailio.org">sr-users@lists.kamailio.org</a>
<a class="moz-txt-link-freetext" href="https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users">https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users</a>
</pre>
</blockquote>
<pre class="moz-signature" cols="72">--
Daniel-Constantin Mierla -- <a class="moz-txt-link-abbreviated" href="http://www.asipto.com">www.asipto.com</a>
<a class="moz-txt-link-abbreviated" href="http://www.twitter.com/miconda">www.twitter.com/miconda</a> -- <a class="moz-txt-link-abbreviated" href="http://www.linkedin.com/in/miconda">www.linkedin.com/in/miconda</a>
Kamailio World Conference - May 6-8, 2019 -- <a class="moz-txt-link-abbreviated" href="http://www.kamailioworld.com">www.kamailioworld.com</a></pre>
</body>
</html>