2009/10/30 Juha Heinanen :
> Iñaki Baz Castillo writes:
>
> > So when a gateway is selected its attributes (strip, tag...) should be
> > loaded. If there are various entries in "gw" table with same ip_addr
> > but different attributes belonging to different groups, then the
> > selected attribu
Iñaki Baz Castillo writes:
> So when a gateway is selected its attributes (strip, tag...) should be
> loaded. If there are various entries in "gw" table with same ip_addr
> but different attributes belonging to different groups, then the
> selected attributes should be those included in the se
2009/10/30 Juha Heinanen :
> Iñaki Baz Castillo writes:
>
> > What do you mean with "gw group"? I just know "gateways" (in "gw"
> > table) and rules (in "lcr" table).
>
> gw groups have been in lcr module as long as it has existed. see
> readme. a gw group consists of one or more gws. it is gw
Iñaki Baz Castillo writes:
> What do you mean with "gw group"? I just know "gateways" (in "gw"
> table) and rules (in "lcr" table).
gw groups have been in lcr module as long as it has existed. see
readme. a gw group consists of one or more gws. it is gw groups that
are referred in lcr table,
2009/10/28 Juha Heinanen :
> it turned out that the problems ricardo reported on gw selection in
> lcr module were due to the fact that he has the same gw (same in terms of
> ip address) in more than one gw group and in each group the gw has
> different trip/tag attributes.
> load_gws() function t
it turned out that the problems ricardo reported on gw selection in
lcr module were due to the fact that he has the same gw (same in terms of
ip address) in more than one gw group and in each group the gw has
different trip/tag attributes.
load_gws() function tries the same gateway only once, but
El Sábado, 24 de Octubre de 2009, Juha Heinanen escribió:
> Iñaki Baz Castillo writes:
> > IMHO Kamailio shouln't start if there are more gateways than
> > MAX_NO_OF_GWS. This is, lcr module should give an error. Does it? (I've
> > not tryed it).
>
> the piece of code that i showed does that.
>
Iñaki Baz Castillo writes:
> IMHO Kamailio shouln't start if there are more gateways than MAX_NO_OF_GWS.
> This is, lcr module should give an error. Does it? (I've not tryed
> it).
the piece of code that i showed does that.
> > i can also add info about the limit in module documentation.
>
El Viernes, 23 de Octubre de 2009, Juha Heinanen escribió:
> Iñaki Baz Castillo writes:
> > Hi Juha, as this limitation is not present in the module
> > documentation, and the module doesn't notify it when starting, it
> > could create serious issues if an admin adds more than 128 gateways
> >
Ricardo Martinez writes:
> I modified the MAX_NO_OF_GWS to 256
> And the lcr_has_size to 256 and I'm still have the problem.
> Do you have the chance to reproduce the problem with kamailio 1.5.2 ?
i just tried with latest 1.5 version and priorities worked fine. i'm
thus unable to reproduce y
Iñaki Baz Castillo writes:
> Hi Juha, as this limitation is not present in the module
> documentation, and the module doesn't notify it when starting, it
> could create serious issues if an admin adds more than 128 gateways
> and he doesn't inspect the module source
> (really should he do t
El Jueves, 22 de Octubre de 2009, Juha Heinanen escribió:
> > #define MAX_NO_OF_GWS 128
> > Can I increase this value too? Maybe 256 ?
>
> yes, you can increase that too, but there is no config variable for it.
> so you need to recompile the module.
Hi Juha, as this limitation is not present in
13:14
Para: Ricardo Martinez
CC: users@lists.kamailio.org
Asunto: RE: [Kamailio-Users] LCR problem with "id" column and match
priorities
Ricardo Martinez writes:
> Can i change the lcr_has_size from the configuration file with the
> parameter?
>
> modparam("lcr&qu
Ricardo Martinez writes:
> Can i change the lcr_has_size from the configuration file with the
> parameter?
>
> modparam("lcr", "lcr_hash_size", 1024)
yes, you can do that.
> Another thing.
> Looking at the lcr_mod.c file there is a parameter called MAX_NO_OF_GWS
> defined as follows :
his value too? Maybe 256 ?
Thanks,
Ricardo.-
-Mensaje original-
De: Juha Heinanen [mailto:j...@tutpro.com]
Enviado el: jueves, 22 de octubre de 2009 12:41
Para: Ricardo Martinez
CC: users@lists.kamailio.org
Asunto: RE: [Kamailio-Users] LCR problem with "id" column and matc
Ricardo Martinez writes:
> I was trying to replicate the problem with another prefix, and was using
> the "id's" 132 and 133, correlative, however the problem persists.
id numbers should not have anything to do with this, because nowhere in
the module is id column used. the only thing that mig
n nombre de Juha Heinanen
Enviado el: jueves, 22 de octubre de 2009 8:17
Para: users@lists.kamailio.org
Asunto: [Kamailio-Users] LCR problem with "id" column and match
priorities
ricardo,
in situation where you see higher priority valued gateway group selected
first, do you know if the lower
ricardo,
in situation where you see higher priority valued gateway group selected
first, do you know if the lower priority valued group would be used if
none of the gateways in the higher priority valued gateway group can
serve the request? if it is used, then both exist in the hash table.
the li
Ricardo Martinez writes:
> This is a production machine..
> I can't do too much debug.
without more info it is hard to say more because i cannot reproduce the
problem here in simple setup.
-- juha
___
Kamailio (OpenSER) - Users mailing list
Users@li
] LCR problem with "id" column and match priorities.
Ricardo Martinez writes:
> This is happening to me with version 1.5.2 svnrevision: 2:5918M.
> In your test, do you have records between the id's 89 and
> 127?... could this something to do with it ?
no, just those two rec
Ricardo Martinez writes:
> This is happening to me with version 1.5.2 svnrevision: 2:5918M.
> In your test, do you have records between the id's 89 and
> 127?... could this something to do with it ?
no, just those two records. if you are able to try, i could add some
more debugging to the gro
21 de octubre de 2009 10:51
Para: Ricardo Martinez
CC: users@lists.kamailio.org
Asunto: RE: [Kamailio-Users] LCR problem with "id" column and match priorities.
ricardo,
i cannot reproduce your problem using sr_3.0 lcr module. i don't have
access to k 1.5 system right now, but this p
ricardo,
i cannot reproduce your problem using sr_3.0 lcr module. i don't have
access to k 1.5 system right now, but this part of the code, i.e.,
selecting gateway groups is the same.
in my test i have
r...@rautu:~# sip-proxy_ctl lcr.dump_gws
{
lcr_id: 1
grp_id: 1
ip_add
IGHT=25 FLAGS=0 PING=1
Ricardo.-
-Mensaje original-
De: Juha Heinanen [mailto:j...@tutpro.com]
Enviado el: miércoles, 21 de octubre de 2009 10:25
Para: Ricardo Martinez
CC: users@lists.kamailio.org
Asunto: RE: [Kamailio-Users] LCR problem with "id" column and match priorities.
Ricardo Martinez writes:
> mysql> select * from lcr where prefix=1351 order by id;
> +-++--++--+
> | id | prefix | from_uri | grp_id | priority |
> +-++--++--+
> | 127 | 1351 | | 51 |1 |
> | 128
miércoles, 21 de octubre de 2009 3:10
Para: Ricardo Martinez
CC: users@lists.kamailio.org
Asunto: [Kamailio-Users] LCR problem with "id" column and match priorities.
Ricardo Martinez writes:
> This keep happening even if change the priority value 2 for priority
> value 5. I
Ricardo Martinez writes:
> This keep happening even if change the priority value 2 for priority
> value 5. I even changed the priority 1 for priority 0 as follows :
>
> +-++--++--+
>
> | id | prefix | from_uri | grp_id | priority |
>
> +-+-
El Martes, 20 de Octubre de 2009, Ricardo Martinez escribió:
> So, when the prefix are with "no correlatives" values in the "id" column
> seems to be a problem to match the first priority. But when the values
> are correlative there is no problem.
>
> Is this the correct behavior? Maybe I'm mis
Hello List.
I'm having a weird behavior with the LCR module.
I have a particular prefix routed as follows (according to the LCR
tables) :
mysql> select * from lcr where prefix=0251;
+-++--++--+
| id | prefix | from_uri | grp_id | priority |
+-+-
29 matches
Mail list logo
