26 Feb
2010
26 Feb
'10
4:17 p.m.
On Feb 24, 2010 at 21:20, Min Wang <wang(a)basis-audionet.com> wrote:
Hi Andrei:
It is know.
You have to define TM_ONREPLY_FINAL_DROP_OK or else it won't be
compiled.
E.g.: make cfg extra_defs=-DTM_ONREPLY_FINAL_DROP_OK; make all
or re-compiling only tm:
make -C modules/tm extra_defs=-DTM_ONREPLY_FINAL_DROP_OK.
You'll get a compile time warning when active.
Try the latest code on master. It was more
complex than I thought, but
now it should be possible to use t_reply() from both kinds of
onreply_routes, even from the script.
E.g.:
onreply_route{ # main/core onreply_route
if (some condition) {
t_reply("600", "Denied");
drop;
}
}
I did some tests on both main and tm onreply_route for 180 msg from
scripts, it works!!
In this case you would still need your function
to send the ack & bye.
It will work too in the tm onreply_routes, but not for 2xx replies.
If someone really needs to drop 2xx replies from tm onreply routes and
volunteers to do the heavy testing, we could try allowing it (along
with
the stop timer changes it should work
theoretically).
Is the changes to drop 2xx in git repo?
My prefered way is to be able to drop 2xx in tm onreply_routes,
otherwise my_function_check in the main onreply_route seems will get
complicated. (am I a little lazy :)? )
Andrei