Juha Heinanen writes:
> While testing xflags, i noticed that a regular flag that I set AFTER
> calling t_newtrans() stays set in onreply_route even when I do not
> call t_flush_flags().
I made the same test with xflags and they do require t_flush_xflags()
call if an xflag is set after t_newtrans(); So the behavior is not the
same with flags and xflags.
This is confusing. The flags should behave the same way and I would
prefer the flags way in order to avoid the flush call.
I added sr-dev to this thread since it now deals also the new feature.
-- Juha
I tested xflags by making these calls in a route block:
INFO(********** setting flag 19);
setflag(19);
INFO(********** setting xflag 19);
setxflag(19);
and these calls in onreply_route block:
if (isflagset(19))
INFO(********* flag 19 is set);
else
INFO(********* flag 19 is NOT set);
if (isxflagset(19))
INFO(********* xflag 19 is set);
else
INFO(********* xflag 19 is NOT set);
The result to syslog was:
Mar 25 10:51:50 trout /usr/bin/sip-proxy[17939]: INFO: ********** setting flag 19
Mar 25 10:51:50 trout /usr/bin/sip-proxy[17939]: INFO: ********** setting xflag 19
Mar 25 10:51:50 trout /usr/bin/sip-proxy[17867]: INFO: ********* flag 19 is set
Mar 25 10:51:50 trout /usr/bin/sip-proxy[17867]: INFO: ********* xflag 19 is NOT set
-- Juha