Daniel-Constantin Mierla writes:
> I pushed a quick fix for the case when db support is not enabled,
> because these locks are useless in that case, so all children will do
> the rtpengine init at the same time, without waiting for the others:
Still took in rtpengine db mode about 2 minutes
No, it is for no-db. For db, it requires another solution, but I don't
have time for it right now. I explanined in my previous email what would
be a solution.
You can make a fix yourself if you want and have the time. It is not a
module I coded, nor the one that added db support for it, so I am
I forgot to say that if the patch makes it work for you, then you can go
ahead and backport to branch 5.2.
Cheers,
Daniel
On 26.12.18 12:01, Daniel-Constantin Mierla wrote:
> I was able to figure out what could be the cause with:
>
> modparam("rtpengine", "rtpengine_sock", "udp:127.0.0.1:2223
>
Daniel-Constantin Mierla writes:
> Maybe you would also want to tune the timeout with the modparam:
>
> modparam("rtpengine", "rtpengine_disable_tout", 5)
>
> So detection of unavailable rtpproxy is fast, otherwise it is 60 sec by
> default, so you may still experience some slow start per child
Daniel-Constantin Mierla writes:
> You can make a fix yourself if you want and have the time. It is not a
> module I coded, nor the one that added db support for it, so I am also
> coding by learning what was done there.
Understand. Perhaps the solution for now is to disable db mode in the
There are many situations that can block a proxy, including writing to
syslog, dns and DB queries,... At the end you cannot rely on a single app
to have a smooth runtime, the ecosystem has to be also in good parameters.
The current implementation is like this now, the choice of developer. You
can
Daniel-Constantin Mierla writes:
> I was able to figure out what could be the cause with:
>
> modparam("rtpengine", "rtpengine_sock", "udp:127.0.0.1:2223
> udp:192.168.64.4:2224")
In my test, I use rtpengine in db mode, i.e., db_url param is set.
Would your patch also fix the delay in that
I was able to figure out what could be the cause with:
modparam("rtpengine", "rtpengine_sock", "udp:127.0.0.1:2223
udp:192.168.64.4:2224")
Host 192.168.64.4 is not running (not existing in my case, just made up
that ip to be on the same network with the kamailio running on
192.168.64.2).
It was
I tried quickly with a rtpengine that was not running, and kamailio
started fine and then was responding fast for sip requests.
To clarify: you actually have more rtpengine configured (at least two)
in a set and one is not available, right?
Is the CPU usage very high? Because it is strange that
Daniel-Constantin Mierla writes:
> I tried quickly with a rtpengine that was not running, and kamailio
> started fine and then was responding fast for sip requests.
>
> To clarify: you actually have more rtpengine configured (at least two)
> in a set and one is not available, right?
Yes, I have
Hey community,
I'm currently trying to config our new 5.1.2 kamailio server and I want to
xlog $mb. Whenever I do this, I get an ERROR logged to my syslog
Dec 26 21:15:58 sjomainkama55 /usr/sbin/kamailio[5954]: {1 1 INVITE
@} ERROR:
As STUN is a client-side construct, I am not aware of any functionality
Kamailio might have to make *use* of a STUN server for its own representations
about its reachability.
But I could be wrong.
--
Sent from mobile. Apologies for brevity and errors.
Hello!
I would be grateful if you could tell me what the causes of the error in
Kamailio version 5.1.5.
2018-12-26T20: 28: 18.3875 "ERROR: tm [tm.c: 1545]: _w_t_relay_to ():
t_forward_noack failed"
2018-12-26T20: 28: 18.3879 "ERROR: sl [sl_funcs.c: 362]: sl_reply_error ():
stateless error
Hello All,
Can I point Kamilio to use a STUN server located on my network? Kamilio will
not relay to my fios router but will relay to other Servers on my network.
Thank you,
___
Kamailio (SER) - Users Mailing List
sr-users@lists.kamailio.org
Thank you, I just was not sure what else would cause the relayed packets to not
be sent out to my fios router. As mentioned, I can pick any other server in my
network and I can see, in the pcap file, that the relay is attempted to the
selected server. I verified our ACL and it is it open for
15 matches
Mail list logo
