Re: [SR-Users] Forward reply in onreply_route

2022-06-29 Thread Yuriy Gorlichenko
Since 5.6.0 there is forward_reply() in corex module https://kamailio.org/docs/modules/5.6.x/modules/corex.html#corex.f.forward_reply it doesn't have enough description but looking at the source it calls core->do_forward_reply function which ( at least as I see ) doesn't block the execution of the

Re: [SR-Users] Forward reply in onreply_route

2022-06-28 Thread Alex Balashov
> On Jun 28, 2022, at 10:06 AM, Olle E. Johansson wrote: > > I don’t know how to do it that way, but I would add stuff to mqueue and > process it asynchronously in the background. +1 — I think this is the way to go. Just push the workload off to some other async routine. -- Alex Balashov |

Re: [SR-Users] Forward reply in onreply_route

2022-06-28 Thread Emmanuel BUU
Le 28/06/2022 à 15:54, Carsten Bock a écrit : Hi, Question: Is there a way to forward a reply from the reply route and do other stuff afterward? We are currently doing operations on a 183 reply and it would be useful if we could forward the reply before continuing to process other stuff.

Re: [SR-Users] Forward reply in onreply_route

2022-06-28 Thread Daniel-Constantin Mierla
I think that what Olle suggested is a good solution. Otherwise, for tm onreply_route, using t_reply() can make tm generate its own reply and you can use it to overwrite the incoming reply, but I am not sure it works for 200ok -- for 300 or greater should be ok-ish all the time, unless you want to

Re: [SR-Users] Forward reply in onreply_route

2022-06-28 Thread Olle E. Johansson
> On 28 Jun 2022, at 15:54, Carsten Bock wrote: > > Hi, > > Question: > Is there a way to forward a reply from the reply route and do other stuff > afterward? We are currently doing operations on a 183 reply and it would be > useful if we could forward the reply before continuing to process

[SR-Users] Forward reply in onreply_route

2022-06-28 Thread Carsten Bock
Hi, Question: Is there a way to forward a reply from the reply route and do other stuff afterward? We are currently doing operations on a 183 reply and it would be useful if we could forward the reply before continuing to process other stuff. High-Level example: *route {