[SR-Users] No error line printed ?

[Daniel-Constantin Mierla]

On 7/15/10 10:15 PM, Raúl Alexis Betancor Santana wrote:
> 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
>    

names for flags were introduced in ser 2.0 and inherited in 3.0 -- since 
they come from ser side, kamailio modules do not support them yet.

setbflag() works on another set of flags -- branch flags -- and the 
respective functions are exported by kex module. So using flag names 
with these functions do not work.

On the other hand #!defined IDs are pre-processor replacements, 
therefore working with any kind of parameter, using them to name flags 
is just a use case.

Cheers,
Daniel

> 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
>    

-- 
Daniel-Constantin Mierla
http://www.asipto.com/