Hello,
right direction, but maybe the change is not required everywhere or
maybe inside some functions, you have to analyze where is pvar and where
is ser-style avp.
Cheers,
Daniel
On 5/24/13 9:22 AM, Victor Seva wrote:
2013/5/23 Victor Seva :
2013/5/23 Daniel-Constantin Mierla :
- update
2013/5/23 Victor Seva :
> 2013/5/23 Daniel-Constantin Mierla :
>> - update the interpreter to use pv cache instead of own spec per pv (I can
>> do it, being in my list and hopefully is no big change)
>
> I will try to do it myself just to get familliar with this area. Let's
> see how it goes.
You
On 5/24/13 12:00 AM, Daniel-Constantin Mierla wrote:
On 5/23/13 10:45 PM, Victor Seva wrote:
2013/5/23 Daniel-Constantin Mierla :
First a general recommendation: try to avoid patching core that much
for
non-common use cases.
Sure. I was just trying to see how this could be done. I don't wan
On 5/23/13 10:45 PM, Victor Seva wrote:
2013/5/23 Daniel-Constantin Mierla :
First a general recommendation: try to avoid patching core that much for
non-common use cases.
Sure. I was just trying to see how this could be done. I don't want to
mess with the core. :-)
[snip]
At this moment, I
2013/5/23 Daniel-Constantin Mierla :
> First a general recommendation: try to avoid patching core that much for
> non-common use cases.
Sure. I was just trying to see how this could be done. I don't want to
mess with the core. :-)
[snip]
> At this moment, I think a good solution could be:
[snip]
First a general recommendation: try to avoid patching core that much for
non-common use cases.
The pv spec does not store the pv name in most of the cases, storing it
there will increase size of structure and it is not needed in typical
use cases.
At this moment, I think a good solution coul
2013/5/23 Daniel-Constantin Mierla :
> Look for ASSIGN_T in core, one place to go to and check is lval_assign(...)
> function, not sure there are other in core.
Ok. First attempt to get this done.
I've created a new core cfg parameter "log_assign_actions" to
activate/deactivate de log. No problem
On 5/23/13 10:47 AM, Victor Seva wrote:
2013/4/22 Daniel-Constantin Mierla :
From what Andreas suggesting, printing the value of variables as they are
assigned is missing, probably can be added by hooking in the interpreter
when doing the assignment operation.
Can you point me to the right di
2013/4/22 Daniel-Constantin Mierla :
> From what Andreas suggesting, printing the value of variables as they are
> assigned is missing, probably can be added by hooking in the interpreter
> when doing the assignment operation.
Can you point me to the right direction here? What are the files involv
On Mon, Apr 22, 2013 at 9:08 PM, Andreas Granig wrote:
> Hi,
>
> I'd like to put a topic up for discussion to test kamailio config logics.
>
> The standard way of doing so is to start kamailio as usual and write sipp or
> sipsak scenarios to perform automated tests. This can get quite complex
> pr
Hi,
On 04/22/2013 07:34 PM, Daniel-Constantin Mierla wrote:
Details about going out can be printed on onsend_route. In this route
block, one can execute drop and nothing is sent to the wire. It can be a
config started with a special define specified with -A parameter.
Enabling debugger module w
22 apr 2013 kl. 19:34 skrev Daniel-Constantin Mierla :
>
> On 4/22/13 5:30 PM, Juha Heinanen wrote:
>> Andreas Granig writes:
>>
>>> Let me know if this is stupid and/or a complete overkill, but what about
>>> introducing some kind of dummy mode, where you'd pipe a message into
>>> kamailio via
On 4/22/13 5:30 PM, Juha Heinanen wrote:
Andreas Granig writes:
Let me know if this is stupid and/or a complete overkill, but what about
introducing some kind of dummy mode, where you'd pipe a message into
kamailio via stdin, and get the resulting message out on stdout (e.g. in
ngrep style wit
13 matches
Mail list logo
