Sorry, please ignore the variable name typo in the "REFRESH_CALLSTATE_TIMER"
route in my initial post.
The issue still stands however.
route[REFRESH_CALLSTATE_TIMER] {
xlog("L_INFO", "Testvariable: $var(testvar)\n");
}
I've also tried enabling the timer on start as well as attempting
Hi,
It is important to know that the scope of $var(...) is per-process[1], and
timer functions run in a different process.
When REFRESH_CALLSTATE_TIMER runs, it is not in response to any particular SIP
message or call, and it does not know the context of any particular SIP message
or call.
Hi,
I have a timer which is called each 5 seconds:
modparam("timer", "declare_timer",
"REFRESH_CALLSTATE_TIMER=REFRESH_CALLSTATE_TIMER,5000,slow");
I'm enabling setting the variable "testvar" and enabling the timer when an
INVITE is received:
if (is_method("INVITE|ACK|UPDATE|CANCEL|BYE")) {
The on failure route was not triggered because I was doing a t_reply before
the timeout was triggered ...
On Tue, Nov 21, 2023 at 1:51 PM Julien Chavanton
wrote:
> Sorry for the incomplete email.
>
> My problem is that the failure route does not trigger on TCP timeout.
>
> ...
> t_on_reply("
Hi Ilie,
Glad it worked out for you, and thank you for forcing me to take a second look
at the mechanics of this for myself. You could say we both learned something.
:-) Likewise thank you to Daniel for the clarity.
-- Alex
> On 29 Nov 2023, at 11:08, Ilie Soltanici wrote:
>
> Hi Alex,
>
>
Hi Alex,
Thanks for your reply. Indeed, it's based on this parameter - our
objective, however, is to avoid altering the global behavior of this
parameter for a specific feature that relies on the response from
evapi_async_relay.
The feature is not critical for the call at all, so in our case it ma
Hi!
After updating from version 5.6.2 to 5.7.3, Kamailio now stores htable
records to the DB on CentOS 7.
чт, 16 лист. 2023 р. о 16:54 James Browne via sr-users <
sr-users@lists.kamailio.org> пише:
> I had a similar problem today. I know I'm replying months later.
> My problem was that I had an
Hi Ilie,
I think the confusion is about behaviour rather than transaction reality. A
transaction suspended by evapi_async_relay() does not generate any productive
replies back to the UAC, it's true.
But it does go away, as Daniel says. Setting an example `fr_timer` value of 4
sec:
loadmod
Hey Fred,
thanks for the info and the example on how to handle this.
I'll take a look at it and try to get it working
Thanks again
On Tue, Nov 28, 2023 at 11:45 PM Fred Posner wrote:
> Hi Saul,
>
> Great to see you here…
>
> So, there’s not a ton of examples out there on UAC, but many of us hav
With the caveat of “everyone does things a bit differently”, etc…
Here’s an example of how I would approach a kamailio front/uac to carrier:
https://github.com/fredposner/scripts/blob/master/kamailio/uac_carrier_example.cfg
Regards,
Fred Posner
p: +1 (352) 664-3733
> On Nov 28, 2023, at 9:4
Hi,
I use evapi_async_relay() very extensively, and can say that the transaction
does time out if it goes unreplied, and relatively quickly. I haven't checked
exactly which timer guides this, but it doesn't remain suspended indefinitely.
I don't think that's a concern.
-- Alex
> On 29 Nov 202
HI Daniel,
That would be great if it were possible, unfortunately, the code I
attempted doesn't seem to be working. Here's the code snippet I tried:
route[TEST] {
t_set_fr(1000);
t_on_failure("CONTACT_LOOKUP_FAILED");
evapi_async_relay({"field":"value"})
}
failure_route[CONTACT_LOOKUP_FAILED] {
>dmq is designed to work only between kamailio nodes that have the same
major version (e.g., only between kamailio 5.7.x nodes).
Yes, looks like I missed this point about compatibility.
Thanks again for your help!
ср, 29 нояб. 2023 г. в 13:39, Daniel-Constantin Mierla :
> Hello,
>
> dmq is desi
Hello,
a suspended transaction is kept silently for the duration of the timeout
(see t_set_fr()), then it fails and jumps to a failure route (if you set
one) -- maybe you can leverage this mechanism somehow.
Cheers,
Daniel
On 29.11.23 12:53, Ilie Soltanici via sr-users wrote:
> Hello,
>
> |I'm t
Hello,
dmq is designed to work only between kamailio nodes that have the same
major version (e.g., only between kamailio 5.7.x nodes).
That's because even on the network the data may look the same, the
internal structures, types of fields, sizes and meaning of values can be
different. This is sim
Hello,
I'm trying to use the evapi_async_relay function from the evapi
module, however,I don't want the transaction to be suspended for more
than 1 second.
For instance, if there's no response from the external application
within this time frame, I want the script to continue and remove that
trans
Hello!
I noticed that there are differences in the DMQ htable replication protocol
for the old version of Kamailio 5.2 and the new 5.7.
For example, the new version uses action 2 when updating values and action
4 to remove.
The old Kamailio version uses the values 1 and 3 respectively.
Well, as a
17 matches
Mail list logo
