2010/5/12 Iñaki Baz Castillo ibc@aliax.net:
2010/5/12 Maciej Bylica mbsip@gazeta.pl:
Hi ALL,
I have a problem to configure LCR module to work properly (kamailio rel. 1.5) The task in my case is to handle:
- All calls coming with CLD number prefix 482223344 from my MGW
(77.77.77.77) towards kamilio and direct them to sip world (88.88.88.88) 2) Calls with CLD starting with 48 coming from SIP world towards kamailio and direct them to my MGWs. Additionaly i need to route it on the basis of CLI number. So MGWs <---> Kamailio <---> SIPProxies (88.88.88.88)
In db: +----+-----------+----------------+--------+----------+ | id | prefix | from_uri | grp_id | priority | +----+-----------+----------------+--------+----------+ | 1 | 48 | 48 | 1 | 1 | | 2 | 48 | 49 | 2 | 1 | | 3 | 482223344 | 77.77.77.77 | 3 | 1 | +----+-----------+----------------+--------+----------+
Unfortunately:
- call is originated on 77.77.77.77 with CLD 48222334455 number and
kamailio forward this call to grp_id=3 SIPWORLD which is okay. The problem is that if the call fail, kamailio will try to use 77.77.77.70 and 77.77.77.71 from grp_id=1 which is wrong. I have no idea how to provide a kind of huntstop in grp_id=3.
Why do you set "77.77.77.77" in the from_uri field of the third entry in 'lcr' table? It makes no sense. As you don't pass a pseudovariable to the command load_gw() then LCR tries to match the *From URI* of the INVITE with the 'from_uri' of the 'lcr' table.
-- Iñaki Baz Castillo ibc@aliax.net
Hi,
Thx for prompt answer. I was playing around with lcr table and found that i may place an IP address which is a part of sip uri there. It means that if a call is originated from 77.77.77.77 (from sip uri 482223344@77.77.77.77) then grp_id=3 should be chosen. Of course i may wipe this out but i am unsure if it help.
Thx, Maciej