<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<p>Hello,</p>
<p>from record routing point of view, that is probably the good
solution.</p>
<p>If you have many aliases like PREFIX.mydomain.net, 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">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 class="moz-cite-prefix">On 25.03.20 03:45, Sergiu Pojoga wrote:<br>
</div>
<blockquote type="cite"
cite="mid:CAJZsGC=XUM_4H1gFddZ4DSUSjc9Qp+W+oAg2fY6D4uVGML3V5A@mail.gmail.com">
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
<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" moz-do-not-send="true">mydomain.net</a>":5060<br>
alias="<a href="http://mydomain.net" moz-do-not-send="true">mydomain.net</a>":5061<br>
alias="<a href="http://client1.mydomain.net"
moz-do-not-send="true">client1.mydomain.net</a>":5060<br>
alias="<a href="http://client1.mydomain.net"
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"
moz-do-not-send="true">65.65.65.65:5060</a> advertise "<a
href="http://mydomain.net" moz-do-not-send="true">mydomain.net</a>":5060<br>
listen=tls:<a href="http://65.65.65.65:5061"
moz-do-not-send="true">65.65.65.65:5061</a> advertise "<a
href="http://mydomain.net" 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 class="moz-txt-link-freetext" href="sip:client1.mydomain.net:5061;transport=tls;lr;r2=on">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 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></pre>
</body>
</html>