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,
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
___
Kamailio (SER) - Users Mailing List
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",
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:
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
>
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 wrote:
>
> Using a domain name in R-R header may not be such a good idea:
>
> Feb 11 12:12:06 lab
