I pushed a patch for it -- onreply_route was using the xflags from reply
structure, not from transaction.
Cheers,
Daniel
On 25.03.18 10:02, Juha Heinanen wrote:
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
_______________________________________________
Kamailio (SER) - Development Mailing List
sr-dev(a)lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-dev
--
Daniel-Constantin Mierla
www.twitter.com/miconda --
www.linkedin.com/in/miconda
Kamailio Advanced Training - April 16-18, 2018, Berlin -
www.asipto.com
Kamailio World Conference - May 14-16, 2018 -
www.kamailioworld.com