On 4/7/10 11:37 PM, Iñaki Baz Castillo wrote:
2010/4/7 Daniel-Constantin Mierlamico...@gmail.com:
It's Kamailio 1.5.1-notls. Now I've compiled 1.5.4-notls and increased
PKG memory to 16.
if I spot it right on the svn commit log, there was a fix for a leak related
to dst_uri when
2010/4/8 Juha Heinanen j...@tutpro.com:
Iñaki Baz Castillo writes:
Would it affect when use LCR module 'next_gw()' funtion in
failure_route? It creates a new branch internally
inaki,
next_gw() sets dst uri if you have given a hostname for the gateway in
hostname column of gw table.
Hi,
I'll participate also.
Regards,
Ramona
On 04/08/2010 10:48 AM, Daniel-Constantin Mierla wrote:
Hello,
I know some of devels are still in Easter vacation, but I hope we can
get together soon on irc to sketch the plan for 3.1 release.
I propose next week, Wednesday, April 14, 15:00UTC,
2010/4/8 Iñaki Baz Castillo i...@aliax.net:
2010/4/8 Daniel-Constantin Mierla mico...@gmail.com:
it does not look as a dump with memory debugging on.
SOrry, I just applied MEMDBG=1 in one of the servers and got the
output in the other.
When memdbg is on, you should get something like:
On 4/8/10 1:21 PM, Iñaki Baz Castillo wrote:
2010/4/8 Iñaki Baz Castilloi...@aliax.net:
2010/4/8 Daniel-Constantin Mierlamico...@gmail.com:
it does not look as a dump with memory debugging on.
SOrry, I just applied MEMDBG=1 in one of the servers and got the
output in the
2010/4/8 Daniel-Constantin Mierla mico...@gmail.com:
Do I miss something? is it possible to log allocated and freeded
memory without generating so many logs?
the goal is to see the places where the memory was allocated. That will give
the proper hints about the leak.
What you can do is to
I too would be interested in the answer to this question. Thank you for
posting it, Andreas.
On 04/08/2010 08:27 AM, Andreas Granig wrote:
Hi,
Looks like behavior of drop has changed in Kamailio 3.0. Before, I was
able to drop() a specific branch in branch_route depending on various
checks.
2010/4/8 Andreas Granig agra...@sipwise.com:
Hi,
Looks like behavior of drop has changed in Kamailio 3.0. Before, I was able
to drop() a specific branch in branch_route depending on various checks.
http://www.kamailio.org/dokuwiki/doku.php/core-cookbook:3.0.x#drop still
says this is
El Thu, 8 Apr 2010 14:52:15 +0200
Iñaki Baz Castillo i...@aliax.net escribió:
So calling drop() in branch_route has no effect, and I have no idea how to
mark a branch in branch_route to be dropped in onsend_route, because
checking a bflag doesn't work there, and neither does checking $rU.
El Thu, 8 Apr 2010 14:52:15 +0200
Iñaki Baz Castillo i...@aliax.net escribió:
Any ideas on how to accomplish dropping a specific branch?
If you use it to drop requests going to unsafe destinations (like
when a REGISTER contains a spoofed Contact URI pointing to a gw or
the proxy itself)
Hi,
seems this part was forgotten during the integration process. I attached
a patch that should fix it, please test it (i didn't at all) and let me
know the results.
If all ok I will double check with Andrei to see if breaks something in
the new TM architecture and then push it to git
Hi Daniel,
Daniel-Constantin Mierla wrote:
seems this part was forgotten during the integration process. I attached
a patch that should fix it, please test it (i didn't at all) and let me
know the results.
If all ok I will double check with Andrei to see if breaks something in
the new TM
In addition, it would be convenient to update this phrase
...It is not possible to drop a message or generate a reply.
http://kamailio.org/docs/modules/3.0.x/modules/tm.html#t_on_branch
as it may indicate that drop does not work in branch_route
___
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
Andreas Granig writes:
Anyhow, it seems to be deprecated anyways, so I'm looking to get
t_set_fr() working. I'm just curious how I can use a var or AVP loaded
from DB to set the value on-the-fly? t_set_fr(...) seems to allow only
constants to be set. Couldn't find anything in the docs
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
El Thu, 8 Apr 2010 18:40:33 +0200
Jon Bonilla (Manwe) ma...@aholab.ehu.es escribió:
Hi
Forgot to comment:
The correct behaviour should be just one INVITE like
U 2010/04/08 17:51:09.614055 77.77.77.77:5060 - 91.121.117.27:5080
INVITE sip:+4644235465675...@sindominio.net SIP/2.0'
right?
El Thu, 8 Apr 2010 20:11:35 +0300
j...@tutpro.com (Juha Heinanen) escribió:
jon,
since you have hostname defined, next_gw() function sets r-uri and
destination uri and t_relay() should relay only based destination uri
unless you call t_relay() more than once.
No append_branch is
Jon Bonilla (Manwe) writes:
I have xloged $du and $ru just after next_gw() call and also in branch_route:
Afer next_gw
ru=sip:58658765876587...@77.77.77.77
du=sip:91.121.117.27:5080
Branch
ru=sip:58658765876587...@77.77.77.77
du=sip:91.121.117.27:5080
Branch
2010/4/8 Juha Heinanen j...@tutpro.com:
Jon Bonilla (Manwe) writes:
I have xloged $du and $ru just after next_gw() call and also in
branch_route:
Afer next_gw
ru=sip:58658765876587...@77.77.77.77
du=sip:91.121.117.27:5080
Branch
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
26 matches
Mail list logo
