Hi,
Thank you all for the suggestions. It makes sense the ARP to be the issue
as we have homer on the same network. So we will relocate it to a another
subnet and we will also consider adding the proxy in-between but again not
on the same subnet.
We will also install the gdb to have some
Sorry Daniel,
I was getting confued with the two pages, You are quite correct.
I suspect we had a backport of the uac module.
Richard
On 03/02/2022 16:51, Daniel-Constantin Mierla wrote:
Hello,
where did you find in the docs that uac_auth() has the mode parameter in
5.3.x series, the html
Hello,
when Kamailio is not processing sip messages, so it looks like stuck,
you can grab the backtraces with gdb to see what each kamailio process
is executing at that moment. You need gdb installed and then run:
kamctl trap
It writes to a file in /tmp, the file name is printed by the command.
Hello,
where did you find in the docs that uac_auth() has the mode parameter in
5.3.x series, the html docs don't show it:
*
https://www.kamailio.org/docs/modules/5.3.x/modules/uac.html#uac.f.uac_auth
In the code is not, so if it is somewhere is the docs, likely it is a
mistaken backport.
hi Henning
I'm trying to find out if we have a back port.
uac_auth() is working , but uac_auth(1) and uac_auth("1") also fail
acording to to the 5.3.x Docs uac_auth([mode]) should work
On 03/02/2022 15:47, Henning Westerholt wrote:
Hello,
5.3.0 was released on 17th October 2019.
The
Hello,
5.3.0 was released on 17th October 2019.
The uac_auth_mode was added to the 5.4.0 branch later:
Date: Tue Oct 29 09:15:49 2019 +0100
uac: optional param for uac_auth() to specify auth mode
- if mode is set to 1, then the password is provided in ha1 format
Maybe you are
we have been running 5.3.4 with the uac_auth_mode() function ans it has
been working
we have upgraded to 5.3.8 and with the same script we are getting an
error with the uac module saying it was unable to find the cmd auc_auth_mode
I have tried this with uac_auth as well with the same result.
Hi James an Angelo,
most of the time my homer or hepic servers are in different subnets.
So that arp think sounds good to me.
@Angelo Take a look at the HEP Fidelity Proxy, it's capable to be in the
middle between your kamailio and the hep-server and can store the HEP
packets if your hep-server
Hello all,
I tried to update $du for REGISTERs sent by the uac module in
event_route[tm:local-request]. (I want to overwrite the auth_proxy under some
conditions.)
However, the requests are still sent to the auth_proxy defined in uacreg. Am I
missing something here, why doesn't it work?
It's
I've encountered a very similar problem in the past.The siptrace module
uses UDP and does not expect a response, so it can be confusing that
kamailio's behavior changes depending on whether the homer server is online.
The problem I've seen in the past is that when kamailio and a statsd server
are
Okay, so I have done that,
Please find here :
https://zerobin.net/?7743b78716b00c72#Jzmdq+5ZlFfZId+M/hP+52Ih0AMAMNUjeUT1cN7jL7Q=
My full config (I redacted some parts like IPs and domains), with the
minimal routing blocks to reproduce and the logs.
If you don't mind checking it, it would be
I have to admit that even looking at the debug logs I cannot understand
what's going on in your case.
As said I'm running an authentication scenario very similar to yours, being
the challenge the only difference.
What I can suggest to further digging is to reduce your configuration as
much as
You said to handle the registrations inside a background process, how do
you achieve that?
In fact I already tried to use the async framework and it wasn't working
too, got the same error.
Inside my REGISTER handling route I do :
challenge, if provided then go:>
> On 3 Feb 2022, at 09:54, Cyril Ramière wrote:
>
> Hi Olle,
>
> I prefer not to use it since you rightly pointed out that it will block the
> thread during the request
Depends of course of your HTTP server… And the number of UDP/TCP listeners. It
won’t block all listeners.
Since
Hi Olle,
I prefer not to use it since you rightly pointed out that it will block the
thread during the request.
Since a lot of sip phones will register & interact with kamailio it could
seriously hurt the performance.
I will implement caching for sure regardless of the
15 matches
Mail list logo
