2010/1/25 Henning Westerholt :
> from the performance POV this three ways make probably not that much a
> difference, but i'd differ them over the intendent use case:
>
> 1. global AVPs
>
> This is the oldest mechanism, i think they were implemented as a list in the
> core. In kamailio we moved th
On Monday 25 January 2010, Antonio Reale wrote:
> > you should upgrade for such features:
> > - in 1.5.x you can use htable to cache value in shared memory and perhaps
> > offers what you need
> > - in 3.0.0 you still have htable, but you have also the global avps, you
> > can set/get them with $av
2010/1/13 Daniel-Constantin Mierla :
> Hello,
>
> you should upgrade for such features:
> - in 1.5.x you can use htable to cache value in shared memory and perhaps
> offers what you need
> - in 3.0.0 you still have htable, but you have also the global avps, you can
> set/get them with $avp(g.name).
2010/1/13 Daniel-Constantin Mierla :
> Hello,
Hi Daniel.
> you should upgrade for such features:
> - in 1.5.x you can use htable to cache value in shared memory and perhaps
> offers what you need
> - in 3.0.0 you still have htable, but you have also the global avps, you can
> set/get them with $a
Hello,
On 1/11/10 12:09 PM, Antonio Reale wrote:
Hi all,
I'd like to simulate in kamailio 1.4.4, the loading of a global
setting (like a parameter that is loaded only at startup), using AVPs.
So, I want to load some AVP only at proxy startup. Probably it is not
possible because, if I'm not wrong
Hi all,
I'd like to simulate in kamailio 1.4.4, the loading of a global
setting (like a parameter that is loaded only at startup), using AVPs.
So, I want to load some AVP only at proxy startup. Probably it is not
possible because, if I'm not wrong, AVPs are transaction persistent.
The problem is th
