On Thursday 15 July 2010 16:04:47 Daniel-Constantin Mierla wrote:
Hello,
the support for named flags isn't yet propagated to modules and functions coming from kamailio -- only the functions coming from core support it (e.g., setflag, isflagset, resetflag).
Hopefully next release will fix some of missing easy to integrate K+S things.
Just to mention that in devel (upcoming 3.1) you can use 'define' to give names to various integer things, e.g.,:
#!define ACCFLAG 1
modparam("acc", "db_flag", ACCFLAG)
setflag(ACCFLAG);
So then .. why define "flags" ... if then you could do it by using #!define sentences ? ... redundant ... IMHO
Continue with the testing ... now other "mistery" errors ...
0(14595) : <core> [cfg.y:3330]: parse error in config file /etc/kamailio/kamailio.cfg, line 161, column 13-20: syntax error 0(14595) : <core> [cfg.y:3330]: parse error in config file /etc/kamailio/kamailio.cfg, line 161, column 13-20: call params error
0(14595) : <core> [cfg.y:3330]: parse error in config file /etc/kamailio/kamailio.cfg, line 161, column 13-20: call params error
0(14595) : <core> [cfg.y:3333]: parse error in config file /etc/kamailio/kamailio.cfg, line 161, column 21: unknown command, missing loadmodule?
[kamailio.cfg] 155: #---- Request is behind NAT(NAT_FLAG) save with bflag NAT_FLAG ----# 156: #---- Use bflag NAT_PING to start SIP pinging (OPTIONS) ----# 157: if(isflagset(NAT_FLAG)) { 158: setbflag(NAT_FLAG); 159: setbflag(NAT_PING); 160: } 161: if(!save("location")) { 162: sl_reply_error(); 163: exit; 164: }
So I'm stucked ... why 161 it's wrong ? registrar module it's loaded
Best regards