Hi,
we are using kamailio 5.8 with t_suspend to suspend calls until a push notification wakes up the phone. The phone will then send an NOTIFY with information, so that t_continue can be called.
This works well, but currently we are facing issues with rtpengine, and looking at the logs, there is something suspicious:
we are calling:
t_continue("$sht(vtp=>id_index::$hdr(X-Resume))", "$sht(vtp=>id_label::$hdr(X-Resume))", "RESUME"); ... route[RESUME] { xdbgl("[RESUME] rm=$rm ru=$ru du=$du \n"); ...
after the call to t_continue i can see the log mentioned above:
Jun 24 16:20:52 proxy5 /usr/sbin/kamailio[2337]: DEBUG: {1 34558 NOTIFY sFsXwoWeDXHOzRHqVfA4E5KDT9U6qoov} <script>: 486:[RESUME] rm=INVITE ru=sip:<URI_REDACTED>
I wondered why the log call still logs the context as the NOTIFY context and not the INVITE context, and if that might lead to issues?
currently we get problems with rtpengine_manage when we try to call it in the route[RESUME]
Jun 24 16:20:52 proxy5 /usr/sbin/kamailio[2337]: DEBUG: {1 34558 NOTIFY sFsXwoWeDXHOzRHqVfA4E5KDT9U6qoov} rtpengine [rtpengine.c:3198]: rtpp_function_call(): proxy reply: d7:warning38:Call-ID not found or tags didn't match6:result2:oke
We are currently checking, if we can work around this issue, but i am hoping to getting a bit of insight from you.
Best Regards JWes
Hello,
the context of the t_continue() is failure_route:
- https://www.kamailio.org/docs/modules/stable/modules/tmx.html#tmx.f.t_contin...
You have to use rtpengine_manage() in branch_route, otherwise in failure-route it does the delete/destroy of the session.
Cheers, Daniel
On 25.06.25 11:15, Johannes Westhuis via sr-users wrote:
Hi,
we are using kamailio 5.8 with t_suspend to suspend calls until a push notification wakes up the phone. The phone will then send an NOTIFY with information, so that t_continue can be called.
This works well, but currently we are facing issues with rtpengine, and looking at the logs, there is something suspicious:
we are calling:
t_continue("$sht(vtp=>id_index::$hdr(X-Resume))", "$sht(vtp=>id_label::$hdr(X-Resume))", "RESUME"); ... route[RESUME] { xdbgl("[RESUME] rm=$rm ru=$ru du=$du \n"); ...
after the call to t_continue i can see the log mentioned above:
Jun 24 16:20:52 proxy5 /usr/sbin/kamailio[2337]: DEBUG: {1 34558 NOTIFY sFsXwoWeDXHOzRHqVfA4E5KDT9U6qoov} <script>: 486:[RESUME] rm=INVITE ru=sip:<URI_REDACTED>
I wondered why the log call still logs the context as the NOTIFY context and not the INVITE context, and if that might lead to issues?
currently we get problems with rtpengine_manage when we try to call it in the route[RESUME]
Jun 24 16:20:52 proxy5 /usr/sbin/kamailio[2337]: DEBUG: {1 34558 NOTIFY sFsXwoWeDXHOzRHqVfA4E5KDT9U6qoov} rtpengine [rtpengine.c:3198]: rtpp_function_call(): proxy reply: d7:warning38:Call-ID not found or tags didn't match6:result2:oke
We are currently checking, if we can work around this issue, but i am hoping to getting a bit of insight from you.
Best Regards JWes __________________________________________________________ Kamailio - Users Mailing List - Non Commercial Discussions -- sr-users@lists.kamailio.org To unsubscribe send an email to sr-users-leave@lists.kamailio.org Important: keep the mailing list in the recipients, do not reply only to the sender!
Hi Daniel,
thanks for pointing that out. I stopped using rtpengine_manage and instead used rtpengine_offer and it seems to solve the problem.
Best Regards, Johannes
Hi Johannes,
I have run into this issue as well; rtpengine_manage() can't resolve its context in certain complex cases (e.g. async), and one must revert to more explicit _offer() / _answer() calls.
I actually tend to avoid rtpengine_manage() nowadays except in very, very simple scenarios, because it's easier not to think about it. :-)
-- Alex
On Jun 25, 2025, at 7:32 AM, Johannes Westhuis via sr-users sr-users@lists.kamailio.org wrote:
Hi Daniel,
thanks for pointing that out. I stopped using rtpengine_manage and instead used rtpengine_offer and it seems to solve the problem.
Best Regards, Johannes __________________________________________________________ Kamailio - Users Mailing List - Non Commercial Discussions -- sr-users@lists.kamailio.org To unsubscribe send an email to sr-users-leave@lists.kamailio.org Important: keep the mailing list in the recipients, do not reply only to the sender!
-- Alex Balashov Principal Consultant Evariste Systems LLC Web: https://evaristesys.com, https://www.csrpswitch.com Tel: +1-706-510-6800
Hello,
by using rtpengine_manage() only in a branch_route when one has in mind that is about engaging rtpengine for an outgoing request (e.g., INVITE, UPDATE, ...), then it should not be anything complex, imo.
I actually think is a rather bad practice that rtpengine functions (being _manage()/_offer()/_answer()) are used anywhere else than a branch_route for outgoing requests. For example, using it inside request_route compromises any sane serial/parallel forking.
If you have mixed calls with initial as well as late SDP offer, I think using _offer()/_answer() functions can lead to a more complex configuration file rather than being careful where rtpengine_manage() is used.
Cheers, Daniel
On 25.06.25 13:48, Alex Balashov via sr-users wrote:
Hi Johannes,
I have run into this issue as well; rtpengine_manage() can't resolve its context in certain complex cases (e.g. async), and one must revert to more explicit _offer() / _answer() calls.
I actually tend to avoid rtpengine_manage() nowadays except in very, very simple scenarios, because it's easier not to think about it. :-)
-- Alex
On Jun 25, 2025, at 7:32 AM, Johannes Westhuis via sr-users sr-users@lists.kamailio.org wrote:
Hi Daniel,
thanks for pointing that out. I stopped using rtpengine_manage and instead used rtpengine_offer and it seems to solve the problem.
Best Regards, Johannes __________________________________________________________ Kamailio - Users Mailing List - Non Commercial Discussions -- sr-users@lists.kamailio.org To unsubscribe send an email to sr-users-leave@lists.kamailio.org Important: keep the mailing list in the recipients, do not reply only to the sender!
-- Alex Balashov Principal Consultant Evariste Systems LLC Web: https://evaristesys.com, https://www.csrpswitch.com Tel: +1-706-510-6800
Kamailio - Users Mailing List - Non Commercial Discussions -- sr-users@lists.kamailio.org To unsubscribe send an email to sr-users-leave@lists.kamailio.org Important: keep the mailing list in the recipients, do not reply only to the sender!
-
Alex Balashov -
Daniel-Constantin Mierla -
Johannes Westhuis -
johannes.westhuis＠auerswald.de