Thanks Juha
I populated the lcr tables by hand. This is how they look now, I have 2 lcr_ids
[1 and 2], each instance has its own gw. And each instance has its own prefix
to match for [ and ].
The idea is that a call comes in with R-URI 13051234567, it should match
the
lcr.reload load the tables to memory and does not print
anything. lcr.dump_[gws|rules] prints what is in memory.
perhaps you didn't set lcr_count. please read whole README carefully.
-- juha
you are right, I guess I did not have the module well configured
From: fbo...@hotmail.com
To: sr-u
Fabian Borot writes:
> Then I tried the sercmd commands to reload and dump and I do not see
> the contents o the screen. Is this how is supposed to work now?. How
> do I know that the new values are being loaded into memory w/o
> restarting kamailio?
lcr.reload load the tables to memory and does
Thanks Juha
I populated the lcr tables by hand. This is how they look now, I have 2 lcr_ids
[1 and 2], each instance has its own gw. And each instance has its own prefix
to match for [ and ].
The idea is that a call comes in with R-URI 13051234567, it should mat
Fabian Borot writes:
> I am trying to port our setup from kamailio 1.4.3 to 3.1.4 and I see
> huge differences on the LCR module.
there is a script somewhere (read wiki) that upgrades the tables.
> I have these main questions:
>
> 1- does lcr_id replaces the grp_id?
not really. lcr_ids denote
I am trying to port our setup from kamailio 1.4.3 to 3.1.4 and I see huge
differences on the LCR module.
I have these main questions:
1- does lcr_id replaces the grp_id?
2- what happened to the fifo commands to add gws etc:
lcr addgw
... add a gateway with fla
