15 Oct
2009
15 Oct
'09
5:48 p.m.
Hello list.
I have a question/problem regarding the LCR module. I'm using Kamailio
version 1.5.2. The LCR tables have :
gw table : 126 records
lrc tables : 120 records.
I'm using the "ping" (ping = 1) feature in all my gateways, part of the
cfg file is as follows :
modparam("lcr","db_url","mysql://openserro:openserro@localhost/openser")
modparam("tm", "fr_inv_timer_avp", "$avp(i:704)")
modparam("lcr", "gw_uri_avp", "$avp(i:709)")
modparam("^auth$|lcr", "rpid_avp", "$avp(i:302)")
modparam("lcr", "ruri_user_avp", "$avp(i:500)")
modparam("lcr", "flags_avp", "$avp(i:712)")
modparam("lcr", "fetch_rows", 3000)
modparam("lcr", "ping_interval", 10)
modparam("lcr", "ping_from", "sip:pinger@mydomain.net")
modparam("lcr", "ping_method", "OPTIONS")
From time to time I can see 3 o 4 gateways marked as
down (with the
command kamctl lcr dump). I'm not manually monitoring the
gateways
every minute so is possible that in a particular moment the gateways
could be unreachable, but when I run the command "kamctl lcr dump" the
gateways are on-line, that's for sure.
So I'm not understanding why LCR keep marking the gateways as down, even
if they are answering to the OPTIONS request. Could this be a bug in
the LCR module? Or maybe I'm missing something?. The silly part of all
this is the gateways marked as down are always the same. Could this be
related to a memory issue??
Can someone guide me here?.
Thanks in advance,
Regards,
Ricardo Martinez.-
15 Oct
15 Oct
5:47 p.m.
New subject: [Kamailio-Users] Problem with LCR "ping"
Ricardo Martinez writes:
So I'm not understanding why LCR keep marking the
gateways as down, even
if they are answering to the OPTIONS request. Could this be a bug in
the LCR module? Or maybe I'm missing something?. The silly part of all
this is the gateways marked as down are always the same. Could this be
related to a memory issue??
ricardo,
lcr keepalive was introduced in 1.5 by another person and i don't know
much about it. in k 3.0 the feature has been replaced by a non-polling
version. if lcr keepalive in 1.5 gives you problems, i suggest that you
don't use it.
-- juha
16 Oct
16 Oct
4:56 p.m.
On Donnerstag, 15. Oktober 2009, Juha Heinanen wrote:
Perhaps the person who introduced this functionality can comment on this? I
reviewed the patches but not found the commit in question and not remember at
the moment. Of course its also possible that you just take a look to the code
and try to find the bug by yourself. ;)
Regards,
Henning
So I'm not
understanding why LCR keep marking the gateways as down, even
if they are answering to the OPTIONS request. Could this be a bug in
the LCR module? Or maybe I'm missing something?. The silly part of all
this is the gateways marked as down are always the same. Could this be
related to a memory issue??
lcr keepalive was introduced in 1.5 by another person and i don't know
much about it. in k 3.0 the feature has been replaced by a non-polling
version. if lcr keepalive in 1.5 gives you problems, i suggest that you
don't use it.
5 p.m.
Henning Westerholt writes:
Perhaps the person who introduced this functionality
can comment on this? I
reviewed the patches but not found the commit in question and not
remember at the moment. Of course its also possible that you just
take a look to the code and try to find the bug by yourself. ;)
not going to do it, because the whole keepalive feature has been changed
by another one in 3.0. this new implementation will be supported.
-- juha
5:03 p.m.
On Freitag, 16. Oktober 2009, Juha Heinanen wrote:
Henning Westerholt writes:
Juha,
yes, i referred to Ricardo with this statement, think i understand your
previous mail correctly.
Regards,
Henning
Perhaps the person who introduced this
functionality can comment on
this? I reviewed the patches but not found the commit in question and
not remember at the moment. Of course its also possible that you just
take a look to the code and try to find the bug by yourself. ;)
not going to do it, because the whole keepalive feature has been changed
by another one in 3.0. this new implementation will be supported. 
6:41 p.m.
Hi Henning,
here is the missing commit, feature was developed by Alexandr Dubovikov:
http://openser.svn.sourceforge.net/viewvc/openser?view=rev&revision=5424
regards,
Andreas
2009/10/16 Henning Westerholt <henning.westerholt(a)1und1.de>
On Donnerstag, 15. Oktober 2009, Juha Heinanen
wrote:
Perhaps the person who introduced this functionality can comment on this? I
reviewed the patches but not found the commit in question and not remember
at the moment. Of course its also possible that you just take a look to the
code and try to find the bug by yourself. ;)
Regards,
Henning
_______________________________________________
Kamailio (OpenSER) - Users mailing list
Users(a)lists.kamailio.org
http://lists.kamailio.org/cgi-bin/mailman/listinfo/users
http://lists.openser-project.org/cgi-bin/mailman/listinfo/users
> So I'm not understanding why LCR keep
marking the gateways as down,
even
if they
are answering to the OPTIONS request. Could this be a bug in
the LCR module? Or maybe I'm missing something?. The silly part of all
this is the gateways marked as down are always the same. Could this be
related to a memory issue??
lcr keepalive was introduced in 1.5 by another person and i don't know
much about it. in k 3.0 the feature has been replaced by a non-polling
version. if lcr keepalive in 1.5 gives you problems, i suggest that you
don't use it.
5519
days inactive
5520
days old
5 comments
4 participants
participants (4)
-
Andreas Heise -
Henning Westerholt -
jh＠tutpro.com -
Ricardo Martinez