Atle Samuelsen writes:
i have a question related to this:
In you reply_route, setflag(10);
in order to get to reply route, one must call t_on_reply(x) in a route
block. is there some way to unset t_on_reply in reply_route and thus
prevent further replies getting into there?
if i remember correctly, one must re-call t_on_failure in failure route,
but t_on_reply seems to stick on forever.
-- juha