<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<p>Hello,</p>
<p>the note about aliases was not related to record routing
processing.</p>
<p>Not clearly stated indeed, but it was only as an independent
suggestion in case it helps not listing many subdomains as
explicit alias parameter.</p>
<p>Cheers,<br>
Daniel<br>
</p>
<div class="moz-cite-prefix">On 25.03.20 15:10, Sergiu Pojoga wrote:<br>
</div>
<blockquote type="cite"
cite="mid:CAJZsGCmYVLSqXh3-mMRTw4bWVZjLdFmLWBWmi9o6T53gwhsSTQ@mail.gmail.com">
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
<div dir="ltr">Hi Daniel and thanks for the suggestion, however it
doesn't seem to be a matter of matching against 'myself' (alias)
but rather matching against a socket.
<div><br>
</div>
<div>In an old post, I found this explanation of yours that
seems to apply to my case:</div>
<div><br>
</div>
<div>"<i>loose_route() matches the alias as being local (myself
condition), but there is no relation between aliases and
sockets, so searching a socket using an alias value does not
work.</i></div>
<i>The advertise for listen does what you need, if it fits in
what you try to achieve:<br>
<br>
</i>
<div><i>listen=IP1 advertise IP2<br>
<br>
</i></div>
<div><i>If Route has IP2 then the socket IP1 is used for
relaying</i>."
<div><br>
<div><a
href="https://lists.kamailio.org/pipermail/sr-users/2012-September/074825.html"
moz-do-not-send="true">https://lists.kamailio.org/pipermail/sr-users/2012-September/074825.html</a><br>
</div>
</div>
<div><br>
</div>
<div>Thanks,</div>
<div>--Sergiu</div>
</div>
</div>
<br>
<div class="gmail_quote">
<div dir="ltr" class="gmail_attr">On Wed, Mar 25, 2020 at 9:38
AM Daniel-Constantin Mierla <<a
href="mailto:miconda@gmail.com" moz-do-not-send="true">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>
<p>Hello,</p>
<p>from record routing point of view, that is probably the
good solution.</p>
<p>If you have many aliases like <a
href="http://PREFIX.mydomain.net" target="_blank"
moz-do-not-send="true">PREFIX.mydomain.net</a>, instead
of listing them individually, you can use:</p>
<p> * <a
href="http://www.kamailio.org/docs/modules/5.3.x/modules/corex.html#corex.p.alias_subdomains"
target="_blank" moz-do-not-send="true">http://www.kamailio.org/docs/modules/5.3.x/modules/corex.html#corex.p.alias_subdomains</a></p>
<p>Provided that you do not have any need to skip some
specific subdomains.</p>
<p>Cheers,<br>
Daniel<br>
</p>
<div>On 25.03.20 03:45, Sergiu Pojoga wrote:<br>
</div>
<blockquote type="cite">
<div dir="ltr">Hi there,
<div><br>
</div>
<div>Question: how can I advertise and later match
multiple FQDNs per socket?</div>
<div><br>
</div>
<div>Example:</div>
<div>auto_aliases=no<br>
alias="<a href="http://mydomain.net" target="_blank"
moz-do-not-send="true">mydomain.net</a>":5060<br>
alias="<a href="http://mydomain.net" target="_blank"
moz-do-not-send="true">mydomain.net</a>":5061<br>
alias="<a href="http://client1.mydomain.net"
target="_blank" moz-do-not-send="true">client1.mydomain.net</a>":5060<br>
alias="<a href="http://client1.mydomain.net"
target="_blank" moz-do-not-send="true">client1.mydomain.net</a>":5061<br>
<br>
# looks like I can advertise only one address per
socket?<br>
listen=udp:<a href="http://65.65.65.65:5060"
target="_blank" moz-do-not-send="true">65.65.65.65:5060</a>
advertise "<a href="http://mydomain.net"
target="_blank" moz-do-not-send="true">mydomain.net</a>":5060<br>
listen=tls:<a href="http://65.65.65.65:5061"
target="_blank" moz-do-not-send="true">65.65.65.65:5061</a>
advertise "<a href="http://mydomain.net"
target="_blank" moz-do-not-send="true">mydomain.net</a>":5061<br>
</div>
<div><br>
</div>
<div>Adding RR before relaying downstream like so:</div>
<div>record_route_preset("client1.mydomain.net:5061;transport=tls;r2=on",
"client1.mydomain.net:5060;r2=on");<br>
</div>
<div><br>
</div>
<div>This is the warning (just warning, works fine
otherwise) after receiving for example the ACK from
upstream following the 200 OK:</div>
<div><b>WARNING</b>: {1 19082 ACK } rr [loose.c:768]:
rr_do_force_send_socket(): no socket found to match
second RR (<a moz-do-not-send="true">sip:client1.mydomain.net:5061;transport=tls;lr;r2=on</a>)</div>
<div><br>
</div>
<div>Figured warning itself can be turned off with
modparam "enable_socket_mismatch_warning" of RR, still
I'd like to know if I'm doing something wrong or
there's a better way.</div>
<div><br>
</div>
<div>Much obliged,</div>
<div>--Sergiu</div>
<div><br>
</div>
<div><br>
</div>
</div>
<br>
<fieldset></fieldset>
<pre>_______________________________________________
Kamailio (SER) - Users Mailing List
<a href="mailto:sr-users@lists.kamailio.org" target="_blank" moz-do-not-send="true">sr-users@lists.kamailio.org</a>
<a href="https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users" target="_blank" moz-do-not-send="true">https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users</a>
</pre>
</blockquote>
<pre cols="72">--
Daniel-Constantin Mierla -- <a href="http://www.asipto.com" target="_blank" moz-do-not-send="true">www.asipto.com</a>
<a href="http://www.twitter.com/miconda" target="_blank" moz-do-not-send="true">www.twitter.com/miconda</a> -- <a href="http://www.linkedin.com/in/miconda" target="_blank" moz-do-not-send="true">www.linkedin.com/in/miconda</a></pre>
</div>
</blockquote>
</div>
</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></pre>
</body>
</html>