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
Hello,
I think I have the same problem, at least in my case the problem is with
the Shared memory.
Kamailio is configured to use 4GB of shared memory (-m 4096) and after
restart, he is getting all 4GB of memory and keep it decreasing slowly
until it reaches the low values (40-50MiB) and then
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:
Hi,
In my failover setting using Dispatcher module, I mark the GW if fails to
response. OPTIONS are being sent every 30 sec:
failure_route[DISPATCH_FAILOVER]{
if (t_is_canceled()) exit;
if (t_check_status("500") or (t_branch_timeout() and !t_branch_replied())) {
ds_mark_dst("ip");
if
Daniel-Constantin Mierla writes:
> The record_route_preset() is supposed to offer the flexibility of
> setting the address part in RR headers via variables. I do not see how
> the record_route() can be better variant, because it will end up in the
> same kind functionality: for which to use the
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
>
If it can help you ... this is a working example:
tag: snd
pid: 19012
process: 1
time: 1612951019.957348
date: Wed Feb 10 10:56:59 2021
proto: tls ipv4
srcip: SBC-IP-ADDR
srcport: 5061
dstip: 52.114.76.76
dstport: 5061
SIP/2.0 200 OK
Via: SIP/2.0/TLS
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
I do not see benefits of the variant you propose, there must be
conditions to figure outing tenants, which direction is going to be, how
to route it, etc...
But you can add new functions as you consider useful, there is also a
function for record route with advertised address.
Cheers,
Daniel
On
On 11.02.21 16:16, Alex Balashov wrote:
> Carsten,
>
> Thanks for the neat trick! I did not realise one could use an FQDN
> with the 'advertise' parameter to a listener.
>
> An example of this is present in the 5.4.x core cookbook, but not in
> prior versions.
... and many people complain that
On 11.02.21 14:52, Juha Heinanen wrote:
> Daniel-Constantin Mierla writes:
>
>> The address, port and protocol are taken from listen socket by the usual
>> record_route() function, they are known.
> Yes, that is what I'm normally using.
>
>>> I haven't tested yet, if I only give host, will
Daniel-Constantin Mierla writes:
> If not, then that has to be added because the purpose of
> record_route_preset() is to be able to set rr header as one needs based
> on variables that can be used in parameters. Note that the parameters
> are only "host:port;transport=", without protocol, for
Carsten,
Thanks for the neat trick! I did not realise one could use an FQDN with
the 'advertise' parameter to a listener.
An example of this is present in the 5.4.x core cookbook, but not in
prior versions.
-- Alex
On 2/11/21 3:54 AM, Carsten Bock wrote:
Hi,
I don't understand the
Daniel-Constantin Mierla writes:
> The code of add_rr_param() used after the record-route header is added
> indicates that the values should be added. I didn't have the time to
> check what is with the cached params if add_rr_param() used beore the
> record-route header is added. I will try to
Hi Guys
Thanks for all your recommendations.
I did the change and rr headers only show the fqdn of Kamailio as you can
see below in the 200 OK sent back to MS Teams, however still the same issue
no ACK.
tag: snd
pid: 31232
process: 6
time:
Henning Westerholt writes:
> not 100% sure what the other blog post is suggesting - but in my
> setups there is no need for a special record_route(..) in reply
> handling (like reply route).
Its is not question about reply handling, but direction of INVITE. See
my earlier message.
-- Juha
Carsten Bock writes:
> I don't understand the trouble:
> Wouldn't the following lead to the exact example:
>
> listen=tls:1.2.3.4:8007 advertise teams.tutpro.com:8007
> listen=tcp:1.2.3.4:5070
That would not work when K is a multi-tenant carrier Teams SBC proxy
that requires tenant specific
Daniel-Constantin Mierla writes:
> What exactly do you need to do for R-R in replies?
>
> The R-R headers are mirrored in replies, so if you add R-R for requests
> using the right order of parameters based on the direction, there is
> nothing to be done for replies, or at least I haven't had to
Sergey Safarov writes:
> Maybe need to move into more global changes...
>
> How about DNS hostname usage for all headers?
> "Via", "Record-Route" maybe "Contact" when Kamailio with extra modules
> play media?
>
> how about global directive like
> header_with_hostname=tue
I'm not sure if that
Pepelux writes:
> Try to put SBC-FQDN instead of SBC-IP-ADDR in the Record-Route:
>
> Record-Route: :5060;ftag=c3da9477e05d45fca31c24a155af3318;lr=on>
Also, it better to follow OpenSIPS tips on the matter
https://blog.opensips.org/2019/09/16/opensips-as-ms-teams-sbc/
since it also mentions
Daniel,
I don't want to use record_route_preset at all, since its use is very
complicated when Kamailio is listening on multiple IP addresses and when
request can come over UDP, TCP, or TLS and when R-R URIs can have many
parameters depending on if rtpengine is used, etc.
So I simply want to
On 11.02.21 09:52, Juha Heinanen wrote:
> Daniel-Constantin Mierla writes:
>
>> I think the parameters are added even if you use the
>> record_route_preset(), isn't it? If you use add_rr_param() and this
>> function, the params are not showing up in headers?
> Daniel,
>
> That exactly is the
Hello Juha,
not 100% sure what the other blog post is suggesting - but in my setups there
is no need for a special record_route(..) in reply handling (like reply route).
So I saw no need to update it.
Cheers,
Henning
--
Henning Westerholt - https://skalatan.de/blog/
Kamailio services -
Hi,
I don't understand the trouble:
Wouldn't the following lead to the exact example:
listen=tls:1.2.3.4:8007 advertise teams.tutpro.com:8007
listen=tcp:1.2.3.4:5070
As soon as you do:
$fs = "tcp:1.2.3.4:5070";
record_route();
(or put the other socket into $fs)
This results into two
On 11.02.21 09:34, Juha Heinanen wrote:
> Pepelux writes:
>
>> Try to put SBC-FQDN instead of SBC-IP-ADDR in the Record-Route:
>>
>> Record-Route: > :5060;ftag=c3da9477e05d45fca31c24a155af3318;lr=on>
> Also, it better to follow OpenSIPS tips on the matter
>
>
I think the parameters are added even if you use the
record_route_preset(), isn't it? If you use add_rr_param() and this
function, the params are not showing up in headers?
If not, then that has to be added because the purpose of
record_route_preset() is to be able to set rr header as one needs
Maybe need to move into more global changes...
How about DNS hostname usage for all headers?
"Via", "Record-Route" maybe "Contact" when Kamailio with extra modules
play media?
how about global directive like
header_with_hostname=tue
Sergey
On Thu, Feb 11, 2021 at 10:44 AM Olle E. Johansson
Try to put SBC-FQDN instead of SBC-IP-ADDR in the Record-Route:
Record-Route:
On Thu, 11 Feb 2021 at 08:32, Phillman25 Kyriacou
wrote:
> Dear List
>
> Hope this email finds you all well.
>
> I have followed the below tutorial on how to integrate Kamailio with MS
> Teams
>
>
30 matches
Mail list logo
