LOL! Yes, I did understand, but it is an important distinction.
On Thu, 3 Dec 2020 at 15:53, Ben Newlin wrote:
> It seems like you read that as I intended, but I want to clarify I meant
> to say I *wouldn’t* feel safe assuming that this would work long term.
>
>
>
> Ben Newlin
>
>
>
> *From:
It seems like you read that as I intended, but I want to clarify I meant to say
I wouldn’t feel safe assuming that this would work long term.
Ben Newlin
From: Users on behalf of Mark Allen
Date: Thursday, December 3, 2020 at 10:40 AM
To: OpenSIPS users mailling list
Subject: Re:
> a memory leak or segfault after continued use
Yes - it would be useful to know if this could result in problems down the
road. Not sure how else I can run a timed job if I can't use the TIMER
route though.
On Thu, 3 Dec 2020 at 15:17, Ben Newlin wrote:
> Mark,
>
>
>
> My concern was less
Mark,
My concern was less about you using the message object in LUA as it was with
how robust OpenSIPS’ handling is if a message if expected to be there and
memory is allocated and passed but there is no actual message due to this
“trick”. Without digging into the actual code, I would feel
I would love to see a SQL engine, a real one, being pulled inside Opensips.
Right now I have to use unixODBC and execute a stored procedure 3000 times
per second, only to achieve a routing decision. It is very inefficient.
Some engines like RocksDB, open-source, should be part of Opensips and run
Thanks, Johan and Ben.
Johan:
I tried your suggested approach and (much to my surprise) it worked both
for lua_exec and cache_remove_chunk. Thanks for that.
Ben:
I understand what you are saying for LUA. However, I think that if it's
made clear that you do not have access to (or should not use)
I wouldn’t recommend trying to bypass the restriction in this way. Both the lua
and python exec modules were designed to operate on a SIP message, which is why
they can only be called from routes that process messages. Calling it from
time_route where there is no message, even if you could get
what you can try, is to call another route in the time route.
And then in that route, you execute the lua script.
maybe (just a myabe) that will work.
wkr,
Op do 3 dec. 2020 om 12:23 schreef Mark Allen :
> Hi Johan
>
> In the documentation for 3.1 lua module - TIMER_ROUTE is not one of the
>
Hi Johan
In the documentation for 3.1 lua module - TIMER_ROUTE is not one of the
routes available to lua_exec. If I include it in a TIMER route, OpenSIPS
fails to start with syntax error and the log error is:
CRITICAL:core:yyerror: parse error in
/etc/opensips/opensips.cfg:265:19-20: Command
It for sure does not run in async mode.
Did you try executing a script in timer route ?
What's the output in the log ?
Op do 3 dec. 2020 om 11:56 schreef Mark Allen :
> Is there a way to run a lua_exec from a timer route?
> ___
> Users mailing list
>
Is there a way to run a lua_exec from a timer route?
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
Gentle reminder,
We do not want you to miss your favorite feature for 3.2 and the we are
getting closer and closer to closing this poll.
Best regards,
Bogdan-Andrei Iancu
OpenSIPS Founder and Developer
https://www.opensips-solutions.com
OpenSIPS Bootcamp 2020 online
Hi All ,
I just encountered a scenario that Opensips is generating " 408 Request
Time out" continuously for 6hr . I have attached the flow diagram . USC
does not send ACK for the last 408 Error message . So , opensips is simply
re-transmitting it again and again till next 6hr .
Is this default
13 matches
Mail list logo
