25 Mar
2020
25 Mar
'20
4:03 p.m.
Hello,
the note about aliases was not related to record routing processing.
Not clearly stated indeed, but it was only as an independent suggestion
in case it helps not listing many subdomains as explicit alias parameter.
Cheers,
Daniel
On 25.03.20 15:10, Sergiu Pojoga wrote:
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.
In an old post, I found this explanation of yours that seems to apply
to my case:
"/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./
/The advertise for listen does what you need, if it fits in what you
try to achieve:
/
/listen=IP1 advertise IP2
/
/If Route has IP2 then the socket IP1 is used for relaying/."
https://lists.kamailio.org/pipermail/sr-users/2012-September/074825.html
Thanks,
--Sergiu
On Wed, Mar 25, 2020 at 9:38 AM Daniel-Constantin Mierla
<miconda(a)gmail.com <mailto:miconda@gmail.com>> wrote:
Hello,
from record routing point of view, that is probably the good solution.
If you have many aliases like PREFIX.mydomain.net
<http://PREFIX.mydomain.net>, instead of listing them
individually, you can use:
*
http://www.kamailio.org/docs/modules/5.3.x/modules/corex.html#corex.p.alias…
Provided that you do not have any need to skip some specific
subdomains.
Cheers,
Daniel
On 25.03.20 03:45, Sergiu Pojoga wrote:
--
Daniel-Constantin Mierla -- www.asipto.com
www.twitter.com/miconda -- www.linkedin.com/in/miconda
Hi there,
Question: how can I advertise and later match multiple FQDNs per
socket?
Example:
auto_aliases=no
alias="mydomain.net <http://mydomain.net>":5060
alias="mydomain.net <http://mydomain.net>":5061
alias="client1.mydomain.net <http://client1.mydomain.net>":5060
alias="client1.mydomain.net <http://client1.mydomain.net>":5061
# looks like I can advertise only one address per socket?
listen=udp:65.65.65.65:5060 <http://65.65.65.65:5060> advertise
"mydomain.net <http://mydomain.net>":5060
listen=tls:65.65.65.65:5061 <http://65.65.65.65:5061> advertise
"mydomain.net <http://mydomain.net>":5061
Adding RR before relaying downstream like so:
record_route_preset("client1.mydomain.net:5061;transport=tls;r2=on",
"client1.mydomain.net:5060;r2=on");
This is the warning (just warning, works fine otherwise) after
receiving for example the ACK from upstream following the 200 OK:
*WARNING*: {1 19082 ACK } rr [loose.c:768]:
rr_do_force_send_socket(): no socket found to match second RR
(sip:client1.mydomain.net:5061;transport=tls;lr;r2=on)
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.
Much obliged,
--Sergiu
_______________________________________________
Kamailio (SER) - Users Mailing List
sr-users(a)lists.kamailio.org <mailto:sr-users@lists.kamailio.org>
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
--
Daniel-Constantin Mierla -- www.asipto.com <http://www.asipto.com>
www.twitter.com/miconda <http://www.twitter.com/miconda> --
www.linkedin.com/in/miconda <http://www.linkedin.com/in/miconda>