Using a domain name in R-R header may not be such a good idea:
Feb 11 12:12:06 lab /usr/bin/sip-proxy[735]: WARNING: rr [loose.c:799] rr_do_force_send_socket(): no socket found to match second RR (sip:tenantX.teams.tutpro.com:8007;transport=tls;r2=on;pm=0;savp=avp;lr)
Or is there some means to tell K, which FQDN maps to which IP address, when there are many such FQDNs?
-- Juha
That is the main reason I had previously thought it wasn’t possible!
— Sent from mobile, with due apologies for brevity and errors.
On Feb 11, 2021, at 11:45 AM, Juha Heinanen jh@tutpro.com wrote:
Using a domain name in R-R header may not be such a good idea:
Feb 11 12:12:06 lab /usr/bin/sip-proxy[735]: WARNING: rr [loose.c:799] rr_do_force_send_socket(): no socket found to match second RR (sip:tenantX.teams.tutpro.com:8007;transport=tls;r2=on;pm=0;savp=avp;lr)
Or is there some means to tell K, which FQDN maps to which IP address, when there are many such FQDNs?
-- Juha
Kamailio (SER) - Users Mailing List sr-users@lists.kamailio.org https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
Alex Balashov writes:
That is the main reason I had previously thought it wasn’t possible!
Have you changed your mind?
The document
https://skalatan.de/de/blog/kamailio-sbc-teams
tells
Change in your configuration the existing record_route() function call to this one:
record_route_preset("SBC-DNS-DOMAIN:5061;transport=tls", "SBC-IP-ADDR:5060");
but does not tell, how to change loose_route() so that it would work on the resulting Route headers.
It would be nice to learn the secret.
-- Juha
On 11.02.21 18:51, Juha Heinanen wrote:
Alex Balashov writes:
That is the main reason I had previously thought it wasn’t possible!
Have you changed your mind?
Probably you confuse the people, that blog post is from Henning, not from Alex ... or maybe you refer to another message from Alex and I am out of topic here.
Cheers, Daniel
The document
https://skalatan.de/de/blog/kamailio-sbc-teams
tells
Change in your configuration the existing record_route() function call to this one:
record_route_preset("SBC-DNS-DOMAIN:5061;transport=tls", "SBC-IP-ADDR:5060");
but does not tell, how to change loose_route() so that it would work on the resulting Route headers.
It would be nice to learn the secret.
Even before the socket name, it was possible using other parameters in the record route to store information about what sockets to be used. The warning message can be disabled with "enable_socket_mismatch_warning" parameter for rr module, then use script operations to figure out the socket from the parameters you added.
Cheers, Daniel
Daniel-Constantin Mierla writes:
Probably you confuse the people, that blog post is from Henning, not from Alex ... or maybe you refer to another message from Alex and I am out of topic here.
No, I was asking from Alex if he has changed his mind on the topic. I know that Alex did not write the blog post.
-- Juha
Had to remove Class 4 responses:
#modparam("dispatcher", "ds_ping_reply_codes", "class=2;class=3;class=4") modparam("dispatcher", "ds_ping_reply_codes", "class=2;class=3")
Thanks, AL
Sent with ProtonMail Secure Email.
‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐ On Thursday, February 11, 2021 11:46 AM, Alex Balashov abalashov@evaristesys.com wrote:
That is the main reason I had previously thought it wasn’t possible!
— Sent from mobile, with due apologies for brevity and errors.
On Feb 11, 2021, at 11:45 AM, Juha Heinanen jh@tutpro.com wrote: Using a domain name in R-R header may not be such a good idea: Feb 11 12:12:06 lab /usr/bin/sip-proxy[735]: WARNING: rr [loose.c:799] rr_do_force_send_socket(): no socket found to match second RR (sip:tenantX.teams.tutpro.com:8007;transport=tls;r2=on;pm=0;savp=avp;lr) Or is there some means to tell K, which FQDN maps to which IP address, when there are many such FQDNs? -- Juha
Kamailio (SER) - Users Mailing List sr-users@lists.kamailio.org https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
Kamailio (SER) - Users Mailing List sr-users@lists.kamailio.org https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
On 11.02.21 17:44, Juha Heinanen wrote:
Using a domain name in R-R header may not be such a good idea:
Feb 11 12:12:06 lab /usr/bin/sip-proxy[735]: WARNING: rr [loose.c:799] rr_do_force_send_socket(): no socket found to match second RR (sip:tenantX.teams.tutpro.com:8007;transport=tls;r2=on;pm=0;savp=avp;lr)
Or is there some means to tell K, which FQDN maps to which IP address, when there are many such FQDNs?
Set names to the sockets (https://www.kamailio.org/wiki/cookbooks/devel/core#listen):
listen= ..... name "s1"
And then add parameter "sn=s1" to the specific Record-Route header.
Cheers, Daniel
Daniel-Constantin Mierla writes:
Or is there some means to tell K, which FQDN maps to which IP address, when there are many such FQDNs?
Set names to the sockets (https://www.kamailio.org/wiki/cookbooks/devel/core#listen):
listen= ..... name "s1"
And then add parameter "sn=s1" to the specific Record-Route header.
Nice, thanks,
-- Juha
Daniel-Constantin Mierla writes:
Set names to the sockets (https://www.kamailio.org/wiki/cookbooks/devel/core#listen):
listen= ..... name "s1"
And then add parameter "sn=s1" to the specific Record-Route header.
If sockname_mode param has value 1:
modparam("rr", "sockname_mode", 1)
does it mean that ;sn=name param needs to be included in every R-R URI, i.e, also in those that have an IP address that K is listening on?
Or may the ;sn param may be omitted in those URIs without causing loose_route() to fail?
-- Juha
Seems to be OK not to include ;sn param in IP address R-R URIs. At least I didn't get any errors or warning to syslog when I called loose_route() on in-dialog requests that had such Route headers.
-- Juha
-
Alex Balashov -
alirsm -
Daniel-Constantin Mierla -
Juha Heinanen