On 4/9/10 6:47 AM, Juha Heinanen wrote:
Daniel-Constantin Mierla writes:
for 3.1 we should get
rid of them and have only one mode. it also makes writing the docs
easier, when people can concentrate on one version of the docs instead
of two or three.
I
I noticed this too.
On 04/08/2010 11:11 AM, Andreas Granig wrote:
Hi,
In the docs at
http://kamailio.org/docs/modules/3.0.x/modules/tm.html#fr_inv_timer it
says that fr_inv_timer_avp should be defined like this, without $ or $avp:
modparam(tm, fr_inv_timer_avp, my_fr_inv_timer)
In kam = 1.5
Juha,
Juha Heinanen wrote:
for example, this kind of call works for me:
t_set_fr($avp(i:722), @cfg_get.local.phone_timeout);
Thanks. I was doing it wrong, namely without the double-quotes. D'oh.
Andreas
___
Kamailio (OpenSER) - Users
On 4/8/10 10:05 PM, Juha Heinanen wrote:
Daniel-Constantin Mierla writes:
When #!KAMAILIO is defined and the value of timeout avp is less than
120, then it is multiplied with 1000 (auto-correction from second to
milisecond), but since it actually second for AVP case, will result
On 04/08/2010 05:06 PM, Ovidiu Sas wrote:
I have to agree with Juha here. In the next major release we should
get rid of this flavor stuff.
Everyone should bite the bullet and make their old scripts compatible
with the new architecture.
Even I will agree with this, and I am very resistant to
On 4/8/10 5:35 PM, Andreas Granig wrote:
Juha,
Juha Heinanen wrote:
for example, this kind of call works for me:
t_set_fr($avp(i:722), @cfg_get.local.phone_timeout);
Thanks. I was doing it wrong, namely without the double-quotes. D'oh.
I committed on git master and
On 4/8/10 11:06 PM, Alex Balashov wrote:
On 04/08/2010 05:06 PM, Ovidiu Sas wrote:
I have to agree with Juha here. In the next major release we should
get rid of this flavor stuff.
Everyone should bite the bullet and make their old scripts compatible
with the new architecture.
Even I will
The thing is that the flavor is controlling the behavior of several
module as opposed to params that are controlling the behavior of a
single module.
For the next release, it would be nice to get rid of it and maybe
perform the following:
- we should switch to ms for all tm timers;
- maybe we
Daniel-Constantin Mierla writes:
for 3.1 we should get
rid of them and have only one mode. it also makes writing the docs
easier, when people can concentrate on one version of the docs instead
of two or three.
I agree we should reduce as much as possible, but as said
