Dear all
Would you have any feedback about this query?
thanks a lot!
David Escartín
El jue, 11 feb 2021 a las 23:56, David Escartin ()
escribió:
> Hello
>
> seems with t_flush_xflags() after setxflag on failure_route, it makes it
> work. However i don't know if that should be
any UDP message
Would you have any idea about the reason for this behaviour?
I would expect the evapi socket not to interfer with UDP receivers
thanks a lot and regards
david
El mar, 15 dic 2020 a las 15:05, David Escartin ()
escribió:
> Hello Daniel
>
> Thanks a lot for the feedback
Hello
seems with t_flush_xflags() after setxflag on failure_route, it makes it
work. However i don't know if that should be the expected behaviour, since
with regular transaction flags there is no need to use t_flush_flags()
best regards
david
El mié, 10 feb 2021 a las 16:08, David Escartin
xflag is set inside an onreply_route.
We have seen it on versions 5.3 and 5.4
Could you please confirm this?
thanks a lot
regards
david escartin
--
[image: Logo]
David Escartín Almudévar
VoIP/Switch Engineer
descar...@sonoc.io
*SONOC*
C/ Josefa Amar y Borbón, 10, 4ª · 50001 Zaragoza, España
Tlf
and attempt to send its own op command **when an rtpengine is
disabled because the socket or host is unreachable**. This is causing an
impact in cases where the rtpengine crashes (luckily not so often).
We have been doing some tests, and with this change
El vie, 5 feb 2021 a las 10:43, David
Dear all
since version 4.4 we are using this parameter to 1 to allow that ongoing
calls process their messages through a particular rtpengine when disabling
it manually from database.
But we see that enabling it also makes all the messages select the
rtpengine and attempt to send its own op
recommend that mode for heavy traffic.
>
> At the end, we can introduce modparams for evapi to set TCP_NODELAY, it
> can be useful to reduce delays when sending short data messages from time
> to time, but it won't help in your case.
>
> Cheers,
> Daniel
> On 11.12.20 09
hem to line mode. This way we could reach up to 1000 processed messages
per second.
best regards
david
El lun, 30 nov 2020 a las 11:19, David Escartin ()
escribió:
> Dear all
>
> we have been testing this module with the following setup
> kamailio 5.3.2
> evapi params
> mod
Dear all
we have been testing this module with the following setup
kamailio 5.3.2
evapi params
modparam("evapi", "workers", 4)
modparam("evapi", "netstring_format", 0)
modparam("evapi", "bind_addr", "127.0.0.1:8448")
modparam("evapi", "max_clients", 32)
then in the configuration we do
Dear all
this would be related to one query we sent to sr-users some time ago?
https://lists.kamailio.org/pipermail/sr-users/2018-November/103842.html
we would also be interested in having the dialog structure to be written on
db_redis during early dialog, but it still was in a to do list
Daniel
> On 06.04.20 10:49, David Escartin wrote:
>
> Dear Daniel
>
> hope everything is ok.
> Sorry if i missed something, but has been this patch already backported
> from master to 5.3 yet?
>
> thanks alot and regards
> david
>
> El jue., 13 feb. 2020 a las 18:1
Dear Daniel
hope everything is ok.
Sorry if i missed something, but has been this patch already backported
from master to 5.3 yet?
thanks alot and regards
david
El jue., 13 feb. 2020 a las 18:12, David Escartin ()
escribió:
> hello Daniel
>
> i have tried it and seems fine.
>
&g
Hello all
we just noticed an issue using this function
when we call it with 2 params (display and uri) and the SIP INVITE comes
with a From uri like
sip:anonymous@anonymous.invalid; tag=13133439191609, without <> delimiters,
then doing the uac replace in the ACK we have
2(14923) DEBUG: uac
t:
>
> -
> https://github.com/kamailio/kamailio/commit/6c557efc1b9cb8c880a05235c94780bbaf305073
>
> Can you try and see if now works ok? If yes, it will be backported.
>
> Cheers,
> Daniel
>
>
> On 13.02.20 13:27, David Escartin wrote:
>
> Hello all
>
Hello all
Testing dialog timeout event callback for kemi lua setup on kamailio
5.4.0-dev3 (x86_64/linux) d74157-dirty, i had some problems to perform the
dlg timeroute behaviour the same as we could on native version.
If i used KSR.dialog.var_sets to set $dlg_ctx(timeout_route), I saw that on
a
modf():
function 'dlg_set_ruri' is not available)
-tm t_relay_to_tcp
if you have any update about this function exportation, it would be great
best regards
david
El jue., 27 jun. 2019 a las 15:28, David Escartin ()
escribió:
> Hello Daniel
>
> thanks a lot for the feedback, ok i will
g a bit, anyhow the docs are at:
>> *
>> https://kamailio.org/docs/tutorials/devel/kamailio-kemi-framework/core/#ksrhdr-submodule
>>
>> Cheers,
>> Daniel
>>
>> On Thu, Jun 27, 2019 at 12:07 PM David Escartin
>> wrote:
>>
>>> he
hello all
we are trying to rewrite our code to lua kemi, and we have found some
issues/questions until we would like to share with you.
-module call_obj not exported, we have tested a patch for the module to
export the functions to kemi, which seems works fine
-KSR.xlog.xinfo seems not able to
18 matches
Mail list logo
