20 Oct
2016
20 Oct
'16
10:51 p.m.
Hi,
If a transaction is currently t_suspended() and has not been
t_continued(), will t_check_trans() still find that transaction for
retransmission-dampening purposes, e.g. if a retransmission of the same
request as the original one is received?
Thanks,
--
Alex Balashov | Principal | Evariste Systems LLC
Tel: +1-706-510-6800 (direct) / +1-800-250-5920 (toll-free)
Web: http://www.evaristesys.com/, http://www.csrpswitch.com/
21 Oct
21 Oct
12:22 p.m.
Hello,
On 20/10/16 21:51, Alex Balashov wrote:
Hi,
If a transaction is currently t_suspended() and has not been
t_continued(), will t_check_trans() still find that transaction for
retransmission-dampening purposes, e.g. if a retransmission of the
same request as the original one is received?
yes, the transaction is detected. Also the timeout runs for it and
failure_route can be executed in that case.
Cheers,
Daniel
--
Daniel-Constantin Mierla
http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda
Kamailio Advanced Training, Berlin, Oct 24-26, 2016 - http://www.asipto.com
12:26 p.m.
On 10/21/2016 05:22 AM, Daniel-Constantin Mierla wrote:
Also the timeout runs for it and failure_route can be
executed in
that case.
Interesting. That brings up two more questions:
1. If fr_timer is set to 3000 but I suspend the transaction for 4
seconds, does that mean that failure_route is going to be called at the
3000 mark anyway? If so, does that mean the transaction is implicitly
woken up (t_continue()'d) at that moment?
2. Does the failure_route run in a normal SIP worker, or in an async
worker, if using async_task_route() here?
--
Alex Balashov | Principal | Evariste Systems LLC
Tel: +1-706-510-6800 (direct) / +1-800-250-5920 (toll-free)
Web: http://www.evaristesys.com/, http://www.csrpswitch.com/
12:29 p.m.
On 21/10/16 11:26, Alex Balashov wrote:
On 10/21/2016 05:22 AM, Daniel-Constantin Mierla
wrote:
if you resume, the
transaction is back in processing -- from timeout
point of view, you can think of t_suspend() as a t_relay() without
sending out and the t_continue() as receiving a negative response and
willing to re-route the request.
Also the timeout runs for it and failure_route
can be executed in
that case.
Interesting. That brings up two more questions:
1. If fr_timer is set to 3000 but I suspend the transaction for 4
seconds, does that mean that failure_route is going to be called at
the 3000 mark anyway? If so, does that mean the transaction is
implicitly woken up (t_continue()'d) at that moment?
2. Does the failure_route run in a normal SIP worker, or in an async
worker, if using async_task_route() here?
Failure route for local triggered timeout is executed in the timer
process, the others by the sip worker that received the negative response.
Cheers,
Daniel
--
Daniel-Constantin Mierla
http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda
Kamailio Advanced Training, Berlin, Oct 24-26, 2016 - http://www.asipto.com
2937
days inactive
2938
days old
3 comments
2 participants
participants (2)
-
Alex Balashov -
Daniel-Constantin Mierla