Andrei Pelinescu-Onciul wrote:
On Jul 01, 2009 at 13:11, Juha Heinanen wrote:
Daniel-Constantin Mierla writes:
> For kamailio, in request and failure route they are the same, stop
> processing of the actions. But in branch route and reply route drop does
> a bit more: drop current process
On Wednesday 01 July 2009 15:02:32 Juha Heinanen wrote:
> Henning Westerholt writes:
> > So that means we could drop the "drop" command? Fine, one statement
> > less. :)
>
> i just commented on it from my own point of view. perhaps there are
> other needs for 'drop' than dropping transactionless
Andrei Pelinescu-Onciul writes:
> You still need one in the sl_reply_route. It should contain only drop if
> you want to be equivalent to your if (!t_check_trans()) drop; in the
> onreply_route. If it doesn't contain a drop or a return 0, it won't
> drop the reply :-)
i understood that 'retu
Hi Andrei,
On 07/01/2009 04:02 PM, Andrei Pelinescu-Onciul wrote:
On Jul 01, 2009 at 13:11, Juha Heinanen wrote:
Daniel-Constantin Mierla writes:
> For kamailio, in request and failure route they are the same, stop
> processing of the actions. But in branch route and reply route drop does
On 07/01/2009 04:00 PM, Henning Westerholt wrote:
On Mittwoch, 1. Juli 2009, Juha Heinanen wrote:
> I see, so you did it before tm module saw the reply. In fact both
> solutions wrap to the same function, t_check(), so you should get the
> same result.
fine. so in my config, i don't anymore
On Jul 01, 2009 at 16:56, Juha Heinanen wrote:
> Miklos Tirpak writes:
>
> > I see, so you did it before tm module saw the reply. In fact both
> > solutions wrap to the same function, t_check(), so you should get the
> > same result.
>
> fine. so in my config, i don't anymore have a need fo
On Jul 01, 2009 at 13:11, Juha Heinanen wrote:
> Daniel-Constantin Mierla writes:
>
> > For kamailio, in request and failure route they are the same, stop
> > processing of the actions. But in branch route and reply route drop does
> > a bit more: drop current processed branch respectively r
Henning Westerholt writes:
> So that means we could drop the "drop" command? Fine, one statement
> less. :)
i just commented on it from my own point of view. perhaps there are
other needs for 'drop' than dropping transactionless replies (for which
purpose it is not needed).
-- juha
_
On Mittwoch, 1. Juli 2009, Juha Heinanen wrote:
> > I see, so you did it before tm module saw the reply. In fact both
> > solutions wrap to the same function, t_check(), so you should get the
> > same result.
>
> fine. so in my config, i don't anymore have a need for 'drop' command.
So that mea
Miklos Tirpak writes:
> I see, so you did it before tm module saw the reply. In fact both
> solutions wrap to the same function, t_check(), so you should get the
> same result.
fine. so in my config, i don't anymore have a need for 'drop' command.
-- juha
__
On 07/01/2009 02:25 PM, Juha Heinanen wrote:
Miklos Tirpak writes:
> Anyway, I think your particular problem can be solved with the
> on_sl_reply modparam:
>
> modparam(tm, on_sl_reply, "stateless_reply");
>
> onreply_route["stateless_reply"]
> {
> # This route is executes if tm
Miklos Tirpak writes:
> Anyway, I think your particular problem can be solved with the
> on_sl_reply modparam:
>
> modparam(tm, on_sl_reply, "stateless_reply");
>
> onreply_route["stateless_reply"]
> {
> # This route is executes if tm module does not find
> # the transaction
Hi,
as I know only t_drop_replies() function exists in tm module that does
something similar, but it drops all the replies received so far, and it
is usable only from failure_route.
Anyway, I think your particular problem can be solved with the
on_sl_reply modparam:
modparam(tm, on_sl_repl
Daniel-Constantin Mierla writes:
> For kamailio, in request and failure route they are the same, stop
> processing of the actions. But in branch route and reply route drop does
> a bit more: drop current processed branch respectively reply, so they
> are not forwarded.
i'm calling 'drop' i
Hello,
in kamailio there is a difference between exit and drop, while in ser is
basically the same (exit functionality).
For kamailio, in request and failure route they are the same, stop
processing of the actions. But in branch route and reply route drop does
a bit more: drop current proces
15 matches
Mail list logo
