Hello Juha, i have my lcr_count set as modparam("lcr", "lcr_count", 102). This is really messy then. Is there something else which could help to understand the cause of this? I see you use sip-proxy as flavorful, maybe there something is a bit different? Antanas On 2012.07.27 12:41, Juha Heinanen wrote:
Antanas Masevicius writes:
it looks like column order a bit changed in my system after using alter table during migrations. That is prefix col is not it its place. Thus this data: (1424,90,'OP1','10.10.10.10','',5060,NULL,1,0,NULL,'11#',1,NULL,NULL); should be fixed as: (1424,90,'OP1','10.10.10.10','',5060,NULL,1,0,NULL,NULL,'11#',1,NULL); antanas,
i tried with your lcr data and calling 118 worked fine. by changing load_gw function syslog log messages to INFOs, i got:
Jul 27 12:18:56 siika /usr/sbin/sip-proxy[7260]: INFO: lcr [lcr_mod.c:1855]: load_gws(90, 118, sip:+35832345670@test.fi) Jul 27 12:18:56 siika /usr/sbin/sip-proxy[7260]: INFO: lcr [lcr_mod.c:1929]: added matched_gws[0]=[1, 3, 0, 545355600]
and then my proxy tried to send the request to the given ip address.
check that your lcr_count param value is at least 90. name of the param is misleading. it should be called max_lcr_id.
-- juha
-- Antanas Masevičius Technikos direktorius UAB "Nacionalinis telekomunikaciju tinklas" Tel. +370 5 2056000 Tel. +370 700 00031 (tiesioginis) Fax. +370 700 00034 el.p: antanas.masevicius@ntt.lt www.ntt.lt www.spykas.com